-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
Using 2.3.2 xunit plugin, Jenkins ver. 2.165 on a AWS Centos box.
-
-
2.3.3
When running Unity3d tests in playmode and generating results xml file e.g(https://pastebin.com/BfhaJj0M) we get the message that all the reports are empty. Is there anything else xunit needs to actually parse these results? Do you see any problem with the resulting xml file?
Worth noting that reports generated using editmore are being read properly by the plugin.
- is related to
-
-
- Resolved
-
[JENKINS-56271] xUnit produce an empty report for NUnit3 type
Slavko Fodor
added a comment - Apologies. Unity3d exports the xml test result (Nunit 3). The sample is at this [paste|https://pastebin.com/BfhaJj0M.] I choose Nunit3 for the xunit.
Everything I see in the log after Unity completes the tests is:
INFO: Starting to record.
INFO: Processing NUnit-3 (default)
INFO: [NUnit-3 (default)] - 1 test report file(s) were found with the pattern '**/UnityUiResults.xml' relative to '/var/lib/jenkins/workspace/Unity UI tests' for the testing framework 'NUnit-3 (default)'.
WARNING: All test reports are empty.
INFO: Check 'Failed Tests' threshold.
INFO: Check 'Skipped Tests' threshold.
INFO: Setting the build status to SUCCESS
INFO: Stopping recording.
Finished: SUCCESS
As far as I can tell, there is nothing wrong with that xml and it looks like the others we produce.
Slavko Fodor
added a comment - Apologies. Unity3d exports the xml test result (Nunit 3). The sample is at this [paste| https://pastebin.com/BfhaJj0M .] I choose Nunit3 for the xunit.
Everything I see in the log after Unity completes the tests is:
INFO: Starting to record.
INFO: Processing NUnit-3 (default)
INFO: [NUnit-3 (default)] - 1 test report file(s) were found with the pattern '**/UnityUiResults.xml' relative to '/var/lib/jenkins/workspace/Unity UI tests' for the testing framework 'NUnit-3 (default)'.
WARNING: All test reports are empty.
INFO: Check 'Failed Tests' threshold.
INFO: Check 'Skipped Tests' threshold.
INFO: Setting the build status to SUCCESS
INFO: Stopping recording.
Finished: SUCCESS
As far as I can tell, there is nothing wrong with that xml and it looks like the others we produce. nfalco I think there's a small mistake, the fix is actually in version 2.3.2 according to the commits and not 2.3.2, right?
Could you explain better? Which kind of test report do you generate? Whick kind type did you choose for the xunit plugin. Which is the plugin configuration? Do you have any log?