Lines Matching +full:bsim +full:- +full:test +full:- +full:results
9 In the Zephyr project we use the `Babblesim`_ simulator to test some of the Zephyr radio protocols,
13 :ref:`bsim boards<bsim boards>`
15 When we build Zephyr targeting a :ref:`bsim board<bsim boards>` we produce a Linux
32 Tests without radio activity: bsim tests with twister
35 The :ref:`bsim boards<bsim boards>` can be used without radio activity, and in that case, it is not
47 These tests are kept in the :code:`tests/bsim/` folder. The ``compile.sh`` and ``run_parallel.sh``
57 built with some checks which decide if the test is passing or failing. These embedded
61 * Test using the EDTT_ tool, in which a EDTT (python) test controls the embedded applications over
62 an RPC mechanism, and decides if the test passes or not.
63 Today these tests include a very significant subset of the BT qualification test suite.
65 More information about how different tests types relate to BabbleSim and the bsim boards can be
66 found in the :ref:`bsim boards tests section<bsim_boards_tests>`.
68 Test coverage and BabbleSim
73 test coverage information.
75 You can use the script :zephyr_file:`tests/bsim/generate_coverage_report.sh` to generate an html
94 .. code-block:: bash
97 ${ZEPHYR_BASE}/tests/bsim/compile.sh
101 SEARCH_PATH=${ZEPHYR_BASE}/tests/bsim \
102 ${ZEPHYR_BASE}/tests/bsim/run_parallel.sh
106 .. code-block:: bash
109 ${ZEPHYR_BASE}/tests/bsim/bluetooth/host/adv/compile.sh
113 SEARCH_PATH=${ZEPHYR_BASE}/tests/bsim/bluetooth/host/adv \
114 ${ZEPHYR_BASE}/tests/bsim/run_parallel.sh
119 After building the tests' required binaries you can run a test directly using its individual test
124 .. code-block:: bash
126 WORK_DIR=${ZEPHYR_BASE}/bsim_out ${ZEPHYR_BASE}/tests/bsim/net/compile.sh
130 .. code-block:: bash
132 ${ZEPHYR_BASE}/tests/bsim/net/sockets/echo_test/tests_scripts/echo_test_802154.sh
137 Test code
138 ---------
140 …phyr_file:`Bluetooth sample test <tests/bsim/bluetooth/host/misc/sample_test/README.rst>` for conv…
144 -------------
146 The build scripts ``compile.sh`` simply build all the required test and sample applications
158 Test scripts
159 ------------
161 Please follow the existing conventions and do not design one-off bespoke runners (e.g. a python
164 The rationale is that it is easier and faster for the maintainers to perform tree-wide updates for
168 If you have a good idea for improving your test script, please make a PR changing *all* the test
178 - Each test is defined by a shell script with the extension ``.sh``, in a subfolder called
180 - It is recommended to run a single test per script file. It allows for better parallelization of
182 - Scripts expect that the binaries they require are already built. They should not compile binaries.
183 - Scripts will spawn the processes for every simulated device and the physical layer simulation.
184 - Scripts must return 0 to the invoking shell if the test passes, and not 0 if the test fails.
185 - Each test must have a unique simulation id, to enable running different tests in parallel.
186 - Neither the scripts nor the images should modify the workstation filesystem content beyond the
187 ``${BSIM_OUT_PATH}/results/<simulation_id>/`` or ``/tmp/`` folders.
189 - Tests that require several consecutive simulations (e.g, if simulating a device pairing, powering
193 - Avoid overly long tests. If the test takes over 20 seconds of runtime, consider if it is possible
195 - If the test takes over 5 seconds, set ``EXECUTE_TIMEOUT`` to a value that is at least 5 times
196 bigger than the measured run-time.
197 - Do not set ``EXECUTE_TIMEOUT`` to a value lower than the default.
198 - Tests should not be overly verbose: less than a hundred lines are expected on the outputs. Do make