Kotlin test assertions - Time & Space Complexity

Time Complexity: Kotlin test assertions

O(n * m)

Understanding Time Complexity

We want to understand how the time it takes to run Kotlin test assertions changes as the number of tests or checks grows.

How does adding more assertions affect the total time to run them all?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

fun testSum() {
    val numbers = listOf(1, 2, 3, 4, 5)
    val result = numbers.sum()
    assert(result == 15) { "Sum should be 15" }
}

fun testAll() {
    testSum()
    testSum()
    testSum()
}

This code runs a simple sum test three times, each with one assertion checking the result.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The sum() function loops through the list to add numbers.
• How many times: sum() runs once per testSum call, and testSum is called three times.

How Execution Grows With Input

As the number of tests or assertions increases, the total work grows proportionally.

Input Size (number of tests)	Approx. Operations
10	10 sums and 10 assertions
100	100 sums and 100 assertions
1000	1000 sums and 1000 assertions

Pattern observation: Doubling the number of tests doubles the total operations.

Final Time Complexity

Time Complexity: O(n * m)

This means the time grows with both the number of tests (n) and the size of data each test processes (m).

Common Mistake

[X] Wrong: "Assertions run instantly and don't affect time complexity."

[OK] Correct: Each assertion checks a condition, so more assertions mean more checks and more time.

Interview Connect

Understanding how test assertions scale helps you write efficient tests and reason about test suite performance in real projects.

Self-Check

"What if each test had multiple assertions instead of one? How would the time complexity change?"

Practice

1. Which Kotlin test assertion checks if two values are equal?

easy

A. assertEquals(expected, actual)

B. assertTrue(condition)

C. assertNull(value)

D. assertFails { block }

Solution

1. Step 1: Understand assertion types

   assertEquals is used to check if two values are equal.

2. Step 2: Match assertion to purpose

   assertTrue checks if a condition is true, assertNull checks for null, and assertFails checks for exceptions.

3. Final Answer:

   assertEquals(expected, actual) -> Option A

4. Quick Check:

   Equality check = assertEquals [OK]

Hint: Use assertEquals to compare expected and actual values [OK]

Common Mistakes:

• Confusing assertTrue with assertEquals
• Using assertNull for equality checks
• Using assertFails to check values

2. Which of the following is the correct syntax to assert a condition is true in Kotlin tests?

easy

A. assertTrue { condition }

B. assertTrue condition

C. assertTrue(condition)

D. assertTrue: condition

Solution

1. Step 1: Recall Kotlin assertion syntax

   assertTrue takes a Boolean condition as a parameter inside parentheses.

2. Step 2: Identify correct syntax

   Only assertTrue(condition) is valid Kotlin syntax; others are incorrect.

3. Final Answer:

   assertTrue(condition) -> Option C

4. Quick Check:

   assertTrue uses parentheses for condition [OK]

Hint: Remember assertions use parentheses for arguments [OK]

Common Mistakes:

• Using curly braces instead of parentheses
• Omitting parentheses
• Using colon instead of parentheses

3. What will be the result of this Kotlin test assertion?

val result = 5
assertEquals(5, result)

medium

A. Test passes without error

B. Test fails with AssertionError

C. Compilation error

D. Runtime exception other than AssertionError

Solution

1. Step 1: Check values compared

   The expected value is 5 and actual value stored in result is also 5.

2. Step 2: Understand assertEquals behavior

   Since both values are equal, assertEquals passes without throwing an error.

3. Final Answer:

   Test passes without error -> Option A

4. Quick Check:

   Equal values = test passes [OK]

Hint: Equal expected and actual means test passes [OK]

Common Mistakes:

• Assuming assertEquals throws error on equal values
• Confusing expected and actual order
• Thinking assertEquals returns a value

4. Identify the error in this Kotlin test assertion code:

assertEquals(10, 5 + 3)

medium

A. Runtime exception due to invalid operation

B. No error, test passes

C. Syntax error due to missing parentheses

D. Test fails because expected and actual differ

Solution

1. Step 1: Calculate actual value

   The expression 5 + 3 equals 8.

2. Step 2: Compare expected and actual

   Expected is 10 but actual is 8, so assertEquals fails and throws AssertionError.

3. Final Answer:

   Test fails because expected and actual differ -> Option D

4. Quick Check:

   Different values = test fails [OK]

Hint: Check actual calculation matches expected value [OK]

Common Mistakes:

• Assuming test passes despite value mismatch
• Thinking syntax error occurs
• Confusing runtime exceptions with assertion failures

5. You want to test that a function throws an exception when given invalid input. Which Kotlin assertion should you use?

hard

A. assertNull(function(invalidInput))

B. assertFails { function(invalidInput) }

C. assertEquals(exception, function(invalidInput))

D. assertTrue(function(invalidInput))

Solution

1. Step 1: Understand exception testing

   To check if a function throws an exception, use assertFails with a lambda calling the function.

2. Step 2: Evaluate other options

   assertEquals compares values, not exceptions; assertNull checks for null; assertTrue checks a Boolean condition.

3. Final Answer:

   assertFails { function(invalidInput) } -> Option B

4. Quick Check:

   Exception test = assertFails [OK]

Hint: Use assertFails with lambda to test exceptions [OK]

Common Mistakes:

• Using assertEquals to check exceptions
• Using assertNull expecting exception
• Using assertTrue for exception testing