Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Please Add ReportPortal::Cucumber::JUnitFormatter #89

Open
sspieker-cc opened this issue Jun 8, 2020 · 0 comments
Open

Comments

@sspieker-cc
Copy link

Currently the Ruby Cucumber JUnit Output Formatter does not include any STDOUT or STDERR output into the test execution output either at the suites or the test case levels. This may be related to interceptors, other formatters perhaps or even a logger that is swallowing this output before the junit outputter can do any real actions with the messages.

In our production and staging environments we have no access to the central reportportal services. Therefore we have been attempting to use the JUnit output formatter in order to produce files that can be copied and imported into reportportal for consumption. One of the complaints is the missing information surrounding the step execution and the additional information that the Agent-Ruby provides when the information is imported from JUnit output.

It would be absolutely wonderful if the ReportPortal::Cucumber::Formatter could be expanded to include a JUnit output file that would contain all of the information that the tooling can produce in terms of the feature file (test suites), scenario (test suite) and test-case (scenario) into this junit output file. This is the best source of the information as the tooling provides this already, it seems that the enhancement would "just" need to write output to a series of files instead of using the API connections.

This feature request would be greatly beneficial for our very restrictive use case and would be something that others may also benefit from within the CI use cases also.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant