tdd

Test-driven development implements features by enforcing a Red-Green-Refactor cycle to drive small, test-first iterations, requiring you to write a failing test, provide minimal code to pass it, and then refactor safely.

The Red-Green-Refactor cycle is a test-driven development workflow where you first write a failing test (Red), implement the minimal code to pass it (Green), and then iteratively refactor the code while keeping all tests passing.

To write a failing pytest test for an API endpoint, start by defining the expected inputs, outputs, and edge cases. Run the test to confirm it fails, then add the minimal implementation logic required to make the test pass.

Yes, test-driven development applies to software engineering tasks like unit-level functions, API endpoints, and algorithmic logic where incremental tests, minimal implementations, and iterative refactoring are appropriate for verifiable increments.

To ensure test automation covers edge cases, use a test design checklist to confirm inputs, outputs, and enumerate test cases. This covers happy paths and error conditions before running coverage checks to validate the results.

You should avoid a test-first development workflow for exploratory prototypes or tasks where verifiable increments and iterative refactoring are inappropriate, as it may restrict rapid scope changes and delay initial feedback.