tdd

A red-green-refactor workflow enforces a tests-first approach by writing failing tests, developing minimal production code to pass them, and then refactoring. This skill provides cycle guidance and practical workflow examples to structure your testing process effectively.

Behavior-focused testing organizes tests by feature and behavior rather than implementation details. It utilizes factory-based test data practices to ensure test isolation, providing clear naming guidelines and structure for your test suite.

You need factory-based test data when ensuring test isolation across typical software projects. It provides structured organization practices and reliable data generation, preventing test dependencies from causing flaky results during your development cycles.

Yes, you can apply TDD to existing projects by enforcing a tests-first workflow and writing minimal production code to pass new tests. The skill offers practical workflow examples and refactoring practices to integrate TDD incrementally.

The best way to structure tests for clear public API testing is using behavior-focused patterns with specific naming guidelines. This approach ensures you satisfy requirements by validating behaviors and organizing tests by feature rather than internal methods.

Refactoring breaks test suites when tests are tied to implementation rather than behavior. Adopting behavior-focused testing and factory-based test data ensures test isolation, allowing you to refactor production code safely without breaking API expectations.