Jun 14, 2023
No image
Unification of Execution & Automation

Unification of Execution & Automation

4-6 months
United States
view project
Service categories
Service Lines
QA and Testing
Domain focus
QA and Testing


- Too much effort would be required. Imagine 200 test cases written and changing the execution status of each test case - Due to increased manual efforts, more time will be spent in changing execution status than actually executing test cases - For each test case, a team member needs to check the report for its execution and change the status accordingly which is sluggish


- To overcome such a challenge, we have used a very fine feature of the Test link. It provides its own API through which the execution status of test cases can be updated. This API can be integrated with the Selenium automation framework. - If the test cases are automated, then obviously we need to create automation scripts for its execution. All we needed to do was, add some parameters which refer Test link API and update the status automatically. So whenever tests are run, the Selenium script will automatically update the execution status of test cases on the Test link. If the Selenium script is passed, then the status will be set to PASSED for mapped Test cases in the Test link. The same applies to FAILED and BLOCKED test cases.


- Create test cases: Create test cases with an automated type that needs to be executed via script - Create script: Create automation script which uses Test link API and integrates selenium test cases with Test link test cases with test case Ids - Execute test cases through the script: Run the created script and check the status of mapped test cases in the Test link - Outcome The approach which we adopted reduced manual efforts by a remarkable amount. Test case status is in parallel with automation execution itself if the application is having automation testing in scope.