Lines Matching full:test
5 subsystem. The tests run on the BabbleSim simulator, using the BabbleSim test
11 src/ directory containing the necessary test harnesses to execute the tests.
13 There's only a single test application for all the Bluetooth Mesh BabbleSim
14 tests. The test application is built from this directory, and includes all test
15 harnesses in every build. The overlying bsim test framework selects the harness
16 to use at runtime, using the test identifiers passed in the test scripts.
30 Individual test harnesses can be run outside of ``RunTest()`` by setting the
36 When running test applications independently, make sure to assign the original
39 Example: To debug the ``transport_tx_seg_block`` test harness in the transport
40 seg_block test, change transport/seg_block.sh to
60 The Bluetooth Mesh BabbleSim tests mainly operate on the test framework for the
66 All test scripts in the Bluetooth Mesh BabbleSim test suite follow a common
67 pattern for running a single test across N devices with different test
68 harnesses. ``mesh_test.sh`` is sourced in each test script, and its ``RunTest``
73 RunTest <test name> <harness_name_1> <harness_name_2>...
85 The mesh_test module is never called from the framework, so each test harness
93 Each test needs a separate test script and one or more test harnesses that
94 execute the test on target.
96 Test scripts should be organized by submodules under the test_scripts
97 directory, and each test case needs a separate test script with a single test
100 Each test harness is defined by a ``struct bst_test_instance`` structure, that
101 is presented to the test runner through an ``install`` function called from the
102 test application's main function. The harness contains a set of callback
103 functions that allows starting the test behavior.
105 Each mesh test harness should call the ``bt_mesh_test_cfg`` function from its
106 ``test_init_f`` callback to set up the test timeout and mesh metadata. The test
108 test times out. At the test timeout, the test will pass if the ``PASS()`` macro