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
- Graphics.RenderMeshIndirect does not issue multi-draw rendering commands when using a graphics API capable of multi-draw commands
- Error "InvalidOperationException: An error occured while deserializing asset reference" is thrown when deserializing a BlackboardVariable that is a dynamically loaded monobehavior
- Removing a Camera Component from a Physics 2D Raycaster GameObject brings pop-up message twice
- UnityYAMLMerge does not open fallback merge tool when encountering merge conflicts
- Editor crash when resetting Quality settings after adding "New Group" in Mipmap Limit Groups
Resolution Note:
2018.4/stagining
https://ono.unity3d.com/unity/draft/changeset/28550c6d8436fe378a35ce52b874939df6471480