Search Issue Tracker
Fixed in 2017.1.X
Votes
1
Found in
2017.1.0b1
Issue ID
900957
Regression
Yes
[EditorTest] Running a single edit mode test is really slow
To reproduce:
1. Open attached project.
2. Open Test Runner.
3. Select an Edit Mode test : CrossSceneReferenceTests -> CrossSceneReferencesShouldStillBePresentAfterSavingScenes
4. Press "Run Selected"
Expected result: Test runs instantly.
Actual result: Editor freezes on main thread for 2-3 seconds before even starting to run the test.
Note: Only happens when there are a lot of tests. On fresh empty project, slowdown is not visible.
Reproducible on: 2017.1.0b1 (a29fc4a7eb25)
Not reproducible: 5.6.0b9 (e1cc23a55ad8)
Comments (2)
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
- "GetPreferedValue" returns max value when using auto-sizing
- UI Builder doesn't update the style sheet when using "Extract inline style" right-click option
- “Assertion failed on expression” errors thrown when undoing Nodes creation with keyboard shortcut
- Crash on various stack traces when using Texture2D.CreateExternalTexture() while rendering
- Clicking on section text in Node Library > Context folder throws NullReferenceException errors
DrRixxo
Aug 11, 2017 23:51
It doesn't look like it has been fixed. I am using Unity 2017.1.0f3 and it takes about a minute for the test to even run.
CanisLupus
Jul 12, 2017 09:07
This was not fixed for the FINAL release of Unity 2017.1 ?! You have been destroying the tests runner performance version after version and didn't find the means to fix it when it was reported in the FIRST beta version of Unity 2017? Really?