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
- Crash regression on ComputeShader inspector "Compile and show code" button
- Silent Crash on Windows when opening a project created in Ubuntu
- Profiler mouse and keyboard navigation is inconsistent and skips entries when analyzing Instantiate calls from a unit test
- Unmaximizing Editor Window results in a new window being created and deleted
- Sphere's cloth explodes/rotates and constraints disappear (only one is left) when entering Play mode
Resolution Note (fix version 1.0.11):
Fixed in Test Framework v1.0.11 package.
Backported to 2019.1.2f1