| /Zephyr-latest/scripts/pylib/pytest-twister-harness/src/twister_harness/ |
| D | twister_harness_config.py | 37 fixtures: list[str] = None variable in DeviceConfig
84 fixtures=config.option.fixtures,
|
| D | plugin.py | 17 'twister_harness.fixtures'
123 help='The scope for which `dut` and `shell` fixtures are shared.'
126 '--twister-fixture', action='append', dest='fixtures', metavar='FIXTURE', default=[],
|
| /Zephyr-latest/tests/drivers/sensor/ina237/src/ |
| D | ina237_test.c | 256 static struct ina237_fixture fixtures[] = { variable
262 ZTEST(ina237_##inst, test_shunt_cal) { test_shunt_cal(&fixtures[inst]); } \
263 ZTEST(ina237_##inst, test_current) { test_current(&fixtures[inst]); } \
264 ZTEST(ina237_##inst, test_bus_voltage) { test_bus_voltage(&fixtures[inst]); } \
265 ZTEST(ina237_##inst, test_power) { test_power(&fixtures[inst]); } \
266 ZTEST(ina237_##inst, test_temperature) { test_temperature(&fixtures[inst]); } \
267 ZTEST(ina237_##inst, test_vshunt) { test_vshunt(&fixtures[inst]); } \
|
| /Zephyr-latest/doc/develop/test/twister/ |
| D | twister_blackbox.rst | 73 Fixtures subsection
76 Blackbox tests use ``pytest`` 's fixtures, further reading on which is available
79 If you would like to add your own fixtures,
85 - :zephyr_file:`scripts/tests/twister_blackbox/conftest.py` already contains some fixtures -
|
| /Zephyr-latest/scripts/pylib/twister/twisterlib/ |
| D | hardwaremap.py | 69 self.fixtures = []
219 # the fixtures given by twister command explicitly should be assigned to each DUT
222 d.fixtures.extend(self.options.fixture)
293 fixtures = dut.get('fixtures', [])
314 new_dut.fixtures = fixtures
|
| D | testinstance.py | 209 def testsuite_runnable(testsuite, fixtures): argument
218 can_run = fixture in map(lambda f: f.split(sep=':')[0], fixtures)
265 fixtures = options.fixture
306 testsuite_runnable = self.testsuite_runnable(self.testsuite, fixtures)
311 self.testsuite_runnable(self.testsuite, h.fixtures)):
|
| /Zephyr-latest/scripts/west_commands/tests/ |
| D | conftest.py | 5 '''Common fixtures for use testing the runner package.'''
|
| D | test_pyocd.py | 125 # Fixtures
|
| D | test_mdb.py | 150 # Fixtures
|
| /Zephyr-latest/scripts/schemas/twister/ |
| D | hwmap-schema.yaml | 53 "fixtures":
|
| /Zephyr-latest/scripts/tests/twister/ |
| D | test_hardwaremap.py | 135 ' device_serial, device_serial_pty, fixtures,' \
154 fixtures, argument
183 mocked_hm.options.fixture = fixtures
211 [fixture in dut.fixtures for fixture in fixtures]
277 fixtures:
318 'fixtures': ['dummy fixture 1', 'dummy fixture 2'],
330 'fixtures': [],
|
| D | test_testinstance.py | 76 fixtures=fixture,
449 fixtures = ['dummy fixture']
451 can_run = TestInstance.testsuite_runnable(testsuite, fixtures)\
525 …mock.ANY, 'not runnable', ['?'], mock.Mock(duts=[mock.Mock(platform='demo_board_2', fixtures=[])])…
531 ' enable_slow, filter, fixtures, hardware_map, expected',
547 fixtures, argument
560 fixtures=fixtures,
|
| D | README.md | 53 - conftest.py: Contains common fixtures for use in testing the twister tool.
|
| D | test_handlers.py | 756 fixtures=[],
764 fixtures=['dummy fixture'],
772 fixtures=['dummy fixture'],
782 fixtures=['dummy fixture'],
791 fixtures=['dummy fixture'],
807 fixtures=[],
815 fixtures=['dummy fixture'],
823 fixtures=['dummy fixture'],
833 fixtures=['dummy fixture'],
842 fixtures=['dummy fixture'],
[all …]
|
| D | conftest.py | 6 '''Common fixtures for use in testing the twister tool.'''
|
| D | test_harness.py | 480 hardware.fixtures = ["fixture1:option1", "fixture2"]
|
| /Zephyr-latest/scripts/tests/twister_blackbox/test_data/tests/pytest/pytest/ |
| D | test_sample.py | 9 # tests or in other fixtures
|
| /Zephyr-latest/samples/subsys/testsuite/pytest/basic/pytest/ |
| D | test_sample.py | 9 # tests or in other fixtures
|
| /Zephyr-latest/tests/drivers/can/host/pytest/ |
| D | conftest.py | 30 for fixture in dut.device_config.fixtures:
|
| /Zephyr-latest/doc/develop/test/ |
| D | twister.rst | 690 The scope for which ``dut`` and ``shell`` pytest fixtures are shared.
1242 Fixtures subsubsection
1248 of a board and the fixtures it supports via the command line or using the hardware
1251 Fixtures are defined in the hardware map file as a list:
1256 fixtures:
1265 in the hardware map file will be matched to test scenarios requesting the same fixtures
1268 .. figure:: figures/fixtures.svg
1271 Fixtures can also be provided via twister command option ``--fixture``, this option
1272 can be used multiple times and all given fixtures will be appended as a list. And the
1273 given fixtures will be assigned to all boards, this means that all boards set by
[all …]
|
| D | pytest.rst | 16 utilizes the concept of plugins and fixtures, increasing its expendability and reusability.
103 Fixtures section in Integration with pytest test framework
|
| D | ztest.rst | 65 Test fixtures
68 Test fixtures can be used to help simplify repeated test setup operations. In many cases, tests in
70 This is achieved via fixtures in the following way:
|
| /Zephyr-latest/scripts/tests/twister_blackbox/ |
| D | conftest.py | 6 '''Common fixtures for use in testing the twister tool.'''
|
| /Zephyr-latest/tests/net/lib/lwm2m/interop/pytest/ |
| D | conftest.py | 2 Common test fixtures
|
| /Zephyr-latest/doc/develop/test/figures/ |
| D | fixtures.svg | 3 …ext-align: left"> connected: true</div><div style="text-align: left"> fixtures:</div><div style=…
|
