| /Zephyr-latest/scripts/tests/twister/ |
| D | test_errors.py | 15 from twisterlib.harness import Test
29 harness = Test()
35 harness.status = "OK"
|
| D | test_harness.py | 21 from twisterlib.harness import (
58 def process_logs(harness, logs): argument
60 harness.handle(line)
219 harness = Harness()
220 harness.record = {"regex": patterns}
221 harness.record_patterns = [re.compile(p) for p in patterns]
223 harness.record_merge = merge
224 harness.record_as_json = as_json
226 harness.record["as_json"] = as_json
228 assert not harness.recording
[all …]
|
| D | test_handlers.py | 24 import twisterlib.harness
133 harness = twisterlib.harness.Test()
134 harness.status = TwisterStatus.NONE
135 harness.detected_suite_names = mock.Mock()
136 harness.matched_run_id = False
137 harness.run_id_exists = True
138 harness.recording = mock.Mock()
142 handler._final_handle_actions(harness, handler_time)
151 handler._final_handle_actions(harness, handler_time)
153 instance.assert_has_calls([mock.call.record(harness.recording)])
[all …]
|
| D | test_testinstance.py | 47 harness, argument
67 testsuite.harness = harness
439 harness, argument
446 testsuite.harness = harness
554 testinstance.testsuite.harness = testsuite_harness
|
| D | test_runner.py | 29 from twisterlib.harness import Pytest
1524 instance_mock.testsuite.harness = 'test'
2239 instance_mock.testsuite.harness = 'test'
2316 harness, argument
2341 instance_mock.testsuite.harness = harness
|
| /Zephyr-latest/scripts/pylib/twister/twisterlib/ |
| D | handlers.py | 146 def _final_handle_actions(self, harness, handler_time): argument
149 harness_class_name = type(harness).__name__
152 harness.status,
153 harness.detected_suite_names,
158 if not harness.matched_run_id and harness.run_id_exists:
165 self.instance.record(harness.recording)
213 def _output_handler(self, proc, harness): argument
234 harness.handle(stripped_line)
236 harness.status != TwisterStatus.NONE
238 or harness.capture_coverage
[all …]
|
| D | testinstance.py | 221 if testsuite.harness in [
273 if self.testsuite.harness == "ctest":
310 self.testsuite.harness == "ctest" or \
316 if self.testsuite.harness in ['pytest', 'shell']:
|
| D | runner.py | 48 from twisterlib.harness import Ctest, HarnessImporter, Pytest
659 if self.instance.testsuite.harness == 'bsim':
1071 if self.instance.testsuite.harness in ['ztest', 'test']:
1735 harness = HarnessImporter.get_harness(self.instance.testsuite.harness.capitalize())
1738 if harness:
1739 harness.instance = self.instance
1740 harness.build()
1768 harness = HarnessImporter.get_harness(instance.testsuite.harness.capitalize())
1770 harness.configure(instance)
1777 if isinstance(harness, Pytest):
[all …]
|
| D | testplan.py | 552 if suite.harness in ['ztest', 'test']:
949 if ts.harness:
951 if ts.harness == 'robot' and not (sim and sim.name == 'renode'):
|
| D | testsuite.py | 479 if self.harness == 'console' and not self.harness_config:
|
| /Zephyr-latest/scripts/pylib/pytest-twister-harness/ |
| D | README.rst | 2 Pytest Twister harness
33 export PYTHONPATH=${ZEPHYR_BASE}/scripts/pylib/pytest-twister-harness/src:${PYTHONPATH}
39 pytest --twister-harness --device-type=native --build-dir=build -p twister_harness.plugin
43 pytest --twister-harness --device-type=qemu --build-dir=build -p twister_harness.plugin
47 …pytest --twister-harness --device-type=hardware --device-serial=/dev/ttyACM0 --build-dir=build -p …
|
| D | setup.cfg | 2 name = pytest-twister-harness
|
| /Zephyr-latest/tests/bsim/bluetooth/mesh/ |
| D | README.rst | 15 harnesses in every build. The overlying bsim test framework selects the harness
39 Example: To debug the ``transport_tx_seg_block`` test harness in the transport
75 ``RunTest`` starts one mesh application for each selected harness, before
85 The mesh_test module is never called from the framework, so each test harness
87 All utility functions can be replaced by custom behavior in each harness if the
88 generic implementation does not fit with the harness requirements.
100 Each test harness is defined by a ``struct bst_test_instance`` structure, that
102 test application's main function. The harness contains a set of callback
105 Each mesh test harness should call the ``bt_mesh_test_cfg`` function from its
114 the harness, as the previous callbacks are all executed in hardware threads.
|
| /Zephyr-latest/doc/develop/test/ |
| D | pytest.rst | 17 A pytest plugin ``pytest-twister-harness`` was introduced to provide an integration between pytest
31 of test/sample.yaml. Inside, a keyword ``harness`` tells twister how to handle a given test.
32 In the case of ``harness: pytest``, most of twister workflow (test suites discovery,
41 If ``harness: pytest`` is used, twister delegates the test execution to pytest, by calling it as
66 .yaml file contains a ``harness: pytest`` entry, it calls pytest in a separate subprocess. A sample
73 harness: pytest
110 the core of pytest harness plugin. It is required to launch DUT (initialize logging, flash device,
246 harness: pytest
260 harness: pytest
272 harness: pytest
[all …]
|
| D | twister.rst | 29 - The test configuration has defined a ``harness`` but you don't have
542 harness: <string>
543 A harness keyword in the ``testcase.yaml`` file identifies a Twister
544 harness needed to run a test successfully. A harness is a feature of
548 A harness can be seen as the handler that needs to be implemented in
550 keyboard harness is set on tests that require keyboard interaction to reach
552 harness implementation at the moment.
588 harness_config: <harness configuration options>
589 Extra harness configuration options to be used to select a board and/or
613 harness: robot
[all …]
|
| /Zephyr-latest/doc/ |
| D | requirements.txt | 18 # Used by pytest-twister-harness plugin (imported by autodoc)
|
| /Zephyr-latest/scripts/ |
| D | requirements-build-test.txt | 23 # used for JUnit XML parsing in CTest harness
|
| /Zephyr-latest/samples/ |
| D | sample_definition_and_criteria.rst | 53 harness: console
60 run on the documented platforms. Use the ``harness`` option to skip the
62 the harness is set to ``ztest`` or ``console``.
|
| /Zephyr-latest/tests/boot/with_mcumgr/ |
| D | README.rst | 5 using **sysbuild**. Tests are automated with pytest, a new harness of Twister
|
| /Zephyr-latest/scripts/tests/twister/pytest_integration/ |
| D | test_harness_pytest.py | 11 from twisterlib.harness import Pytest
21 testsuite.harness = 'pytest'
|
| /Zephyr-latest/samples/drivers/espi/ |
| D | README.rst | 24 Sample requires a correct harness and fixture setup.
|
| /Zephyr-latest/ |
| D | .ruff-excludes.toml | 668 "./scripts/pylib/pytest-twister-harness/src/twister_harness/device/binary_adapter.py" = [
672 "./scripts/pylib/pytest-twister-harness/src/twister_harness/device/device_adapter.py" = [
676 "./scripts/pylib/pytest-twister-harness/src/twister_harness/device/factory.py" = [
681 "./scripts/pylib/pytest-twister-harness/src/twister_harness/device/fifo_handler.py" = [
685 "./scripts/pylib/pytest-twister-harness/src/twister_harness/device/hardware_adapter.py" = [
690 "./scripts/pylib/pytest-twister-harness/src/twister_harness/device/qemu_adapter.py" = [
694 "./scripts/pylib/pytest-twister-harness/src/twister_harness/device/utils.py" = [
697 "./scripts/pylib/pytest-twister-harness/src/twister_harness/fixtures.py" = [
703 "./scripts/pylib/pytest-twister-harness/src/twister_harness/helpers/domains_helper.py" = [
708 "./scripts/pylib/pytest-twister-harness/src/twister_harness/helpers/shell.py" = [
[all …]
|
| /Zephyr-latest/tests/kernel/timer/timer_behavior/ |
| D | Kconfig | 51 tool (such as a logic analyzer) to gather timing data. A pytest harness
|
| /Zephyr-latest/samples/subsys/testsuite/pytest/shell/ |
| D | README.rst | 17 is defined in ``pytest-twister-harness`` plugin. More information about plugin
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-3.1.rst | 1255 - :github:`45848` - tests: console harness: inaccuracy testcases report
1309 * :github:`45942` - tests: twister: harness: Test harness report pass when there is no console outp…
|
