Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.3.1
2.0.1-pre.18
Issue ID
DSTR-707
Regression
No
Test runner fails the second test when testing identical tests that contain the ExitPlayMode method
Reproduction steps:
- Open the attached project “TestRunnerBug”
- Open the Test Runner (General > Test Runner)
- Click the button “EditMode”
- Press the button “Run All”
Expected result: All tests pass
Actual result: The second test fails despite being identical to the first one
Reproducible with: 1.3.1 (2020.3.42f1, 2021.3.14f1, 2022.1.23f1, 2022.2.0f1, 2023.1.0a20), 2.0.1-pre.18, 2.0.1-exp.2 (2020.3.42f1, 2021.3.14f1, 2022.1.23f1, 2022.2.0f1)
Reproducible on: Windows 11
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.