Searched refs:scenario (Results 1 – 25 of 42) sorted by relevance
12
63 scenario = data.get_scenario("test_config.main")64 assert scenario77 assert scenario["extra_args"] == ["UNRELATED1=abc", "UNRELATED2=xyz"]80 assert ";".join(scenario["extra_conf_files"]) == \84 assert ";".join(scenario["extra_dtc_overlay_files"]) == \88 assert scenario["extra_overlay_confs"] == \92 assert scenario["extra_configs"] == ["CONFIG_FOO=y"]
232 scenario, argument263 scenario=scenario,270 scenario=scenario,
954 testplan.scenarios = [scenario for testsuite in testsuites \955 for scenario in testsuite.scenarios]
20 To run this sample, build it for the desired board and scenario and flash it.22 The Flash scenario is supported on the nrf52dk/nrf52832 board.23 The RAM disk scenario is supported on the mimxrt1064_evk board.
5 Illustrates zbus priority boost feature with a priority inversion scenario.10 application implements the below figure scenario. When the priority boost feature is disabled, the27 :alt: ZBus priority boost scenario example.39 The figure below illustrates the execution of the cited scenario but with the priority boost43 :alt: ZBus example scenario for priority boost disabled.121 The figure below illustrates the execution of the same scenario but with the priority boost enabled.125 :alt: ZBus example scenario for priority boost enabled.
4 # Device/scenario dependent information that is not available in
115 scenario: str,123 and (matched := _is_element_matched(scenario, qelem.re_scenarios)) is False):
875 for scenario in options.test:876 if dirname := os.path.dirname(scenario):
177 Available RAM on the board (specified in KB). This is used to match test scenario180 Available FLASH on the board (specified in KB). This is used to match test scenario191 This indicates the board does support PCI. You can make a test scenario build or200 A test scenario can depend on 'eth' to only test ethernet or on 'netif' to run224 Multiply each test scenario timeout by specified ratio. This option allows to tune timeouts only271 subsection names delimited with a dot (``.``). For example, a test scenario359 A set of string tags for the test scenario. Usually pertains to364 skip test scenario unconditionally. This can be used for broken tests for368 Don't run this test scenario unless ``--enable-slow`` or ``--enable-slow-only`` was375 test scenario.[all …]
233 To select just one of the test scenarios, run Twister with ``--scenario`` command:237 ./scripts/twister --scenario tests/foo/bar/your.test.scenario.name240 ``your.test.scenario.name`` references a test scenario defined in :file:`testcase.yaml`
129 It calls ``wait_for_promt`` method, to not start scenario until DUT is ready. The shell fixture169 # continue test scenario, check version etc.
25 usage scenario is to run echo-server application inside QEMU. This is
27 usage scenario is to run echo-server application inside QEMU. This is114 There is one useful testing scenario that can be used with Linux host.
56 The ideal scenario is when the output "bandwidth" exceeds the input rate. If64 ideal scenario. In reality, it is not. The rates could be matched, but a
8 ACRN hypervisor supports a hybrid scenario where Zephyr runs in a so-called11 practical user scenario in the real world because Zephyr's real-time14 how a hybrid scenario works:41 type of scenario. Use ``acrn_ehl_crb`` as the target board parameter.
44 In the scenario below, the button attached to GPIO0 was pressed and held for
18 Use other sample to verify positive scenario for the watchdog driver.
42 ``/tmp/ivshmem_socket`` for your deployment scenario. For instance:
26 usage scenario is to run echo-client application inside QEMU. This is150 There is one useful testing scenario that can be used with Linux host.
42 limit, one could even imagine a scenario where the extensions are built by
91 …EST_CLK1`` and ``LITEX_CLK_TEST_CLK2``. Tests are controlled by separate defines for each scenario.
167 :alt: ZBus example scenario170 ZBus VDED execution example scenario.203 execution. The scenario considers the following priorities: T1 > MS1 > MS2 > S1. T1 has the highest254 channel A. The scenario considers the following priorities: T1 < MS1 < MS2 < S1.318 channel A. The scenario considers the priority boost feature and the following priorities: T1 < MS1374 acceptable in the zbus scenario since it will ensure a small bus latency.861 inversion scenario;
92 a Wi-Fi driver successfully connecting to an access point. In this scenario,
105 ``/tmp/ivshmem_socket`` for your deployment scenario. For instance:
93 the second core to the worst-case scenario from TF-M.552 …e tfm_integration sample for more details about integrating with TF-M and multiple images scenario.
