Searched refs:harness (Results 1 – 7 of 7) sorted by relevance
| /Zephyr-Core-2.7.6/tests/bluetooth/bsim_bt/bsim_test_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-Core-2.7.6/scripts/pylib/twister/ |
| D | twisterlib.py | 413 def record(self, harness): argument
414 if harness.recording:
417 cw = csv.writer(csvfile, harness.fieldnames, lineterminator=os.linesep)
418 cw.writerow(harness.fieldnames)
419 for instance in harness.recording:
439 def add_missing_testscases(self, harness): argument
446 if c not in harness.tests:
447 harness.tests[c] = "BLOCK"
480 def _output_handler(self, proc, harness): argument
481 if harness.is_pytest:
[all …]
|
| /Zephyr-Core-2.7.6/scripts/tests/twister/ |
| D | test_testinstance.py | 29 …uite, monkeypatch, all_testcases_dict, platforms_list, build_only, slow, harness, platform_type, p… argument
41 testcase.harness = harness
|
| /Zephyr-Core-2.7.6/samples/drivers/espi/ |
| D | README.rst | 23 Sample requires a correct harness and fixture setup.
|
| /Zephyr-Core-2.7.6/doc/guides/test/ |
| D | twister.rst | 28 - The test configuration has defined a ``harness`` but you don't have
327 harness: <string>
328 A harness string needed to run the tests successfully. This can be as
334 harness_config: <harness configuration options>
335 Extra harness configuration options to be used to select a board and/or
385 harness: console
406 harness: pytest
|
| /Zephyr-Core-2.7.6/doc/releases/ |
| D | release-notes-2.3.rst | 915 * :github:`24943` - Add a harness property to boards in sanitycheck's hardware_map
|
| D | release-notes-2.5.rst | 1162 * :github:`31194` - twister: using unsupported fixture without defined harness causes an infinite l…
|
