test(fragment-check): protect optional coverage remedy #1161
No reviewers
Labels
No labels
bump
major
bump
minor
bump
patch
kind/bug
kind/chore
kind/docs
kind/feature
priority/critical
priority/high
priority/low
priority/medium
size/L
size/M
size/S
size/XL
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
frankenbit/release-toolkit!1161
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "i/1145-fragment-coverage-remedy"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Refs #1145
Related: #1098 (the original optional-coverage behavior landed on main in
05605428).Change
The real-binary optional coverage control now asserts the complete skip disclosure exactly once, including the actionable remedy to set FRAGMENT_CHECK_COVERAGE=required in a PR workflow. Removing only that remedy is a mutation that the same control rejects. The existing required positive and forgotten-fragment controls are unchanged.
Verification
go test ./... -count=1go vet ./...andgo build ./...bats tests/(152/152)find scripts -type f ( -name "*.sh" -o -name "*.bash" ) -print0 | xargs -0 shellcheck --severity=warningReviewed exact head
670ea703ed(base226cc806de). APPROVED. The workflow now executes the real binary in optional coverage mode and requires exactly one full skip-disclosure line, including the actionable FRAGMENT_CHECK_COVERAGE=required remedy; removing only that remedy makes the control fail. I reproduced the control and mutation, and ran Bats 152/152, go test -count=1 ./..., go vet ./..., go build, ShellCheck, YAML parse, and diff-check successfully. The added #1145 fragment is valid. Server CI is terminal 27/27 success.