An ACCELQ test job can contain multiple test cases, either from a data-driven Scenario or from a test suite (a collection of Scenarios). The Run dialog displays the test case count when you select a suite or scenario.
ACCELQ runs each test case as an independent flow and supports parallel execution to reduce overall run time. The system automatically collates results from all parallel threads and generates a unified report for the complete test job.
Setting up Parallel Execution
- In the Run dialog, expand the "Agent/Parallel Execution" section.
- Select your target execution Agent.
- Enter the desired parallel thread count for this run. The available range is based on your selected Agent's capacity.
Important Considerations:
-
When running a Static Test Suite in parallel, the sequential order defined in your suite will not be preserved, as test cases are assigned to threads as they become available.
-
If your application under test is sensitive to mouse movements (hovers etc.) or keyboard inputs, a higher parallel execution count may cause conflicts. Adjust your parallel count based on your application's sensitivity.
-
If you select a parallel count that exceeds your host Agent's configured capacity, the actual parallel execution will be limited to the Agent's maximum capacity.
Configuring Parallel Execution Capacity for an Agent
- Navigate to the Agent Dashboard Portal and click "Edit Configuration".
- Specify the maximum parallel execution count for this Agent.
- Be sure to restart the Agent.
Note: Since each test case launches a new browser instance, ensure your Agent machine has adequate system resources (memory and CPU) to handle your desired parallel execution count.
If you are using the command line Agent (without the Dashboard portal), you can set this parallel count in the Agent.properties file as shown below:
Be sure to restart the Agent after setting the parallel count.
Comments
1 comment
Hi.. Can I get more detail on below?
When you are running a Static Test Suite, parallel execution does not guarantee the order of execution of tests, since the test cases are picked up as and when a thread gets freed up.
How can we ensure the order of execution in suite (static/filterbased) when run in parallel?
Please sign in to leave a comment.