@@ -62,22 +62,6 @@ The primary advantage of the Robot framework is that it is agnostic of the targe
The interaction with the layers below the framework can be done using the libraries built-in or
user-created that make use of application interfaces.
**Listener Mechanism**
# Custom Listener Benefits
Custom listeners in Robot Framework offer a range of benefits to enhance your test automation process. These advantages include:
Custom listeners are valuable when the default logging and reporting mechanisms. For testing processes that demand comprehensive
insights into test case execution, including individual step outcomes, timing, and custom attributes, a custom listener proves to be a suitable solution.
Custom listeners play a pivotal role when debugging and troubleshooting are critical aspects of your test automation process.
When real-time visibility into the progress of test executions is crucial, a custom listener can be specifically designed to provide ongoing updates and insights as the tests are running.
These benefits make custom listeners a valuable tool for optimizing and customizing your Robot Framework test automation process.
The custom listener script is written in Python and should be saved with a .py extension. It defines listener functions and handles logging to the console and files.
Run your Robot Framework tests with the listener using the --listener option:
`robot --listener <listener.py> <Robot_file>`
**Test Libraries & Test Tools**
A library in a Robot Framework terminology, extends the Robot
...
...
@@ -89,7 +73,7 @@ tested, or of the environment in which the item to be tested is present.
**System Under Test**
This is the actual target on which the testing activity is performed. It could either be a
library or a app. Libraries act as an interface between the Robot Framework and the system
library or an app. Libraries act as an interface between the Robot Framework and the system
under test. Hence, there is no way through which the framework can directly talk to the
system under test. The Robot Framework supports various file formats namely HTML, TSV
(Tab Separated Values), reST (Restructured Text), and Plain text. As per the official
...
...
@@ -100,8 +84,7 @@ documentation of Robot framework, the plain text format is recommended.
Apertis does the complete test automation setup on LAVA infrastructure for all it's reference hardware.
System integration and boot level testing is done as part of automated on successfully generated image
from CI/CD image generation pipeline. Test report are displayed on [QA report app](https://qa.apertis.org/)
and bug task is created for each [failure test cases](https://phabricator.apertis.org/tag/test-failure/)
on Phabricator.
and bug task is created for each [failure test cases](https://gitlab.apertis.org/infrastructure/apertis-issues/-/boards/30) on gitlab issue board and tagged it under `test-area:test-failure`.
There are two main constraints on automated tests setup on LAVA, the asynchronous way of updating results
and user not having control over the job once it is submitted. Developers and CI pipeline can both submit
...
...
@@ -109,25 +92,30 @@ jobs to LAVA, but they cannot interact with a job while it is running. The LAVA
of submitting a job, wait for the job to be selected for execution, wait for the job to complete it's execution,
and download test results.
Considering the above constraints and covering the wide range of test areas including HMI tests,
integrating Robot Framework on LAVA setup will provide more chances to automate complex tests.
Considering the above constraints and covering the wide range of test areas including HMI tests, on Automated test infrastructure setup of LAVA integrating automated test framework of Robot Framework, provide more chances to automate complex tests by make use of open source library under RFW.
A LAVA instance consists of two primary components **masters** and **workers**. The simplest possible
A LAVA instance consists of two primary components **masters** and **workers** works like server and client mechanisms. The simplest possible
configuration is to run the master and worker components on a single machine, but for larger instances
it can also be configured to support multiple workers controlling a larger number of attached devices
in a [multi node](https://docs.lavasoftware.org/lava/multinode.html) mechanism.
/*
There are two possible approaches available to integrate Robot Framework on LAVA:
1. Creating a QEMU emulator which uses Apertis SDK image and starts to execute Robot Framework test suites
2. Creating a Docker based container and start executing Robot Framework test suites
The first approach consists in creating a QEMU emulator with Apertis SDK image and
installing Robot Framework. By using it all the SDK related test cases can be migrated
to Robot Framework and run successfully. However, running tests on Fixed Function or HMI
images is not feasible, making this approach not suitable for testing target relates tests,
and therefore not meeting all the use cases.
*/
...
...
@@ -151,6 +139,21 @@ and monitor the job completion. The test cases execution will be done inside the
and once the test execution is completed the generated report will be sent back to dispatcher to be parsed
and send back to server.
**Listener Mechanism**
Custom listeners in Robot Framework offer a range of benefits to enhance your test automation process. These advantages include:
Custom listeners are valuable when the default logging and reporting mechanisms. For testing processes that demand comprehensive
insights into test case execution, including individual step outcomes, timing, and custom attributes, a custom listener proves to be a suitable solution.
Custom listeners play a pivotal role when debugging and troubleshooting are critical aspects of your test automation process.
When real-time visibility into the progress of test executions is crucial, a custom listener can be specifically designed to provide ongoing updates and insights as the tests are running.
These benefits make custom listeners a valuable tool for optimizing and customizing your Robot Framework test automation process.
The custom listener script is written in Python and should be saved with a .py extension. It defines listener functions and handles logging to the console and files.
Run your Robot Framework tests with the listener using the --listener option:
`robot --listener <listener.py> <Robot_file>`
# Impact analysis on Apertis distribution
