Parallel test execution in Testing Fundamentals - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use parallel test execution?

Which of the following is the main benefit of running tests in parallel?

A It guarantees that tests will never fail due to shared resources.

B It ensures tests run in a specific order to avoid conflicts.

C It reduces the total time needed to run all tests by running multiple tests at the same time.

D It automatically fixes bugs found during testing.

💡 Hint

Think about how doing many things at once affects total time.

Parallel test execution runs multiple tests simultaneously, which reduces the total testing time. It does not guarantee order or fix bugs automatically.

❓ Predict Output

intermediate

Output of parallel test simulation

Consider this Python code simulating parallel test execution with threads. What is the output?

Testing Fundamentals

import threading
import time
results = []
def test(id):
    time.sleep(0.1)
    results.append(f"Test{id} done")
threads = [threading.Thread(target=test, args=(i,)) for i in range(3)]
for t in threads:
    t.start()
for t in threads:
    t.join()
print(results)

A []

B ['Test2 done', 'Test1 done', 'Test0 done']

C ['Test0 done', 'Test1 done', 'Test2 done']

D ['Test0 done']

💡 Hint

All threads complete before printing results, but order is not guaranteed.

Threads append results after sleeping. Because threads run concurrently, the order of results in the list is not guaranteed and can vary between runs.

❓ assertion

advanced

Correct assertion for parallel test results

You run tests in parallel and collect results in a list. Which assertion correctly checks that all expected tests completed?

Testing Fundamentals

expected = {'Test1', 'Test2', 'Test3'}
results = ['Test3', 'Test1', 'Test2']

A assert set(results) == expected

B assert results == expected

C assert all(test in results for test in expected)

D assert results.sort() == expected.sort()

💡 Hint

Think about comparing collections ignoring order.

Using set comparison checks that all expected tests are present regardless of order. Option A fails because list and set are different types. Option A is true but less strict (does not check for extra items). Option A is invalid because list.sort() returns None.

🔧 Debug

advanced

Identify the cause of flaky tests in parallel execution

Tests run fine individually but sometimes fail when run in parallel. What is the most likely cause?

A Tests have syntax errors causing random failures.

B Tests use different programming languages.

C Tests run too slowly and timeout.

D Tests share and modify the same global data without isolation.

💡 Hint

Think about what changes when tests run at the same time.

Sharing global data without isolation causes race conditions and flaky failures in parallel runs. Syntax errors or slow tests would fail consistently. Different languages do not cause flaky behavior.

❓ framework

expert

Configuring parallel test execution in a test framework

In a popular test framework, which configuration option enables running tests in parallel across multiple CPU cores?

A pytest -n auto

B pytest --disable-parallel

C pytest --max-workers=1

D pytest --sequential

💡 Hint

Look for the option that automatically uses multiple cores.

The option -n auto in pytest-xdist plugin runs tests in parallel using all available CPU cores. Other options disable or limit parallelism.

Practice

1. What is the main benefit of parallel test execution in software testing?

easy

A. It automatically fixes bugs found during testing.

B. It ensures tests run one after another to avoid conflicts.

C. It runs multiple tests at the same time to save testing time.

D. It slows down tests to check for memory leaks.

Solution

1. Step 1: Understand parallel execution purpose

   Parallel test execution means running tests simultaneously, not sequentially.

2. Step 2: Identify the main benefit

   Running tests at the same time saves overall testing time and speeds feedback.

3. Final Answer:

   It runs multiple tests at the same time to save testing time. -> Option C

4. Quick Check:

   Parallel execution = faster testing [OK]

Hint: Parallel means tests run together, saving time [OK]

Common Mistakes:

• Confusing parallel with sequential execution
• Thinking parallel fixes bugs automatically
• Assuming parallel slows down tests

2. Which of the following is the correct way to enable parallel test execution in a test framework configuration?

easy

A. enableParallelExecution = false

B. runTestsSequentially = true

C. testMode = singleThread

D. parallel = true

Solution

1. Step 1: Identify enabling parallel execution

   Setting parallel = true typically enables parallel runs in configs.

2. Step 2: Check other options

   Options A, B, and D disable or prevent parallel execution.

3. Final Answer:

   parallel = true -> Option D

4. Quick Check:

   Enable parallel = true [OK]

Hint: Look for 'parallel = true' to enable parallel runs [OK]

Common Mistakes:

• Using flags that disable parallel execution
• Confusing sequential and parallel settings
• Misreading boolean values

3. Consider this pseudocode for running tests in parallel:

start test1
start test2
wait for test1
wait for test2
print('All tests done')

What will be the output if both tests pass quickly?

medium

A. test1
test2

B. All tests done

C. Error: tests cannot run in parallel

D. No output

Solution

1. Step 1: Understand parallel start

   Both tests start without waiting, so they run at the same time.

2. Step 2: Wait for both tests to finish

   The code waits for test1 and test2 to complete before printing.

3. Final Answer:

   All tests done -> Option B

4. Quick Check:

   Wait then print = 'All tests done' [OK]

Hint: Wait for all tests before printing output [OK]

Common Mistakes:

• Assuming output prints before tests finish
• Thinking tests run sequentially
• Expecting test names printed automatically

4. You configured parallel test execution but notice tests fail due to shared data conflicts. What is the best way to fix this?

medium

A. Make tests independent by avoiding shared data or using separate data copies.

B. Run tests sequentially instead of parallel.

C. Ignore failures as they are caused by parallelism.

D. Increase the number of parallel threads.

Solution

1. Step 1: Identify cause of failure

   Failures happen because tests share data and interfere with each other.

2. Step 2: Fix by isolating tests

   Making tests independent or using separate data copies avoids conflicts.

3. Final Answer:

   Make tests independent by avoiding shared data or using separate data copies. -> Option A

4. Quick Check:

   Isolate tests to fix conflicts [OK]

Hint: Avoid shared data to fix parallel test conflicts [OK]

Common Mistakes:

• Ignoring failures caused by data conflicts
• Just reducing parallel threads without fixing data
• Assuming parallel always works without changes

5. You have 10 independent tests that each take 1 minute to run sequentially. Your test framework supports running 5 tests in parallel. How long will the total test run take if you use parallel execution correctly?

hard

A. 2 minutes

B. 5 minutes

C. 10 minutes

D. 1 minute

Solution

1. Step 1: Calculate sequential time

   Running 10 tests one by one takes 10 minutes (10 x 1 minute).

2. Step 2: Calculate parallel batches

   With 5 tests running at once, tests run in 2 batches (10 / 5 = 2).

3. Step 3: Calculate total parallel time

   Each batch takes 1 minute, so total time is 2 minutes.

4. Final Answer:

   2 minutes -> Option A

5. Quick Check:

   10 tests / 5 parallel = 2 minutes [OK]

Hint: Divide tests by parallel threads for total time [OK]

Common Mistakes:

• Assuming parallel time equals single test time
• Multiplying instead of dividing tests by threads
• Ignoring batch count in calculation