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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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.