The Testsigma Quality Awards are in their second year. Quality work is invisible when it goes well, and nobody sends a note about the release that didn’t break. Every World Testers Day we fix that for a few teams.
Nominations came in across all four categories this year, from customer QA teams of every size, and the panel judged them on the strength of the story and impact. Best Use of Agents in Testing goes to a team where the system pursues a goal on its own, plans, acts and retries, while a person sets the objective and reads the outcome. It went to IndusInd Bank, and to the automation programme Digvijay Singh built there.
At IndusInd Bank, getting a testing tool cleared took longer than testing with it.
Table Of Contents
Clearing Security Took Longer Than Testing
IndusInd Bank is one of India’s largest private sector banks, and everything its QA team touched had to clear the bank’s own defences first. A firewall. A WAF layer. Every single Selenium dependency whitelisted one at a time, which took real effort every time. Getting a device meant a trip through procurement.
Testing ended up scattered across a handful of tools, mostly manual, with more effort going into getting set up than into the testing itself.
Digvijay Singh wanted one thing: a single solution that wouldn’t fight the bank’s security setup at every turn.
One Hour a Day, for Five Days
The team ran an experiment. An hour a day, five days a week, using Testsigma Copilot to keep widening coverage.
If the team could get that far on an hour a day, his engineers could put in six or seven. That’s the reason IndusInd Bank onboarded Testsigma at all. Multiple journeys for the main app moved in parallel, and the team started generating test cases straight from screenshots.
Thirty-Six Manual Testers, One Department at a Time
The harder work wasn’t technical. Close to 36 people had been doing purely manual testing, and plenty of them had real worries about automation touching bank data or reaching outside the network. Queries came in from different departments.
Digvijay took them one department at a time and answered each objection where it was raised. Manual QA staff got reskilled into automation. A few of them now run things on their own.
Regression Finishes before the Team Logs in
The bank has close to 1,500 test cases automated, and the regression suite is still growing as more journeys go in.
The daily difference is the one the team feels. Testers used to run a manual regression pass and then start testing. Now regression runs on its own before the working day begins, and the report is already sitting there each morning, showing what needs attention.
Why IndusInd Bank Won Best Use of Agents in Testing
What tipped it for the panel was the perimeter. Unattended regression is one thing on a public web app. It’s another inside an Indian bank’s security stack, with close to 36 people who had to be convinced first, one department at a time.
The Part Worth Stealing
If you’re fighting for budget on automation, don’t build the business case on a slide. Build one journey yourself, on an hour a day, and show your leadership what a week of that looks like.
Congratulations to Digvijay and the QA team at IndusInd Bank. Thirty-six people moved across, and regression now finishes before anyone walks in. That’s the slow, unglamorous version of this work, and it’s the version that holds.
