Search Issue Tracker
Fixed in 2018.2.X
Votes
1
Found in
2017.3.1p1
Issue ID
1006488
Regression
Yes
[UnityTestRunner] NUnit tests in a DLL stored under an Editor folder are run when -testPlatform is set to 'playmode' (batchmode)
How to reproduce:
1. Open up the terminal (or command line for Windows).
2. Run the command <Path_To_Unity> -batchmode -projectPath <Path_To_Project> -runTests -buildTarget OSX -testPlatform playmode
3. Observe the results in the root directory of the project (TestResults-XXXXX.xml)
Expected Result: Only playmode tests PlaymodePass & RangeTest are run.
Actual Result: DLL tests built with NUnit are run (ExternalNUnit.Tests.Test1 / ExternalNUnit.Tests.Test2 ).
Regression first introduced in - Unity 2017.2
Reproducable with - 2017.3.1p1
Not reproducable with - 2017.1.0f3
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
Add comment