Search Issue Tracker
Fixed
Fixed in 1.1.32
Votes
0
Found in [Package]
1.1.0
Issue ID
DSTR-20
Regression
No
[2018.4] Exception in UnitySetUp is not thrown because of exceptions thrown in UnityTearDown
How to reproduce:
1. Open the attached project
2. Open the test runner and run the tests
3. Look at the tests in the group named "DoesntWork"
4. Note that there is only one exception message
5. If you look at the code inside DoesntWork.cs, the exception inside the UnitySetUp method is not reported
6. Comment out the exception inside the UnityTearDown method and run the tests again
7. The exception inside the UnitySetUp method is now correctly reported
Actual result: Exception in UnitySetUp is not thrown.
Expected result: Exception in UnitySetUp is thrown.
Reproducible with: 2018.4.11f1, 2019.1.14f1.
Not reproducible with: 2019.2.0a1, 2019.2.8f1, 2019.3.0b6, 2020.1.0a8.
Notes:
- The UnitySetUp and UnityTearDown IEnumerators are not implemented in 2017.4
------------------------
Fixed in 2019.2.0a1.
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
- The Editor crashes when Generating Font Atlas in the Font Asset Creator with “9999999999” padding and 256x256 Atlas Resolution
- [iOS] An “ArgumentNullException” error is thrown when GetIntroductoryPriceDictionary() method is called
- Memory leak warnings are constantly thrown when Generating Font Atlas in Font Asset Creator with 4096x8192 Atlas Resolution
- “Glyph rendering has been aborted due to sampling point size” Log is printed and Font Atlas is not generated when Atlas Resolution is 8192x8192, and the Render Mode is SDF
- Font Import Settings documentation page is missing when the documentation button is pressed in the Inspector window
Resolution Note:
2018.4/stagining
https://ono.unity3d.com/unity/draft/changeset/28550c6d8436fe378a35ce52b874939df6471480