test-writer

Behavioral tests validate expected interactions, while conformance tests check architecture dependencies. Both types reference STORY IDs for traceability, import real implementations, avoid mocks, and run npm test to confirm RED state.

Yes, test generation supports both standalone and pipeline modes. In pipeline mode, it reads stories and architecture docs automatically to produce behavioral and conformance tests that enforce RED state without manual intervention.

RED state in behavioral and conformance testing means tests intentionally fail before implementations are complete. By importing real implementations and avoiding mocks, running npm test validates that failures are detected early and never masked.

No, generated end-to-end test suites avoid mocks entirely. They import real implementations to ensure that running npm test accurately validates the RED state against actual architecture dependencies.

Generated test files reference STORY IDs to maintain traceability between user stories, architecture docs, and test suites. This ensures every behavioral and conformance test maps back to specific acceptance criteria.