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
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- TextMeshPro Text Component reads bottom-to-top instead of top-to-bottom when using RTL Editor
Add comment