Lines Matching +full:scripts +full:- +full:tests
3 Twister blackbox tests
7 to understand existing files and create their own. All developers should fix any tests
14 Twister blackbox tests are written in python, using the ``pytest`` library.
17 Tests and data are wholly contained in the :zephyr_file:`scripts/tests/twister_blackbox`
20 Blackbox tests should not be aware of the internal twister code. Instead, they should
35 .. code-block:: console
37 twister -i --outdir $OUTDIR -T $TEST_DATA/tests -y --level $LEVEL
38 --test-config $TEST_DATA/test_config.yaml -p qemu_x86 -p frdm_k64f
40 It presumes a CLI with the ``zephyr-env.sh`` or ``zephyr-env.cmd`` already run.
48 ``twister-out`` directories. Most of the time, we will use the ``out_path`` fixture in conjunction
49 with ``--outdir`` flag (L52) to keep test-generated files in temporary directories.
50 Typical files read in blackbox tests are ``testplan.json`` , ``twister.xml`` and ``twister.log`` .
59 - allows us to use ``clear_log`` fixture from ``conftest.py`` .
63 - this is an example of ``pytest`` 's test parametrization.
64 …here <https://docs.pytest.org/en/7.1.x/example/parametrize.html#different-options-for-test-ids>`__.
67 - this decorator allows us to use only tests defined in the ``test_data`` and
68 ignore the Zephyr testcases in the ``tests`` directory. **Note that all ``test_data``
69 tests use** ``test_data.yaml`` **as a filename, not** ``testcase.yaml`` **!**
76 Blackbox tests use ``pytest`` 's fixtures, further reading on which is available
83 :zephyr_file:`scripts/tests/twister_blackbox/conftest.py` file.
85 - :zephyr_file:`scripts/tests/twister_blackbox/conftest.py` already contains some fixtures -
89 - Consider using class fields instead - look at TESTDATAs for an example.
97 Sometimes we want to test something that requires prior Twister use. ``--test-only``
98 flag would be a typical example, as it is to be coupled with previous ``--build-only``
118 ------
127 of your tests, as it is used for the common test setup.