Search Issue Tracker
Active
Votes
0
Found in
1.0.0
1.1.1
Issue ID
UUM-140580
Regression
No
Coverage does not cover some lines when executed code path throws an exception
Reproduction steps:
1. Open user attached Project
2. Open Window > General > Test Runner
3. Run All Playmode tests
4. Open Window > Analysis > Code Coverage
5. Generate From Last
6. Open Tests_TestATest.html
Actual result: Line 17 and 34 are marked as uncovered. Line 25 is marked as uncoverable
Note: This is an expected behaviour. Since method throws an exception, it exists out early and curly brackets at the end will show up as not covered. A more detailed explanation will be added to code coverage docs.
Reproducible with: preview-0.3.1, preview-0.4.3 (2019.4.24f1, 2020.3.5f1) 1.0.0 (2019.4.24f1, 2020.3.5f1, 2021.1.3f1, 2021.2.0a14)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Attempting to use an invalid operation handle" error is thrown when stopping Play Mode after loading an Addressable scene using LoadSceneAsync
- Arabic separator character (066B) is treated as a full-width character when Duospacing is enabled on a TMP text component
- Crash on CheckDeviceStatus when converting materials from built-in to URP and using DX12
- Alt+click on List header does not recursively toggle child foldouts when items use a UI Toolkit CustomPropertyDrawer
- Artifacts are rendered in UITK when using Font Assets and using negative outlines
Add comment