You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 18, 2019. It is now read-only.
We use WDIO in combination with wdio-junit-reporter to get test reports parsed in Jenkins.
The issue is that even if all jUnit XML files are correctly produced by the reporter, Jenkins sometimes misses reporting part of the test suites and cases results.
Example, we have 8 tests being executed, for each build we always have all the jUnit xml files reporting all 8 tests but Jenkins will only report between 5 to 8, producing inconsistency and making us impossible to rely on the report.
Investigation showed that adding "package" attribute to the testsuite tag fixes the issue.
We use WDIO in combination with wdio-junit-reporter to get test reports parsed in Jenkins.
The issue is that even if all jUnit XML files are correctly produced by the reporter, Jenkins sometimes misses reporting part of the test suites and cases results.
Example, we have 8 tests being executed, for each build we always have all the jUnit xml files reporting all 8 tests but Jenkins will only report between 5 to 8, producing inconsistency and making us impossible to rely on the report.
Investigation showed that adding "package" attribute to the testsuite tag fixes the issue.
Based on https://github.com/jenkinsci/xunit-plugin/blob/master/src/main/resources/org/jenkinsci/plugins/xunit/types/model/xsd/junit-10.xsd#L112, this attribute is optional.
Is it possible to add a configuration parameter to specify this attribute?
The text was updated successfully, but these errors were encountered: