Lines Matching +full:- +full:vv

17 A pytest plugin ``pytest-twister-harness`` was introduced to provide an integration between pytest
25 developed as a part of Zephyr’s tree. To enable install-less operation, twister first extends
27 ``-p twister_harness.plugin`` argument. If one prefers to use the installed version of the plugin,
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
38    :figclass: align-center
52 .. code-block:: none
69 .. code-block:: yaml
81 …//docs.pytest.org/en/7.1.x/explanation/goodpractices.html#conventions-for-python-test-discovery>`_.
88 #. From .yaml file, using ``pytest_args`` placed under ``harness_config`` section - more info
90 #. Through Twister command line interface as ``--pytest-args`` argument. This can be particularly
94    .. code-block:: console
96       $ ./scripts/twister --platform native_sim -T samples/subsys/testsuite/pytest/shell \
97       -s samples/subsys/testsuite/pytest/shell/sample.pytest.shell \
98       --pytest-args='-k test_shell_print_version'
113 writing tests which are device-type-agnostic. Scope of this fixture is determined by the
118 .. code-block:: python
135 .. code-block:: python
145 Sample fixture to wrap ``mcumgr`` command-line tool used to manage remote devices. More information
154 .. code-block:: python
179 .. code-block:: python
228 * :zephyr:code-sample:`pytest_shell`
229 * MCUmgr tests - :zephyr_file:`tests/boot/with_mcumgr`
230 * LwM2M tests - :zephyr_file:`tests/net/lib/lwm2m/interop`
231 * GDB stub tests - :zephyr_file:`tests/subsys/debug/gdbstub`
244    .. code-block:: yaml
258    .. code-block:: yaml
263             - "pytest/test_shell.py::test_shell_print_help"
265    Particular tests can be also chosen by pytest ``-k`` option (more info about pytest keyword
267 …ps://docs.pytest.org/en/latest/example/markers.html#using-k-expr-to-select-tests-based-on-their-na…
268    ). It can be applied by adding ``-k`` filter in ``pytest_args`` in .yaml file:
270    .. code-block:: yaml
275             - "-k test_shell_print_help"
279    .. code-block:: console
281       $ ./scripts/twister ... --pytest-args='-k test_shell_print_help'
288    .. code-block:: python
299    This can be achieved by running Twister once again with ``--test-only`` argument added to Twister
300    command. Another way is running Twister with highest verbosity level (``-vv``) and then
301    copy-pasting from logs command dedicated for spawning pytest (log started by ``Running pytest
307    Basically ``pytest-harness-plugin`` wasn't written with intention of running pytest tests in
311    `pytest-xdist plugin <https://pytest-xdist.readthedocs.io/en/stable/>`_) they do so at their own