Repository navigation
test(deploy_keys): drop the cases the contract tests and scenarios already pin - #392
Merged
Merged
Conversation
…ready pin Two cases and one table row leave the section suite. The two-live-keys-under-one-title case is a twin of the duplicate-live suite's deploy_keys row and of its sibling ordering case, which fail first under the same source change. The duplicate-title validate row restates the generic list-section identity wiring that the validate-hook and list-section suites pin; the material row stays as a plain test. The read-port shape case's one runtime assertion is the port's key list, which test/sections/setup-section.test.ts pins generically; its compile-time pins move to the canonical case in test/sections.
Contributor
File size check0 over a hard cap (fails), 31 warning(s).
Split the file, wrap the line, shorten or exempt the comment, or list the path in 5 managed file(s) skipped; repo-platform owns them. |
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
The removed cases are adequately covered by shared contract tests and the remaining section-specific tests.
Review effort: Balanced
Findings: None
What changed in this PR
Removes redundant deploy-key tests now covered by shared contract suites.
Changes:
- Removes duplicate declaration and live-identity cases.
- Simplifies the remaining material-conflict test.
- Removes redundant read-port assertions.
| File | Description |
|---|---|
src/sections/deploy_keys/deploy_keys.test.ts |
Deduplicates deploy-key tests while retaining section-specific coverage. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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.
Before / After
src/sections/deploy_keys/deploy_keys.test.tsThe count is
test(andtest.each(lines: two cases leave, and the two-row validation table becomes one plain test.How
Two deletions are censused by a mutant of the shared source that reddened the deleted case and its named twins in one
bun testrun, with the source restored afterwards.One deletion is a shape case whose compile-time pins move to the canonical case in
test/sections.Twins: the deploy_keys row of
test/sections/duplicate-live.test.ts(two live "ci" titles) and the sibling "the guard runs before the section's live conflicts", which asserts the same refusal and empty mutations.Mutant:
src/sections/contract/live.ts, thecollisions.length > 0guard inliveByIdentitybecomesfalse; the deleted case, the sibling, and every duplicate-live row red, 65 pass.It restates the identity wiring every
listSection(src/sections/shared/list-section.ts) gets fromduplicateIssuesinsrc/sections/contract/module.ts.That wiring is pinned by
test/sections/list-section.test.tsand eighteen rows oftest/sections/validate-hook.test.ts.Mutant:
module.ts,duplicateIssuesnever records a second sighting; the deleted row and those generic pins red together, 80 pass.Its one runtime assertion is the port's key list, which
test/sections/setup-section.test.tspins generically and sibling suites pin for their own ports.Control: flipping the list's
notFoundposture insrc/sections/deploy_keys/index.tsleft this file green (57 pass);tscand the posture assertion intest/sections/registry.test.tsrefuse it.Proof
bun test src/sections/deploy_keys54 pass (13 counted cases plus seven typedtest.each<...>tables the count regex skips).The full
bun testis 4225 pass, 0 fail.bun run check(lint, arch lint, compat, typecheck, build:check) green;bun run knipgreen.bun run test:e2e --sections deploy_keys6/6 passed.Kept
conflicts.declaredhook.The validate-hook row for
deploy_keyscannot separate it from the title duplicate because its doubled entry repeats both.They pin the public-key and stored-key parses, the private-key refusal at parse, the live-holder conflict table, the ordering guard, and the loud live extraction.
They also pin the reconcile shapes with the read_only table, the phantom-key note, the undeclared-policy table, the convergence run, and the mock's material uniqueness.
@ts-expect-errorpin outside the deleted read-port case stays; there were none elsewhere in this file.Technical details
git diff --numstat origin/main...HEADis 13 added, 52 deleted, in one file.The added lines are the material row rewritten as a plain test; the deleted lines are the table scaffold, the two-live-keys case, and the read-port case.
test/sections, which lands in a separate PR before this one merges.git checkout -- srcbefore the next.BEGIN_COMMIT_OVERRIDE
test(deploy_keys): drop the cases the contract tests and scenarios already pin
END_COMMIT_OVERRIDE