Skip to content

test: broaden quickstart --concurrency witnesses - #202

Open
ethanj wants to merge 1 commit into
fix/quickstart-json-stdoutfrom
test/quickstart-concurrency-coverage
Open

test: broaden quickstart --concurrency witnesses#202
ethanj wants to merge 1 commit into
fix/quickstart-json-stdoutfrom
test/quickstart-concurrency-coverage

Conversation

@ethanj

@ethanj ethanj commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Broaden the quickstart --concurrency witnesses (stacked on #201)

Test-only additions to test/quickstart-json-stdout.test.ts, pinning the coordinates the
defect report named but the original oracle left open:

  • Input-space coverage: parameterized over eight / 0 / 2.5 / -1 — one case per
    rejection branch of !Number.isInteger(n) || n <= 0.
  • Exit-code pinning: expectCLIExit(result, 0) in every case. runCLI never throws, so
    previously a nonzero-exit regression with an intact envelope would pass; the defect was
    precisely "exit 0 + unparseable stream", so both coordinates are pinned.
  • Human-mode witness: same invalid flag without --json — exit 0 and the warning visible.
    Channel-agnostic by design: it survives the channel fix and fails only if the diagnostic is
    dropped entirely.
  • Hermeticity: the fixture env now also blanks LLMWIKI_COMPILE_CONCURRENCY and points
    LLMWIKI_CLAUDE_SETTINGS_PATH at a nonexistent file, so ambient developer configuration
    cannot perturb the subprocess.

Mutation-tested both directions: restoring the stdout write turns the four channel witnesses
red (human-mode stays green, as designed); deleting the diagnostic turns all five red.
Full suite green (5033 passed), tsc --noEmit clean, fallow clean.

Based on fix/quickstart-json-stdout (#201) — merging order stays with #201.

Four additions to the JSON-stdout oracle, all pinning coordinates the
defect report named but the original test left open:

- the invalid value is parameterized over eight/0/2.5/-1 - one case
  per rejection branch of !Number.isInteger(n) || n <= 0;
- every case pins exit 0 via expectCLIExit (runCLI never throws, so a
  nonzero-exit regression with an intact envelope previously passed);
- a human-mode witness pins that the warning stays visible without
  --json (channel-agnostic by design: it survives the channel fix and
  fails only if the diagnostic is dropped);
- the fixture env blanks LLMWIKI_COMPILE_CONCURRENCY and points
  LLMWIKI_CLAUDE_SETTINGS_PATH at a nonexistent file, so ambient
  developer configuration cannot perturb the run.

Mutation-tested both directions: restoring the stdout write fails the
four channel witnesses; deleting the diagnostic fails all five.
Full suite green (5033 passed), tsc clean.
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