Sanity tests: 10–14 hrs to under 1 hour

The Challenge

Automate testing and cut sanity test times for all modules from 10-14 hours per release, since a smooth, performant experience is vital to the client's own brand credibility.

Our Solution

Automated sanity testing with Jenkins for quick regression testing of every deployment, maintained separate execution lists for Sanity/Regression/UAT scopes, and implemented dynamic waits and smart locators in WebdriverIO to reduce flakiness.

Impacts

• 100% of sanity tests automated
• 80% of regression tests automated
• Sanity tests down from 10-14 hours to under 1 hour
• Human error eliminated