Parallel execution configuration in Selenium Java - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is parallel execution in Selenium testing?

Parallel execution means running multiple tests at the same time to save time and get faster results.

intermediate

How do you configure parallel execution in TestNG?

You set the 'parallel' attribute in the TestNG XML file to 'tests', 'methods', or 'classes' and specify 'thread-count' to control how many tests run at once.

intermediate

Why is thread safety important in parallel execution?

Thread safety ensures that tests running at the same time do not interfere with each other, preventing errors and unreliable results.

advanced

What is a common problem when running Selenium tests in parallel and how to fix it?

A common problem is sharing the same WebDriver instance across tests, causing conflicts. Fix it by creating a separate WebDriver instance for each test thread.

beginner

Example of TestNG XML snippet to run tests in parallel by classes with 3 threads:

<suite name="Suite" parallel="classes" thread-count="3">
  <test name="Test1">
    <classes>
      <class name="tests.TestClass1"/>
      <class name="tests.TestClass2"/>
    </classes>
  </test>
</suite>

What does setting 'parallel="methods"' in TestNG XML do?

A Disables parallel execution

B Runs all test methods in the same thread sequentially

C Runs all test classes in parallel

D Runs each test method in its own thread simultaneously

Setting 'parallel="methods"' runs each test method in a separate thread at the same time.

Why should each test thread have its own WebDriver instance?

A To reduce memory usage

B To avoid conflicts and ensure thread safety

C To speed up browser startup

D To share cookies between tests

Each thread needs its own WebDriver to prevent interference and errors during parallel execution.

Which TestNG XML attribute controls how many threads run in parallel?

A thread-count

B parallel

C max-threads

D concurrency

'thread-count' sets the number of threads to run tests in parallel.

What is a benefit of parallel execution in testing?

A Tests run faster by using multiple threads

B Tests run only on one browser

C Tests use less memory

D Tests run slower but more accurately

Parallel execution speeds up testing by running multiple tests at the same time.

If tests share the same WebDriver instance in parallel, what can happen?

A Tests run faster

B Tests use less CPU

C Tests may fail or behave unpredictably

D Tests run sequentially

Sharing WebDriver causes conflicts and unreliable test results.

Explain how to set up parallel execution in Selenium tests using TestNG.

Think about the XML configuration and how WebDriver instances relate to threads.

Describe common challenges when running Selenium tests in parallel and how to solve them.

Focus on what can go wrong when tests run at the same time.

Practice

1. What is the main purpose of configuring parallel execution in Selenium with TestNG?

easy

A. To run multiple tests at the same time and save execution time

B. To run tests one after another in a fixed order

C. To increase the number of test cases manually

D. To disable test execution temporarily

Solution

1. Step 1: Understand parallel execution concept

   Parallel execution means running tests simultaneously instead of sequentially.

2. Step 2: Identify the benefit of parallel execution

   Running tests at the same time saves overall test execution time.

3. Final Answer:

   To run multiple tests at the same time and save execution time -> Option A

4. Quick Check:

   Parallel execution = run tests simultaneously [OK]

Hint: Parallel means running tests together to save time [OK]

Common Mistakes:

• Thinking parallel means running tests one by one
• Confusing parallel execution with increasing test count
• Assuming parallel disables tests

2. Which XML attribute correctly sets the number of threads for parallel execution in TestNG?

easy

A. thread-count

B. parallel-count

C. max-threads

D. execution-threads

Solution

1. Step 1: Recall TestNG XML attributes for parallelism

   TestNG uses thread-count to specify how many threads run tests in parallel.

2. Step 2: Verify other options are incorrect

   Attributes like parallel-count, max-threads, and execution-threads are not valid TestNG attributes.

3. Final Answer:

   thread-count -> Option A

4. Quick Check:

   Thread count = number of parallel threads [OK]

Hint: Use thread-count to set parallel threads in TestNG XML [OK]

Common Mistakes:

• Using wrong attribute names like parallel-count
• Confusing thread-count with parallel attribute
• Misspelling thread-count

3. Given this TestNG XML snippet, how many tests will run in parallel?

<suite name="Suite" parallel="tests" thread-count="3">
  <test name="Test1"></test>
  <test name="Test2"></test>
  <test name="Test3"></test>
  <test name="Test4"></test>
</suite>

medium

A. All 4 tests run in parallel

B. 3 tests run in parallel, 1 waits

C. Only 1 test runs at a time

D. 2 tests run in parallel, 2 wait

Solution

1. Step 1: Understand thread-count and parallel attribute

   parallel="tests" means tests run in parallel. thread-count="3" limits max parallel threads to 3.

2. Step 2: Apply thread-count to number of tests

   There are 4 tests but only 3 threads, so 3 tests run simultaneously and 1 waits.

3. Final Answer:

   3 tests run in parallel, 1 waits -> Option B

4. Quick Check:

   thread-count limits parallel tests to 3 [OK]

Hint: thread-count limits max parallel tests running [OK]

Common Mistakes:

• Assuming all tests run parallel ignoring thread-count
• Confusing parallel="tests" with parallel="methods"
• Ignoring that thread-count caps parallelism

4. You configured parallel="methods" and thread-count="2" in TestNG XML, but tests still run sequentially. What is the likely cause?

medium

A. TestNG does not support parallel execution

B. thread-count must be set to 1 for parallel methods

C. Test methods share state and are not thread-safe

D. parallel attribute should be set to "tests" for methods

Solution

1. Step 1: Understand parallel methods and thread safety

   parallel="methods" runs test methods in parallel only if they are thread-safe and independent.

2. Step 2: Identify cause of sequential execution

   If tests share data or state, TestNG runs them sequentially to avoid conflicts.

3. Final Answer:

   Test methods share state and are not thread-safe -> Option C

4. Quick Check:

   Shared state blocks parallel method execution [OK]

Hint: Ensure test methods are independent for parallel execution [OK]

Common Mistakes:

• Setting thread-count to 1 disables parallelism
• Using wrong parallel attribute value
• Believing TestNG lacks parallel support

5. You want to run test classes in parallel but ensure each class uses its own WebDriver instance to avoid conflicts. Which TestNG XML configuration is best?

hard

A. <suite name="Suite" parallel="instances" thread-count="4">

B. <suite name="Suite" parallel="tests" thread-count="4">

C. <suite name="Suite" parallel="methods" thread-count="4">

D. <suite name="Suite" parallel="classes" thread-count="4">

Solution

1. Step 1: Understand parallel modes in TestNG

   parallel="classes" runs test classes in parallel, isolating each class's WebDriver instance.

2. Step 2: Match requirement to configuration

   Running classes in parallel with thread-count=4 allows 4 classes to run simultaneously, each with its own driver.

3. Final Answer:

   <suite name="Suite" parallel="classes" thread-count="4"> -> Option D

4. Quick Check:

   parallel="classes" isolates WebDriver per class [OK]

Hint: Use parallel="classes" for separate WebDriver per class [OK]

Common Mistakes:

• Using parallel="methods" causing shared driver issues
• Choosing parallel="tests" which runs test tags, not classes
• Using parallel="instances" which is less common and may confuse