TDD Test Agent FAQs

Question 1

What architectural layers are covered by the generated tests?

Accepted Answer

It provides full-stack coverage: Entity validation (Zod schemas), Use Case logic (business rules and authorization), Services (CRUD and data transformation), API endpoints (HTTP status and formatting), and E2E workflows (Playwright flows including accessibility and keyboard navigation).

Question 2

How does this skill ensure it uses the latest testing patterns?

Accepted Answer

The skill includes a mandatory Phase 0 research step that integrates with Context7. It queries the latest documentation for libraries like Vitest, Playwright, and Zod to ensure the generated test patterns follow current best practices and API standards.

Question 3

When should I use this skill in my development workflow?

Accepted Answer

You should activate this skill immediately after your Architect agent delivers the PRD and entity definitions, but before the Implementer agent begins writing the actual code. This ensures your tests act as an immutable specification for the feature.

Question 4

What does the TDD Test Agent skill do?

Accepted Answer

The TDD Test Agent automates the 'RED' phase of Test-Driven Development. It generates comprehensive, failing test suites across your entire application architecture—including Entities, Use Cases, APIs, and E2E flows—to define feature specifications before any implementation code is written.

Question 5

Why is it mandatory for the generated tests to fail initially?

Accepted Answer

Initial failure is a core TDD principle. By ensuring tests fail with 'not implemented' or 'not defined' errors, the agent proves that the test suite is correctly targeting the missing feature and providing a true benchmark for the implementation phase.

TDD Test Agent

TDD Test Agent

主要功能

使用场景

主要功能

使用场景