Search Issue Tracker
By Design
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.3.0b12
2019.1.0b4
2019.3.0a6
Issue ID
1109130
Regression
No
Test Runner's results change after first Test run when using Singleton
To reproduce:
1. Open attached project ("SingletonInstancesTest")
2. In Test Runner window click "Run All"
- Tests return positive
3. Run Tests again
- Tests return negative
Expected: Results are the same after every run
Actual: Results change to negative after first run
Reproduced with: 2017.4.20f2, 2018.3.6f1, 2019.1.0b4, 2019.2.0a6
Note:
- Issue occurs only when tests are run EditMode
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
- [2D] Texture 2D Array preview looks corrupted when Mip Map Filtering is set to Box at different Mip levels
- [HDRP][XR] Shadergraph tessellation work differently with XR
- Not uploading texture to the 3D API / GPU during importing has regressed StreamingTests.TextureLoad test in performance
- [Physics] The capsule jitters falling into the cracks between triangle edges
- ArgumentOutOfRangeException is thrown when right-clicking certain Hierarchy window items during Play Mode exit process
Resolution Note:
The test is working as intended.
The singleton is being reinitialized whenever it is not present in its static variable, which will only happen after a domain reload. When running an editmode test, no domain reload will happen, unless needed. Thus the singleton from the previous run still exists.
A recommend solution could be to do a TearDown in the test, which destroys the singleton, as cleanup.