Search Issue Tracker
Fixed in 2018.1.X
Votes
10
Found in
5.6.0f3
Issue ID
913030
Regression
Yes
Severe performance regression in "Test Runner" (5.6.x compared to 5.5.x)
Repro steps:
1. Open provided project in 5.6.x
2. Click on "Window" -> "Test Runner" ("Editor Tests Runner" for 5.5.x)
3. Click on "Run All" and measure the time it takes for the tests to finish
4. Repeat for 5.5.x
Expected result: The speed at which the tests run should be approximately the same for both of the versions
Actual result: In 5.6.x the speed at which the tests are run is significantly slower than in 5.5.x
Fixed in: 2018.1.0b1
Reproduced with: 5.6.1p1. 2017.1.0b6, 2017.2.0a1
Did not reproduce on: 5.5.3p4
Note:
All of the tests are like this: "[Test] public void Test001() { Assert.IsTrue(true); }"
In version 2017.x it's even slower
Added videos of all 3 major versions
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
srivello
Sep 05, 2017 11:59
I experienced the same problems with the same versions above. 2017.1.0b6 was unusable due to this issue.
However, in 2017.1.0p5 the issue is no longer present. At least in my example (100+ tests), it performs similar to 5.5.x. Not the same (likely because tests are each run in isolated scenes in > 5.5.x) and the results are acceptable and don't warrant a bug from my perspective.