Repository navigation
docs: add Scrutinizer coverage badge to README - #129
Merged
Merged
Conversation
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
Adds the Scrutinizer test coverage badge to the README, right next to the existing code quality badge, and records it in the changelog.
Scrutinizer already tracks coverage for
mainand currently reports 95% (badges/coverage.png?b=main), so the badge is live rather than a placeholder.About the local coverage number
go test -cover ./...only credits a package with the tests that live inside it. In this repo most behavior is exercised by the integration suites intest/, so per-package numbers understate the real coverage. To attribute every package correctly:Changes
README.md— add the Scrutinizer Code Coverage badge (links to themainbranch report, matching the quality badge).CHANGELOG.md—[Unreleased]entry.Checks
python3 scripts/check-docs.pypasses (22 Markdown files, 3 runnable Go examples).