การเขียนการทดสอบก่อน

Welcome to the core of Test-Driven Development (TDD)! In this lesson, we'll dive into the crucial first step: writing a failing test first.

This is often called the 'Red' phase of the TDD cycle, because when you run your tests, you expect to see a 'red bar' indicating a failure.

It might feel counter-intuitive to write a test for code that doesn't exist yet, or isn't fully implemented. But this approach offers great benefits:

• Clarity: It forces you to think about what the code should *do* before you think about *how* to do it.
• Proof of Failure: It proves your test works correctly by showing it can fail. If it passes without any code, your test might be faulty!
• Focus: It gives you a clear, immediate goal: make this one test pass.

Think of your failing test as a precise specification or a mini-requirement. It describes a specific behavior your future code must exhibit.

• It defines the input.
• It defines the expected output or outcome.
• It's concrete and executable.

This helps prevent misunderstandings and ensures your code delivers exactly what's needed for that specific scenario.

Let's practice by building a simple Calculator class. For our first piece of functionality, we want it to be able to add two numbers.

Our goal is to write a test for an add method that will fail before we even write the correct implementation of add.

Before writing code, let's think:

• What input? We'll add 2 and 3.
• What output? We expect the result to be 5.
• What method? A method called add on a Calculator object.

We'll write a test that calls calculator.add(2, 3) and asserts that the result is 5.

Here's a simulated example of writing a test first. Notice the Calculator's add method is intentionally incorrect (it returns 0). This makes our 'test' fail, demonstrating the 'Red' phase.

Run this code to see the simulated failure!

After running the previous code, you saw a 'Test FAILED' message. This is exactly what we wanted!

• Expected: 5
• Actual: 0

This failure confirms two things: our test is correctly written, and the production code (the add method) does not yet meet the specified behavior.

Once you have a failing test, the next step in TDD (the 'Green' phase) is to write the *simplest possible code* to make that test pass.

• Don't over-engineer.
• Don't add extra features.
• Just focus on satisfying the current failing test.

This keeps your code clean and focused, building functionality incrementally.

Embracing the 'Red' phase of TDD leads to:

• Better Design: Tests guide you towards more modular and testable code.
• Increased Confidence: Each passing test gives you confidence in your code's correctness.
• Reduced Bugs: Catch issues early, before they become complex problems.
• Living Documentation: Your tests serve as up-to-date examples of how your code should be used.

Let's test your understanding of the 'Red' phase in Test-Driven Development.

You've explored the crucial first step of TDD: writing a failing test.

• The 'Red' phase means writing a test that fails.
• This test acts as a clear specification for new functionality.
• Seeing the test fail confirms its validity and that the code isn't yet correct.
• This methodical approach leads to clearer requirements and more robust code.

Next, we'll learn how to make that failing test pass – the 'Green' phase!