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
- Icon section shows incomplete message and unusable check box in Build Profiles and Player Settings window instead of “Not applicable for this platform” for Dedicated Server Platform
- "Editor unavailable" message is displayed when navigating to "Get set up" tab in Unity Hub
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
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.