How MSC moved from full regression every release to risk-based QE.

MSC Industrial Supply has been in business 75 years. Around 60% of its revenue now runs through its e-commerce site. The rest flows through SAP and legacy ERPs — a mix of systems that have to work together so an order can move from the website through inventory to pick, pack, and ship.

Suresh Gadagoju, Senior Manager of Digital Quality Engineering at MSC, walks through the four-year shift from manual to intelligent, risk-based quality engineering across that ecosystem. Working with LTIMindtree, his team moved from executing every test case on every release to targeting only what changed, and from quarterly releases to releasing on demand.

“The right support from the customer, some runway, and aligning with your technology and service partner — that was the success mantra for us.”

If your testing has to span systems that were never designed to work together, this is the playbook.

• How to target testing by risk instead of re-running the full regression suite every release
• Why end-to-end coverage matters more than any single system when revenue flows across all of them
• What it takes to move from quarterly releases to releasing on demand, and what that frees your team to do