Search Issue Tracker
Fixed in 2018.1.X
Fixed in 5.6.X
Votes
1
Found in
5.6.1p4
Issue ID
1008883
Regression
No
[TestRunner] command -editorTestsCategories does not work in Unity 5.6
Reproduction steps:
1. Download "Testrunner.zip" project and open command prompt
2. Change path to Unity.exe (version 5.6)
3. Run the command - Unity.exe -runEditorTests -projectPath [PATH_TO_PROJECT] -editorTestsResultFile [PATH_TO_RESULT_FILE]\Report.xml -editorTestsCategories AAA -testPlatform editmode -nographics -batchmode
Expected: in the result file one test with category "AAA" should be passed
Actual: in the result file two tests with categories "AAA" and "BBB" are passed
NOTE:
Category filter was removed in Unity 5.6 and added again in 2017.1 here:
https://ono.unity3d.com/unity/unity/changeset/729302e5858af84da231a7894132742dbec871eb
So this bug is basically a backport request for this feature.
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
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
- Moving a Tab to a floating window fails when floating windows are docked next to each other
DematicTeltov
Aug 14, 2018 12:08
I see this problem is still reproducible in 2018.2.3.12711 (Status: Fixed in Unity 2018.1). I'm not sure but looks like the current problem is duplicate of https://issuetracker.unity3d.com/issues/unitytestrunner-editortestsfilter-and-editortestscategories-command-line-arguments-dont-work-in-batchmode.