Home
last modified time | relevance | path

Searched refs:harness_config (Results 1 – 13 of 13) sorted by relevance

/Zephyr-latest/scripts/tests/twister/pytest_integration/
Dtest_harness_pytest.py20 testsuite.harness_config = {}
61 testinstance.testsuite.harness_config['pytest_dut_scope'] = dut_scope
70 testinstance.testsuite.harness_config['pytest_args'] = pytest_args
90 testinstance.testsuite.harness_config['pytest_args'] = [pytest_args_from_yaml]
153 testinstance.testsuite.harness_config['pytest_root'] = pytest_root
/Zephyr-latest/scripts/tests/twister/
Dtest_harness.py287 mock_testsuite.harness_config = {}
295 instance.testsuite.harness_config = {
318 mock_testsuite.harness_config = {}
368 mock_testsuite.harness_config = {}
422 mock_testsuite.harness_config = {}
430 instance.testsuite.harness_config = {
483 mock_testsuite.harness_config = {}
545 mock_testsuite.harness_config = {}
638 id="id", testcases=[], source_dir="source_dir", harness_config={}
641 mock_testsuite.harness_config = {}
[all …]
Dtest_testinstance.py447 testsuite.harness_config['fixture'] = fixture
Dtest_handlers.py915 mocked_instance.testsuite.harness_config = {'fixture': fixture}
/Zephyr-latest/doc/develop/test/
Dpytest.rst77 with binary sources. A keyword ``pytest_root`` placed under ``harness_config`` section in .yaml file
88 #. From .yaml file, using ``pytest_args`` placed under ``harness_config`` section - more info
114 ``pytest_dut_scope`` keyword placed under ``harness_config`` section (more info
132 fixture is determined by the ``pytest_dut_scope`` keyword placed under ``harness_config`` section
242 under ``harness_config`` section:
247 harness_config:
256 placed under ``harness_config`` with list of tests which should be run:
261 harness_config:
273 harness_config:
Dtwister.rst588 harness_config: <harness configuration options>
607 The following is an example yaml file with robot harness_config options.
614 harness_config:
624 harness_config:
637 harness_config:
768 The following is an example yaml file with a few harness_config options.
777 harness_config:
822 harness_config:
848 The following is an example yaml file with pytest harness_config options,
858 harness_config:
[all …]
/Zephyr-latest/scripts/pylib/twister/twisterlib/
Dharness.py92 config = instance.testsuite.harness_config
191 config = instance.testsuite.harness_config
394 config = self.instance.testsuite.harness_config
635 config = self.instance.testsuite.harness_config
646 def _get_shell_commands_file(self, harness_config): argument
647 if shell_commands := harness_config.get('shell_commands'):
653 test_shell_file = harness_config.get('shell_commands_file', 'test_shell.yml')
986 new_exe_name: str = self.instance.testsuite.harness_config.get('bsim_exe_name', '')
1021 config = self.instance.testsuite.harness_config
Dtestinstance.py234 fixture = testsuite.harness_config.get('fixture')
Dtestsuite.py479 if self.harness == 'console' and not self.harness_config:
Dhandlers.py492 fixture = instance.testsuite.harness_config.get("fixture")
/Zephyr-latest/samples/
Dsample_definition_and_criteria.rst54 harness_config:
75 * Sample output can be validated by leveraging the ``harness_config`` regex option,
/Zephyr-latest/tests/kernel/timer/timer_behavior/
DREADME58 "harness_config/pytest_args" from "kernel.timer.timer_behavior_external" must
/Zephyr-latest/tests/benchmarks/thread_metric/
Dthread_metric_readme.txt143 For more details see Twister testcase.yaml documentation and 'harness_config:'