Lines Matching +full:- +full:testplan

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>`__.
66 * ``@mock.patch.object(TestPlan, 'TESTSUITE_FILENAME', testsuite_filename_mock)``
67     - this decorator allows us to use only tests defined in the ``test_data`` and
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 ------