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
- [Android] AssetBundle loading performance degradation when loading from a local Assetbundle
- [iOS][Android] Reflection with Generic Class returns unexpected values
- Shader Variant Collection Asset UI is hard to read when multiple Shaders and keywords are added
- Regression for "WebGL build is missing "malloc" and "free" functions when passing "-sERROR_ON_UNDEFINED_SYMBOLS=0" to emscriptenArgs"
- Resetting Quality Levels in Project Settings adds new Quality Levels instead of restoring default ones
Add comment