testing-tdd

To start TDD, write a failing test that defines the expected behavior of your new function or API endpoint before writing any production code. This enforces a strict red-green-refactor cycle, ensuring testability and correctness from the start.

The red-green-refactor cycle is a TDD methodology where you write a failing test (Red), implement minimal code to pass the test (Green), and then clean up the code (Refactor). This workflow ensures robust and reliable software development.

You should use test-driven development for all new features, bug fixes, and refactoring tasks. It mandates writing tests before implementation to define expected request and response behaviors, ensuring the endpoint or function behaves as intended.

Common TDD anti-patterns include skipping the failing test phase or writing excessive code before testing. This skill provides detailed instructions on rationalizations to avoid, ensuring you maintain a strict red-green-refactor cycle for high code quality.

Yes, you can use TDD for refactoring existing code safely by writing tests that define current behavior before making changes. This ensures testability and correctness while cleaning up the code during the refactor phase of the cycle.