Test-driven development in Swift in iOS Swift

Introduction

Test-driven development helps you write code that works well by writing tests first. It makes your app more reliable and easier to fix.

When you want to make sure your app features work correctly before building them.

When you want to avoid bugs by checking your code step-by-step.

When you want to improve your coding skills by thinking about how your code should behave.

When you want to safely change or add new features without breaking existing ones.

Syntax

iOS Swift

func testExample() {
  // 1. Write a failing test
  XCTAssertEqual(add(2, 3), 5)
}

func add(_ a: Int, _ b: Int) -> Int {
  // 2. Write code to pass the test
  return a + b
}

// 3. Run tests and refactor if needed

Tests are written inside functions starting with test.

Use XCTAssert functions to check if your code works as expected.

Examples

This test checks if the sum function adds two numbers correctly.

iOS Swift

func testSum() {
  XCTAssertEqual(sum(1, 2), 3)
}

func sum(_ x: Int, _ y: Int) -> Int {
  return x + y
}

This test checks if the isEven function correctly identifies even numbers.

iOS Swift

func testIsEven() {
  XCTAssertTrue(isEven(4))
  XCTAssertFalse(isEven(5))
}

func isEven(_ number: Int) -> Bool {
  return number % 2 == 0
}

Sample App

This is a simple test class that checks if the add function returns the correct sum of two numbers.

When you run this test, it will pass if the sum is correct.

iOS Swift

import XCTest

class CalculatorTests: XCTestCase {
  func testAdd() {
    XCTAssertEqual(add(10, 5), 15)
  }
}

func add(_ a: Int, _ b: Int) -> Int {
  return a + b
}

Important Notes

Write the test first, then write just enough code to pass it.

Run tests often to catch mistakes early.

Use descriptive test names to know what each test checks.

Summary

Test-driven development means writing tests before code.

Tests help you catch bugs early and keep your app working well.

Use XCTest in Swift to write and run your tests.

Practice

1. What is the main idea behind Test-driven development (TDD) in Swift?

easy

A. Write tests before writing the actual code

B. Write code first, then write tests later

C. Write tests only after the app is complete

D. Skip tests and focus on UI design

Solution

1. Step 1: Understand TDD concept

   TDD means you write tests before you write the code that makes those tests pass.

2. Step 2: Compare options with TDD definition

   Only Write tests before writing the actual code correctly states that tests come before code in TDD.

3. Final Answer:

   Write tests before writing the actual code -> Option A

4. Quick Check:

   TDD = Write tests first [OK]

Hint: Remember: Tests come first in TDD [OK]

Common Mistakes:

• Thinking tests are written after code
• Believing tests are optional
• Confusing TDD with UI design

2. Which of the following is the correct way to import the testing framework in a Swift test file?

easy

A. import XCTest

B. import SwiftTest

C. import TestKit

D. import Testing

Solution

1. Step 1: Identify the official Swift testing framework

   The official framework for testing in Swift is called XCTest.

2. Step 2: Match the import statement

   Only import XCTest is correct to use XCTest in your test files.

3. Final Answer:

   import XCTest -> Option A

4. Quick Check:

   Use XCTest for Swift tests [OK]

Hint: Always import XCTest for Swift tests [OK]

Common Mistakes:

• Using incorrect or non-existent import names
• Forgetting to import XCTest
• Confusing XCTest with other frameworks

3. Given the following Swift test code, what will be the test result?

func testSum() {
  let result = sum(2, 3)
  XCTAssertEqual(result, 5)
}

func sum(_ a: Int, _ b: Int) -> Int {
  return a + b
}

medium

A. Test fails because sum(2, 3) equals 6

B. Test passes but result is 6

C. Test fails due to syntax error

D. Test passes because sum(2, 3) equals 5

Solution

1. Step 1: Analyze the sum function

   The function adds two integers and returns their sum. sum(2, 3) returns 5.

2. Step 2: Check the test assertion

   The test asserts that result equals 5, which is true, so the test passes.

3. Final Answer:

   Test passes because sum(2, 3) equals 5 -> Option D

4. Quick Check:

   sum(2,3) == 5 passes test [OK]

Hint: Check function output matches XCTAssertEqual value [OK]

Common Mistakes:

• Assuming sum returns wrong value
• Confusing test failure with syntax error
• Ignoring the actual return value

4. Identify the error in this Swift test code snippet:

func testIsEven() {
  let number = 4
  XCTAssertTrue(isEven(number))
}

func isEven(_ n: Int) -> Bool {
  return n % 2 == 1
}

medium

A. XCTAssertTrue is used incorrectly; should be XCTAssertFalse

B. The isEven function returns true for odd numbers, causing test failure

C. The test function name is invalid

D. Missing import XCTest statement

Solution

1. Step 1: Check the isEven function logic

   It returns true if n % 2 == 1, which means odd numbers, not even.

2. Step 2: Understand test expectation

   The test expects isEven(4) to be true, but 4 is even, so the function logic is wrong and test fails.

3. Final Answer:

   The isEven function returns true for odd numbers, causing test failure -> Option B

4. Quick Check:

   Wrong modulo logic causes test fail [OK]

Hint: Check function logic matches test expectation [OK]

Common Mistakes:

• Mixing odd/even logic in modulo
• Misusing XCTAssertTrue vs XCTAssertFalse
• Ignoring function implementation errors

5. You want to use TDD to create a function that filters out negative numbers from an array. Which sequence of steps follows TDD best?

hard

A. Write tests only for positive numbers, ignore negatives

B. Write the filtering function first, then write tests after it works

C. Write a failing test for filtering negatives, write code to pass test, refactor code

D. Write code and tests simultaneously without order

Solution

1. Step 1: Understand TDD workflow

   TDD requires writing a failing test first that defines desired behavior.

2. Step 2: Follow TDD steps for filtering negatives

   Write a test that expects negatives filtered out, then write code to pass it, then improve code.

3. Final Answer:

   Write a failing test for filtering negatives, write code to pass test, refactor code -> Option C

4. Quick Check:

   TDD = Test first, code second, refactor [OK]

Hint: Always write failing test before code in TDD [OK]

Common Mistakes:

• Writing code before tests
• Ignoring refactoring step
• Writing incomplete tests