Lines Matching refs:tests

13 Pytest is a python framework that *“makes it easy to write small, readable tests, and can scale to
30 Pytest-based test suites are discovered the same way as other twister tests, i.e., by a presence
71    tests:
76 By default, pytest tries to look for tests in a ``pytest`` directory located next to a directory
80 Pytest scans the given locations looking for tests, following its default
113 writing tests which are device-type-agnostic. Scope of this fixture is determined by the
131 optimized for interactions with a shell. It can be used instead of ``dut`` for tests. Scope of this
225 Examples of pytest tests in the Zephyr project
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`
256    placed under ``harness_config`` with list of tests which should be run:
265    Particular tests can be also chosen by pytest ``-k`` option (more info about pytest keyword
267 …`here <https://docs.pytest.org/en/latest/example/markers.html#using-k-expr-to-select-tests-based-o…
296 How to rerun locally pytest tests without rebuilding application by Twister?
304 Is this possible to run pytest tests in parallel?
307    Basically ``pytest-harness-plugin`` wasn't written with intention of running pytest tests in
309    of tests is made by Twister, and it is responsible for managing available sources (jobs and