Performance testing with measure blocks in Swift - Step-by-Step Execution

Concept Flow - Performance testing with measure blocks

Start Test

↓

Setup Code

↓

Enter measure block

↓

Run code multiple times

↓

Record time for each run

↓

Calculate average time

↓

Report performance

↓

End Test

The test runs the code inside the measure block many times, records each run's time, then calculates and reports the average time to check performance.

Execution Sample

Swift

func testPerformanceExample() {
    self.measure {
        let _ = (1...1000).map { $0 * 2 }
    }
}

This code measures how long it takes to double numbers from 1 to 1000 repeatedly.

Execution Table

Iteration	Code Run	Time Taken (ms)	Action	Output
1	Double numbers 1 to 1000	5.2	Run code inside measure block	Array of doubled numbers
2	Double numbers 1 to 1000	5.0	Run code inside measure block	Array of doubled numbers
3	Double numbers 1 to 1000	5.1	Run code inside measure block	Array of doubled numbers
4	Double numbers 1 to 1000	5.3	Run code inside measure block	Array of doubled numbers
5	Double numbers 1 to 1000	5.0	Run code inside measure block	Array of doubled numbers
Average	-	5.12	Calculate average time	Average time for all runs

💡 All iterations completed, average time calculated and reported

Variable Tracker

Variable	Start	After 1	After 2	After 3	After 4	After 5	Final
timeTaken	-	5.2 ms	5.0 ms	5.1 ms	5.3 ms	5.0 ms	5.12 ms (average)
outputArray	-	Array(1000 elements)	Array(1000 elements)	Array(1000 elements)	Array(1000 elements)	Array(1000 elements)	Array(1000 elements)

Key Moments - 3 Insights

Why does the measure block run the code multiple times instead of once?

The measure block runs the code many times to get a reliable average time, avoiding random slowdowns or speedups in a single run (see execution_table rows 1-5).

Does the output of the code inside the measure block affect the performance result?

The output is created each time but not stored outside; the focus is on timing the code execution, not the output itself (see variable_tracker outputArray).

What happens if the code inside the measure block is very fast or very slow?

The measure block still runs multiple times and reports average time, so very fast code shows small times, and slow code shows larger times, helping compare performance fairly.

Visual Quiz - 3 Questions

Look at the execution table, what is the time taken at iteration 3?

A 5.3 ms

B 5.1 ms

C 5.0 ms

D 5.2 ms

💡 Hint

Check the 'Time Taken (ms)' column for iteration 3 in the execution_table.

At which iteration does the time taken equal 5.0 ms?

A Iteration 1

B Iteration 2

C Iteration 4

D Iteration 5

💡 Hint

Look at the 'Time Taken (ms)' values in execution_table rows for iterations 2 and 5.

If the code inside the measure block took longer, how would the average time in variable_tracker change?

A It would increase

B It would stay the same

C It would decrease

D It would become zero

💡 Hint

Average time is calculated from all iteration times shown in variable_tracker under 'timeTaken'.

Concept Snapshot

Performance testing with measure blocks in Swift:
- Use self.measure { code } inside XCTest
- Runs code multiple times automatically
- Records time for each run
- Calculates average time
- Helps find slow or fast code parts

Full Transcript

This visual shows how performance testing works in Swift using measure blocks. The test runs the code inside the measure block multiple times, recording how long each run takes. Then it calculates the average time to give a clear picture of performance. Variables like timeTaken track each run's duration, and the outputArray shows the result of the code run each time. Key points include why multiple runs are needed for accuracy and how the average time helps compare performance. The quiz questions help check understanding by asking about specific times and effects of changes.

Practice

1. What is the main purpose of using measure blocks in Swift XCTest?

easy

A. To measure how long a piece of code takes to run

B. To check if the code compiles without errors

C. To test if the code produces the correct output

D. To count how many times a function is called

Solution

1. Step 1: Understand the role of measure blocks

   measure blocks are used to time how long code takes to run repeatedly.

