Search Issue Tracker
Third Party Issue
Votes
0
Found in
2020.3.39f1
2021.3.10f1
2022.1.17f1
2022.2.0b8
2023.1.0a10
Issue ID
UUM-14469
Regression
No
Test Framework Assert.Inconclusive does not work when used in Async Methods
How to reproduce:
1. Open the user-attached project “AssertInconclusiveTest”
2. Open Window → General → Test Runner
3. In the Test Runner Window click “Run All”
4. Observe the results
Expected results: All tests are Inconclusive
Actual result: The tests that are used in the Async Methods are returning either failed or succeeded result
Reproduced with: 2020.3.39f1, 2021.3.10f1, 2022.1.17f1, 2022.2.0b8, 2023.1.0a10
Reproduced on: Windows 11 Pro
Note: In Unity versions 2023.1.0a5-2023.1.0a10 running the tests causes Unity to freeze completely
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note:
Exceptions thrown within a task is invisible from the Unit test actually, and if you try to rethrow it using Task.Result or Task.Wait, it will be wrapped in an AggregatedException.
However once the task has run to completion, you can rethrow it's original exception using task.GetAwaiter().GetResults() (this is how async await propagate exceptions)