Searched refs:Twister (Results 1 – 25 of 40) sorted by relevance
12
| /Zephyr-latest/doc/develop/test/ |
| D | twister_statuses.rst | 3 Twister Status
6 What is a Twister Status?
9 Twister Status formulates the current state of
18 of Instances and Cases after the conclusion of their Twister runs.
28 ``Harness`` is a Python class inside Twister that allows us
29 to capture and analyse output from a program external to Twister.
41 One can modify Twister's behaviour on a per-Suite basis via ``testcase.yaml`` files.
43 for it to make sense to treat them all the same by Twister.
48 Twister typically reports its results for Instances,
56 Possible Twister Statuses
[all …]
|
| D | pytest.rst | 49 An example folder containing a pytest test, application source code and Twister configuration .yaml
65 provided in the ``testcase.yaml`` file, Twister builds the application from ``src`` and then, if the
90 #. Through Twister command line interface as ``--pytest-args`` argument. This can be particularly
277 or by adding it to Twister command overriding parameters from the .yaml file:
296 How to rerun locally pytest tests without rebuilding application by Twister?
299 This can be achieved by running Twister once again with ``--test-only`` argument added to Twister
300 command. Another way is running Twister with highest verbosity level (``-vv``) and then
309 of tests is made by Twister, and it is responsible for managing available sources (jobs and
|
| D | coverage.rst | 130 Coverage reports using Twister
164 Twister looks at the environment variable ``ZEPHYR_TOOLCHAIN_VARIANT``
166 default for the Twister ``--gcov-tool`` argument default:
|
| D | twister.rst | 3 Test Runner (Twister)
6 Twister scans for the set of test applications in the git repository
230 A list of environment variables. Twister will check if all these environment variables are set,
248 :alt: Twister and a Test application project.
251 Twister and a Test application project.
304 must be unique for the Twister execution scope.
510 A harness keyword in the ``testcase.yaml`` file identifies a Twister
512 Twister and implemented by Twister, some harnesses are defined as
516 Twister to be able to evaluate if a test passes criteria. For example, a
518 verdict on whether a test has passed or failed, however, Twister lack this
[all …]
|
| D | ztest.rst | 227 use the :ref:`Twister <twister_script>` tool, for example:
233 To select just one of the test scenarios, run Twister with ``--scenario`` command:
243 See :ref:`Twister test project diagram <twister_test_project_diagram>` for more details
244 on how Twister deals with Ztest application.
311 Twister parses the source files looking for test case names, so you
|
| /Zephyr-latest/scripts/pylib/pytest-twister-harness/ |
| D | README.rst | 2 Pytest Twister harness
8 If you plan to use this plugin with Twister, then you don't need to install it
9 separately by pip. When Twister uses this plugin for pytest tests, it updates
17 Run exemplary test shell application by Twister:
|
| /Zephyr-latest/scripts/west_commands/tests/ |
| D | test_twister.py | 9 from twister_cmd import Twister
40 twister = Twister()
|
| /Zephyr-latest/tests/boot/with_mcumgr/ |
| D | README.rst | 5 using **sysbuild**. Tests are automated with pytest, a new harness of Twister
13 To run tests with Twister on ``nrf52840dk/nrf52840`` platform,
22 Twister requires ``--west-flash`` flag enabled (without additional parameters
|
| /Zephyr-latest/scripts/ci/es_upload/ |
| D | README.md | 5 script for [Twister](https://docs.zephyrproject.org/latest/develop/test/twister.html)
9 with explicit scheme having all required Twister JSON report objects associated
11 Besides, it allows to track changes in Twister JSON report scheme
21 in the current Twister report format and in the upload script itself.
70 ### Twister test results
79 Upload Twister test results 'as-is', without additional transformations:
87 ### Twister tests with recording
110 ### Twister test with recording and extracting more data
138 To store Memory Footprint data reported in `twister-footprint.json` (see Twister `--footprint-repor…
|
| /Zephyr-latest/doc/develop/test/twister/ |
| D | twister_blackbox.rst | 3 Twister blackbox tests
9 important for any Twister developer.
14 Twister blackbox tests are written in python, using the ``pytest`` library.
42 Such a test provides us with all the outputs we typically expect of a Twister run thanks to
44 We can easily set up all flags that we expect from a Twister call via ``args`` variable [#f2]_ .
94 Call Twister multiple times in one test?
97 Sometimes we want to test something that requires prior Twister use. ``--test-only``
99 Twister call. How should we approach that?
105 It is caused by the use of logger module variables in the Twister files.
|
| /Zephyr-latest/scripts/west_commands/ |
| D | twister_cmd.py | 30 class Twister(WestCommand): class
32 super(Twister, self).__init__(
|
| /Zephyr-latest/scripts/tests/twister/ |
| D | README.md | 1 # Twister Testing
5 Twister Testsuite are located in $ZEPHYR_BASE/scripts/tests directory with all the data files in $Z…
23 ## Twister Coverage
|
| /Zephyr-latest/samples/subsys/testsuite/pytest/shell/ |
| D | README.rst | 10 Twister test runner.
12 A simple application provides basic Zephyr shell interface. Twister builds it
28 Build and run sample by Twister:
|
| /Zephyr-latest/tests/benchmarks/sched_queues/ |
| D | Kconfig | 29 to the Twister JSON report and recording.csv file(s).
|
| D | README.rst | 27 summary statistics as records to allow Twister parse the log and save that data
|
| /Zephyr-latest/tests/benchmarks/wait_queues/ |
| D | Kconfig | 29 to the Twister JSON report and recording.csv file(s).
|
| D | README.rst | 25 summary statistics as records to allow Twister parse the log and save that data
|
| /Zephyr-latest/tests/drivers/can/host/ |
| D | README.rst | 10 host PC (running :ref:`Twister <twister_script>`) and a device under test (DUT) running Zephyr.
71 be launched using Twister:
113 Twister. Below is an example for running on the :zephyr:board:`lpcxpresso55s36`:
|
| /Zephyr-latest/tests/kernel/timer/timer_behavior/ |
| D | README | 54 Twister
56 For Twister execute the external tool testing, the fixture "gpio_timerout"
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-4.1.rst | 130 * Space-separated lists support has been removed from Twister configuration
133 automatically migrate Twister configuration files.
135 * Twister
143 Twister XML reports have full testsuite name as ``testcase.classname property`` resolving
|
| D | release-notes-3.4.rst | 668 * Twister now supports ``gtest`` harness for running tests written in gTest.
679 * Twister now supports loading test configurations from alternative root
680 folder/s by using ``--alt-config-root``. When a test is found, Twister will
683 ``$test_root/tests/foo/testcase.yaml``, Twister will use
686 * Twister now uses native YAML lists for fields that were previously defined
716 automatically migrate Twister configuration files.
|
| /Zephyr-latest/samples/ |
| D | sample_definition_and_criteria.rst | 38 2. Twister should be able to build every sample.
61 execution. Twister only attempts to flash and execute the build binary if
|
| /Zephyr-latest/boards/intel/adsp/doc/ |
| D | intel_adsp_generic.rst | 179 (its "requests port"). When you run West or Twister on your local host,
190 Running tests with Twister is slightly more complicated.
208 Twister.
227 Any of the arguments you would pass to Twister or West, you can pass with the
298 If West or Twister successfully sign and establish TCP connections
|
| /Zephyr-latest/doc/develop/west/ |
| D | zephyr-cmds.rst | 185 Twister wrapper: ``west twister``
189 Twister can then be invoked via west as follows::
|
| /Zephyr-latest/tests/net/lib/lwm2m/interop/ |
| D | README.md | 4 the Twister's Pytest integration to run testcases against Leshan demo server.
7 These tests require setup that is not done in Twister run, so follow this documentation to set
|
12
