Oxygen is an extensible tool for Robot Framework that enables you to integrate running other testing tools and their reports as part of Robot Framework's reporting.
Oxygen is a Robot Framework tool that empowers the user to convert the results of any testing tool or framework to Robot Framework's reporting. This consolidates all test reporting together regardless of tools used.
Oxygen is designed to be extensible. Users can create their own handlers for other testing framework or tools to transform their reporting into the Robot Framework's
Table of Contents
To install Oxygen, run the following:
$ pip install robotframework-oxygen
- Oxygen is supported on Windows, Linux and MacOS
- Python 3.7 or above
- pip for easy installation
- Robot Framework
- additional dependencies
To check the Python version on the command line, run:
$ python --version
Example: Robot Framework running other test tools
Main usage scenario for Oxygen is the ability to write acceptance test cases that run your tests in other test tools and integrate the resulting test report as part of Robot Framework's. This means you are able to run all of your testing from Robot Framework and thus having all test reporting consolidated together.
After installing Oxygen, it can be used in the Robot Framework suite to write test cases. For example, to build acceptance tests that run different sets of JUnit tests:
*** Settings *** Library oxygen.OxygenLibrary *** Test cases *** JUnit unit tests should pass [Tags] testset-1 Run JUnit path/to/mydir/results.xml java -jar junit.jar --reports-dir=path/to/mydir JUnit integration tests should pass [Tags] testset-2 Run JUnit path/to/anotherdir/results.xml java -jar junit.jar --reports-dir=path/to/anotherdir
Then, run the suite by providing Oxygen as a listener:
$ robot --listener oxygen.listener my_tests.robot
Opening the Robot Framework
report.html, you should see that test case
JUnit unt tests should pass has been replaced by Oxygen with test cases matching with what is in the
path/to/mydir/results.xml JUnit report file. Similarly, test case
JUnit integration tests should pass has been replaced with results from
path/to/anotherdir/results.xml; each JUnit test case with its relevant information has a counterpart in the
log.html. Each JUnit test case is also tagged with the tags from the original Robot Framework test case.
The example above, for the brevity, shows incomplete commands to run JUnit tool from command line. Please refer to keyword documentation for more detailed documentation about keyword's arguments, as well as documentation for Gatling and ZAP related keywords. And, of course, refer to the particular tool documentation as well.
Using from command line
In case where you want to run your other testing tools separately, but yet combine results into unified Robot Framework
report.html, you can use Oxygen's command line interface to convert single result file to single corresponding Robot Framework
$ python -m oxygen oxygen.junit my_junit_results.xml
As a convention, the resulting Robot Framework xml file will be named by adding a suffix to the end. In the example above, the resulting Robot Framework xml file would be named
Note that resulting xml file will also be created at the same location as the original result file. Therefore, when original result files are in another directory:
$ python -m oxygen oxygen.gatling path/to/results.log
results_robot_output.xml will be created under
Clone the Oxygen repository to the environment where you want to the run the tool.
Oxygen requires a set of dependencies to be installed. Dependencies are listed in the
$ pip install -r requirements.txt
Oxygen uses task runner tool
invoke to run tests, build the project, etc.
Please refer to the available tasks for the project:
$ invoke --list
and the task file
Developing Oxygen with Nix
Nix is being used in this project for building development environments with capability of running bulk tests across multiple python versions and multiple Robot Framework versions.
This opens bash shell in current terminal window, with latest python 3.9 and Robot Framework 3.2.2.
$ nix-shell --argstr python python39 --argstr rfVersion 3.2.2
Now you can run the tests, for example:
$ invoke test --in-nix $ invoke utest --in-nix $ invoke atest
To exit the environment/shell type
This command tests all currently supported combinations of Python and Robot Framework.
$ nix-build test.nix
It should run for few minutes, and if all tests pass, the output will be:
Overall tests state: ok
Details of project licensing can be found in the LICENSE file in the project repository.
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Hashes for robotframework_oxygen-0.2-py3-none-any.whl