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 input and output have incompatible types error is shown in VGX graph when connecting Skinned Mesh Renderer property to Skinned Mesh Renderer node
- [UI Toolkit] Missing documentation about RegisterValueChangedCallback being fired on entering Play Mode for Values using SerializedObject data binding
- [Android] CommandBuffer.DrawProcedural fails to render in the Player with RenderGraph enabled
- Importer gets in an endless loop, or "This default asset was generated because the worker process has crashed during the last import" is present when importing a long audio in the Editor
- Editor performance degrades when PlayableDirector with multiple bindings remains visible in the Inspector during Play mode
Add comment