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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
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.