CASE STUDY

How Setting Up Automation Testing Saved 64 Hours of Manual Testing for McQueen Autocorp

Expertise Delivered

QA

Industry

Automotive

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.

Automate testing, minimize costs, and expedite success.




Phone

Don't take our word for it, take theirs!

Technology Stack

Automation Testing.png

Results

  • 64 hours of manual testing efforts were reduced every sprint release
     
  • Resources were better utilized to plan for the upcoming release
     
  • Test cases were tested more efficiently
Our Process
Sprint Planning
The QA process begins with the user story. By working with the Business Analysts, the QA team determines the requirements and defines the acceptance criteria for the story. With better visibility, the team can effectively plan the testing strategy for the forthcoming stories.
Story Kick-off
This is a crucial review stage where the developers, BA and QA teams conduct a comprehen- sive discussion to identify the scope of the story and prioritize relevant test scenarios. Inputs are taken from everyone involved in the process to minimize redundancies and gain clarity.
Test Scenarios Creation
The QA team begins to prepare test data, identify the manual and automated test scenarios, followed by the steps for their implementation. The developer and BA also review the scenarios to help validate the functionality for each test case.
Automated Test Scenario Implementation
Before diving into the automation phase, the QA team identifies which scenarios can be suc- cessfully automated. We follow test automation best practices and use enterprise-grade tools and software for efficient implementation, thereby reducing the margin of error with each iteration.
Story Testing
At this stage, a preliminary build is ready for the QA team to run manual test scripts, while main- taining internal code quality. Usability and exploratory testing is done to check key scenarios for errors, and simulate the end-user functionality of the software.
Automation Test Execution
With every iteration, numerous automated tests are run through the CI/CD deployment pipe- line. This enables quicker bug detection and closure, seamless coordination between multiple teams, and lesser turnaround time for product release.
Release Testing
This is the acid test phase of the software. The build is tested for intended performance and functionality in live production environment. The objective is to verify if all the requirements are accurately met while also being stringently tested for quality.
Sprint Demo
This is where the stakeholders come together for a high-level overview of the product. At this stage, the product is a work in progress, and through client feedback, the QA team gathers infor- mation about any new requirements or expectations based on what has been achieved so far.
Automation Test Maintenance
Whenever there is a state change in the system, the automated tests require immediate updation for the software to perform smoothly. The team needs to periodically refactor these tests for better maintainability, speed, and more targeted automation.
Sprint Planning
The QA process begins with the user story. By working with the Business Analysts, the QA team determines the requirements and defines the acceptance criteria for the story. With better visibility, the team can effectively plan the testing strategy for the forthcoming stories.
Story Kick-off
This is a crucial review stage where the developers, BA and QA teams conduct a comprehen- sive discussion to identify the scope of the story and prioritize relevant test scenarios. Inputs are taken from everyone involved in the process to minimize redundancies and gain clarity.
Test Scenarios Creation
The QA team begins to prepare test data, identify the manual and automated test scenarios, followed by the steps for their implementation. The developer and BA also review the scenarios to help validate the functionality for each test case.
Automated Test Scenario Implementation
Before diving into the automation phase, the QA team identifies which scenarios can be suc- cessfully automated. We follow test automation best practices and use enterprise-grade tools and software for efficient implementation, thereby reducing the margin of error with each iteration.
Story Testing
At this stage, a preliminary build is ready for the QA team to run manual test scripts, while main- taining internal code quality. Usability and exploratory testing is done to check key scenarios for errors, and simulate the end-user functionality of the software.
Automation Test Execution
With every iteration, numerous automated tests are run through the CI/CD deployment pipe- line. This enables quicker bug detection and closure, seamless coordination between multiple teams, and lesser turnaround time for product release.
Release Testing
This is the acid test phase of the software. The build is tested for intended performance and functionality in live production environment. The objective is to verify if all the requirements are accurately met while also being stringently tested for quality.
Sprint Demo
This is where the stakeholders come together for a high-level overview of the product. At this stage, the product is a work in progress, and through client feedback, the QA team gathers infor- mation about any new requirements or expectations based on what has been achieved so far.
Automation Test Maintenance
Whenever there is a state change in the system, the automated tests require immediate updation for the software to perform smoothly. The team needs to periodically refactor these tests for better maintainability, speed, and more targeted automation.

More social proof incase you're still on the fence

Our Clients Review
Our Happy Clients
Review Everything
Why choose Maruti Techlabs?
14+ years experience
Start as quickly as week
Recurring cost of training and benefits - $0
Risk of failure? Next to none. 4.8/5 NPS on Clutch
Certified PMs & delivery teams
Rapid deployment & on-time delivery of projects
Complete transparency
Robust communication across shared channels
Agile & lean startup methodology
Experience across 16 industries

Years of Experience

Professionals

Projects Delivered

NPS on Clutch

Services
  • Software Product Development
  • Artificial Intelligence
  • Data Engineering
  • DevOps
  • UI/UX
  • Product Strategy
Case Study
  • DelightfulHomes (Product Development)
  • Sage Data (Product Development)
  • PhotoStat (Computer Vision)
  • UKHealth (Chatbot)
  • A20 Motors (Data Analytics)
  • Acme Corporation (Product Development)
Technologies
  • React
  • Python
  • Nodejs
  • Staff Augmentation
  • IT Outsourcing
Company
  • About Us
  • WotNot
  • Careers
  • Blog
  • Contact Us
  • Privacy Policy
mtechlogo.svg
Our Offices

USA 
5900 Balcones Dr Suite 100 
Austin, TX 78731, USA

India
302, Regency Plaza,Nr. Anandnagar Crossroads,
Satellite, Ahmedabad, Gujarat- 380015

clutch_review
goodfirms_review
Social
Social
Social
Social
©2024 Maruti TechLabs Pvt Ltd . All rights reserved.

  • Software Product Development
  • Artificial Intelligence
  • Data Engineering
  • DevOps
  • UI/UX
  • Product Strategy

  • DelightfulHomes (Product Development)
  • Sage Data (Product Development)
  • PhotoStat (Computer Vision)
  • UKHealth (Chatbot)
  • A20 Motors (Data Analytics)
  • Acme Corporation (Product Development)

  • React
  • Python
  • Nodejs
  • Staff Augmentation
  • IT Outsourcing

  • About Us
  • WotNot
  • Careers
  • Blog
  • Contact Us
  • Privacy Policy

USA 
5900 Balcones Dr Suite 100 
Austin, TX 78731, USA

India
302, Regency Plaza,Nr. Anandnagar Crossroads,
Satellite, Ahmedabad, Gujarat- 380015

©2024 Maruti TechLabs Pvt Ltd . All rights reserved.