By leveraging automated testing, our client reduced a 21-week testing process to just 5.5 weeks.

The Challenge:

Our client, a leading natural gas and electric utility company, had a series of seven releases scheduled to deploy. Before deployment, it was necessary to conduct user acceptance testing to ensure the products being delivered matched the needs and expectations of end-users.

Each product release was estimated to take three weeks of manual testing time
before a successful release. This meant, in total, the deployment would require
21-weeks of just manual testing time.

These looming timelines frustrated our client and threatened overall organizational timelines. Something needed to be done. That’s where automation came in.

The Testing Automation Solution:

The client leveraged our experienced Quality Assurance (QA) consultants to design and deploy a testing automation solution.

One of the first critical steps was deciding the automation toolset that would best serve our client’s needs.

Our team ultimately decided to use Custom WebDriver as our automation platform.

Custom WebDriver provided more flexibility for our technical application and is the W3 standard.

Example Test – A Script To Enroll A Customer As Marketing User.

  1. (1) Navigate to the webpage
  2. (2) Login as a marketer
  3. (3) Navigate to enrollments
  4. (4) Enter required data fields
  5. (5) Submit and Verify Success

Manual Test Process: 4 Minutes
VS
Automated : 17 Seconds

Decrease of 92.92% in execution time

The platform supported our team’s core strength in C#, used Selenium which is well supported, and Specflow which was compatible with .NET and allowed the QA team to write scripts the business could understand.

Next, the team determined which tests could be automated and which would still be easier and faster to do manually. After identifying all scripts that could be automated the QA team leveraged existing manual scripts that could easily be migrated to automated scripts.

In the end, more than 300 user interface scripts were created and used for the deployments. The best part? Many of the scripts could be re-used in future deployments outside of the scope of this project.

The Results:

  • Reduced testing time from 21-week schedule to just 5.5 weeks saving hundreds of thousands of dollars by eliminating QA time
  • Provided a foundation of scripts that could be used for future deployments, further reducing testing time for all future deployments