Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.5.0b9
Issue ID
847165
Regression
No
Exceptions are not treated as a test failure when they occur in the TestCaseAttribute
Steps to reproduce:
1. Open the attached project (New Unity Project.zip)
2 Open the test.unity scene
3. Open Editor Tests Runner
4. Click 'Run All'
5. Unit test throws an OverflowException(in the TestCaseAttribute()). OverflowException does not treated as a test failure
Expected result: OverflowException should be treated as a test failure
Actual result: OverflowException does not treated as a test failure
Reproduced with: 5.3.6p4, 5.4.2p3, 5.5.0b9, 5.5.0b11
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
Add comment