You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
test(cli): isolate shared Archera command harness state #2269
The Archera command tests execute a shared Cobra command tree and temporarily replace command arguments, flag values, environment and logger output. Test isolation should restore the complete pre-test state so later executions do not depend on suite order.
Scope
Recover the existing focused test-only draft: snapshot and restore command and logger state, use it in the existing command runner, and verify that each configured logger sink actually receives its fixture marker. Keep production command behavior and provider contracts unchanged.
This is follow-up test maintenance for the already delivered comparison command and filters, including #2264. It does not add a new provider capability or require any live vendor request.
Verification
Exercise the real root command with intercepted synthetic HTTP responses. Keep seeded-state restoration and existing command assertions. Complete pinned local tests, race checks, vet, lint, build and normal commit hooks; require two independent reviewers, each making two passes on the exact head, followed by CI and the normal review gates.
An isolated 166-line draft is preserved and source-reviewed. Final verification and publication remain pending; this issue does not claim that those checks have passed.
Claiming recovery of the existing isolated test-harness draft. Plan: preserve its reviewed test-only scope, finish bounded local verification and independent current-head reviews, then publish an atomic PR with CI and review watchers. No production code, vendor requests or deployment are part of this work.
Activity
cristim commentedon Oct 18, 2026
resume-cc-audit
Claiming recovery of the existing isolated test-harness draft. Plan: preserve its reviewed test-only scope, finish bounded local verification and independent current-head reviews, then publish an atomic PR with CI and review watchers. No production code, vendor requests or deployment are part of this work.