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
- The previous element in the array is modified when assigning an Asset to a new element of AssetReferenceT
- Unity Perforce Integration: VCS Connection Active State Fails via CLI with Valid Inputs
- Joint Gizmos for anchor and connectedAnchor do not respect their defined bodies when Swap Bodies is enabled
- Project Settings window opens up with a blank details pane when the "Configure" button is clicked in the Package Manager after installing the Cloud Diagnostics package
- [UI Builder] Viewport's gizmos for Margin and Padding disappear when dragging to modify the value and the cursor leaves the Spacing section
Add comment