michaelh/zephyr
1
0
Fork 0
Code Releases Activity

scripts: west robot & simulation: Fix OOT

Browse source 
The current version of scipts do not consider OOT boards use cases and
the tests with robot now are strict to only one robot file, which is
not realistic for real environment. This address those issues and allow
multiple testsuits at command line and lists at tests entries. It add
another test parameter to allow configure robotframework options.

Fixes: #74563

Signed-off-by: Gerson Fernando Budke <gerson.budke@ossystems.com.br>
This commit is contained in:
Gerson Fernando Budke 2024-06-19 21:00:58 +02:00 • committed by Anas Nashif
commit 768b8bbca3
8 changed files with 78 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

35
doc/develop/test/twister.rst
View file

@ -615,8 +615,11 @@ harness_config: <harness configuration options>
If the scope is set to ``function``, DUT is launched for every test case
in python script. For ``session`` scope, DUT is launched only once.
robot_test_path: <robot file path> (default empty)
Specify a path to a file containing a Robot Framework test suite to be run.
robot_testsuite: <robot file path> (default empty)
Specify one or more paths to a file containing a Robot Framework test suite to be run.
robot_option: <robot option> (default empty)
One or more options to be send to robotframework.
bsim_exe_name: <string>
If provided, the executable filename when copying to BabbleSim's bin
@ -673,7 +676,33 @@ harness_config: <harness configuration options>
robot.example:
harness: robot
harness_config:
robot_test_path: [robot file path]
robot_testsuite: [robot file path]
It can be more than one test suite using a list.
.. code-block:: yaml
tests:
robot.example:
harness: robot
harness_config:
robot_testsuite:
- [robot file path 1]
- [robot file path 2]
- [robot file path n]
One or more options can be passed to robotframework.
.. code-block:: yaml
tests:
robot.example:
harness: robot
harness_config:
robot_testsuite: [robot file path]
robot_option:
- --exclude tag
- --stop-on-error
filter: <expression>
Filter whether the test scenario should be run by evaluating an expression