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.
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
- Referred style sheet stays dirty after saving when using the UIBuilder
- The Height map Amplitude is not working when using HDRP/LayeredLit
- Crash on internalABP::BoxManager::prepareData when entering Play Mode
- Crash at "UnityEngine.Object:FindObjectsOfType" when quitting the Player
- Creating material variant produces errors if there is no Materials folder
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.