writing-system-tests

This approach generates failing acceptance tests directly from user stories, ensuring tests are written before implementation. It requires knowledge of your project's test framework and directory conventions to produce tests that match your existing setup.

Creating failing acceptance tests involves converting user stories into test cases that verify acceptance criteria. This provides an early signal for potential issues and ensures coverage before any feature implementation is written.

Automated test generation supports both headless/API and full-stack projects. It handles multi-step flow testing and generates language-agnostic tests that adhere to the specific conventions of your project.

Yes, specifying your test framework and directory conventions is required. This knowledge is necessary to generate tests that correctly adhere to your project's specific setup and structure.

To ensure coverage of acceptance criteria, the skill analyzes the user story and creates tests specifically designed to validate each defined criterion. This guarantees comprehensive coverage before implementation starts.