I think the information will be automatically calculated by Jenkins. If not, do not add it, it will not be displayed in any case.
Here is a good tip on how to debug such things: create a task (let it be called jUnitReport) that "touches" the file (let it be called jUnit.xml) at the shell / batch assembly stage; add "Publish JUnit Retest Report" and specify jUnit.xml in the "Edit XML Test Report Data" field. Running the task once - this will create a workspace. Now put the actual jUnit.xml that you want to test in the workspace. Run the job again and check how the test results look.
It is important not to delete the βtouchβ step, otherwise Jenkins will consider the test results obsolete and not complete the assembly.
Now you can play with jUnit.xml without performing real tests and learn how this affects the results displayed by Jenkins.
malenkiy_scot
source share