Search Issue Tracker
Fixed in 2017.2.0f3
Fixed in 5.6.X, 2017.1.X, 2017.2.X
Votes
15
Found in
5.6.0p4
Issue ID
910845
Regression
No
The XML report generated by the editor tests runner is missing the required "test-run" root element
Steps to reproduce:
1. Download the attached project
2. Run the tests through a command line
3. Unity.exe -projectPath PATH_TO_PROJECT -runEditorTests -editorTestsResultFile .\testresults.xml
4. Open testresults.xml
Expected result: <test-run> element is present
Actual result: <test-run> element is missing
Reproduced on 5.6.0p4, 5.6.1f1, 2017.1.0b4
Unable to run testes headless on earlier versions
Verified FIXED 2018.1.0b3
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Warning 'Unable to find player assmebly' is thrown when building some Project Templates
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
fltech
Sep 08, 2017 07:31
Duplicated with https://issuetracker.unity3d.com/issues/running-unity-in-batchmode-gives-a-result-file-with-the-wrong-test-type
fltech
Sep 07, 2017 14:34
Also reproduced in 2017.1.0f3
LavapotionNiklas
Aug 16, 2017 15:12
Also a problem in 5.6.3f1
Toadwolf
Jul 11, 2017 09:41
Also reproduced in 5.6.2p1.