Test automation of a Sales and Operations platform

Success Stories

Being a complex Sales and Operations platform with best in-class functionalities and with new versions of the product being planned on a quarterly basis, regression and functional testing remained a major challenge in meeting the release cycle and Geval6 helped ease the situation through automation of testing.

About the Customer

For more than 2 decades, our customer has been helping people realize the dream of owning a low-cost, home-based franchise in the home services industry. Over the years, has built a few thousand strong franchisee network across several cities in North America and Mexico. Our customers proven business model is to provide a life-changing opportunity for independent franchise owners and this is done with hands-on training, comprehensive marketing support driving brand awareness, and a results-based leadership team.

Problem Statement

The sales and operations platform is going through a lot of new additions in terms of features/improvements and bug fixes. It is essential to ensure that the business-critical features are always working fine irrespective of the number of changes the application is going through.

Testing the application for its stability and reliability from the UI point of view is very time-consuming. Hence, automation of the smoke and regression tests help in saving a lot of manual testing efforts. The objective is to include test automation process as part of the build process and should be run

  • On daily builds and

  • On-demand in any environment.

Our Solution

Testing of the platform was planned to evolve as follows

Our Solution

  • Stage
  • Smoke Testing

    Happy path coverage to assure the intra-release stability of the application.

  • Functional Regression

    End to end functional flow of the application to ensure the stability of the application for each released version in different environments.

  • Continuous

    Automation script generation integrated into sprints. Test automation will no longer be an independent activity.

Automation was achieved using Selenium WebDriver in Cucumber, BDD and Data Driven framework to evaluate the stability of the application for each released version. The table provides some metrics about our test automation efforts

  • Parameter
  • Total # of test cases


  • Total # of test cases automated


  • # of LOC of scripts


  • Automation Coverage


  • Cost per bug fix reduced by


Team Structure

Our automation team structure is as follows

Team Structure Figure - 1

Our Automation Test Team worked closely with our Agile Development Team, which also comprised our manual test team.

Process followed

Test automation process essentially had a one-time planning phase

  • Feasibility Analysis

  • Tool and Framework selection/setup

  • Test Strategy

  • Test Plan

Sprint Development
  • Test Case Design

  • Test Script Development

  • Smoke Test Script Execution

  • Regression Test Script Execution

  • Generate Reports and Results Analysis

Technology Portfolio

Behaviour Driven Tool

Object Repository Design Pattern

Test Automation Framework

Web Automation Framework

Script Language

Testing Framework

Build Automation

*All Trade Marks belong to the respective owners

Benefits Accrued
  • Manual testing efforts brought down by more than 50%

  • Cycle release cycle was reduced by about 2 days.

  • Production release cycle was reduced by more than 7 days

  • Higher Overall Test Coverage

  • Effective and detailed defect reporting including publishing results instantly through email to all stakeholders.

  • Ability to perform Testing on multiple concepts and Test Environment.