Lines Matching +full:all +full:- +full:outputs

7 to understand existing files and create their own. All developers should fix any tests
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.
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]_ .
47 Beside the standard outputs, we can also investigate the file outputs, normally placed in
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.
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``
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``
113                          # Note that if you want output from all runs after each other,
118 ------
126 .. [#f2] We advise you to keep the first section of ``args`` definition intact in almost all