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
Comments (1)
-
lucas_fortis
Feb 12, 2026 21:39
The API for this is clearly broken.
It's an easy fix that the community already solved.
it would probably take 1-dev-day to add it.
Fix this.
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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
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.