Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.1.13
Issue ID
1229942
Regression
No
[Unity Test Framework] UnityTearDown is skipped when a test fails during the UnitySetUp
How to reproduce:
1. Open attached project "TestTimeoutIssue.zip"
2. Open Test Runner window and PlayMode tab
3. In Test Runner, run "SetupFail" test
4. Observe the Console window
Expected result: the test is not successful, Teardown and UnityTearDown is run
Actual result: the test is not successful, Teardown does not run
Reproducible with: 2018.4.20f1, 2019.3.6f1, 2020.1.0b3, 2020.2.0a3 (1.1.11, 1.1.13)
Could not test with: 2017.4 (test runner missing features, errors in the console window)
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note:
In the attached project an exception is thrown from UnitySetup and respectively Setup is never being called. Thus TearDown doesn't need to be called either. When an exception is thrown from a Setup method, then all the necessary TearDowns are being called in expected order.