Search Issue Tracker
Won't Fix
Won't Fix in 1.4.X
Votes
0
Found in [Package]
1.4.3
Issue ID
DSTR-1031
Regression
No
The Game view appears empty after executing an Asynchronous Test Method
Reproduction steps:
1. Open the attached “Chicken.zip” project
2. Open the “Game” Scene
3. Open the “Test Runner” Window (Window > General > Test Runner)
4. Select “PlayMode”
5. Click on “Run All” and wait for the tests to complete
6. Enter the Play mode
7. Observe the Game view
Expected result: The Scene is visible in the Game view
Actual result: The Game view appears empty after running the tests
Reproducible with: 1.4.3 (2022.3.20f1, 2023.2.10f1)
Fixed in: 2.0.1-exp.1 (2022.3.20f1, 2023.2.10f1)
Couldn’t test with: 1.4.3 (2021.3.35f1, 2023.3.0b7), 2.0.1-exp.1 (2021.3.35f1, 2023.3.0b7) (Unfixable errors associated with 3rd party packages)
Reproducible on: Windows 11, macOS 14.3.1 (M2) (User reported)
Not reproducible on: no other environment tested
Comments (1)
-
Yuki0715
Mar 25, 2024 05:54
Thank you for your investigation.
I have one question.
According to https://forum.unity.com/threads/unity-test-framework-2-0-ready-for-feedback.1230126/page-3#post-9531214, v2 will not be updated in the future and will be backported.
Will this bug be fixed in v1.x by backporting?
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (1.4.X):
Fixed in: 2.0.1-exp.1