Why testing is central to Ruby culture - Performance Analysis

Time Complexity: Why testing is central to Ruby culture

O(n)

Understanding Time Complexity

Testing code is a key part of writing Ruby programs. It helps catch mistakes early and keeps code working well as it grows.

We want to understand how the time it takes to run tests changes as the program gets bigger.

Scenario Under Consideration

Analyze the time complexity of running a simple test suite on Ruby code.

    def run_tests(tests)
      tests.each do |test|
        result = test.call
        puts "Test passed" if result
      end
    end
    
    tests = Array.new(100) { -> { true } }
    run_tests(tests)
    

This code runs each test in a list and prints a message if it passes.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Running each test once in a loop.
• How many times: Once for every test in the list.

How Execution Grows With Input

As the number of tests grows, the time to run them grows too.

Input Size (n)	Approx. Operations
10	10 test runs
100	100 test runs
1000	1000 test runs

Pattern observation: The time grows directly with the number of tests. Double the tests, double the time.

Final Time Complexity

Time Complexity: O(n)

This means the time to run tests grows in a straight line with how many tests there are.

Common Mistake

[X] Wrong: "Running more tests doesn't affect how long testing takes much."

[OK] Correct: Each test adds work, so more tests mean more time needed.

Interview Connect

Understanding how test time grows helps you write better code and tests. It shows you care about keeping your programs reliable as they grow.

Self-Check

"What if each test ran multiple smaller checks inside? How would the time complexity change?"