Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2017.1.X, 2017.2.X, 2017.3.X
Won't Fix in 5.6.X
Votes
3
Found in
5.6.1p4
Issue ID
945000
Regression
No
"TestRunner" "PlayMode" test leaves behind "InitTestScene..." scene assets after test runs
Reproduction steps:
1. Create a New Project
2. "Window" -> "Test Runner"
3. "PlayMode"
4. "Enable Playmode tests"
5. Restart Editor
6. "Create Playmode tests with methods"
7. Spam "Run All"
Fixed in: 2018.1.0a7
Expected Result: Spamming isn't allowed and only one test at a time is run, with only one temporary scene created for that one test
Actual Result: Only one test is run, but multiple scenes are created, leaving all untested scenes in the assets folder
Reproduced with: 2017.8.0a1, 2017.3.0b4, 2017.2.0f3, 2017.1.2p1, 5.6.4f1, 5.6.0f3
Did not reproduce on: 5.5.5f1(Play Mode tests were only implemented in 5.6)
Note:
Reproduced on both Windows 10 and mac 10.12.6
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
- The terrain appears darker when "Per-pixel Normal" is enabled
- [Linux] Editor assertion causes Test Runner to fail when executing it in Batch Mode
- Color selection by the mouse cursor is still enabled when the "Esc" button is pressed
- Game view becomes black and the Scene window becomes grey, “ArgumentOutOfRangeException” errors and “Render Pipeline error” warnings appear after changing the name or deleting URP/HDRP global settings file
- Transform Component is not accessible inside the Player when RuntimeInitializeOnLoadMethod is used
chantey
May 20, 2022 05:58
Still getting this in 2021.3.2f1
JacobK
Aug 06, 2021 09:59
Still happening in 2020.3.14f1, Test Framework 1.1.27
g05u
Jun 20, 2021 00:21
Still in Unity 2021.1.11f1
c8theino
Mar 25, 2021 07:38
Still happening in Unity 2019.4.19f1.
Haapavuo
Jan 31, 2021 14:35
Still happens on Unity 2020.1.17f1.
sang
Dec 25, 2020 11:53
This is still present in 2019.4.16. I also see an error message in the console: NullReferenceException: Object reference not set to an instance of an object
UnityEditor.TestTools.TestRunner.PlaymodeLauncher+BackgroundWatcher.OnPlayModeStateChanged. Framework version 1.1.19
jreigota
Dec 11, 2020 16:17
Still happening, very easy to repro:
Create a playmode unit test that OPENS an existing scene (addictively) and when the test finish the InitTestScene is left behind.
RoutineAyhan
Sep 21, 2020 08:08
This happens to me in 2020.1f1 as well. I'm using the SceneManager to open existing scenes to test those with runtime tests, but now I have a bunch of these "InitTestScene" files under the assets folder.
eelstork
Jul 01, 2020 04:08
Seeing this in Unity 2019.3.3f1 - how is this "resolved"?
DrummerB
May 06, 2020 17:40
Still happening. Unity 2019.3.0f6, Test Framework 1.1.14.
It doesn't happen always, but after some time I end up with lots of InitTestScene scenes in my Assets folder.