Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.2.X, 2018.3.X
Votes
0
Found in
2018.2.6f1
Issue ID
1077871
Regression
No
[TestRunner] Tests are not torn down properly when they fail due to logging an Error
To reproduce:
1. Download attached project "TearDownRepro.zip" and open in Unity
2. Open "SampleScene" scene
3. Open Test Runner window
4. In Test Runner window press "PlayMode" button
5. Run TestFail or UnityTestFail
6. Notice that the TearDown and UnityTearDown methods are called (logged to a Console)
7. Run UnityTestError
8. Notice that the TearDown and UnityTearDown methods are not called
Notes:
- This issue appears on both Windows and OSX
Reproduced on Unity 2018.2.0a3, 2018.2.6f1, 2018.2.7f1 and 2018.3.0b1
Could not reproduce on Unity 2017.4 and 2018.1 because scripts becomes corrupted
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Multiple errors occur when setting the Render Object Event to AfterRenderingPostProcessing while using STP for Upscaling
- UnityYamlMerge.exe doesn't correctly handle merge conflicts in modified properties on a prefab variant
- Inconsistent color scheme in "Details" section of "Select Presets" inspector window
- Crash on __pthread_kill when launching Editor via command-line with "-disableManagedDebugger" argument
- [VFX] Deleting “New Group Node” name doesn’t allow to type or add new name
Add comment