XCTest framework in iOS Swift - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a test case class in XCTest.

iOS Swift

import XCTest

class MyTests: [1] {
}

Drag options to blanks, or click blank then click option'

AXCTestCase

BUIViewController

CNSObject

DAppDelegate

Attempts:

3 left

💡 Hint

Common Mistakes

Using UIViewController instead of XCTestCase.

Forgetting to inherit from any class.

Test case classes in XCTest must inherit from XCTestCase to gain testing capabilities.

2fill in blank

medium

Complete the code to define a test method that XCTest will run.

iOS Swift

func [1]() {
    XCTAssertEqual(2 + 2, 4)
}

Drag options to blanks, or click blank then click option'

AadditionTest

BtestAddition

CcheckAddition

DverifyAddition

Attempts:

3 left

💡 Hint

Common Mistakes

Naming test methods without the 'test' prefix.

Using spaces or special characters in method names.

Test methods must start with 'test' so XCTest recognizes and runs them automatically.

3fill in blank

hard

Fix the error in the assertion to check if a value is true.

iOS Swift

XCTAssert[1](isReady)

Drag options to blanks, or click blank then click option'

ANil

BEqual

CFalse

DTrue

Attempts:

3 left

💡 Hint

Common Mistakes

Using XCTAssertFalse when expecting true.

Using XCTAssertEqual for boolean checks.

To assert a boolean is true, use XCTAssertTrue in XCTest.

4fill in blank

hard

Fill both blanks to set up and tear down test resources.

iOS Swift

override func [1]() {
    super.[1]()
    // setup code here
}

override func [2]() {
    super.[2]()
    // teardown code here
}

Drag options to blanks, or click blank then click option'

AsetUp

BtearDown

CviewDidLoad

Dinit

Attempts:

3 left

💡 Hint

Common Mistakes

Using viewDidLoad instead of setUp or tearDown.

Not calling super in overridden methods.

setUp() runs before each test, tearDown() runs after each test to prepare and clean up.

5fill in blank

hard

Fill all three blanks to write a test that expects an error to be thrown.

iOS Swift

func testError() [3] {
    XCTAssertThrows[1](try someFunctionThat[2](), "Expected error")
    // Additional checks can be done here
}

Drag options to blanks, or click blank then click option'

AError

BThrows

Cthrows

DThrow

Attempts:

3 left

💡 Hint

Common Mistakes

Using XCTAssertThrow instead of XCTAssertThrowsError.

Omitting 'try' before the function call.

Not marking the test method with 'throws'.

XCTAssertThrowsError checks if a function throws an error; the function call uses 'try' and the method name uses 'throws'.

Practice

1. What is the main purpose of the XCTest framework in iOS development?

easy

A. To manage app navigation between screens

B. To write automated tests that check app behavior

C. To design user interfaces visually

D. To optimize app performance during runtime

Solution

1. Step 1: Understand XCTest role

   XCTest is designed to help developers write tests that automatically verify if the app works as expected.

2. Step 2: Compare options with XCTest purpose

   Only To write automated tests that check app behavior describes writing automated tests, which matches XCTest's main use.

3. Final Answer:

   To write automated tests that check app behavior -> Option B

4. Quick Check:

   XCTest = Automated testing [OK]

Hint: XCTest is for testing, not UI or navigation [OK]

Common Mistakes:

• Confusing XCTest with UI design tools
• Thinking XCTest manages app navigation
• Assuming XCTest improves runtime speed

2. Which of the following is the correct way to declare a test method inside an XCTestCase subclass?

easy

A. func TestExample() { }

B. func exampleTest() { }

C. func testExample() { }

D. test func example() { }

Solution

1. Step 1: Recall XCTest method naming rules

   Test methods must start with 'test' and be declared as functions with no parameters.

2. Step 2: Check each option

   func testExample() { } uses 'func testExample() { }' which follows the naming convention. Others either have wrong order, capitalization, or syntax.

3. Final Answer:

   func testExample() { } -> Option C

4. Quick Check:

   Test methods start with 'test' [OK]

Hint: Test methods must start with 'test' keyword [OK]

Common Mistakes:

• Starting method name without 'test'
• Capitalizing 'Test' instead of 'test'
• Incorrect function syntax

3. What will be the result of this test method when run?

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

medium

A. Test passes successfully

B. Test fails with assertion error

C. Test causes a compile-time error

D. Test is ignored and not run

Solution

1. Step 1: Evaluate the calculation

   The code calculates 2 + 3 and stores 5 in 'result'.

2. Step 2: Check the assertion

   XCTAssertEqual compares 'result' with 5, which is true, so the assertion passes.

3. Final Answer:

   Test passes successfully -> Option A

4. Quick Check:

   2 + 3 equals 5, assertion passes [OK]

Hint: If values match in XCTAssertEqual, test passes [OK]

Common Mistakes:

• Assuming test fails if no explicit pass message
• Confusing compile errors with assertion failures
• Thinking test is skipped without reason

4. Identify the error in this test method:

func testDivide() {
  let result = 10 / 0
  XCTAssertEqual(result, 0)
}

medium

A. XCTAssertEqual syntax is incorrect

B. Missing return type in function declaration

C. Test method name does not start with 'test'

D. Division by zero causes runtime crash

Solution

1. Step 1: Analyze the division operation

   Dividing 10 by 0 causes a runtime error (crash) because division by zero is undefined.

2. Step 2: Check other parts

   XCTAssertEqual syntax is correct, method name starts with 'test', and return type is not needed for test methods.

3. Final Answer:

   Division by zero causes runtime crash -> Option D

4. Quick Check:

   Division by zero crashes app [OK]

Hint: Division by zero always crashes at runtime [OK]

Common Mistakes:

• Thinking XCTAssertEqual syntax is wrong
• Believing test method needs return type
• Ignoring runtime errors from invalid math

5. You want to test a function that returns an optional string. Which assertion correctly verifies the function returns a non-nil value?

func testOptionalString() {
  let result = getOptionalString()
  // Which assertion to use?
}

hard

A. XCTAssertNotNil(result)

B. XCTAssertEqual(result, "")

C. XCTAssertTrue(result == nil)

D. XCTAssertFalse(result != nil)

Solution

1. Step 1: Understand the goal

   We want to check that 'result' is not nil, meaning it contains a value.

2. Step 2: Match assertion to goal

   XCTAssertNotNil checks that the value is not nil, which fits perfectly. Other options either check for empty string or nil incorrectly.

3. Final Answer:

   XCTAssertNotNil(result) -> Option A

4. Quick Check:

   Use XCTAssertNotNil to check non-nil values [OK]

Hint: Use XCTAssertNotNil to confirm value exists [OK]

Common Mistakes:

• Using XCTAssertEqual with empty string instead of nil check
• Confusing XCTAssertTrue with wrong condition
• Using XCTAssertFalse with incorrect logic