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. Quality Champion of the Year is the one category that goes to a person rather than a team. It went to Yasna Adhikari, Automation Test Specialist at Hansard Global.
A test at Hansard Global would find an element, click it, and come back green. Green meant the click happened. Whether the policy behind it did the right thing was a separate question, and nobody was asking it the same way twice.
Table Of Contents
Automation at Scale, with No Shared Definition of a Test
Hansard Global is an international life assurance and savings provider, and the software behind that is five integrated web applications, each one’s data and outcomes feeding the next. Life insurance rules are dense. Some workflows can’t continue until an outcome or a settlement lands, so a test fires, then waits for a person to pick it back up.
Yasna Adhikari’s team wasn’t short of automation. They’d built plenty of it. The problem was that everyone had a slightly different idea of what a test should look like, what counted as reusable, what needed verifying, and what evidence to capture. Effort drained into manual intervention, keeping evidence current, and keeping execution results lined up with Xray.
Hansard had automation, people, tools and experience. It didn’t yet have one way of putting them together.
One Agreed Way of Building a Test
So the team settled that first. One shared shape for a test, version control tied to releases, stronger verification, better evidence, agreed once and then built to instead of reinvented scenario by scenario.
Then they went after the gap between automated and fully automated. Those workflows that triggered an action and then sat waiting for a human once a settlement landed now close through Testsigma’s APIs. Smoke coverage got wider, end-to-end testing expanded, API testing came in, and the Testsigma-Xray link got tighter.
Yasna’s reasoning was short. Script count was never the measure. The quality of the feedback those scripts give back is.
A Month of Regression, down to Two Weeks
Coverage now runs at roughly 80% across the major functional and end-to-end areas. The smoke suite finishes in about an hour. A full regression pack, end-to-end tests included, went from a month to around two weeks.
Manual intervention in the long workflows has dropped, with APIs handling the outcomes and settlements that used to need someone standing by. Execution status and evidence capture automatically through Xray, so the team spends less time maintaining records and more time reading results.
The change Yasna values most doesn’t show up in any of those numbers. Her team no longer accepts an element being found and clicked as proof. A pass has to show the right thing happened and the expected response followed.
“Yasna’s recognition as Testsigma’s Quality Champion of the Year is thoroughly deserved. She has been instrumental in driving the adoption and maturity of test automation within our organisation, consistently demonstrating a strong commitment to quality, innovation and continuous improvement. Her passion for delivering reliable, efficient testing practices has had a significant positive impact on both our team and the wider business. We are delighted to see her contributions recognised by the wider testing community.”
Mathew Oasgood, Test Manager, Hansard Global Plc
Why Yasna Won Quality Champion of the Year
What tipped it for the panel was that her change outlives the project. A suite can be rebuilt. A definition of “passed” that five applications and a whole team hold to is harder to build and harder to lose, and it keeps paying after Yasna moves on to the next thing.
The Part Worth Stealing
If your suite is growing and your confidence isn’t, the gap probably isn’t coverage. Write down what your team accepts as proof that a test passed. If three people give you three answers, that’s the work.
Congratulations, Yasna. A green test at Hansard means something now, and everyone who has to trust it knows exactly what. That’s a bar worth being recognised for, and the whole team is better for where you set it.
