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
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
- Entities Hierarchy window allows Cyclic nesting and throws an “ArgumentException: Cyclic nesting detected” error when dragging a Prefab onto the same Prefab in the Entities Hierarchy
- EnterPlayModeOptions doesn't take effect if user manually modifies m_EnterPlayModeOptionsEnabled to 0
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.