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
- Crash on ScriptableBatchRenderer::GenerateBuiltInCBuffer when opening a project after adding HDRP Samples to a specific project
- ArgumentException is thrown and reference is missing when deserializing and using MultiColumnListView
- “You may not pass in objects that are already persistent” error is thrown when entering the Play Mode and the "Active Input Handling" system was changed in a custom Build Profile
- [Linux] Assertion failed on expression 'success && actual == size' error is thrown when building project to another partition with a different file system
- Import Activity window shows "(None)" in the Asset field when changing the path of the asset
Resolution Note:
2018.4/stagining
https://ono.unity3d.com/unity/draft/changeset/28550c6d8436fe378a35ce52b874939df6471480