Assertions (XCTAssertEqual, XCTAssertTrue) in Swift - Step-by-Step Execution

Concept Flow - Assertions (XCTAssertEqual, XCTAssertTrue)

Start Test Function

↓

Run XCTAssertEqual

↓

Compare Values

↓

Continue

↓

Run XCTAssertTrue

↓

Check Condition

↓

Continue

↓

End Test Function

The test runs assertions one by one. Each assertion checks a condition or equality. If it passes, the test continues. If it fails, the test stops and reports failure.

Execution Sample

Swift

func testExample() {
    XCTAssertEqual(2 + 2, 4)
    XCTAssertTrue(3 > 1)
}

This test checks if 2+2 equals 4 and if 3 is greater than 1, both should pass.

Execution Table

Step	Assertion	Check	Result	Action
1	XCTAssertEqual(2 + 2, 4)	2 + 2 == 4	Pass	Continue to next assertion
2	XCTAssertTrue(3 > 1)	3 > 1 is true	Pass	Test completes successfully

💡 All assertions passed, test function ends successfully

Variable Tracker

Variable	Start	After Step 1	After Step 2	Final
2 + 2	N/A	4	4	4
3 > 1	N/A	N/A	true	true

Key Moments - 2 Insights

Why does the test stop immediately if an assertion fails?

Because assertions like XCTAssertEqual and XCTAssertTrue are designed to stop the test on failure to prevent running further code that depends on correct conditions. See execution_table step 1 or 2 if failure occurred.

What happens if XCTAssertEqual compares two different values?

The assertion fails, the test stops, and reports the mismatch. This is shown in the execution_table where a 'Fail' result would stop further steps.

Visual Quiz - 3 Questions

Look at the execution_table, what is the result of the first assertion?

A Pass

B Fail

C Skipped

D Error

💡 Hint

Check the 'Result' column in row 1 of execution_table

At which step does the test complete successfully?

A Before Step 1

B Step 1

C Step 2

D After Step 3

💡 Hint

Look at the 'Action' column in execution_table row 2

If the condition in XCTAssertTrue was false, what would happen?

A Test continues to next assertion

B Test stops and reports failure

C Test ignores the failure

D Test restarts

💡 Hint

Refer to the concept_flow where failure leads to stopping the test

Concept Snapshot

Assertions in Swift tests check conditions.
XCTAssertEqual compares two values for equality.
XCTAssertTrue checks if a condition is true.
If an assertion fails, the test stops immediately.
Passing assertions let the test continue.
Use them to verify your code works as expected.

Full Transcript

This visual execution shows how Swift test assertions work. The test function runs each assertion in order. XCTAssertEqual compares two values; if they are equal, the test continues. XCTAssertTrue checks if a condition is true; if so, the test continues. If any assertion fails, the test stops immediately and reports failure. Variables like expressions are evaluated step by step. This helps catch errors early in testing.

Practice

1. What does XCTAssertEqual(a, b) check in a Swift test?

easy

A. It checks if a and b are equal.

B. It checks if a is greater than b.

C. It checks if a is less than b.

D. It checks if a is not equal to b.

Solution

1. Step 1: Understand XCTAssertEqual purpose

   XCTAssertEqual is used to compare two values for equality in tests.

2. Step 2: Match the function behavior

   It returns success if both values are equal, otherwise it fails the test.

3. Final Answer:

   It checks if a and b are equal. -> Option A

4. Quick Check:

   XCTAssertEqual checks equality = B [OK]

Hint: XCTAssertEqual means values must be the same [OK]

Common Mistakes:

• Confusing XCTAssertEqual with greater or less than checks
• Thinking it checks inequality
• Mixing it up with XCTAssertTrue

2. Which of the following is the correct syntax to check if a boolean variable isReady is true using XCTest?

easy

A. XCTAssertFalse(isReady)

B. XCTAssertEqual(isReady == true)

C. XCTAssert(isReady == true)

D. XCTAssertTrue(isReady)

Solution

1. Step 1: Identify the correct assertion for boolean true

   XCTAssertTrue is designed to check if a condition is true.

2. Step 2: Compare options

   XCTAssertTrue(isReady) uses XCTAssertTrue directly on isReady, which is the simplest and correct syntax.

3. Final Answer:

   XCTAssertTrue(isReady) -> Option D

4. Quick Check:

   Use XCTAssertTrue for true checks = A [OK]

Hint: Use XCTAssertTrue(variable) to check if true [OK]

Common Mistakes:

• Using XCTAssertFalse instead of XCTAssertTrue
• Using XCTAssertEqual unnecessarily for booleans
• Writing XCTAssert without True or False

3. What will happen when this test runs?

let result = 5 + 3
XCTAssertEqual(result, 8)

medium

A. The test will pass because 5 + 3 equals 8.

B. The test will fail because 5 + 3 does not equal 8.

C. The test will cause a syntax error.

D. The test will crash at runtime.

Solution

1. Step 1: Calculate the expression

   5 + 3 equals 8, so result is 8.

2. Step 2: Check XCTAssertEqual condition

   XCTAssertEqual compares result (8) with 8, which are equal, so the test passes.

3. Final Answer:

   The test will pass because 5 + 3 equals 8. -> Option A

4. Quick Check:

   5 + 3 = 8, XCTAssertEqual passes = A [OK]

Hint: Calculate values, then check equality assertion [OK]

Common Mistakes:

• Assuming test fails without checking actual values
• Confusing syntax error with test failure
• Thinking XCTAssertEqual compares types only

4. Identify the error in this test code:

let isActive = false
XCTAssertTrue(isActive)

medium

A. No error; the test will pass.

B. XCTAssertTrue cannot be used with boolean variables.

C. The test will fail because isActive is false but XCTAssertTrue expects true.

D. Syntax error due to missing parentheses.

Solution

1. Step 1: Check the value of isActive

   isActive is set to false.

2. Step 2: Understand XCTAssertTrue behavior

   XCTAssertTrue expects its argument to be true; since isActive is false, the test will fail.

3. Final Answer:

   The test will fail because isActive is false but XCTAssertTrue expects true. -> Option C

4. Quick Check:

   False value with XCTAssertTrue causes failure = D [OK]

Hint: XCTAssertTrue fails if condition is false [OK]

Common Mistakes:

• Thinking test passes when condition is false
• Confusing syntax error with test failure
• Believing XCTAssertTrue only works with expressions

5. You want to test a function isEven(_ number: Int) -> Bool that returns true if a number is even. Which assertion correctly tests that isEven(4) returns true?

hard

A. XCTAssertEqual(isEven(4), true)

B. Both A and B are correct

C. XCTAssertTrue(isEven(4))

D. XCTAssertFalse(isEven(4))

Solution

1. Step 1: Understand the function output

   isEven(4) returns true because 4 is even.

2. Step 2: Check assertion options

   XCTAssertEqual(isEven(4), true) uses XCTAssertEqual to compare with true, which works.
   XCTAssertTrue(isEven(4)) uses XCTAssertTrue directly on the result, which also works.

3. Step 3: Determine correct choice

   Both assertions correctly test that the function returns true.

4. Final Answer:

   Both A and B are correct -> Option B

5. Quick Check:

   Both XCTAssertEqual and XCTAssertTrue work for true checks = C [OK]

Hint: XCTAssertEqual and XCTAssertTrue both check true values [OK]

Common Mistakes:

• Choosing only one assertion as correct
• Using XCTAssertFalse incorrectly
• Confusing equality with boolean checks