Search Issue Tracker
Fixed in 1.1.12
Votes
6
Found in [Package]
1.1.3
Issue ID
1014908
Regression
No
[Test Runner] PlayMode tests not storing results if "Maximize On Play" selected
How to reproduce:
1. Open the "Playmode Tests.zip" project
2. Open the Test Runner
3. Select PlayMode tests
4. Make sure the Game window has "Maximize On Play" checked
5. Run the "Freeze" test
Actual result: After the test is done, the status is not updated and the test runner shows test status as "not run".
Expected result: After the test is done, the status should be updated to "Succeeded" or "Failed".
Reproducible with: 2019.3.0b10, 2018.2.0a6, 2018.1.0b13, 2017.4.1f1, 2017.3.2f1, 2017.2.2p2, 2017.1.3p3.
-
Bunderant
Nov 06, 2019 23:31
I'd like to add that even if the game window isn't set to maximize, the test filter buttons don't reflect the results in the test hierarchy. After running a simple project with a single play mode test in it, when the test succeeds the filters at the top-right of the test runner show 0 succeeded, 0 failed, and 1 not run (even though the only test has a green check next to it in the hierarchy).
I'm running Unity 2019.3.0b8.
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/HDRP/DownsampleDepth'" warnings are thrown after building a project
- Scene is not rendered and appears black when the Custom Renderer Feature is utilized
- The Context Menu is not updated in the Shortcuts menu when resolving a Binding Conflict
- [Quest] Foveation Level is 0 when SRP Foveation is enabled
- Freeze when displaying text with "-T" in Play mode
Resolution Note (fix version 1.1.12):
Fixed in 2020.2.0a5
Resolution Note (fix version 1.1.12):
Fixed in 1.1.13 (tested on Unity 2019.3.8f1)
Resolution Note (fix version 1.1.12):
Fixed in Test Framework 1.1.12