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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment