reportportal
Feature Request: Please Add ReportPortal::Cucumber::JUnitFormatter
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.
