Why Writing basic test functions in Go? - Purpose & Use Cases

The Big Idea

What if your code could tell you instantly when something breaks, saving hours of frustration?

The Scenario

Imagine you just finished writing a Go program, and you want to check if it works correctly. You try running it and manually check the output every time you make a change.

This means running the program, looking at the screen, and guessing if everything is right.

The Problem

Manually checking your program is slow and tiring. You might miss mistakes because you forget what the correct output should be.

Also, if you change your code, you have to check everything again from scratch, which wastes time and can cause errors.

The Solution

Writing basic test functions in Go lets you automate these checks. You write small pieces of code that run your program parts and tell you if they work as expected.

This saves time, reduces mistakes, and helps you fix problems quickly.

Before vs After

✗ Before

func main() {
    result := add(2, 3)
    fmt.Println("Result:", result) // Check output manually
}

✓ After

func TestAdd(t *testing.T) {
    got := add(2, 3)
    want := 5
    if got != want {
        t.Errorf("got %d, want %d", got, want)
    }
}

What It Enables

It enables you to catch errors early and confidently improve your code without fear of breaking things.

Real Life Example

Think of a calculator app: writing test functions ensures that adding, subtracting, or multiplying always gives the right answer, even after you add new features.

Key Takeaways

Manual checks are slow and error-prone.

Basic test functions automate correctness checks.

Tests help you build reliable and maintainable Go programs.