| /Zephyr-latest/scripts/tests/twister/ |
| D | test_quarantine.py | 67 scenarios, argument
77 scenarios=scenarios,
84 scenarios=scenarios,
137 scenarios=[],
240 scenarios=['all'],
246 scenarios=['bad scenario 1', 'bad scenario 2'],
252 scenarios=['all'],
|
| D | test_testplan.py | 467 testplan.scenarios = ['sc1', 'sc1-1', 'sc1-2', 'sc2']
479 assert sorted(level.scenarios) == sorted(expected_scenarios[level.name])
906 scenarios=['scenario1', 'scenario2']
910 scenarios=['scenario1']
924 scenarios=['scenario.a.1', 'scenario.a.2']
928 scenarios=['scenario.b.1']
951 return list(filter(lambda x: name in x.scenarios, testsuites))
954 testplan.scenarios = [scenario for testsuite in testsuites \
955 for scenario in testsuite.scenarios]
|
| /Zephyr-latest/scripts/pylib/twister/twisterlib/ |
| D | quarantine.py | 48 scenarios: list[str] = field(default_factory=list) variable in QuarantineElement
61 if 'all' in self.scenarios:
62 self.scenarios = []
70 self.re_scenarios = [re.compile(pat) for pat in self.scenarios]
78 if not any([self.scenarios, self.platforms, self.architectures, self.simulations]):
122 if (qelem.scenarios
|
| D | config_parser.py | 95 self.scenarios = {}
103 self.scenarios = self.data['tests']
168 for k, v in self.scenarios[name].items():
209 self.scenarios[name].get("extra_conf_files", [])
216 self.scenarios[name].get("extra_overlay_confs", [])
222 self.scenarios[name].get("extra_dtc_overlay_files", [])
|
| D | testplan.py | 81 scenarios = [] variable in TestLevel
124 self.scenarios = []
155 adds.extend(list(filter(r.fullmatch, self.scenarios)))
159 tl.scenarios = adds
171 _inherited_scenarios = _inherited.scenarios
172 level_scenarios = _level.scenarios if _level else []
207 self.scenarios.append(ts.id)
365 dupes = [item for item, count in collections.Counter(self.scenarios).items() if count > 1]
610 for name in parsed_data.scenarios:
921 planned_scenarios = tl.scenarios
|
| /Zephyr-latest/samples/basic/hash_map/ |
| D | Kconfig | 16 heap memory. For test scenarios using the Minimal C library, the heap
|
| /Zephyr-latest/tests/boards/espressif/wifi/ |
| D | Kconfig | 20 use during test scenarios.
27 during test scenarios. The device will use this password to authenticate
|
| /Zephyr-latest/tests/lib/hash_map/ |
| D | Kconfig | 16 heap memory. For test scenarios using the Minimal C library, the heap
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | cfg.rst | 15 scenarios, this API can be used to change the configuration locally.
|
| /Zephyr-latest/tests/boot/with_mcumgr/ |
| D | README.rst | 26 scenarios with described procedures, one can use a pytest command:
|
| /Zephyr-latest/doc/develop/optimizations/ |
| D | footprint.rst | 10 usage in different scenarios on as many supported platforms as possible. You
|
| /Zephyr-latest/samples/subsys/fs/format/ |
| D | README.rst | 11 devices for different file systems. There are 2 scenarios prepared for this
|
| /Zephyr-latest/tests/benchmarks/posix/threads/ |
| D | README.rst | 40 A tester may mix and match them allowing them different scenarios to
|
| /Zephyr-latest/doc/kernel/data_structures/ |
| D | index.rst | 27 structures are thread safe in specific usage scenarios (see
|
| /Zephyr-latest/subsys/net/l2/ieee802154/ |
| D | Kconfig.radio | 33 channel access and fits most usage scenarios (see IEEE 802.15.4-2020,
|
| /Zephyr-latest/samples/sysbuild/hello_world/ |
| D | README.rst | 12 scenarios could include boards embedding multiple SoCs. When building with
|
| /Zephyr-latest/doc/develop/test/ |
| D | twister.rst | 369 passed in on the command line. Intended for time-consuming test scenarios that
371 scenarios are still compiled.
860 :ref:`Snippets <snippets>` are supported in twister for test scenarios that
877 The set of test scenarios that actually run depends on directives in the test scenario
880 (:file:`twister_discard.csv`) can help show why particular test scenarios were
1265 in the hardware map file will be matched to test scenarios requesting the same fixtures
1274 current twister command can run those test scenarios which request the same fixtures.
1278 requested by test scenarios.
1358 ``scenarios`` and ``platforms`` entries listing combinations of scenarios and platforms
1363 When quarantining a class of tests or many scenarios in a single testsuite or
[all …]
|
| D | ztest.rst | 226 To build and execute all applicable test scenarios defined in your test application
233 To select just one of the test scenarios, run Twister with ``--scenario`` command:
305 Tests (test applications) in the Zephyr tree consist of many test scenarios that run as
307 feature. The ``twister`` script can parse the test scenarios, suites and cases in all
|
| /Zephyr-latest/subsys/ipc/ipc_service/lib/ |
| D | Kconfig.icmsg | 42 scenarios, such as when synchronous IPC is executed from the system
|
| /Zephyr-latest/tests/drivers/watchdog/wdt_error_cases/ |
| D | README.txt | 2 Test scenarios validate that invalid use of the watchdog driver
|
| /Zephyr-latest/drivers/serial/ |
| D | Kconfig.nrfx_uart_instance | 63 It is recommended to use hardware byte counting in such scenarios.
|
| /Zephyr-latest/drivers/dma/ |
| D | Kconfig.xilinx_axi_dma | 102 can raise an interrupt before the threshold is reached, minimizing latency in scenarios
|
| /Zephyr-latest/boards/rakwireless/rak5010/doc/ |
| D | index.rst | 16 and indoor scenarios, where location-based services need be present.
|
| /Zephyr-latest/samples/drivers/clock_control_litex/ |
| D | README.rst | 77 … a simple way of checking various clock output settings. User can pick one of 4 possible scenarios:
|
| /Zephyr-latest/subsys/net/l2/wifi/ |
| D | Kconfig | 40 interface has a valid IP address might be desirable in most scenarios.
|
