Allow robot scripts without renode #64825
Assignees
Labels
area: Test Framework
Issues related not to a particular test, but to the framework instead
area: Twister
Twister
Feature Request
A request for a new feature
Comments
|
Interesting request. Is it something that you would like to implement? |
|
Hey, I have time and motivation to implement this! Is there any opinion on backwards compatibility, in case it is not perfectly transparent that things changed? |
No. I think limiting robot framework to just renode is quite unnecessary anyway. It should be able to orchestrate the hardware abstractions that are exposed to pytest through twister and work as automation that runs along side of the test on native_posix, qemu and on device testing. |
|
@PiotrZierhoffer FYI |
This was referenced Jan 15, 2024
MP-StefanKraus
added a commit
to tiacsys/zephyr
that referenced
this issue
Jan 16, 2024
This change adds an entrypoint for the common robot framework and a first library to interact with the board, similar to the functionality currently available in pytest. To reuse the command line parsing and have a proper twister config, we provide a robot_wrapper which serializes the configuration and reloads it in the library. This change addresses zephyrproject-rtos#64825, which asks for robot scripts without renode. Signed-off-by: Stefan Kraus <[email protected]>
MP-StefanKraus
added a commit
to tiacsys/zephyr
that referenced
this issue
Jan 16, 2024
This change adds some test cases to test correct calls and parsing for the robot framework integration with twister. This change addresses zephyrproject-rtos#64825, which asks for robot scripts without renode. Signed-off-by: Stefan Kraus <[email protected]>
nashif
added
area: Test Framework
Kerstin20
added a commit
to tiacsys/bridle
that referenced
this issue
Feb 16, 2024
These tests works only this branch: https://github.com/tiacsys/zephyr/tree/snks/robot-twister-int See also: zephyrproject-rtos/zephyr#64825 Signed-off-by: Kerstin Jenett <[email protected]>
MP-StefanKraus
added a commit
to tiacsys/zephyr
that referenced
this issue
Mar 19, 2024
This change adds an entrypoint for the common robot framework and a first library to interact with the board, similar to the functionality currently available in pytest. To reuse the command line parsing and have a proper twister config, we provide a robot_wrapper which serializes the configuration and reloads it in the library. This change addresses zephyrproject-rtos#64825, which asks for robot scripts without renode. Signed-off-by: Stefan Kraus <[email protected]>
MP-StefanKraus
added a commit
to tiacsys/zephyr
that referenced
this issue
Mar 19, 2024
This change adds some test cases to test correct calls and parsing for the robot framework integration with twister. This change addresses zephyrproject-rtos#64825, which asks for robot scripts without renode. Signed-off-by: Stefan Kraus <[email protected]>
MP-StefanKraus
added a commit
to tiacsys/zephyr
that referenced
this issue
Jul 1, 2024
This change adds an entrypoint for the common robot framework and a first library to interact with the board, similar to the functionality currently available in pytest. To reuse the command line parsing and have a proper twister config, we provide a robot_wrapper which serializes the configuration and reloads it in the library. This change addresses zephyrproject-rtos#64825, which asks for robot scripts without renode. Signed-off-by: Stefan Kraus <[email protected]>
MP-StefanKraus
added a commit
to tiacsys/zephyr
that referenced
this issue
Jul 1, 2024
This change adds some test cases to test correct calls and parsing for the robot framework integration with twister. This change addresses zephyrproject-rtos#64825, which asks for robot scripts without renode. Signed-off-by: Stefan Kraus <[email protected]>
schlotter
pushed a commit
to ZEISS/zephyr
that referenced
this issue
Jul 1, 2024
This change adds an entrypoint for the common robot framework and a first library to interact with the board, similar to the functionality currently available in pytest. To reuse the command line parsing and have a proper twister config, we provide a robot_wrapper which serializes the configuration and reloads it in the library. This change addresses zephyrproject-rtos#64825, which asks for robot scripts without renode. Signed-off-by: Stefan Kraus <[email protected]>
schlotter
pushed a commit
to ZEISS/zephyr
that referenced
this issue
Jul 1, 2024
This change adds some test cases to test correct calls and parsing for the robot framework integration with twister. This change addresses zephyrproject-rtos#64825, which asks for robot scripts without renode. Signed-off-by: Stefan Kraus <[email protected]>
schlotter
pushed a commit
to ZEISS/zephyr
that referenced
this issue
Sep 13, 2024
This change adds an entrypoint for the common robot framework and a first library to interact with the board, similar to the functionality currently available in pytest. To reuse the command line parsing and have a proper twister config, we provide a robot_wrapper which serializes the configuration and reloads it in the library. This change addresses zephyrproject-rtos#64825, which asks for robot scripts without renode. Signed-off-by: Stefan Kraus <[email protected]>
schlotter
pushed a commit
to ZEISS/zephyr
that referenced
this issue
Sep 13, 2024
This change adds some test cases to test correct calls and parsing for the robot framework integration with twister. This change addresses zephyrproject-rtos#64825, which asks for robot scripts without renode. Signed-off-by: Stefan Kraus <[email protected]>
philipprued
pushed a commit
to ZEISS/zephyr
that referenced
this issue
Oct 31, 2024
This change adds an entrypoint for the common robot framework and a first library to interact with the board, similar to the functionality currently available in pytest. To reuse the command line parsing and have a proper twister config, we provide a robot_wrapper which serializes the configuration and reloads it in the library. This change addresses zephyrproject-rtos#64825, which asks for robot scripts without renode. Signed-off-by: Stefan Kraus <[email protected]>
philipprued
pushed a commit
to ZEISS/zephyr
that referenced
this issue
Nov 4, 2024
This change adds some test cases to test correct calls and parsing for the robot framework integration with twister. This change addresses zephyrproject-rtos#64825, which asks for robot scripts without renode. Signed-off-by: Stefan Kraus <[email protected]>
philipprued
pushed a commit
to ZEISS/zephyr
that referenced
this issue
Nov 5, 2024
This change adds some test cases to test correct calls and parsing for the robot framework integration with twister. This change addresses zephyrproject-rtos#64825, which asks for robot scripts without renode. Signed-off-by: Stefan Kraus <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
It is common to run end to end tests against the device using robot framework. With the new better pytest integration it should be possible to allow robot scripts to run in device testing mode. Currently it seems that only renode is supported when running the robot script as part of robot test harness in twister.
Describe the solution you'd like
Ability to specify a robot harness and run in in device testing mode. Having it have access to the same "dut" interface as is available in pytest.
Describe alternatives you've considered
Running robot scripts manually which is not very practical since twister has better knowledge of the test environment and can provide for example executable path, tty etc.
The text was updated successfully, but these errors were encountered: