How we tested a critical feature of cloud platform with zero customer defects

We got a critical(architecture level change ) feature for testing. We followed a different approach to testing this feature and we achieved zero customer defects.

Why the different approach?

Our Cloud platform is integrated with many other cloud products.We use an integrated environment for regular testing. If we directly test on the regular integrated environment then all other product teams may get disturbed if we have any critical bugs. Instead of wasting other team members time we followed a different approach.

Steps followed:

1) Dev Testing

QA provided automation tests to Developer. Developer ran all automation tests on dev environment

and fixed the defects. Provided a good stable build to QA.

2) Regular QA build testing

QA did a full round of testing on regular QA build. Ran all automation suites like Manual tests, API tests, UI tests.. etc

Verified all existing defects.

3) Testing on Cluster setup

QA did a full round of testing on Cluster setup. Ran all test suites on cluster setup.

4) Testing on Customer environment 

We simulated a customer environment. The customer who is going to get benefited more with this feature. We executed customer-specific tests.

5) Testing on Integrated environment

QA did a full round of testing. Executed all automation tests. Did not find any integration defects

6) Testing on Stage-prod

QA did sanity test of all features.

Finally, we released the feature and no defects reported by customers.