Lines Matching +full:- +full:babblesim

3 BabbleSim  chapter
6 BabbleSim and Zephyr
9 In the Zephyr project we use the `Babblesim`_ simulator to test some of the Zephyr radio protocols,
18 When there is radio activity, this Linux executable will connect to the BabbleSim Phy simulation
21 In the BabbleSim documentation you can find more information on how to
22 `get <https://babblesim.github.io/fetching.html>`_ and
23 `build <https://babblesim.github.io/building.html>`_ the simulator.
43 When there is radio activity, BabbleSim tests require at the very least a physical layer simulation
65 More information about how different tests types relate to BabbleSim and the bsim boards can be
68 Test coverage and BabbleSim
81    https://BabbleSim.github.io
94 .. code-block:: bash
106 .. code-block:: bash
124 .. code-block:: bash
130 .. code-block:: bash
138 ---------
144 -------------
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
170 an RFC issue or on the babblesim discord channel.
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
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