👯Parallel Testing

Introduction

Overview

Parallel Testing in Scriptless Automation is a feature that allows multiple API test cases to run concurrently by specifying the ThreadCount parameter. This feature helps in reducing the overall execution time of your test suite by executing multiple tests simultaneously. Currently, this capability is available for API testing, while parallel execution for Web testing is under development.

Benefits of Parallel Testing

• Time Efficiency: Significantly reduce the total execution time by running multiple API tests at once.

• Resource Utilization: Efficiently utilize system resources by executing tests across multiple threads.

• Faster Feedback: Accelerate the testing process, enabling quicker identification of issues within your APIs.

Setting Up Parallel Testing with ThreadCount

Configuration

To enable parallel testing, you simply need to set the ThreadCount parameter in your configuration file. This parameter controls how many test cases will be executed simultaneously.

Example Configuration

# Parallel Testing Configuration for API
ReportName = AutomationReport
Platform = API
Env = staging
ThreadCount = 4
FAILED_RETRY_COUNT = 0
SET_TEST_SUITE_NAME = ParallelAPISuite
SET_TEST_NAME = ParallelAPITesting
TEST_IDS = ALL
GROUPS = regression

ThreadCount: This defines the number of API test cases that will run in parallel. For example, ThreadCount = 4 allows four API tests to be executed concurrently.

How It Works

• When you set ThreadCount = 4, the Scriptless Automation framework will pick four test cases and execute them at the same time.

• This concurrent execution helps in reducing the overall time needed to run the entire test suite.

• You can adjust the ThreadCount value based on your system’s capability and the complexity of the tests.

Execution Process

1. Set the ThreadCount:

   • Determine the optimal ThreadCount for your environment, considering factors like available CPU cores and memory.

   • Update the configuration file with the desired ThreadCount value.

2. Run the Tests:

   • Execute your test suite, and the framework will handle the parallel execution of the specified number of test cases.

Current Limitations

Web Testing Parallel Execution

Currently, the ThreadCount parameter is applicable only to API tests. The Scriptless Automation team is working on enabling this feature for Web testing, which will be available in future updates.

Recommendations for Web Testing

• Continue to run web tests sequentially for now.

• Monitor updates from the Scriptless Automation team for the release of parallel execution capabilities for Web testing.

Best Practices for Using ThreadCount

Optimize Resource Allocation

• Adjust the ThreadCount according to the available system resources. Too high a value might overwhelm the system, while too low might not fully utilize available resources.

Ensure Test Independence

• Make sure that the API tests you run in parallel are independent of each other to avoid issues related to shared resources or execution order.

Monitor Performance

• Keep an eye on the performance of your tests as you increase the ThreadCount. This will help you find the best balance between execution speed and system stability.

Conclusion

Summary

Parallel Testing in Scriptless Automation, enabled by configuring the ThreadCount parameter, provides an efficient way to execute multiple API tests concurrently. This feature enhances testing efficiency by reducing the total time required for test execution. Web testing support for parallel execution is under development and will be available in future updates.

Further Resources

Scriptless Automation Documentation