Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.3
2019.3.6f1
2020.1
2020.2
Issue ID
1233494
Regression
No
Command line testing in batchmode with legacy -runEditorTests is not equivalent to -runTests -testPlatform EditMode
How to reproduce:
1. Download tester-submitted project (MainProject.zip)
2. Make sure the Library folder is not present in the root project folder
3. Run Unity via Terminal with the following arguments: -runTests -testPlatform EditMode -batchmode -projectPath <path> -logFile <path>
4. Execute 'echo $?' - note that it returns 1; note that test results xml is not generated
5. Remove the Library folder from the project's root folder
6. Run Unity via Terminal with the following arguments: -runEditorTests -batchmode -projectPath <path> -logFile <path>
7. Execute 'echo $?' - note that it returns 0; note that test results xml is generated
Expected result: -runTests -testPlatform EditMode is equivalent to -runEditorTests
Actual result: -runTests -testPlatform EditMode works different from -runEditorTests
Reproducible with: 2019.3.0b9, 2019.3.9f1, 2020.1.0b4, 2020.2.0a5
Could not test with: 2017.4.39f1, 2018.4.20f1, 2019.3.0b8(packages necessary for showcasing the issue incompatible)
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
Issue due to version conflicts between Entities and Data Flow Graph packages. Resolved by using compatible versions.