Search Issue Tracker
Won't Fix
Won't Fix in 1.3.X
Votes
2
Found in [Package]
1.1.27
1.3.0
Issue ID
DSTR-320
Regression
No
Test Runner PlayMode tests do not run when EditorSceneManager.PlaymodeStartScene is set to any Scene
Reproduction steps:
1. Open the attached project "PlayMode_Bug.zip"
2. Open Unity Test Runner (Window -> General -> Test Runner)
3. Set test mode to PlayMode
4. Run all tests
5. In the Menu bar, click on "test" -> "SetPlaymodeStartScene"
6. Run all tests
Expected result: PlayMode tests start before and after setting PlaymodeStartScene
Actual result: PlayMode tests do not start after setting PlaymodeStartScene
Reproducible with: 1.1.27 (2019.4.29f1, 2020.3.15f2, 2021.1.16f1, 2021.2.0b6, 2022.1.0a4)
Notes: the issue also reproduces in 1.3.0-pre.3, however it seems to be working as intended in 2.0.1-epx.1
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (1.3.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.