Searched refs:tests (Results 951 – 975 of 1029) sorted by relevance
1...<<31323334353637383940>>...42
| /Zephyr-latest/doc/develop/getting_started/ |
| D | installation_linux.rst | 215 certain conditions (for example, running tests in QEMU for some architectures).
301 flags when building applications or running tests. In addition to
|
| /Zephyr-latest/doc/security/ |
| D | security-overview.rst | 464 can be partially achieved by automated tests, it is inevitable to
575 From these threat models and mitigation techniques tests shall be
576 derived that prove the effectiveness of the countermeasures. These tests
600 - **Fuzzing tests** shall be performed on both exposed APIs and
610 If possible (as in case of fuzzing analyses), these tests shall be
|
| /Zephyr-latest/doc/develop/west/ |
| D | build-flash-debug.rst | 701 Running Robot Framework tests: ``west robot``
710 (essentially a wrapper for running Robot tests in Renode), but can be
717 This will run all tests from testsuite.robot and print output provided
809 The test cases in :zephyr_file:`scripts/west_commands/tests` add unit test
812 Please try to add tests when adding new runners. Note that if your
|
| /Zephyr-latest/tests/bsim/bluetooth/mesh/src/ |
| D | test_beacon.c | 2250 struct bst_test_list *test_beacon_install(struct bst_test_list *tests) in test_beacon_install() argument
2252 tests = bst_add_tests(tests, test_beacon); in test_beacon_install()
2253 return tests; in test_beacon_install()
|
| D | test_persistence.c | 1157 struct bst_test_list *test_persistence_install(struct bst_test_list *tests) in test_persistence_install() argument
1159 return bst_add_tests(tests, test_persistence); in test_persistence_install()
|
| /Zephyr-latest/boards/snps/iotdk/doc/ |
| D | index.rst | 63 You can try many of the sample applications or tests, but let us discuss
|
| /Zephyr-latest/doc/connectivity/bluetooth/autopts/ |
| D | autopts-win10.rst | 120 west build -p auto -b nrf52840dk/nrf52840 zephyr/tests/bluetooth/tester/
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | smp_protocol.rst | 131 | ``5`` | Run-time tests |
|
| /Zephyr-latest/samples/subsys/llext/shell_loader/ |
| D | README.rst | 35 :zephyr_file:`tests/subsys/llext/no_mem_protection.conf`.
|
| /Zephyr-latest/modules/mbedtls/ |
| D | CMakeLists.txt | 19 This is meant to be used only for tests, not in production!")
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-tools.rst | 254 The main use case for a virtual controller is to do Bluetooth connectivity tests without
255 the need of Bluetooth hardware. This allows to automate Bluetooth integration tests with
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-3.4.rst | 251 * Legacy Ztest API was deprecated. All new tests shall use the new Ztest API.
358 in tests and samples.
668 * Twister now supports ``gtest`` harness for running tests written in gTest.
683 ``$test_root/tests/foo/testcase.yaml``, Twister will use
684 ``$alt_config_root/tests/foo/testcase.yaml`` if it exists.
1442 * Two Babblesim based networking (802.15.4) tests have been added, which are run in Zephyr's CI
1444 * For native_posix and the nrf52_bsim: Many tests have been fixed and enabled.
1446 * Migrated all tests to new Ztest API and deprecated legacy Ztest.
|
| /Zephyr-latest/scripts/pylib/twister/twisterlib/ |
| D | reports.py | 166 tests="0",
241 tests="0",
|
| /Zephyr-latest/boards/nxp/imx93_evk/doc/ |
| D | index.rst | 194 Use this configuration to run basic Zephyr applications and kernel tests,
263 Use this configuration to run basic Zephyr applications and kernel tests,
|
| /Zephyr-latest/tests/lib/devicetree/api/ |
| D | app.overlay | 9 * with real-world devicetree nodes, to allow these tests to run on
65 * test_gpio_1, or dependency ordinal tests may fail.
|
| /Zephyr-latest/doc/services/tfm/ |
| D | build.rst | 26 * tfm_ns - TF-M non-secure app (only used by regression tests).
|
| /Zephyr-latest/boards/nxp/ls1046ardb/doc/ |
| D | index.rst | 84 kernel tests on LS1046A RDB board. For example, with the :zephyr:code-sample:`synchronization` samp…
|
| /Zephyr-latest/subsys/net/lib/coap/ |
| D | Kconfig | 16 bool "Test API for CoAP unit tests"
|
| /Zephyr-latest/doc/contribute/ |
| D | guidelines.rst | 203 tests. All of these are available for developers to contribute to and enhance.
286 :file:`tests`
441 * **how** you know it works -- for example, which tests you ran.
581 of tests is not supported on all target devices.
591 west twister -p native_sim -s tests/drivers/build_all/sensor/sensors.generic_test
|
| /Zephyr-latest/doc/services/mem_mgmt/ |
| D | index.rst | 72 ``tests/subsys/mem_mgmt/mem_attr/``.
|
| /Zephyr-latest/doc/develop/toolchains/ |
| D | zephyr_sdk.rst | 11 certain conditions (for example, running tests in QEMU for some architectures).
|
| /Zephyr-latest/doc/kernel/ |
| D | code-relocation.rst | 183 ``$ZEPHYR_BASE/tests/application_development/code_relocation``
|
| /Zephyr-latest/boards/snps/nsim/arc_classic/doc/ |
| D | index.rst | 104 Note that even if both GNU and MWDT toolchain support is declared for the target some tests or
108 Use this configuration to run basic Zephyr applications and kernel tests in
|
| /Zephyr-latest/subsys/debug/ |
| D | Kconfig | 301 around compiler bugs for specific tests.
342 condition is false. The tests that validate the assert feature may
|
| /Zephyr-latest/doc/build/ |
| D | zephyr_cmake_package.rst | 427 Same responsibility as ``ZephyrConfigVersion.cmake``, but for unit tests.
437 Same responsibility as ``ZephyrConfig.cmake``, but for unit tests.
|
1...<<31323334353637383940>>...42
