Search Issue Tracker
Won't Fix
Votes
1
Found in [Package]
1.4.2
1.4.3
Issue ID
DSTR-1022
Regression
No
Inconsistency between Exported Results and Test Runner Window when using Unity Test Framework
Reproduction steps:
1. Open the attached “TaskTestsInternalException.zip” project
2. Open the “Test Runner” Window (Window > General > Test Runner)
3. Select “NonYieldingTaskTestsFailedInXmlReport (2 tests)”
4. Click “Run Selected”
5. Observe the green checkboxes next to the tests
6. Click “Export Results” and save them
7. Open the results and observe the messages
Expected result: Test Runner GUI results match the export results, no failure messages are shown
Actual result: Failure message is visible in the Exported Results
Reproducible with: 1.4.2 (2021.3.35f1, 2022.3.19f1, 2023.2.10f1, 2023.3.0b7), 1.4.3 (2021.3.35f1, 2022.3.19f1, 2023.2.10f1, 2023.3.0b7)
Reproducible on: Windows 11
Not reproducible on: no other environment tested
Notes:
- A possible workaround is to yield at least one frame/update at the start of every async test or use other async mechanisms e.g. IEnumerator
- Full failure message in the exported results: “<failure><message><![CDATA[System.InvalidOperationException : EditMode test can only yield null]]></message><stack-trace><![CDATA[]]></stack-trace></failure>”
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
There are no fixes planned for this Bug