Search Issue Tracker
Duplicate
Votes
0
Found in
2018.2.6f1
Issue ID
1077008
Regression
No
[UnityTest] Playmode tests create a new testing thread when testing array with size of SceneManager.sceneCountInBuildSettings
How to reproduce:
1. Download project from the link to the cloud and open it
2. Open Test Runner (Windows -> General -> Test Runner)
3. Select "PlayMode" inside of Test Runner
4. Click "Run All"
Expected result: testing will be done in order by one thread
Actual result: after testing FullScenePerformanceTest(0) testing not only continuous to go in order but new thread at the beginning will start to test all over again
Notes:
- It is hard to notice with the stripped project, for more obvious example download user's attached project
- when the first thread reaches the end testing stops, no matter where the other threads were at that moment
- to disable infinite loop comment out CharacterweaponTests.cs files line 17 "[Repeat(10)]" it prevents testing thread reaching the end
- when new thread start you receive an error: NullReferenceException: Object reference not set to an instance of an object
Reproducible with: 2018.2.7f1, 2018.3.0b1
Could not reproduce with: 2018.1.9f2 (test runner didn't recognize scene array), 2017.4.9f2 (package manager error)
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
This is a duplicate of issue #1078243