-
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
-
JENKINS-55907 NUnit3 fails when SetUpFixture feature is used
-
- Resolved
-
[JENKINS-56271] xUnit produce an empty report for NUnit3 type
Environment |
Original:
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. Using 2.3.2 xunit plugin, Jenkins ver. 2.165 on a AWS Centos box. |
New:
Using 2.3.2 xunit plugin, Jenkins ver. 2.165 on a AWS Centos box. |
Description |
New:
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. |
Summary | Original: WARNING: All test reports are empty. | New: xUnit produce an empty report for NUnit3 type |
Link |
New:
This issue is related to |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Released As | New: 2.3.2 |
Released As | Original: 2.3.2 | New: 2.3.3 |