Searched refs:fixtures (Results 1 – 17 of 17) sorted by relevance
256 static struct ina237_fixture fixtures[] = { variable262 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]); } \
37 fixtures: list[str] = None variable in DeviceConfig84 fixtures=config.option.fixtures,
209 def testsuite_runnable(testsuite, fixtures): argument218 can_run = fixture in map(lambda f: f.split(sep=':')[0], fixtures)265 fixtures = options.fixture306 testsuite_runnable = self.testsuite_runnable(self.testsuite, fixtures)311 self.testsuite_runnable(self.testsuite, h.fixtures)):
69 self.fixtures = []222 d.fixtures.extend(self.options.fixture)293 fixtures = dut.get('fixtures', [])314 new_dut.fixtures = fixtures
488 for fixture in hardware.fixtures:
495 if fixture and fixture not in map(lambda f: f.split(sep=':')[0], d.fixtures):
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=[])])…547 fixtures, argument560 fixtures=fixtures,
154 fixtures, argument183 mocked_hm.options.fixture = fixtures211 [fixture in dut.fixtures for fixture in fixtures]
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 …]
53 - conftest.py: Contains common fixtures for use in testing the twister tool.
480 hardware.fixtures = ["fixture1:option1", "fixture2"]
30 for fixture in dut.device_config.fixtures:
76 Blackbox tests use ``pytest`` 's fixtures, further reading on which is available79 If you would like to add your own fixtures,85 - :zephyr_file:`scripts/tests/twister_blackbox/conftest.py` already contains some fixtures -
690 The scope for which ``dut`` and ``shell`` pytest fixtures are shared.1248 of a board and the fixtures it supports via the command line or using the hardware1256 fixtures:1265 in the hardware map file will be matched to test scenarios requesting the same fixtures1268 .. figure:: figures/fixtures.svg1272 can be used multiple times and all given fixtures will be appended as a list. And the1273 given fixtures will be assigned to all boards, this means that all boards set by1274 current twister command can run those test scenarios which request the same fixtures.1276 Some fixtures allow for configuration strings to be appended, separated from the1277 fixture name by a ``:``. Only the fixture name is matched against the fixtures[all …]
65 Test fixtures68 Test fixtures can be used to help simplify repeated test setup operations. In many cases, tests in70 This is achieved via fixtures in the following way:
16 utilizes the concept of plugins and fixtures, increasing its expendability and reusability.
701 "./scripts/pylib/pytest-twister-harness/src/twister_harness/fixtures.py" = [1586 "./scripts/pylib/pytest-twister-harness/src/twister_harness/fixtures.py",
