Search Issue Tracker
Fixed in 1.0.11
Votes
0
Found in [Package]
0.0.0
Issue ID
1142553
Regression
Yes
[TestRunner] TearDown and UnityTearDown get called on base class first
Steps to reproduce:
1. Open attached project
2. Open test runner and run test
Actual behaviour: Notice that Parent TearDown is printed before Child TearDown . This means that TearDown attribute in base class got executed first
Expected behaviour: TearDown in base class is executed after TearDown in derived class
Reproduced with: 2018.3.12, 2019.1.0b8, 2019.2.0a7
Not reproducible: 2018.3.11, 2019.1.0b7, 2019.2.0a6
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
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- Crash on EnumerateDisabledKeywordsInVariantsArray or UNITY_XXH32 when rapidly saving ShaderGraph or VFXGraph changes
Resolution Note (fix version 1.0.11):
Fixed in Test Framework v1.0.11 package.
Backported to 2019.1.2f1