XCTest framework in iOS Swift - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ ui_behavior

intermediate

What happens when a failing XCTAssert is encountered?

In an XCTest case, what is the behavior when an XCTAssert condition fails during a test method execution?

iOS Swift

func testExample() {
  XCTAssert(1 + 1 == 3)
  print("This line is reached")
}

A The test continues running, prints the message, but marks as failed at the end.

B The test immediately stops and marks as failed; the print statement is not executed.

C The test passes because print executes, ignoring the failed XCTAssert.

D The test crashes and stops the entire test suite.

💡 Hint

XCTAssert failures report errors but do not stop the test method immediately.

XCTAssert failures record a failure but allow the test method to continue running. This means subsequent lines execute, but the test is marked as failed overall.

📝 Syntax

intermediate

Which code correctly defines a test case class?

Select the correct Swift code snippet that defines a valid XCTestCase subclass with one test method.

A

class MyTests: XCTestCase {
  func exampleTest() {
    XCTAssertTrue(true)
  }
}

B

class MyTests: XCTestCase {
  func testExample() {
    XCTAssertTrue(true)
  }
}

C

class MyTests {
  func testExample() {
    XCTAssertTrue(true)
  }
}

D

class MyTests: XCTestCase {
  func testExample() {
    assert(true)
  }
}

💡 Hint

Test methods must start with 'test' and class must inherit XCTestCase.

Option B correctly inherits XCTestCase and defines a method starting with 'test'. Option B lacks inheritance, C method name does not start with 'test', D uses assert instead of XCTAssertTrue.

❓ lifecycle

advanced

What is the order of XCTest lifecycle methods?

Arrange the following XCTest lifecycle methods in the order they are called when running multiple test methods in a test case class.

A 2, 3, 1, 4

B 2, 1, 3, 4

C 1, 2, 4, 3

D 1, 2, 3, 4

💡 Hint

Class methods run once per class; instance methods run per test method.

setUp() class method runs once before all tests, setUp() instance method runs before each test, tearDown() instance method runs after each test, and tearDown() class method runs once after all tests.

🔧 Debug

advanced

Why does this test always pass even if the code is wrong?

Given the test below, why does it always pass even if the function under test returns wrong results? func testSum() { let result = sum(2, 3) XCTAssertEqual(result, 6) }

iOS Swift

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

A The test passes because XCTAssertEqual is comparing to the wrong expected value (6 instead of 5).

B The test passes because sum function is correct and returns 6.

C The test passes because the test method is not named starting with 'test'.

D The test passes because XCTAssertEqual does not check equality.

💡 Hint

Check the expected value in XCTAssertEqual carefully.

The sum function incorrectly returns 6 for inputs 2 and 3 (should be 5), but the test expects 6, so the test passes even though the function under test returns wrong results.

🧠 Conceptual

expert

What is the purpose of XCTestExpectation in asynchronous tests?

Why do we use XCTestExpectation in XCTest when testing asynchronous code?

A To mock asynchronous functions without running real code.

B To automatically retry failed tests multiple times for flaky network calls.

C To pause the test until the asynchronous operation completes or times out, ensuring correct test timing.

D To speed up test execution by skipping asynchronous code.

💡 Hint

Think about how XCTest knows when async code finishes.

XCTestExpectation allows the test to wait for async code to finish or timeout, so tests can verify results after asynchronous operations complete.