Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.1.16
Issue ID
DSTR-5
Regression
No
[Test Runner] Execution status stays at 'Running' after Tests have finished if domain reload is disabled
How to reproduce:
1. Open user-submitted project (TestRunnerStatusIssue.zip)
2. Open the SampleScene
3. Enter Play Mode - see that a 'Null' execution status is printed in the Console
4. Open Edit > Project Settings > Editor and enable 'Enter Play Mode Options' with 'Reload Domain' disabled
5. Open the Test Runner window and run all Edit Mode tests
6. After the tests have finished, enter Play Mode again
Expected result: a 'Null' execution status is printed in the Console window
Actual result: a 'Running' execution status is printed in the Console window
Reproducible with: 2019.3.0a2, 2019.4.9f1, 2020.1.3f1, 2020.2.0a21(Test Framework preview - 0.0.29, 1.1.16)
Could not test with: 2018.4.26f1, 2019.3.0a1(Enter Play Mode Settings not yet implemented)
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
- WebGL Player with WebGPU Graphics API fails to render Scene when custom Render Feature is used
- “EndLayoutGroup” error thrown when changing Shader Precision Model settings in Build Profiles window > Player Settings Overrides
- Button hover state uses default theme color when a custom .uss is applied
- Samples Showcase script warning does not clear after enabling required settings until GameObject is reselected
- VFX Particles receive shadow artifacts when using ShaderGraph with enabled shadows and Face Camera Plane Orient mode
Resolution Note:
I could not reproduce with Unity test framework 1.1.16 or 1.1.33 in unity version 2022.2.0a12