Search Issue Tracker
Won't Fix
Won't Fix in 2.0.X
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 UndoManager::RegisterUndoInternal when applying added GameObjects to a Prefab
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
- Icon section shows incomplete message and unusable check box in Build Profiles and Player Settings window instead of “Not applicable for this platform” for Dedicated Server Platform
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
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.
Resolution Note (2.0.X):
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.