Test-driven development in Swift in iOS Swift - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the main purpose of writing tests before code in TDD?

In Test-driven development (TDD), why do developers write tests before writing the actual code?

A To avoid writing any production code

B To make the app run faster

C To delay coding until all tests are ready

D To define the expected behavior and guide the implementation

💡 Hint

Think about how tests help shape the code you write.

In TDD, writing tests first helps clarify what the code should do, guiding development and ensuring correctness.

❓ ui_behavior

intermediate

What happens when a failing test is run in Xcode during TDD?

You write a test for a new feature in Swift and run it in Xcode, but the feature code is not implemented yet. What will you see?

A The test fails, showing a red indicator in the test navigator

B The test passes automatically

C The app UI updates to show the feature

D Xcode crashes

💡 Hint

Think about what happens when code does not meet test expectations.

A failing test shows a red mark in Xcode, indicating the feature is not yet implemented or does not behave as expected.

❓ lifecycle

advanced

What is the correct TDD cycle order?

Arrange the steps of the Test-driven development cycle in the correct order.

A 2,1,3,4

B 1,2,3,4

C 1,3,2,4

D 3,1,2,4

💡 Hint

Remember the mantra: Red, Green, Refactor.

TDD follows the cycle: write a failing test (red), write code to pass it (green), then refactor cleanly.

📝 Syntax

advanced

What is the output of this Swift test code snippet?

Consider this Swift test function: func testSum() { let result = sum(2, 3) XCTAssertEqual(result, 6) } Assuming sum adds two numbers, what will happen when this test runs?

iOS Swift

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

A The test is skipped automatically

B The test passes successfully

C The test fails because 2 + 3 is 5, not 6

D The test causes a runtime error

💡 Hint

Check the expected value in XCTAssertEqual.

The sum function returns 5, but the test expects 6, so the test fails.

🔧 Debug

expert

Why does this Swift test crash with 'fatal error: unexpectedly found nil while unwrapping an Optional'?

Given this test code: func testUserName() { let user: User? = nil XCTAssertEqual(user!.name, "Alice") } Why does this test crash instead of failing?

A Because user is nil and force-unwrapping it causes a runtime crash

B Because XCTAssertEqual cannot compare Optional values

C Because the test function is missing @testable import

D Because the name property is not defined in User

💡 Hint

Focus on the exclamation mark after user.

Force-unwrapping a nil Optional causes a runtime crash, not a test failure.

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