Why testing matters in Kotlin - Visual Breakdown

Concept Flow - Why testing matters

Write code

↓

Run tests

↓

Tests pass?

No→Fix bugs

↓

Re-run tests

↓

Code works well

↓

Confident release

This flow shows how writing code, running tests, fixing bugs, and passing tests lead to confident, working software.

Execution Sample

Kotlin

fun add(a: Int, b: Int): Int {
    return a + b
}

fun testAdd() {
    assert(add(2, 3) == 5)
}

A simple function adds two numbers, and a test checks if the result is correct.

Execution Table

Step	Action	Evaluation	Result
1	Call add(2, 3)	2 + 3	5
2	Check if add(2, 3) == 5	5 == 5	True
3	Test passes	assertion holds	No error
4	Code works as expected	-	-

💡 Test passes, so code is correct and ready to use.

Variable Tracker

Variable	Start	After Step 1	After Step 2	Final
a	-	2	2	2
b	-	3	3	3
result	-	5	5	5
testPass	false	false	true	true

Key Moments - 3 Insights

Why do we run tests after writing code?

Running tests checks if the code works as expected, as shown in execution_table step 2 where the result is compared to the expected value.

What happens if a test fails?

If a test fails, we fix bugs and re-run tests until they pass, as shown in the concept_flow where 'Tests pass?' leads to 'Fix bugs' if No.

Why is testing important before releasing code?

Testing ensures the code works correctly and prevents errors in real use, giving confidence to release, as shown in the final step of concept_flow.

Visual Quiz - 3 Questions

Look at the execution_table, what is the result of add(2, 3) at step 1?

A 5

B 2

C 3

D Error

💡 Hint

Check the 'Result' column in execution_table row for step 1.

At which step does the test confirm the code works as expected?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look for the step where assertion passes without error in execution_table.

If the test failed, what would be the next action according to concept_flow?

A Release code immediately

B Ignore the test

C Fix bugs and re-run tests

D Write more code without testing

💡 Hint

See the 'Tests pass?' decision in concept_flow leading to 'Fix bugs' if No.

Concept Snapshot

Why testing matters:
- Write code and then run tests
- Tests check if code works correctly
- If tests fail, fix bugs and re-test
- Passing tests mean code is reliable
- Testing builds confidence before release

Full Transcript

This lesson shows why testing is important in programming. First, you write your code. Then you run tests to check if the code works as expected. If a test fails, you fix the bugs and run the tests again. When all tests pass, you know your code works well and can be safely released. Testing helps catch mistakes early and makes your software more reliable.

Practice

1. Why is testing important when writing Kotlin programs?

easy

A. It makes the program run faster automatically.

B. It allows the program to work without any user input.

C. It removes the need to write comments in code.

D. It helps find mistakes early and keeps the program working well.

Solution

1. Step 1: Understand the purpose of testing

   Testing is used to find mistakes and ensure the program behaves as expected.

2. Step 2: Compare options with testing goals

   Only It helps find mistakes early and keeps the program working well. correctly states that testing finds mistakes early and keeps the program working well.

3. Final Answer:

   It helps find mistakes early and keeps the program working well. -> Option D

4. Quick Check:

   Testing finds mistakes early = B [OK]

Hint: Testing finds bugs early and keeps code reliable [OK]

Common Mistakes:

• Thinking testing makes code faster
• Believing testing replaces comments
• Assuming testing removes user input

2. Which Kotlin syntax correctly defines a simple test function named testSum?

easy

A. fun testSum() { /* test code here */ }

B. def testSum() { /* test code here */ }

C. function testSum() { /* test code here */ }

D. testSum fun() { /* test code here */ }

Solution

1. Step 1: Recall Kotlin function syntax

   Kotlin functions start with the keyword fun, followed by the function name and parentheses.

2. Step 2: Match options to Kotlin syntax

   Only fun testSum() { /* test code here */ } uses the correct Kotlin syntax: fun testSum() { ... }.

3. Final Answer:

   fun testSum() { /* test code here */ } -> Option A

4. Quick Check:

   Kotlin functions start with fun = A [OK]

Hint: Kotlin functions always start with 'fun' keyword [OK]

Common Mistakes:

• Using 'def' like in Python
• Using 'function' like in JavaScript
• Placing 'fun' after the function name

3. What will be the output of this Kotlin test function?

fun testMultiply() {
    val result = 3 * 4
    if (result == 12) {
        println("Test passed")
    } else {
        println("Test failed")
    }
}
testMultiply()

medium

A. Test passed

B. No output

C. Test failed

D. Compilation error

Solution

1. Step 1: Calculate the multiplication

   The variable result is assigned 3 * 4, which equals 12.

2. Step 2: Check the if condition

   The condition result == 12 is true, so it prints "Test passed".

3. Final Answer:

   Test passed -> Option A

4. Quick Check:

   3 * 4 = 12, prints 'Test passed' = C [OK]

Hint: Calculate expressions before checking conditions [OK]

Common Mistakes:

• Assuming multiplication is wrong
• Ignoring the if condition
• Thinking no output occurs

4. This Kotlin test function is supposed to check if a number is even. What is wrong?

fun testIsEven() {
    val number = 5
    if (number % 2 = 0) {
        println("Even")
    } else {
        println("Odd")
    }
}
testIsEven()

medium

A. The variable 'number' should be a String

B. Missing parentheses around the if condition

C. Using single '=' instead of '==' in the if condition

D. The function name should start with 'is'

Solution

1. Step 1: Identify the if condition syntax error

   The condition uses a single '=' which is assignment, not comparison.

2. Step 2: Correct the comparison operator

   It should use '==' to compare if number % 2 equals 0.

3. Final Answer:

   Using single '=' instead of '==' in the if condition -> Option C

4. Quick Check:

   Comparison needs '==' not '=' = A [OK]

Hint: Use '==' for comparison, '=' is assignment [OK]

Common Mistakes:

• Confusing '=' with '=='
• Thinking parentheses are missing
• Believing variable type is wrong

5. You want to write a Kotlin test that checks if a function calculateDiscount returns the correct discount for a price. Which approach best shows why testing matters?

hard

A. Write a test that changes the price variable but does not check the output.

B. Write a test that calls calculateDiscount(100) and checks if the result is 10.

C. Write a test that always returns true without calling the function.

D. Write a test that prints the price without checking the result.

Solution

1. Step 1: Understand the goal of testing functions

   Tests should call the function and verify if the output matches expected results.

2. Step 2: Evaluate each option

   Only Write a test that calls calculateDiscount(100) and checks if the result is 10. calls the function and checks the result, which helps find mistakes and trust the code.

3. Final Answer:

   Write a test that calls calculateDiscount(100) and checks if the result is 10. -> Option B

4. Quick Check:

   Test calls function and checks output = D [OK]

Hint: Tests must check function output against expected values [OK]

Common Mistakes:

• Writing tests that don't check results
• Returning true without testing
• Changing variables without verification