Search Issue Tracker
Active
Under Consideration for 6000.2.X
Votes
0
Found in
2022.3.59f1
6000.0.41f1
6000.1.0b9
6000.2.0a6
Issue ID
UUM-99631
Regression
No
Test Failure Error is lost when test performs subsequent successful test
Steps to reproduce:
1. Open the attached “ExitPlayModeDoesNotThrow.zip” project
2. Open Window → General → “Test Runner”
3. In the Test Runner Window click “Run All”
4. Observe the test results
Expected result: “TestResult_IsLost_IfSuccessfullyEnteredPlayMode_SubsequentToFailedExitPlayMode” test fails after the first error
Actual result: “TestResult_IsLost_IfSuccessfullyEnteredPlayMode_SubsequentToFailedExitPlayMode” passes the tests
Reproducible in: 2022.2.0a17, 2022.3.59f1, 6000.0.41f1, 6000.1.0b9, 6000.2.0a6
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Long Property names are not truncated in the Add Property dropdown in the Animation window when the Long Property name does not fit
- [iOS] High CPU load when device keyboard is open
- Selected Animation clip in the Animation window changes when the Domain Reload is triggered
- Animation window scrollbar keeps resetting when the scrollbar width is changed after adding an event
- LocalizationSettings.InitializationOperation hangs when re-entering Play Mode with Domain Reload disabled
Add comment