Search Issue Tracker
Fixed
Fixed in 1.4.6, 1.5.1
Votes
1
Found in [Package]
1.4.5
1.5.1
Issue ID
DSTR-1065
Regression
No
System.InvalidOperationException is generated in exported XML when running asynchronous tests in Edit mode
How to reproduce:
1. Open the attached “IN-86059” project
2. Open the Test Runner window (Window → General → Test Runner)
3. Ensure the “EditMode” tab is selected
4. Select “Run All”
5. Select “Export Results”
6. Open the generated XML file and observe the results
Expected result: The test results show no errors
Actual result: The test results contain a “System.InvalidOperationException : EditMode test can only yield null" error
Reproducible in: 1.4.5 (2021.3.44f1, 2022.3.50f1, 6000.0.23f1)
Not reproducible in: 2.0.1-pre.18 (2021.3.44f1, 2022.3.50f1)
Fixed in: 2.0.1-exp.1 (2021.3.44f1, 2022.3.50f1)
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environments tested
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
- HDRP 6-way VFX Shader is lit incorrectly when World coordinates are used
- 2D Sprite Renderer in front is affected by Sprites in the background when using Sorting Layers and a Shadow Caster 2D with Self Shadow
- Modifying UI Prefab child's Height only confirms the first 1 or 2 digits when the Scene is newly opened or the Prefab is newly created
- ProfilingSampler.Get() returns null and makes the Player only render black when building a Release Build
- Search text field visual controls for the Path binding in an Input Actions Asset is misaligned
Resolution Note (fix version 1.5.1):
Async Editmode tests are no longer throwing errors when yielding something different than null, as it's allowed to yield different values in async tests.
Resolution Note (fix version 1.4.6):
Async Editmode tests are no longer throwing errors when yielding something different than null, as it's allowed to yield different values in async tests.