2. Step 2: Differentiate from other test purposes

   Unlike checking correctness or compilation, measure focuses on performance timing.

3. Final Answer:

   To measure how long a piece of code takes to run -> Option A

4. Quick Check:

   Performance timing = A [OK]

Hint: Measure blocks check speed, not correctness or compilation [OK]

Common Mistakes:

• Confusing performance test with correctness test
• Thinking measure checks compilation errors
• Assuming measure counts function calls

2. Which of the following is the correct syntax to start a performance test block in Swift XCTest?

easy

A. testPerformance { /* code to test */ }

B. measureBlock { /* code to test */ }

C. performanceTest { /* code to test */ }

D. measure { /* code to test */ }

Solution

1. Step 1: Recall XCTest performance syntax

   The correct syntax uses measure { } to wrap the code to be timed.

2. Step 2: Identify incorrect options

   Options B, C, and D are not valid XCTest methods for performance testing.

3. Final Answer:

   measure { /* code to test */ } -> Option D

4. Quick Check:

   Correct syntax = A [OK]

Hint: Use exactly 'measure { }' to start performance tests [OK]

Common Mistakes:

• Using outdated or incorrect method names
• Adding parentheses after measure incorrectly
• Confusing with other test function names

3. What will be the output when running this Swift XCTest performance test?

func testExample() {
    measure {
        let sum = (1...1000).reduce(0, +)
        print(sum)
    }
}

medium

A. Prints nothing and reports average time

B. Prints 500500 multiple times and reports average time

C. Prints 1000 once and reports average time

D. Compilation error due to print inside measure

Solution

1. Step 1: Understand the code inside measure

   The code sums numbers 1 to 1000, which equals 500500, then prints it.

2. Step 2: Know measure behavior

   measure runs the block multiple times, so print outputs multiple times, plus it reports average time.

3. Final Answer:

   Prints 500500 multiple times and reports average time -> Option B

4. Quick Check:

   Repeated print of sum = C [OK]

Hint: measure runs code repeatedly, so prints repeat [OK]

Common Mistakes:

• Thinking print runs only once
• Assuming measure blocks suppress output
• Expecting compilation error from print

4. Identify the error in this Swift XCTest performance test code:

func testPerformanceExample() {
    measure {
        let array = [1, 2, 3]
        array.append(4)
    }
}

medium

A. No error; code runs fine

B. measure block must not contain variable declarations

C. Cannot append to a constant array inside measure block

D. Array must be declared outside measure block

Solution

1. Step 1: Check array declaration

   The array is declared with let, making it immutable (constant).

2. Step 2: Identify mutation attempt

   Calling append(4) tries to change the constant array, causing a compile error.

3. Final Answer:

   Cannot append to a constant array inside measure block -> Option C

4. Quick Check:

   Appending to let array = D [OK]

Hint: Use var for arrays you want to change inside measure [OK]

Common Mistakes:

• Thinking measure forbids variable declarations
• Assuming array must be outside measure
• Ignoring let vs var immutability

5. You want to measure the performance of sorting a large array but avoid including array creation time in the measurement. Which is the best way to write the test using measure?

hard

A. Create the array outside measure, then sort inside measure

B. Create the array inside the measure block, then sort it

C. Create and sort the array outside measure, then print inside measure

D. Create the array inside measure, but sort outside measure

Solution

1. Step 1: Understand what to measure

   We want to measure only sorting time, not array creation time.

2. Step 2: Place array creation outside measure

   Creating the array outside measure ensures creation time is excluded.

3. Step 3: Sort inside measure block

   Sorting inside measure captures only sorting performance.

4. Final Answer:

   Create the array outside measure, then sort inside measure -> Option A

5. Quick Check:

   Exclude setup, measure only sorting = B [OK]

Hint: Put setup outside measure, test only target code inside [OK]

Common Mistakes:

• Including setup time inside measure
• Measuring nothing inside measure
• Sorting outside measure by mistake