Searched refs:testing (Results 76 – 100 of 295) sorted by relevance
12345678910>>...12
30 is only usable in testing and should not be used in production code. See56 useful in testing setups where the application can connect to a pre-defined host."64 useful in testing setups where the application can connect to a pre-defined host."
11 is used for testing higher-level API for ADC devices.
16 Enables the dummy SMP backend which can be used for unit testing
13 used for testing drivers for eSPI devices.
16 Disable hw registers interaction for testing.
38 @defgroup testing Testing
16 /* Note: the groups are just meant for testing if properties and
18 /* Note: the groups are just meant for testing if properties and
22 * Samples must not use Zephyr's testing framework.28 expected value to have some level of testing for the sample itself.36 are testing the sample, not the subsystem it builds on top.
11 BabbleSim_ is :ref:`integrated in zephyr <bsim>` and used for testing the Bluetooth stack.
10 This sample allows testing Wi-Fi drivers for various boards by
27 Enable LED shell for testing.
6 * Application overlay for testing driver builds
90 /* requires external CAN transceiver or jumper on RX and TX pins for loopback testing */
36 JEDEC MSPI-NOR flash testing
39 JEDEC QSPI-NOR SPI flash testing
25 For testing purposes without the need of any hardware, the :ref:`native_sim <native_sim>`
34 For testing, this option allows a non-random number generator to be used and52 generator is not random and used for testing only.
82 for testing. To test the optional alarms, update event callback91 To build the test application with the default configuration, testing128 The tests take up to 30 seconds each if they are testing real hardware.
101 /* requires external CAN transceiver or jumper on RX and TX pins for loopback testing */
97 /* requires external CAN transceiver or jumper on RX and TX pins for loopback testing */
91 /* requires external CAN transceiver or jumper on RX and TX pins for loopback testing */
6 The Zephyr Test Framework (Ztest) provides a simple testing framework intended11 integration testing, or for unit testing specific modules.218 Quick start - Integration testing241 file, which is like ``sample.testing.ztest`` in the boilerplate test suite sample.280 either can be testing functionality or APIs. Functions implementing a test case354 Quick start - Unit testing357 Ztest can be used for unit testing. This means that rather than including the358 entire Zephyr OS for testing a single function, you can focus the testing359 efforts into the specific module in question. This will speed up testing since
