TDD Development Workflow FAQs

Question 1

How does the skill handle external dependencies like APIs or databases?

Accepted Answer

It includes standardized mocking patterns for common services like Supabase, Redis, and OpenAI, allowing for isolated and fast-running test suites.

Question 2

What are the success metrics for this workflow?

Accepted Answer

Success is measured by reaching 80%+ code coverage, passing all tests in CI/CD, and ensuring that E2E tests successfully cover all critical user journeys.

Question 3

What is the primary goal of the TDD Workflow skill?

Accepted Answer

The primary goal is to ensure that development follows the Test-Driven Development principles, where tests are written before the implementation code to guarantee at least 80% coverage and high reliability.

Question 4

Does this skill support specific testing frameworks?

Accepted Answer

Yes, it provides optimized patterns and boilerplate for Jest and Vitest (unit/integration) as well as Playwright for end-to-end browser testing.

Question 5

Can I use this skill to improve an existing project's coverage?

Accepted Answer

Absolutely. The workflow is designed to be used for adding new features, fixing bugs, or refactoring existing code, helping you incrementally increase the test suite quality.

TDD Development Workflow

主要功能

使用场景

TDD Development Workflow

主要功能

使用场景