Test-driven basics in Go - Time & Space Complexity

Time Complexity: Test-driven basics

O(n)

Understanding Time Complexity

When writing tests first, it is important to know how the time your tests take grows as your code runs on bigger inputs.

We want to see how the test and code execution time changes when input size changes.

Scenario Under Consideration

Analyze the time complexity of the following test-driven code snippet.

func Sum(nums []int) int {
    total := 0
    for _, n := range nums {
        total += n
    }
    return total
}

func TestSum(t *testing.T) {
    result := Sum([]int{1, 2, 3, 4})
    if result != 10 {
        t.Errorf("Expected 10, got %d", result)
    }
}
    

This code defines a function that adds numbers in a list and a test that checks if it works correctly.

Identify Repeating Operations

Look for loops or repeated steps in the code.

• Primary operation: Looping through each number in the input list to add it.
• How many times: Once for each number in the list.

How Execution Grows With Input

As the list gets bigger, the time to add all numbers grows in a straight line.

Input Size (n)	Approx. Operations
10	10 additions
100	100 additions
1000	1000 additions

Pattern observation: Doubling the input doubles the work because each number is added once.

Final Time Complexity

Time Complexity: O(n)

This means the time grows directly with the number of items you add.

Common Mistake

[X] Wrong: "The test time stays the same no matter how many numbers I add."

[OK] Correct: The test runs the function, and the function adds each number, so more numbers mean more work and more time.

Interview Connect

Understanding how test and code time grows helps you write better tests and code that work well even with bigger inputs.

Self-Check

"What if the Sum function used recursion instead of a loop? How would the time complexity change?"

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