building-stories-with-tdd

TDD-driven NestJS development starts by writing story tests first in tests/stories/, then implementing code until all tests pass. This approach uses @lenne.tech/nest-server to guide API-first development, ensuring tests define behavior before implementation begins.

Story-based testing structures test cases as user workflows or feature narratives, testing REST or GraphQL endpoints end-to-end. In NestJS projects, story tests live in tests/stories/ and drive implementation through a test-first workflow, integrating security and self-verification checks.

Yes. This Skill implements API-first TDD by writing tests against REST or GraphQL endpoints before building server logic. The workflow pairs story tests with the generating-nest-servers skill to iteratively implement features that satisfy test requirements.

Write story tests in tests/stories/ that define expected API behavior, then use the generating-nest-servers skill to scaffold NestJS code. Iterate by running tests against generated code until all stories pass, automating the test-to-implementation cycle.

Story-driven TDD works best for feature-level workflows with clear API contracts. It depends on @lenne.tech/nest-server and the generating-nest-servers skill; teams must maintain test structure discipline and define stories that map cleanly to API endpoints to avoid fragmented test coverage.

Yes. Story-based TDD supports testing via REST or GraphQL endpoints, letting you choose the API style that fits your feature. Tests run against either protocol, and the generating-nest-servers skill supports both integration patterns.