Search Issue Tracker
By Design
Votes
0
Found in
5.6.0f1
Issue ID
892798
Regression
Yes
Running editor tests with Batch Mode and -quit does not write results to XML file
Reproduction Steps:
1. Import attached project.
2. Using the command-line (batch mode), run project with any of these arguments:
"C:\Program Files\Unity560\Editor\Unity.exe" -runEditorTests -projectPath "C:\Users\{my_user}\Desktop\TestRunner" -batchmode -quit
"C:\Program Files\Unity560\Editor\Unity.exe" -runEditorTests -projectPath "C:\Users\{my_user}\Desktop\TestRunner" -batchmode -quit -editorTestsResultFile "C:\Users\{my_user}\Desktop\TestRunner\tests.xml"
"C:\Program Files\Unity560\Editor\Unity.exe" -runEditorTests -projectPath "C:\Users\{my_user}\Desktop\TestRunner" -batchmode -quit -editorTestsResultFile "C:\Users\{my_user}\Desktop\TestRunner\tests.xml" -logFile "C:\Users\{my_user}\Desktop\TestRunner\log.txt"
Expected results: Command-line displays editor test results.
Actual results: Command-line seems to ignore commands and doesn't display results. (Image attached)
Reproducible with: 5.6.0f1, 2017.1.0a4
Not reproducible with: 5.4.5f1, 5.5.2p3
Regression introduced in: 5.6.0b2
Comments (1)
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
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
AndyJenkins30
Aug 03, 2017 08:41
Just thought I would mention here, '-quit' doesn't work nicely with test runner in the command line. If you'd like to set up an automated test run via command line, you should use '-batchmode' instead to close Unity after the test run has complete.
Unity.exe -batchmode -projectPath PATH_TO_PROJECT -runEditorTests -editorTestsResultFile .\testresults.xml