Search Issue Tracker
By Design
Votes
0
Found in
2018.1.0b4
Issue ID
992231
Regression
No
LogAssert.Expect doesn't catch exceptions if not called from Debug.LogException
Steps to reproduce:
1. Open user attached project
2. Open "NewTestScript" from the "PlayModeTests" or "EditModeTests" folder
3. Notice that there 6 unit tests in the script
4. Open Test Runner and run all "PlayMode" or "EditMode" tests
5. Notice that the 3 bottom tests cause a fail
Expected result: LogAssert.Expect should catch exceptions if not called from Debug.LogException
Reproduced in: 2018.2.0a1, 2018.1.0b4, 2017.3.0p4, 2017.2.1p2, 2017.1.3f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Toolkit throws warning and fails to clear references when fields are not typed as UnityEngine.Object
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
Add comment