History

Anas Nashif eaafd30b56 twister: cleanup how we capture results of handlers we use reason for a failure to indicate state and then set the status later and reason for the failure, in case of the failure is taken from the handler status. Clean this up by setting status and reason coming from the handler very early, so we do not have to go through replacing meaning later. Signed-off-by: Anas Nashif <anas.nashif@intel.com>		2024-06-12 21:12:13 -04:00
..
pytest_integration	twister: harness: pytest: list available fixtures in device config	2024-06-04 21:27:35 -05:00
test_data	twister: do not use non-existing architectures	2024-03-19 18:28:06 -04:00
conftest.py
README.md
test_cmakecache.py
test_config_parser.py	twister: ut for config_parser.py	2024-03-29 15:06:44 +00:00
test_environment.py	scripts: twister: Fix overbroad Mock in environment unit tests	2024-04-15 16:25:51 +02:00
test_errors.py
test_handlers.py	twister: cleanup how we capture results of handlers	2024-06-12 21:12:13 -04:00
test_hardwaremap.py	twister: hardwaremap: avoid exceptions when generating hardware map	2024-06-06 07:50:51 -04:00
test_harness.py	twister: cleanup how we capture results of handlers	2024-06-12 21:12:13 -04:00
test_jobserver.py	scripts: twister: Fix Unit Tests on Windows systems	2024-05-15 17:08:06 +02:00
test_log_helper.py
test_mixins.py
test_platform.py	twister: do not use non-existing architectures	2024-03-19 18:28:06 -04:00
test_quarantine.py
test_runner.py	twister: abort on execution and retun 0 on exceptions	2024-06-04 07:58:31 +02:00
test_scl.py
test_testinstance.py	twister: Refactor 'recording' feature	2024-05-14 18:20:12 -04:00
test_testplan.py	llext: xtensa: add support for the xt-clang toolchain	2024-05-29 10:49:40 -07:00
test_testsuite.py	scripts: twister: Fix Unit Tests on Windows systems	2024-05-15 17:08:06 +02:00
test_twister.py

README.md

Twister Testing

Running the tests require the environment variable ZEPHYR_BASE to be set.

Twister Testsuite are located in $ZEPHYR_BASE/scripts/tests directory with all the data files in $ZEPHYR_BASE/scripts/test_data directory.

Dependencies

Install all the dependencies using

pip install -r $ZEPHYR_BASE/scripts/requirements-build-test.txt

Executing testsuite

The testcases can be executed from the root directory using

pytest $ZEPHYR_BASE/scripts/tests/twister

Twister Coverage

The coverage for all the tests can be run using the command below. This will collect all the tests available.

coverage run -m pytest $ZEPHYR_BASE/scripts/tests/twister/

Then we can generate the coverage report for just twister script using

coverage report -m $ZEPHYR_BASE/scripts/pylib/twister/

To generate the coverage report for twister script use below command

coverage report -m $ZEPHYR_BASE/scripts/twister

The html coverage report for twister can be generated using

coverage html twister

If needed,the full coverage html report can be generated in every run of "pytest" in the tests directory using configuration file (setup.cfg).

Organization of tests

conftest.py: Contains common fixtures for use in testing the twister tool.
test_twister.py : Contains basic testcases for environment variables, verifying testcase & platform schema's.
test_testsuite_class.py : Contains testcases for Testsuite class (except reporting functionality) in twisterlib.py.
test_testinstance.py : Contains testcases for Testinstance and Testcase class.
test_reporting_testsuite.py : Contains testcases for reporting functionality of Testsuite class of twister.