Conversation
Five tests under test/integration/pipeline.test.js drive every command in sequence against a real temp directory with no `loadConfig` / `scan` / etc injection. Covers the cross-command seams unit tests can't reach: init writing a config that downstream commands parse, list/show finding spec dirs in the right shape, scan/explain reaching the right branch based on project state. Brownfield path uses a fake Express fixture (package.json + src/index.js with three routes); greenfield path uses an empty dir + canned idea. Agent mode only — no AI mocking needed since agent mode dumps to stdout. API mode integration would need canned `complete` responses for each phase; can layer on later. Closes audit P2 #1.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Five tests under test/integration/pipeline.test.js drive every command in sequence against a real temp directory with no
loadConfig/scan/ etc injection. Covers the cross-command seams unit tests can't reach: init writing a config that downstream commands parse, list/show finding spec dirs in the right shape, scan/explain reaching the right branch based on project state.Brownfield path uses a fake Express fixture (package.json + src/index.js with three routes); greenfield path uses an empty dir + canned idea. Agent mode only — no AI mocking needed since agent mode dumps to stdout. API mode integration would need canned
completeresponses for each phase; can layer on later.Closes audit P2 #1.