Search Issue Tracker
Fixed in 1.0.1
Votes
0
Found in [Package]
1.0.0
Issue ID
1338665
Regression
No
[Code Coverage] Get and Set accessors are still marked as coverable when property has ExcludeFromCodeCoverage attribute
Steps to reproduce:
1. Create new project
2. Import code coverage package
3. Create new script and create a property:
[ExcludeFromCodeCoverage]
public int number { get { return 1; } }
4. Start and stop recording
5. Inspect script in generated report
Actual result: get accessor is shown as coverable
Expected result: get accessor is skipped when calculating coverage results
Workaround: Apply ExcludeFromCoverage attribute directly on the accessor
Reproduced: 1.0.0
Editor: 2019.4.21f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Add comment