Home
last modified time | relevance | path

Searched full:twister (Results 1 – 25 of 212) sorted by relevance

123456789

/Zephyr-latest/scripts/tests/twister/
DREADME.md1 # Twister Testing
5 Twister Testsuite are located in $ZEPHYR_BASE/scripts/tests directory with all the data files in $Z…
20 pytest $ZEPHYR_BASE/scripts/tests/twister
23 ## Twister Coverage
28 coverage run -m pytest $ZEPHYR_BASE/scripts/tests/twister/
31 Then we can generate the coverage report for just twister script using
34 coverage report -m $ZEPHYR_BASE/scripts/pylib/twister/
37 To generate the coverage report for twister script use below command
40 coverage report -m $ZEPHYR_BASE/scripts/twister
43 The html coverage report for twister can be generated using
[all …]
Dtest_platform.py7 This test file contains tests for platform.py module of twister
18 sys.path.insert(0, os.path.join(ZEPHYR_BASE, "scripts/pylib/twister"))
32 'twister': True,
55 twister: true
88 'twister': True,
209 'm0/boards/zephyr/p1/twister.yaml': """\
214 twister: False
246 'm0/boards/arm/p3/twister.yaml': """\
279 'm1/boards/zephyr/p1e1/twister.yaml': """\
310 'm2/boards/misc/twister.yaml': """\
[all …]
Dtest_twister.py7 This test file contains foundational testcases for Twister tool
18 sys.path.insert(0, os.path.join(ZEPHYR_BASE, "scripts/pylib/twister"))
37 schema = scl.yaml_load(ZEPHYR_BASE +'/scripts/schemas/twister//' + schema)
49 schema = scl.yaml_load(ZEPHYR_BASE +'/scripts/schemas/twister//' + schema)
56 …filename = Path(ZEPHYR_BASE) / "scripts/tests/twister/test_data/test_data_with_deprecation_warning…
57 schema = scl.yaml_load(Path(ZEPHYR_BASE) / "scripts/schemas/twister/testsuite-schema.yaml")
99 filename = Path(ZEPHYR_BASE) / "scripts/tests/twister/test_twister.py"
/Zephyr-latest/.github/workflows/
Dtwister_tests.yml4 name: Twister TestSuite
14 - 'scripts/twister'
15 - 'scripts/tests/twister/**'
17 - 'scripts/schemas/twister/'
24 - 'scripts/twister'
25 - 'scripts/tests/twister/**'
27 - 'scripts/schemas/twister/'
30 twister-tests:
31 name: Twister Unit Tests
60 echo "Run twister tests"
[all …]
Dtwister.yaml1 name: Run tests with twister
23 twister-build-prep:
24 uses: ./.github/workflows/twister-prep.yaml
26 twister-build:
29 needs: twister-build-prep
30 if: needs.twister-build-prep.outputs.size != 0
37 subset: ${{fromJSON(needs.twister-build-prep.outputs.subset)}}
133 name: Run Tests with Twister (Push)
138 …./scripts/twister --subset ${{matrix.subset}}/${{ strategy.job-total }} ${TWISTER_COMMON} ${PUSH_O…
140 ./scripts/zephyr_module.py --twister-out module_tests.args
[all …]
Dtwister_tests_blackbox.yml4 name: Twister BlackBox TestSuite
13 - 'scripts/pylib/twister/**'
14 - 'scripts/twister'
19 twister-tests:
20 name: Twister Black Box Tests
72 - name: Run Pytest For Twister Black Box Tests
78 echo "Run twister tests"
Dtwister-publish.yaml1 name: Publish Twister Test Results
5 workflows: ["Run tests with twister"]
33 workflow: twister.yml
47 --index zephyr-main-ci-push-1 artifacts/*/*/twister.json
52 --index zephyr-main-ci-weekly-1 artifacts/*/*/twister.json
/Zephyr-latest/scripts/west_commands/
Dtwister_cmd.py13 # Resolve path to twister libs and add imports
18 sys.path.insert(0, str(twister_path / "pylib" / "twister"))
24 Convenience wrapper for twister. The below options are shared with the twister
25 script and have the same effects as if you ran twister directly. Refer to the
26 twister documentation for more information.
30 class Twister(WestCommand): class
32 super(Twister, self).__init__(
33 "twister",
35 "west twister wrapper",
/Zephyr-latest/scripts/pylib/pytest-twister-harness/
DREADME.rst2 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:
24 ./scripts/twister -p native_sim -p qemu_x86 -T samples/subsys/testsuite/pytest/shell
27 …./scripts/twister -p nrf52840dk/nrf52840 --device-testing --device-serial /dev/ttyACM0 -T samples/…
33 export PYTHONPATH=${ZEPHYR_BASE}/scripts/pylib/pytest-twister-harness/src:${PYTHONPATH}
39 pytest --twister-harness --device-type=native --build-dir=build -p twister_harness.plugin
43 pytest --twister-harness --device-type=qemu --build-dir=build -p twister_harness.plugin
47 …pytest --twister-harness --device-type=hardware --device-serial=/dev/ttyACM0 --build-dir=build -p …
/Zephyr-latest/scripts/west_commands/tests/
Dtest_twister.py9 from twister_cmd import Twister
34 command="twister",
40 twister = Twister()
47 twister.parser = twister.do_add_parser(sub_p)
48 options = twister._parse_arguments(args=test_case["r"], options=None)
/Zephyr-latest/scripts/
D.gitignore4 tests/twister/.pytest_cache
5 tests/twister/htmlcov
6 tests/twister/__pycache__
7 tests/twister/.coverage
Drequirements-run-test.txt3 # things used by twister or related in run time testing
8 # used by twister for board/hardware map
15 # use for twister
Drequirements-build-test.txt3 # things used by twister or other things like code coverage or python
6 # used by twister for ansi color
9 # python lex/yex used by twister
/Zephyr-latest/doc/develop/test/twister/
Dtwister_blackbox.rst3 Twister blackbox tests
9 important for any Twister developer.
14 Twister blackbox tests are written in python, using the ``pytest`` library.
20 Blackbox tests should not be aware of the internal twister code. Instead, they should
21 call twister as user would and check the results.
37 twister -i --outdir $OUTDIR -T $TEST_DATA/tests -y --level $LEVEL
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]_ .
48 ``twister-out`` directories. Most of the time, we will use the ``out_path`` fixture in conjunction
50 Typical files read in blackbox tests are ``testplan.json`` , ``twister.xml`` and ``twister.log`` .
[all …]
/Zephyr-latest/doc/develop/test/
Dtwister_statuses.rst3 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 …]
Dpytest.rst6 *Please mind that integration of twister with pytest is still work in progress. Not every platform
17 A pytest plugin ``pytest-twister-harness`` was introduced to provide an integration between pytest
18 and twister, allowing Zephyr’s community to utilize pytest functionality with keeping twister as
21 Integration with twister
24 By default, there is nothing to be done to enable pytest support in twister. The plugin is
25 developed as a part of Zephyr’s tree. To enable install-less operation, twister first extends
28 they must add ``--allow-installed-plugin`` flag to twister’s call.
30 Pytest-based test suites are discovered the same way as other twister tests, i.e., by a presence
31 of test/sample.yaml. Inside, a keyword ``harness`` tells twister how to handle a given test.
32 In the case of ``harness: pytest``, most of twister workflow (test suites discovery,
[all …]
Dtwister.rst3 Test Runner (Twister)
6 Twister scans for the set of test applications in the git repository
14 Because of the limited test execution coverage, twister
20 When using (at least) one ``-v`` option, twister's console output
24 of a test is likewise reported in the ``twister.json`` and other report files.
25 There are a few reasons why twister only builds a test and doesn't run it:
32 - You or some higher level automation invoked twister with
44 $ ./scripts/twister
51 python .\scripts\twister
63 $ ./scripts/twister --all --enable-slow
[all …]
Dcoverage.rst138 Coverage reports using Twister
141 Zephyr's :ref:`twister script <twister_script>` can automatically
149 $ twister --coverage -p qemu_x86 -T tests/kernel
155 $ twister --coverage -p native_sim -T tests/bluetooth
157 which will produce ``twister-out/coverage/index.html`` report as well as
158 the coverage data collected by ``gcovr`` tool in ``twister-out/coverage.json``.
165 call Twister from your project directory with ``--coverage-basedir $ZEPHYR_BASE``
170 …$ $ZEPHYR_BASE/scripts/twister --coverage -p native_sim --coverage_basedir $ZEPHYR_BASE -T your_pr…
174 By default, Twister calls ``gcovr`` tool which filters source files assuming real paths
178 or ``lcov`` tool used instead of ``gcovr`` with additional Twister command line
[all …]
Dindex.rst10 twister
12 twister/twister_blackbox
/Zephyr-latest/scripts/ci/es_upload/
DREADME.md5 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.
44 The upload script has several command line options to change `twister.json` data:
70 ### Twister test results
79 Upload Twister test results 'as-is', without additional transformations:
83 ./twister-out/**/twister.json
87 ### Twister tests with recording
106 ./twister-out/**/twister.json
[all …]
/Zephyr-latest/tests/boot/with_mcumgr/
DREADME.rst5 using **sysbuild**. Tests are automated with pytest, a new harness of Twister
13 To run tests with Twister on ``nrf52840dk/nrf52840`` platform,
18 ./zephyr/scripts/twister -vv --west-flash --enable-slow -T zephyr/tests/boot/with_mcumgr \
22 Twister requires ``--west-flash`` flag enabled (without additional parameters
/Zephyr-latest/scripts/pylib/pytest-twister-harness/src/twister_harness/
Dexceptions.py7 """General Twister harness exception."""
11 """Twister harness timeout exception"""
/Zephyr-latest/tests/bluetooth/classic/sdp_c/
DREADME.rst10 PC (running :ref:`Twister <twister_script>`) and a device under test (DUT) running Zephyr.
27 ``--hci-transport`` test suite argument (i.e. run ``twister`` with the
46 launched using Twister:
50 …west twister -v -p mimxrt1170_evk@B/mimxrt1176/cm7 --device-testing --device-serial COM4 -T tests/…
57 The test suite can be launched using Twister. Below is an example for running on the
62 …west twister -v -p mimxrt1170_evk@B/mimxrt1176/cm7 --device-testing --device-serial COM4 -T tests/…
/Zephyr-latest/scripts/tests/twister_blackbox/
Dtest_footprint.py6 Blackbox tests for twister's command line functions related to memory footprints.
31 r'Found [1-9]+[0-9]* footprint deltas to .*blackbox-out\.[0-9]+/twister.json as a baseline'
33 DELTA_WARNING_RUN = re.compile(r'Found [1-9]+[0-9]* footprint deltas to the last twister run')
41 apath = os.path.join(ZEPHYR_BASE, 'scripts', 'twister')
75 # Note: if footprint tests take too long, replace first run with a prepared twister.json
77 with open(os.path.join(out_path, 'twister.json')) as f:
84 with open(os.path.join(out_path, 'twister.json'), 'w') as f:
90 'twister.json'
139 with open(os.path.join(out_path, 'twister.json')) as f:
164 with open(os.path.join(out_path, 'twister.json')) as f:
[all …]
/Zephyr-latest/tests/bsim/
Dgenerate_coverage_report.sh25 You can also merge in the twister coverage report by setting
27 TWISTER_COVERAGE_FILE=\${ZEPHYR_BASE}/twister-out/coverage.info
28 after having run twister, for example as
29 twister -p nrf52_bsim -T tests/bluetooth/ --coverage

123456789