test(coverage): add coverlet.collector to the 2 Fuzz test projects - #444
Merged
Merged
Conversation
Wolfgang.Etl.Abstractions.Tests.Fuzz and Wolfgang.Etl.TestKit.Tests.Fuzz were silently contributing zero coverage data (no collector referenced, per the #386 fleet survey). Verified locally before adding: both clear the 90% test-assembly coverage gate comfortably (97.8% and 100% respectively), so this carries no CI risk. Part of #386 (unit test project coverage was already at 100% via #402; this closes the "add collector to every suite that should be measured" gap for the two Fuzz suites specifically). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This was referenced Aug 28, 2026
3 of 9 tasks
This was referenced Sep 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Part of #386's fleet-wide coverage-instrumentation gap. Phase 1 (unit test projects at 100% coverage, the parse-fix gate, and release.yaml alignment) already shipped via #402/#386-follow-ups. This closes the gap for the 2 remaining suites that are safe to add without risk:
Wolfgang.Etl.Abstractions.Tests.Fuzz— was silently emitting zero coverage data (nocoverlet.collectorreferenced)Wolfgang.Etl.TestKit.Tests.Fuzz— same gapBoth were tested locally with coverage collection before committing this PR to make sure they wouldn't trip the coverage gate:
Abstractions.Tests.FuzzTestKit.Tests.FuzzBoth comfortably clear the 90%
CODECOV_MINIMUM(neither matches the*.Tests.Unit99% pattern). No CI risk.Not included here (tracked separately):
TestKit.Tests.DocExamplesneeds a small coverage-closing test first (88.8%, would fail the gate as-is), and the two*.Tests.Concurrencysuites are Coyote-CLI-driven rather than part of the standard xunit job, so adding a collector there wouldn't produce coverage data in the normal PR run — that'll be recorded as a deliberate exclusion instead, same asAotSmoke.Test plan
dotnet test --collect:"XPlat Code Coverage" --settings coverlet.runsettingslocallyPart of #386
🤖 Generated with Claude Code