Repository navigation
docs: describe the coverage the CI enforces, and record the line coverage in the ratchet - #579
Merged
Merged
Conversation
…rage in the ratchet
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.
The README, CONTRIBUTING and CLAUDE.md said the unit tests require 100% coverage. Nothing enforces that: the CI runs
pest --coveragewithout--min, and the line coverage it reports is 53.0% (7127 of 13448 lines onb0cc545). What the CI does enforce is the type coverage, at 98% (composer test:type-coverage)..harness.jsonrecordscoverage: 53in the ratchet, so the Harness fails a change that lowers the line coverage (tolerance 0.05 point). The Harness already measures it: its last run ondevelopreportsLine coverage (%) recorded - measured 53 new..harness.jsonis protected (QA-02): this change was decided by the owner.