Skip to content

Remove redundant configuration and output test cases - #30

Closed
daveosterjr wants to merge 1 commit into
stagingfrom
codex/test-cleanup-staging-20261010
Closed

daveosterjr wants to merge 1 commit into
stagingfrom
codex/test-cleanup-staging-20261010

Conversation

@daveosterjr

@daveosterjr daveosterjr commented Oct 10, 2026 •

Copy link
Copy Markdown
Contributor

Remove eight redundant or implementation-only unit cases: mkdir call avoidance, a repeated encrypted-fallback scenario, mocked filesystem/property passthrough checks, and console-call counts without output-content assertions. Keep storage permissions, credential migration, fallback security, invalid-data handling and meaningful command/output checks. Exported production helpers stay unchanged.

This PR targets the existing staging branch and contains only the test hunks from #29. The affected tests and helper implementations match the pre-cleanup versions byte for byte at the staging base. No master runtime, dependency, package, policy or workflow changes are included. The user subsequently confirmed that the prior master delivery should remain and authorized automatic staging delivery. Use the existing Factory review and guarded staging merge workflow; do not apply the unused local master restoration.

Independent preservation review read the removed cases, retained suites and production helpers. Staging baseline passed 71 cases; final npm run check passed typecheck, build, plugin checks, 63 tests and public-artifact validation. The staging baseline differs from master, so these are staging counts. All 12 master test files were inventoried and read; deletion decisions remain limited to these evidenced cases, not an exhaustive production-owner/history claim.

No runtime behavior, public Command/API contract, package version, dependency, CI or release changes. No publication or live service smoke was run.

@daveosterjr

Copy link
Copy Markdown
Contributor Author

Closing during the October 13 board cleanup: everything in this pull request is already on the base branch, so merging it would change nothing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant