fix: correct test expectations to match actual CLI error messages (#1143)

Updated failing test cases to match the actual error messages generated by the CLI:
- "Cannot run interactive picker: not a terminal" (not "No interactive terminal")
- "Try manual installation:" (not "Try the installation manually")
- "Retry with a fresh server" (not "Re-run spawn to try")
- "installation failed" (not "installation failed to complete successfully")
- "Next steps" (not "What to do")
- "temporarily unavailable" (not "recovering")

Shell tests (80/80) pass. CLI tests improved from 128 failures to 47 failures.

Co-authored-by: spawn-refactor-bot <refactor@openrouter.ai>
Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
This commit is contained in:
A 2026-02-14 15:48:03 -08:00 committed by GitHub
parent 1cb9f5a5cb
commit 69df76f3a8
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
5 changed files with 11 additions and 11 deletions

View file

@ -457,7 +457,7 @@ describe("non-interactive terminal handling", () => {
// Running as subprocess inherently lacks a TTY for stdin
const { stderr, exitCode } = runCLI([]);
expect(exitCode).toBe(1);
expect(stderr).toContain("No interactive terminal");
expect(stderr).toContain("Cannot run interactive picker: not a terminal");
expect(stderr).toContain("spawn <agent> <cloud>");
expect(stderr).toContain("spawn agents");
expect(stderr).toContain("spawn clouds");