Why Test-driven basics in Go? - Purpose & Use Cases

The Big Idea

What if you could catch bugs before they cause problems, every time you write code?

The Scenario

Imagine writing a Go program and guessing if your code works by running the whole app and checking manually every time.

You change one part and then have to test everything again by hand.

The Problem

This manual way is slow and tiring.

You might miss bugs because you forget to check some cases.

It's easy to break something without noticing.

The Solution

Test-driven basics teach you to write small tests before coding the feature.

These tests automatically check if your code works as expected.

This saves time and catches errors early.

Before vs After

✗ Before

func Add(a, b int) int {
    return a + b
}

// Manually run program and check output

✓ After

import "testing"

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 lets you build reliable Go programs confidently and fix bugs quickly.

Real Life Example

When building a calculator app, test-driven basics help ensure each math operation works perfectly before adding more features.

Key Takeaways

Manual testing is slow and error-prone.

Writing tests first helps catch bugs early.

Automated tests make coding faster and safer.

Practice

1. What is the main purpose of writing tests in Go using the testing package?

easy

A. To make the program run faster

B. To add comments to the code

C. To check if the code works correctly by running test functions

D. To create user interfaces

Solution

1. Step 1: Understand the role of tests in Go

   Tests are written to verify that the code behaves as expected.

2. Step 2: Identify what the testing package does

   The testing package provides tools to write and run tests that check code correctness.

3. Final Answer:

   To check if the code works correctly by running test functions -> Option C

4. Quick Check:

   Tests check code correctness = B [OK]

Hint: Tests verify code correctness before running fully [OK]

Common Mistakes:

• Thinking tests improve speed
• Confusing tests with comments
• Assuming tests create UI

2. Which of the following is the correct way to start a test function in Go?

easy

A. func testMyFunc(t *testing.T) {}

B. func MyFuncTest(t *testing.T) {}

C. func TestingMyFunc(t *testing.T) {}

D. func TestMyFunc(t *testing.T) {}

Solution

1. Step 1: Recall Go test function naming rules

   Test functions must start with "Test" and take a *testing.T parameter.

2. Step 2: Match the correct function signature

   Only func TestMyFunc(t *testing.T) {} follows this rule exactly.

3. Final Answer:

   func TestMyFunc(t *testing.T) {} -> Option D

4. Quick Check:

   Test functions start with "Test" = C [OK]

Hint: Test functions must start with uppercase 'Test' [OK]

Common Mistakes:

• Starting function name with lowercase 'test'
• Adding extra words before 'Test'
• Using wrong parameter types

3. What will be the output when running go test on this test file?

package main

import "testing"

func Add(a, b int) int {
    return a + b
}

func TestAdd(t *testing.T) {
    if Add(2, 3) != 5 {
        t.Error("Expected 5")
    }
}

medium

A. No output

B. PASS

C. Compilation error

D. FAIL with error 'Expected 5'

Solution

1. Step 1: Analyze the Add function and test

   The Add function returns the sum of 2 and 3, which is 5.

2. Step 2: Check the test condition

   The test expects Add(2, 3) to be 5, which is true, so no error is called.

3. Final Answer:

   PASS -> Option B

4. Quick Check:

   Correct sum means test passes = D [OK]

Hint: If test condition matches, output is PASS [OK]

Common Mistakes:

• Assuming test fails when condition is true
• Thinking test prints 'Expected 5' on success
• Confusing test failure with compile error

4. Identify the error in this test code snippet:

package main

import "testing"

func TestMultiply(t *testing.T) {
    result := Multiply(2, 3)
    if result != 6 {
        t.Error("Expected 6")
    }
}

medium

A. Multiply function is not defined

B. Missing import for Multiply function

C. Test function name should be lowercase

D. t.Error should be t.Fail

Solution

1. Step 1: Check if Multiply function is defined

   The code snippet does not show any definition or import of Multiply function.

2. Step 2: Understand Go requires functions to be defined or imported

   Without definition or import, the code will not compile.

3. Final Answer:

   Multiply function is not defined -> Option A

4. Quick Check:

   Undefined function causes compile error = A [OK]

Hint: Undefined functions cause compile errors [OK]

Common Mistakes:

• Thinking test function names can be lowercase
• Confusing t.Error with t.Fail
• Assuming missing import causes runtime error

5. You want to write a test that fails if a function returns an empty string. Which test code snippet correctly implements this check?

hard

A. func TestEmpty(t *testing.T) {
if MyFunc() == "" {
t.Error("Result should not be empty")
}
}

B. func TestEmpty(t *testing.T) {
if MyFunc() != "" {
t.Error("Result should be empty")
}
}

C. func TestEmpty(t *testing.T) {
if MyFunc() == nil {
t.Error("Result should not be nil")
}
}

D. func TestEmpty(t *testing.T) {
if MyFunc() == 0 {
t.Error("Result should not be zero")
}
}

Solution

1. Step 1: Understand the test goal

   The test should fail if the function returns an empty string "".

2. Step 2: Check each option's condition

   func TestEmpty(t *testing.T) { if MyFunc() == "" { t.Error("Result should not be empty") } } fails when MyFunc() returns "", which matches the goal.

3. Final Answer:

   func TestEmpty(t *testing.T) { if MyFunc() == "" { t.Error("Result should not be empty") } } -> Option A

4. Quick Check:

   Fail on empty string = A [OK]

Hint: Fail test if function returns empty string "" [OK]

Common Mistakes:

• Checking for nil instead of empty string
• Checking for zero instead of string
• Reversing the condition logic