How Setting Up Automation Testing Saved 64 Hours of Manual Testing for McQueen Autocorp
Expertise Delivered
Industry
Our client,
McQueen Autocorp is a leading US-based used car selling company with a buyer network spread across the entire United States. McQueen Autocorp offers a nationwide modern car selling service, facilitates sellers with an instant offer for their car(s) using price prediction algorithms and real-time bids from an extensive network of licensed buyers.
Disclaimer - The name McQueen Autocorp is a placeholder as there is an NDA signed between both parties.
Challenge
The client worked on Agile methodology for the development of its products. Deployments at the end of a 2-week sprint required their QA team to test the entire product. This was done to ensure that none of the system changes had introduced any unexpected bugs.
Given the dynamic nature and overall complexity of the platform, manual testing alone was not efficient. Manual regression testing was time-consuming and prone to errors as the tester had to know about all the five products of the client, given that certain features were interrelated.
All in all, the QA team would test around 700+ test cases during the sprint deployment.
The entire regression testing process needed to be automated for their products. This would help in achieving better accuracy and a shorter time to market.
Solution
To provide a more scalable solution to this extensive problem, Maruti’s team proposed developing a customized Automation Testing framework that would automatically test all the manual test cases that the quality assurance team used to after sprint deployment.
The testing framework was integrated with CI (Continuous Integration) tool (TeamCity) to schedule the tests in an orderly manner. This automatically triggers the regression test suite as per defined time intervals, which eliminates the need for manual intervention.
The testing framework provides automated regression testing along with analysis and also creates automated reports. Additionally, the framework was designed so that any of the teammates with limited programming knowledge can add automated test cases independently. Adding new test cases would be a continuous improvement to keep checks and balances in place.
The Automation Testing framework was categorized into two -
UI TESTING
600+ UI-related test cases were automated using Saucelabs, a tool used to test all scenarios on any given device.
As these test cases were executed, if any of the test cases failed, the system would post the details of that test case and a recorded video onto a Slack channel.
The QA team would then manually take this test case forward by re-verifying it and creating a bug.
MICROSERVICE TESTING
1600+ microservice test cases were automated using Postman, a tool used to invoke APIs.
As the framework was built, developers could reuse the methods and prepare test cases faster.
This entire testing framework would run every day at a defined time so that all bugs and errors could be weeded out, which was earlier done only once in two weeks.
