robotframework-oxygen
robotframework-oxygen copied to clipboard
eficode
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 to consolidate all test reporting together regardless of...
Currently, different methods of handling time data or lack thereof are spread across the different handlers (particularly JUnit). As a developer, I would like to see - Support for either...
I got a JUnit result for golang run. It contained test cases and each testcase contained only a time field for each test case, giving the elapsed time for a...
Gtest dummy unit tests should pass [Tags] ci:smoke Run JUnit /home/xunit.xml connect -i 6 gives me the following error: Gtest dummy unit tests should pass | FAIL | TypeError: __init__()...
HTML-unsafe characters in suite names break html reporting like log.html and report.html. This is most evident with ZAP handler, as there is always an URL that ends up in the...
Currently, Oxygen knows what handlers are available through the `config.yml` file located within the project. Devise a way for user to give their own config file. Consider following things: -...
The CICD currently relies on Robot Framework exit code to know if the test execution failed or not. However, in cases where the Oxygen listener fails, but the test execution...
When we have Github Actions PR merged, we might look into Black for automatic code formatting. We might use something of a sort (not tested): ```yaml jobs: format: runs-on: ubuntu-latest...
Currently, only stdout is printed out when running a command. It would be helpful to print out stderr as well. This impacts all internal Handlers.
Improve the robotframework-oxygen developer guide.
Debugging RF test cases that use Oxygen needs to explained somewhere. We concluded that it doesen't fit README nor DEVGUIDE, so it could be useful to have in Keyword Documentation...