What is the typical TDD cycle?

What is the typical TDD cycle?

• A. Write production code first, then tests to cover it.
• B. Write a failing test, write minimal code to pass the test, run tests, refactor, and repeat with new tests for new behavior.
• C. Run tests without writing tests first.
• D. Write tests after deployment.

Answer: (B)

The typical TDD cycle centers on driving development through tests. You start by writing a failing test that specifies the exact behavior you want. That test failing gives you a concrete goal to hit. Next, you write the smallest amount of production code necessary to make that test pass—just enough to satisfy the test, nothing more. Once it passes, you run the full test suite to verify that your new code didn’t break any existing behavior. Then you refactor the code to improve structure, readability, and maintainability while keeping all tests green. Finally, you repeat the process with a new test that describes the next piece of behavior you want to add. This incremental approach provides quick feedback and helps ensure you’re always working toward testable, well-designed code.

The typical TDD cycle centers on driving development through tests. You start by writing a failing test that specifies the exact behavior you want. That test failing gives you a concrete goal to hit. Next, you write the smallest amount of production code necessary to make that test pass—just enough to satisfy the test, nothing more. Once it passes, you run the full test suite to verify that your new code didn’t break any existing behavior. Then you refactor the code to improve structure, readability, and maintainability while keeping all tests green. Finally, you repeat the process with a new test that describes the next piece of behavior you want to add. This incremental approach provides quick feedback and helps ensure you’re always working toward testable, well-designed code.