Skip to content

Add CLI smoke test against fixture scaffold#63

Open
advancedresearcharray wants to merge 4 commits into
theDakshJaitly:mainfrom
advancedresearcharray:feat/cli-smoke-test-57
Open

Add CLI smoke test against fixture scaffold#63
advancedresearcharray wants to merge 4 commits into
theDakshJaitly:mainfrom
advancedresearcharray:feat/cli-smoke-test-57

Conversation

@advancedresearcharray
Copy link
Copy Markdown
Contributor

@advancedresearcharray advancedresearcharray commented Jun 4, 2026

Summary

  • Add test/fixtures/smoke-project/ minimal .mex scaffold
  • Add test/cli-smoke.test.ts running top-level commands (--version, commands, check, doctor, log, timeline, heartbeat, sync, setup, init, watch) with exit-code and output assertions
  • --version is asserted against package.json so a hard-coded version drift would fail CI

Closes #57

Test plan

  • npm test -- test/cli-smoke.test.ts
  • npm run typecheck

@advancedresearcharray
Copy link
Copy Markdown
Contributor Author

Ready for review — CI is green on Node 20/22 and the suite covers all non-interactive top-level commands against the fixture scaffold (issue #57 acceptance criteria).

Latest push:

  • Removed Cursor co-author trailers from prior commits
  • Added expectSuccess helper so failed CLI invocations surface stdout/stderr in assertion output
  • Guarded afterAll cleanup when fixture setup fails before projectRoot is set

tui is intentionally excluded (interactive; covered in test/tui.test.ts).

@advancedresearcharray advancedresearcharray force-pushed the feat/cli-smoke-test-57 branch 2 times, most recently from ff919f9 to a4271ba Compare June 6, 2026 04:55
@advancedresearcharray
Copy link
Copy Markdown
Contributor Author

@theDakshJaitly — ready for review when you have a moment.

Latest push adds explicit coverage for default mex check output (not just --quiet), matching issue #57’s acceptance criteria for the check command path.

CI was green on the prior push (Node 20/22); this is a one-test addition only.

root and others added 4 commits June 7, 2026 05:59
Run top-level CLI commands in a git-backed smoke project and assert exit
codes and key output, including --version matching package.json.
Add pattern add to the CLI smoke suite, clean up unused imports,
and remove the temp project directory after tests finish.
Surface CLI stdout/stderr in assertion messages on non-zero exits and
guard fixture teardown when setup fails before projectRoot is assigned.
Cover the non-quiet check path explicitly so regressions in the
standard drift report are caught alongside --quiet.
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.

Add a CLI smoke test against a fixture scaffold

1 participant