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&#8217;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.



<div id="toc_container" class="no_bullets">Table Of Contents<ul class="toc_list"><li><a href="#Automation_at_scale_with_no_shared_definition_of_a_test">1 Automation at scale, with no shared definition of a test</a></li><li><a href="#One_agreed_way_of_building_a_test">2 One agreed way of building a test</a></li><li><a href="#A_month_of_regression_down_to_two_weeks">3 A month of regression, down to two weeks</a></li><li><a href="#Why_Yasna_won_Quality_Champion_of_the_Year">4 Why Yasna won Quality Champion of the Year</a></li><li><a href="#The_part_worth_stealing">5 The part worth stealing</a></li></ul></div>
<h2 id="h-automation-at-scale-with-no-shared-definition-of-a-test" class="wp-block-heading">Automation at scale, with no shared definition of a test</h2>



Hansard Global is an international life assurance and savings provider, and the software behind that is five integrated web applications, each one&#8217;s data and outcomes feeding the next. Life insurance rules are dense. Some workflows can&#8217;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&#8217;s team wasn&#8217;t short of automation. They&#8217;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&#8217;t yet have one way of putting them together.



<h2 id="h-one-agreed-way-of-building-a-test" class="wp-block-heading">One agreed way of building a test</h2>



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&#8217;s APIs. Smoke coverage got wider, end-to-end testing expanded, API testing came in, and the Testsigma-Xray link got tighter.



Yasna&#8217;s reasoning was short. Script count was never the measure. The quality of the feedback those scripts give back is.



<h2 id="h-a-month-of-regression-down-to-two-weeks" class="wp-block-heading">A month of regression, down to two weeks</h2>



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&#8217;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.



&#8220;Yasna&#8217;s recognition as Testsigma&#8217;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.&#8221;



Mathew Oasgood, Test Manager, Hansard Global Plc



<h2 id="h-why-yasna-won-quality-champion-of-the-year" class="wp-block-heading">Why Yasna won Quality Champion of the Year</h2>



What tipped it for the panel was that her change outlives the project. A suite can be rebuilt. A definition of &#8220;passed&#8221; 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.



<h2 id="h-the-part-worth-stealing" class="wp-block-heading">The part worth stealing</h2>



If your suite is growing and your confidence isn&#8217;t, the gap probably isn&#8217;t coverage. Write down what your team accepts as proof that a test passed. If three people give you three answers, that&#8217;s the work.



Congratulations, Yasna. A green test at Hansard means something now, and everyone who has to trust it knows exactly what. That&#8217;s a bar worth being recognised for, and the whole team is better for where you set it.

Nagasai Krishna Javvadi

Testsigma Quality Awards 2026: Quality Champion of the Year – Yasna Adhikari, Hansard Global

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&#8217;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. The Everyone Tests Award goes to a team that made testing something the whole organisation gets the benefit of, instead of a queue that forms in front of QA. It went to Space42.



Every new feature Space42 shipped added one more thing to manually check before the next release. The platform was adding features fast. You can do that arithmetic in your head, and Devendra Singh Josan&#8217;s team did.



<div id="toc_container" class="no_bullets">Table Of Contents<ul class="toc_list"><li><a href="#Growing_faster_than_QA_could_check">1 Growing faster than QA could check</a></li><li><a href="#Stability_first_coverage_second">2 Stability first, coverage second</a></li><li><a href="#60_automated_in_just_over_four_months">3 60% automated in just over four months</a></li><li><a href="#Why_Space42_won_The_Everyone_Tests_Award">4 Why Space42 won The Everyone Tests Award</a></li><li><a href="#The_part_worth_stealing">5 The part worth stealing</a></li></ul></div>
<h2 id="h-growing-faster-than-qa-could-check" class="wp-block-heading">Growing faster than QA could check</h2>



Space42 is the Abu Dhabi space technology company, and its QA team had been working the way good QA teams work: close to developers and product, validating new features as they were built, catching defects, running a regression pass before every release.



That held until the platform scaled. More features meant more workflows, more workflows meant more manual regression, and holding the same coverage at the same speed got harder every single cycle.&nbsp;



Two ways out were obvious and both were bad. Slow the releases down, or test less of the product.



<h2 id="h-stability-first-coverage-second" class="wp-block-heading">Stability first, coverage second</h2>



The team went after the hours instead, and they were deliberate about the order. Key workflows first, the ones eating the most manual time. Then stability, before anyone chased a coverage number, because a suite that fails at random costs more attention than the manual pass it replaced.



Only after that did they widen it. The target Devendra set the team was testing that comes back faster, stays consistent, and doesn&#8217;t get harder to maintain as the platform keeps growing. A bigger pile of scripts was never the goal.



The result is that a change now gets tested as it lands, whether or not a tester is free to look at it. QA didn&#8217;t get smaller. Its reach got bigger.



<h2 id="h-60-automated-in-just-over-four-months" class="wp-block-heading">60% automated in just over four months</h2>



Roughly 60% of Space42&#8217;s current platform scope runs on automation today, covering the key modules and critical workflows that used to eat the most manual hours. Regression that meant serial manual passes now runs in parallel and comes back faster.



That gives the team back real time, and they spend it where automation can&#8217;t help: new features, edge cases, and the failures a script won&#8217;t flag on its own.



What the team is proudest of isn&#8217;t the 60%. It&#8217;s the four months. They moved from a mostly manual regression process to covering the workflows that mattered most, and releases never slowed down to let it happen.



Next marker is 90%. The plan is more of the same: keep the suite stable, keep widening it.



<h2 id="h-why-space42-won-the-everyone-tests-award" class="wp-block-heading">Why Space42 won The Everyone Tests Award</h2>



What tipped it for the panel was the order they worked in. Plenty of teams can point at a coverage number. Space42 earned theirs by fixing stability first, in four months, without asking a single release to wait.



<h2 id="h-the-part-worth-stealing" class="wp-block-heading">The part worth stealing</h2>



Fix stability before you chase a coverage number. A flaky suite at 60% buys you nothing, and a trustworthy one at 60% buys you the rest of the year.



Congratulations to Devendra and the QA team at Space42. Sixty percent in four months is an achievement. The part that lasts is a suite the team believes when it goes red, and that&#8217;s what makes the next 30% possible.

Testsigma Quality Awards 2026: The Everyone Tests Award – Space42

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&#8217;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.



<div id="toc_container" class="no_bullets">Table Of Contents<ul class="toc_list"><li><a href="#Clearing_security_took_longer_than_testing">1 Clearing security took longer than testing</a></li><li><a href="#One_hour_a_day_for_five_days">2 One hour a day, for five days</a></li><li><a href="#Thirty-six_manual_testers_one_department_at_a_time">3 Thirty-six manual testers, one department at a time</a></li><li><a href="#Regression_finishes_before_the_team_logs_in">4 Regression finishes before the team logs in</a></li><li><a href="#Why_IndusInd_Bank_won_Best_Use_of_Agents_in_Testing">5 Why IndusInd Bank won Best Use of Agents in Testing</a></li><li><a href="#The_part_worth_stealing">6 The part worth stealing</a></li></ul></div>
<h2 id="h-clearing-security-took-longer-than-testing" class="wp-block-heading">Clearing security took longer than testing</h2>



IndusInd Bank is one of India&#8217;s largest private sector banks, and everything its QA team touched had to clear the bank&#8217;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&#8217;t fight the bank&#8217;s security setup at every turn.



<h2 id="h-one-hour-a-day-for-five-days" class="wp-block-heading">One hour a day, for five days</h2>



The team ran an experiment. An hour a day, five days a week, using Testsigma Copilot to keep widening coverage.&nbsp;



If the team could get that far on an hour a day, his engineers could put in six or seven. That&#8217;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.



<h2 id="h-thirty-six-manual-testers-one-department-at-a-time" class="wp-block-heading">Thirty-six manual testers, one department at a time</h2>



The harder work wasn&#8217;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.



<h2 id="h-regression-finishes-before-the-team-logs-in" class="wp-block-heading">Regression finishes before the team logs in</h2>



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.



<h2 id="h-why-indusind-bank-won-best-use-of-agents-in-testing" class="wp-block-heading">Why IndusInd Bank won Best Use of Agents in Testing</h2>



What tipped it for the panel was the perimeter. Unattended regression is one thing on a public web app. It&#8217;s another inside an Indian bank&#8217;s security stack, with close to 36 people who had to be convinced first, one department at a time.



<h2 id="h-the-part-worth-stealing" class="wp-block-heading">The part worth stealing</h2>



If you&#8217;re fighting for budget on automation, don&#8217;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&#8217;s the slow, unglamorous version of this work, and it&#8217;s the version that holds.

Testsigma Quality Awards 2026: Best Use of Agents in Testing – IndusInd Bank

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&#8217;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. The Quality Bar Award goes to the change that made releases safer or testing leaner, whether that&#8217;s one initiative or a whole function. It went to Spacewell, and to the QA team Arun Subramanian leads.



Spacewell&#8217;s QA team knew exactly which part of the release they dreaded. The last sprint of every two-month cycle was regression, two weeks to retest everything, and two weeks was never enough.



<div id="toc_container" class="no_bullets">Table Of Contents<ul class="toc_list"><li><a href="#Nobody_knew_what_still_worked">1 Nobody knew what still worked</a></li><li><a href="#Two_specialists_became_a_team_of_seven">2 Two specialists became a team of seven</a></li><li><a href="#Critical_bugs_down_to_about_one_a_year">3 Critical bugs, down to about one a year</a></li><li><a href="#Why_Spacewell_won_The_Quality_Bar_Award">4 Why Spacewell won The Quality Bar Award</a></li><li><a href="#The_part_worth_stealing">5 The part worth stealing</a></li></ul></div>
<h2 id="h-nobody-knew-what-still-worked" class="wp-block-heading">Nobody knew what still worked</h2>



Spacewell makes the software that organisations run their buildings and workplaces on. Web, mobile, API, and mobile stretches to kiosk devices. The legacy products had Selenium automation. The newer mobile and web apps had none at all, just functional testing by hand.



So regression became risk-based out of necessity. Run a build, log the bugs, get fixes, retest, move on. Build one might cover 400 test cases and build two only 100, and the other 300 went untested into a release that shipped anyway.



Four or five people carried all of it. Three or four critical bugs reached production every release, and 100 to 115 support tickets came back each cycle. The team priced the obvious fix, building it out in Selenium or Playwright, and the honest estimate was close to a three-year project. The bugs weren&#8217;t going to wait three years.



<h2 id="h-two-specialists-became-a-team-of-seven" class="wp-block-heading">Two specialists became a team of seven</h2>



Spacewell’s fix started with people, not scripts. Automation had been sitting with two people, in their own lane, separate from the five doing functional testing. He merged the lanes.



Seven people now do functional testing, automation, API testing, execution reporting and maintenance as one job. That was the actual goal: getting automation out of being a specialist skill that only two people in the building could touch.



Arun was clear about what he didn&#8217;t want measured. Not script count. He wanted the scripts to mean something as feedback.



<h2 id="h-critical-bugs-down-to-about-one-a-year" class="wp-block-heading">Critical bugs, down to about one a year</h2>



The automated regression suite runs at about 1,500 test cases. Mobile runs against every new build. A full run takes 16 to 20 hours.



Out of those 1,500 cases, a typical run turns up one or two failures on critical or high-priority tests. Maintenance sits under 10 to 15% most years.



Critical production bugs have gone from three or four a release to about one a year. Support tickets are down 50 to 60%. Both numbers moved together, which is the tell that quality actually improved rather than the reporting changing.



Arun&#8217;s own summary: the team just has to worry about quality now, not automation.



&#8220;Winning &#8216;The Quality Bar&#8217; award is a proud moment for Spacewell. Working with Testsigma, our QA team has scaled automation across releases and cut our testing cycles significantly. This recognition belongs to them for their consistency and relentless effort. Congratulations to the entire QA team.&#8221;



Ammar Mannan, CTO, Spacewell



<h2 id="h-why-spacewell-won-the-quality-bar-award" class="wp-block-heading">Why Spacewell won The Quality Bar Award</h2>



What tipped it for the panel was how the Spacewell team solved it. The obvious version of this project is a bigger automation team. They went the other way and made automation everyone&#8217;s job, which is why the numbers held after the first year instead of drifting back.



<h2 id="h-the-part-worth-stealing" class="wp-block-heading">The part worth stealing</h2>



Count how many people on your team can write an automated test. If the answer is two, that number is your real coverage ceiling, whatever your dashboard says.



Congratulations to the QA team at Spacewell and Arun. Three or four critical bugs a release down to about one a year is the kind of number the rest of the business feels without ever knowing who to thank.

Testsigma Quality Awards 2026: The Quality Bar Award – Spacewell

Meet this year&#8217;s winners, and hear how they keep raising the bar for quality.



Quality work is invisible when it goes well.



Nobody sends a note about the release that didn&#8217;t break. Nobody outside the QA team can name the person who caught the bug that would have taken checkout down on a Friday night. The better a testing team gets, the less anyone hears about them.



Every year on World Testers Day, we try to fix that for a few teams. This is the second year of the Testsigma Quality Awards. Nominations came in across every category, and each one carried a story that deserved more room than a form field gives it. These are the five we&#8217;re telling today.



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="2400" height="1261" src="https://s3.amazonaws.com/blog-assets-production.testsigma.com/blogs/wp-content/uploads/2026/09/09180007/image-2026-09-09T175819.126-1.png" alt="" class="wp-image-72504" srcset="https://s3.amazonaws.com/blog-assets-production.testsigma.com/blogs/wp-content/uploads/2026/09/09180007/image-2026-09-09T175819.126-1.png 2400w, https://s3.amazonaws.com/blog-assets-production.testsigma.com/blogs/wp-content/uploads/2026/09/09180007/image-2026-09-09T175819.126-1-768x404.png 768w, https://s3.amazonaws.com/blog-assets-production.testsigma.com/blogs/wp-content/uploads/2026/09/09180007/image-2026-09-09T175819.126-1-1536x807.png 1536w, https://s3.amazonaws.com/blog-assets-production.testsigma.com/blogs/wp-content/uploads/2026/09/09180007/image-2026-09-09T175819.126-1-2048x1076.png 2048w" sizes="auto, (max-width: 2400px) 100vw, 2400px" /></figure>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<div id="toc_container" class="no_bullets">Table Of Contents<ul class="toc_list"><li><a href="#Best_Use_of_Agents_in_Testing_IndusInd_Bank">1 Best Use of Agents in Testing: IndusInd Bank</a></li><li><a href="#Best_Use_of_AI_in_Testing_VFC">2 Best Use of AI in Testing: VFC</a></li><li><a href="#The_Everyone_Tests_Award_Space42">3 The Everyone Tests Award: Space42</a></li><li><a href="#The_Quality_Bar_Award_Spacewell">4 The Quality Bar Award: Spacewell</a></li><li><a href="#Quality_Champion_of_the_Year_Yasna_Adhikari_Hansard_Global_Plc">5 Quality Champion of the Year: Yasna Adhikari, Hansard Global Plc</a></li><li><a href="#What_they_say_about_the_future_of_QA">6 What they say about the future of QA</a></li></ul></div>
<h2 id="h-best-use-of-agents-in-testing-indusind-bank" class="wp-block-heading">Best Use of Agents in Testing: IndusInd Bank</h2>



At IndusInd Bank, one of India&#8217;s largest private sector banks, getting a jar file cleared took longer than testing with it. Every dependency needed sign-off, every device went through procurement, and close to 36 manual testers had good reasons to be wary of anything that touched bank data. Digvijay Singh spent an hour a day for five days proving agentic testing with Testsigma could work, then took the case to each department in turn. Regression now runs on its own before the working day starts, and the report is waiting when the team logs in.



<h2 id="h-best-use-of-ai-in-testing-vfc" class="wp-block-heading">Best Use of AI in Testing: VFC</h2>



When a test needed changing at VFC, the company behind The North Face, Vans and Timberland, someone filed a request with an outside vendor and waited for the change. The vendor&#8217;s tool covered one product. The tests were written in Chinese. <a href="https://www.linkedin.com/in/jess-tang-b9899421/">Jess Tang</a>&#8216;s team brought all of it in-house, with Atto and Testsigma Copilot drafting new tests and turning the Chinese-language ones into working automation, and an engineer signing off on every result before anyone trusts it. Checks that took days now run in about two hours. The testing is VFC&#8217;s now.



<h2 id="h-the-everyone-tests-award-space42" class="wp-block-heading">The Everyone Tests Award: Space42</h2>



Every new feature at Space42, the Abu Dhabi space technology company, added one more thing to check by hand before release, and the platform was adding features fast.&nbsp; <a href="https://www.linkedin.com/in/elfacasuco/">Mark Angelo Casuco</a>&#8216;s team could see where that ended: slower releases or thinner testing. So they built the automation into the way everyone ships, and every change now gets tested as it lands, whether or not a tester is watching. More than 60% of the platform runs on automation four months in. Releases haven&#8217;t slowed down.



<h2 id="h-the-quality-bar-award-spacewell" class="wp-block-heading">The Quality Bar Award: Spacewell</h2>



Three or four critical bugs a release were reaching the organisations that run their buildings and workplaces on Spacewell&#8217;s software. A QA team of four or five was testing several products inside two-week regression windows, and two weeks was never enough. <a href="https://www.linkedin.com/in/arunkumar-subramanian/">Arun Subramanian</a>&#8216;s fix started with people: automation stopped being the job of two specialists and became the whole team&#8217;s. Critical bugs are down to about one a year. &#8220;We just have to worry about quality now, not automation.&#8221;



&#8220;Winning &#8216;The Quality Bar&#8217; award is a proud moment for Spacewell. Working with Testsigma, our QA team has scaled automation across releases and cut our testing cycles significantly. This recognition belongs to them for their consistency and relentless effort. Congratulations to the entire QA team.&#8221; <a href="https://www.linkedin.com/in/ammarmannan/">Ammar Mannan</a>, CTO, Spacewell



<h2 id="h-quality-champion-of-the-year-yasna-adhikari-hansard-global-plc" class="wp-block-heading">Quality Champion of the Year: Yasna Adhikari, Hansard Global Plc</h2>



At Hansard Global, an international life assurance and savings provider, the tests were green. Whether the software was working was a separate question. The team had plenty of automation, but a pass only meant something had been found and clicked, and different people checked different things.&nbsp;



<a href="https://www.linkedin.com/in/yasna-adhikari-82aa8a160/" target="_blank" rel="noreferrer noopener">Yasna Adhikari</a> changed what &#8220;passed&#8221; has to mean: the evidence has to show the right thing happened. Regression went from a month to about two weeks, and a green result is something the team can act on now. Her line on it: automation is not the same thing as quality.



&#8220;Yasna&#8217;s recognition as Testsigma&#8217;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.&#8221;&nbsp;



<a href="https://www.linkedin.com/in/mathew-oasgood-47956b12a/">Mathew Oasgood</a>, Test Manager, Hansard Global Plc



<h2 id="h-what-they-say-about-the-future-of-qa" class="wp-block-heading">What they say about the future of QA</h2>



Read the five stories side by side and three things repeat, and none of them is a tool.



<ul class="wp-block-list">
<li>Automation stopped being a specialist&#8217;s job: The wall between &#8220;manual tester&#8221; and &#8220;automation engineer&#8221; is coming down, and in every one of these cases QA got bigger in scope, not smaller.</li>



<li>Regression turned from an event into a rhythm: Release cadence has outrun the two-week regression window at every company, and each of them answered the same way: run smaller, run constantly, find the problem while the change is still fresh.</li>



<li>As automation grew, &#8220;passed&#8221; got stricter: This is the one that matters most right now. The volume of tests a team can produce has gone up sharply, with AI in the authoring loop for two of these five. The teams winning with it are the ones that raised the bar for what counts as a result at the same time.</li>
</ul>



Every one of these teams did the unglamorous part, release after release, in the part of the job where nobody sends a note.



At Testsigma, we believe testing should be inclusive, autonomous, and aligned with how AI-native teams work. That’s why we built an <a href="https://testsigma.com/">agentic test automation platform</a> where anyone: devs, QAs, business professionals can contribute to quality. Where AI removes bottlenecks. And where testing moves at the speed of AI-generated code.



To every winner and every nominee: congratulations, and thank you. The recognition is well earned, and your stories make the case for strong quality practice in the AI era better than we ever could.

Announcing the 2026 Testsigma Quality Awards Winners

Agile DevOps Metrics Every Online Tech Team Should Track

Sauce Labs vs BrowserStack

At Testsigma, we believe great software isn’t only defined by speed or scale, it’s defined by how many people it empowers. True quality means building experiences that everyone can access and enjoy, no matter their abilities. That’s why one of the most meaningful recognitions in our Customer Awards this year was the Best Accessibility Testing Initiative Award.



This honor went to SpotGenius, a team that placed inclusivity at the center of their QA journey. Their commitment to ensuring that digital experiences are not just functional but accessible to all has redefined what quality assurance can achieve.



<div id="toc_container" class="no_bullets">Table Of Contents<ul class="toc_list"><li><a href="#A_Challenge_Beyond_Functionality">1 A Challenge Beyond Functionality</a></li><li><a href="#Building_Inclusivity_into_QA">2 Building Inclusivity into QA</a></li><li><a href="#The_Transformation">3 The Transformation</a></li><li><a href="#Recognition_Well_Earned">4 Recognition Well Earned</a></li><li><a href="#Looking_Ahead">5 Looking Ahead</a></li></ul></div>
<h3 class="wp-block-heading" id="h-a-challenge-beyond-functionality">A Challenge Beyond Functionality</h3>



SpotGenius is known for its innovative digital engagement solutions, serving enterprises that depend on seamless, user-friendly experiences. But as their customer base grew, so did the awareness that not all users were experiencing products the same way. Traditional QA processes, focused on core functionality, weren’t enough to ensure accessibility for users with visual, auditory, or cognitive challenges.



The team realized this wasn’t a nice-to-have, it was a necessity. Accessibility had to be embedded into the heart of their testing approach. But how do you scale accessibility testing without slowing down releases or overwhelming the QA team? That was the defining question.



<h3 class="wp-block-heading" id="h-building-inclusivity-into-qa">Building Inclusivity into QA</h3>



That’s where Testsigma came into the picture. SpotGenius began leveraging the platform not just for functional automation, but to design a scalable framework for accessibility testing. With Testsigma’s natural language interface and integrations, accessibility checks could be embedded into their regression suite, making inclusivity part of every release, not an afterthought.



Tests that once required specialized, time-intensive effort became part of their standard automation runs. The QA team could simulate accessibility scenarios early and often, ensuring issues were identified long before products reached end users. This shift gave them confidence that accessibility wasn’t dependent on a single specialist, it was baked into the process.



<h3 class="wp-block-heading" id="h-the-transformation">The Transformation</h3>



The impact was immediate and far-reaching. Accessibility validation that previously slowed down sprints was now automated and repeatable. Release cycles stayed on schedule while inclusivity standards were strengthened. Perhaps most importantly, accessibility became part of the team’s culture, something everyone, from developers to product managers, engaged with.



This wasn’t about checking a compliance box. It was about delivering experiences that every user could rely on. SpotGenius turned accessibility into a driver of innovation, proving that quality and inclusivity go hand in hand.



<h3 class="wp-block-heading" id="h-recognition-well-earned">Recognition Well Earned</h3>



It’s this dedication that earned SpotGenius the Best Accessibility Testing Initiative Award at the Testsigma Customer Awards. Their journey shows that <a data-wpil="url" href="https://testsigma.com/accessibility-checker" target="_blank" rel="noreferrer noopener">accessibility testing automation</a> isn’t just possible at scale, it’s transformative. By making inclusivity part of automation, SpotGenius raised the bar for what it means to deliver true software quality.



<h3 class="wp-block-heading" id="h-looking-ahead">Looking Ahead<gwmw style="display:none;"></h3>



As we celebrate SpotGenius, we also celebrate what their win represents for the QA community: a future where accessibility is not an exception but the expectation. Their story is proof that with the right mindset and tools, teams can go beyond building products that simply work, they can build products that work for everyone.



Congratulations once again to SpotGenius for this remarkable achievement. Your commitment to accessibility doesn’t just improve software, it improves lives.



<gwmw style="display:none;">

Testsigma Customer Awards: Best Accessibility Testing Initiative – SpotGenius

At <a href="https://testsigma.com/" target="_blank" rel="noreferrer noopener">Testsigma</a>, we’ve always believed that software quality isn’t just about catching bugs, it’s about building trust. Every product release, every digital experience, every innovation depends on a team ensuring that what reaches the customer is reliable, secure, and built to last. The Testsigma Customer Awards 2025 were created to celebrate those teams, customers who take testing beyond routine and redefine what excellence in QA looks like.



One such story comes from Sanofi, a global healthcare leader whose QA team turned a daunting challenge into a benchmark for the entire industry. Their journey not only showcases the transformative power of codeless automation but also earned them the recognition of Best Use of Codeless Test Automation at our inaugural awards.



<div id="toc_container" class="no_bullets">Table Of Contents<ul class="toc_list"><li><a href="#A_Defining_Moment">1 A Defining Moment</a></li><li><a href="#The_Turning_Point">2 The Turning Point</a></li><li><a href="#Scaling_Quality_and_Speed">3 Scaling Quality and Speed</a></li><li><a href="#Recognition_Well_Deserved">4 Recognition Well Deserved</a></li><li><a href="#Looking_Ahead">5 Looking Ahead</a></li></ul></div>
<h2 class="wp-block-heading" id="h-a-defining-moment">A Defining Moment</h2>



Sanofi’s digital platforms are more than just corporate assets, they serve as essential gateways for healthcare professionals to access critical resources like brochures, videos, and seminars that guide medical practice and patient care. With so much depending on these platforms, the margin for error was razor-thin.



Yet, behind the scenes, the QA team was up against mounting challenges. A lean group of just three members was responsible for quality across hundreds of sites. Regression testing alone stretched to three days, slowing down releases and creating a risk of defects slipping into production. Add in the complexity of enterprise security policies, Mac/iOS compatibility issues, and the need for scalability, and the cracks in the process became impossible to ignore. The team faced a turning point: either continue patching together manual processes or reimagine their approach entirely.



<h2 class="wp-block-heading" id="h-the-turning-point">The Turning Point</h2>



That reimagination came with Testsigma. After evaluating nearly ten tools, Sanofi chose Testsigma for its unique ability to combine enterprise-readiness with true ease of use. The platform’s 100% browser-based setup aligned seamlessly with strict security requirements, while its no-code, record-and-playback capabilities empowered the team to automate test cases in minutes. Suddenly, the barriers that had once slowed progress began to fall away.



Within just three months, the team had mapped and automated 54 core components of their platform. By building reusable, component-driven logins and variable-driven test designs, they created a framework that was not only scalable but also remarkably easy to maintain. For the first time, test automation wasn’t a bottleneck but a catalyst.



<h2 class="wp-block-heading" id="h-scaling-quality-and-speed">Scaling Quality and Speed</h2>



The results were transformative. Regression cycles that once consumed three days were reduced to just 80 minutes, enabling validation of 80 sites in the time it once took to validate a handful. Reported bugs dropped sevenfold, hotfixes in production became a rarity, and more than 17,000 automated test executions were carried out annually across Sanofi’s critical healthcare portals. The efficiencies gained were equivalent to adding an extra full-time QA resource, while also reducing QA costs by nearly 10 percent.



But beyond metrics, the cultural shift was equally powerful. Sanofi’s QA team evolved into a center of excellence within the organization. Other teams across the company began turning to them for guidance on automation practices, creating a ripple effect that spread innovation far beyond the original scope. As Luis Mendez, Scrum Master at Sanofi, put it:



“Testsigma has turned us into a center of excellence for QA. We are at the point where other teams across Sanofi are asking us about automation and our tools. Testsigma is making that snowball effect possible.”



<h2 class="wp-block-heading" id="h-recognition-well-deserved">Recognition Well Deserved</h2>



It is this blend of technical innovation and cultural impact that made Sanofi the clear winner of the Best Use of Codeless Test Automation award. Their story proves that when simplicity meets scalability, even the leanest QA teams can deliver enterprise-grade quality at speed. Sanofi has shown the QA community that codeless automation isn’t just a convenience but a strategy that can redefine what’s possible.



<h2 class="wp-block-heading" id="h-looking-ahead">Looking Ahead</h2>



As we honor Sanofi’s achievement, we also celebrate what it represents: that even in the face of immense complexity, there’s always room to innovate, to adopt smarter tools, and to build quality into the heart of every digital experience.



Congratulations once again to Sanofi on this well-deserved recognition. Your success is not only a milestone for your team but also an inspiration for QA leaders worldwide who are reimagining the future of software quality.

Testsigma Customer Awards: Best Use of Codeless Test Automation – Sanofi

G2’s Fall 2025 reports mark a turning point for Testsigma. From over 100 vendors that claim to be AI-powered, we’re among just 17 present in the AI-powered Automation Testing grid and one of only 8 in the Mid-Market AI grid. Add to that our new Regional Leader placements across Americas, APAC, and EMEA, plus continued recognition as Leader and Momentum Leader in Automation Testing, and our stellar debut as leaders in Test Management and the message is clear:



With <a href="https://testsigma.com">Testsigma</a>, agentic AI in testing isn’t ‘coming soon’ or ‘the future’,  it’s running in production today and driving impact already across hundreds of Quality Engineering organizations.<gwmw style="display:none;">



That’s the headline. Here’s the story behind it.



<div style="width: 500px; "><iframe src='https://www.g2.com/reports/884aee7d-ca29-43a4-9d2f-7e49ea60ae27/products/testsigma/grid.embed' id='g2-crowd-widget-default' width='500px' height='500px' frameborder='0' scrolling='no' style='border: solid 1px #eaeaea; width:100%;min-height:100%;overflow:hidden;'> </iframe> <a href=https://www.g2.com/categories/automation-testing-tools?segment=mid-market style='font-size: 12px; color: #515159; font-weight: 600'> Mid-Market G2 Grid® for Automation Testing Tools | Fall 2025 </a> </div>



<div id="toc_container" class="no_bullets">Table Of Contents<ul class="toc_list"><li><a href="#1_Big_wins_in_AI-powered_testing_proven_by_real_users_impact">1 1. Big wins in AI-powered testing, proven by real users &amp; impact</a></li><li><a href="#2_Winning_Upmarket_One_of_8_AI_Solutions_Rising_in_the_Mid-Market">2 2. Winning Upmarket: One of 8 AI Solutions Rising in the Mid-Market</a></li><li><a href="#3_Test_Management_From_Launch_to_Leadership_in_Just_5_Months">3 3. Test Management: From Launch to Leadership in Just 5 Months</a></li><li><a href="#Whats_Next_Compounding_on_the_Momentum">4 What’s Next: Compounding on the Momentum</a></li></ul></div>
<h2 class="wp-block-heading" id="h-1-big-wins-in-ai-powered-testing-proven-by-real-users-impact">1. Big wins in AI-powered testing, proven by real users &amp; impact</h2>



Hundreds of vendors in the testing space now claim to be AI-first &#8211; but only a handful are seeing meaningful customer usage of AI in production. Testsigma stands out as one of the handful solutions where users consistently report real-world value from AI-powered testing workflows.



What Atto (Testsigma’s AI coworker) makes effortless



<ul class="wp-block-list"><li>Generate tests from context: Turn stories, Jira, Figma, PRDs, or short videos into ready-to-run cases in minutes.</li><li>Execute smartly: Orchestrate manual + automated runs with parallel execution built in.</li><li>Self-heal &amp; optimize: Fix selectors/waits, refine data and coverage as the app evolves.</li><li>Agentic analysis: Analyse errors for false positives, run deep analysis so you only focus what matters</li><li>Generative bug reports: Generate dev-ready bug reports with steps, screenshots, replays, and console logs in one click.</li></ul>



Where Teams Feel the Difference



<ul class="wp-block-list"><li>The Generator accelerates authoring by 10x with AI-driven test creation while keeping suites resilient. It adapts automatically to UI/API changes with multi-attribute matching and DOM diffs, cutting maintenance effort by up to 90%.</li><li>The Analyzer pinpoints root causes with visual diffs, logs, and video replays. Failures come with RCA hints so developers get the right context on the first pass, making debugging dramatically faster.</li><li>The Bug Reporter files complete, developer-ready bug reports in a single click. It auto-captures steps to reproduce, screenshots, session replays, and console/network logs, then pushes directly to Jira, GitHub, or your tracker linked to test artifacts.</li><li>The Healer self-heals flaky tests while you control what gets updated.</li><li>Native Test Management keeps planning, test generation, execution, approvals, and reporting together with clean traceability across Jira, Azure DevOps and Linear through seamless 2-way syncs</li><li>CI/CD-first design pipes results straight into your builds for instant execution, feedback, audit-ready artifacts, and clean handoffs.</li></ul>



By mobilizing Atto and its network of agents, Testsigma turns QA from a bottleneck into a force multiplier cutting test maintenance by up to 90%, accelerating authoring by 10x, and shortening deployment cycles by 30%.<gwmw style="display:none;">



<h2 class="wp-block-heading" id="h-2-winning-upmarket-one-of-8-ai-solutions-rising-in-the-mid-market">2. Winning Upmarket: One of 8 AI Solutions Rising in the Mid-Market</h2>



Mid-market teams don’t have time for experimental tools or GPT wrappers that demo well but collapse at scale. They need AI layered on top of a proven, enterprise-grade testing platform, something that delivers value on day one and continues to grow with them beyond day 100.



<div style="width: 500px; "><iframe src='https://www.g2.com/reports/fdf31c83-9f0f-49cf-9c5d-50a92e9ffdec/products/testsigma/grid.embed' id='g2-crowd-widget-default' width='500px' height='500px' frameborder='0' scrolling='no' style='border: solid 1px #eaeaea; width:100%;min-height:100%;overflow:hidden;'> </iframe> <a href=https://www.g2.com/categories/ai-software-testing-tools?segment=mid-market style='font-size: 12px; color: #515159; font-weight: 600'> Mid-Market G2 Grid® for AI Software Testing Tools | Fall 2025 </a> </div>



With Testsigma, AI accelerates what’s already solid: a mature platform trusted for web, mobile, and API testing, at scale. Teams start with prompts, or can write tests in plain English, or record the flows they already run. The result is codeless, reusable, and data-driven tests that run in parallel with full context on failures, immediate productivity without compromise.



Inclusive testing for every role: Testsigma makes testing collaborative, not siloed. Business analysts, SMEs, manual testers, and developers can all author and maintain tests in plain English, while the platform compiles them into powerful automation for web, mobile, and API. The result is QA that reflects how the whole team builds software &#8211; everyone contributes, and quality becomes a shared responsibility.



Run at scale: Execute thousands of tests in parallel across 3,000+ browsers and devices, covering Android, iOS, web, and APIs. Whether in the cloud or on-prem, scaling test execution is as simple as one click.



Unified platform maturity: Manage planning, execution, approvals, and reporting in one place. With enterprise-grade features like SSO, role-based access control, deep security and compliance, and native CI/CD integrations (GitHub Actions, Jenkins, GitLab, Azure), Testsigma keeps QA connected to the delivery pipeline with audit-ready traceability.



<h2 class="wp-block-heading" id="h-3-test-management-from-launch-to-leadership-in-just-5-months">3. Test Management: From Launch to Leadership in Just 5 Months</h2>



We introduced <a href="https://testsigma.com/test-management-software">AI-native Test Management </a>in May 2025 to unite manual and automated testing in one workspace, powered by Testsigma’s Generator, Runner, and Bug Reporter agents. By September, it is already a Leader in G2’s Test Management category, as teams left behind spreadsheets and legacy tools for a faster, clearer way to plan, run, and sign off releases.<gwmw style="display:none;">



<div style="width: 500px;"><iframe src='https://www.g2.com/reports/1c9eb959-de69-47e7-8b54-dfc23a8bdb67/products/testsigma/grid.embed' id='g2-crowd-widget-default' width='500px' height='500px' frameborder='0' scrolling='no' style='border: solid 1px #eaeaea; width:100%;min-height:100%;overflow:hidden;'> </iframe> <a href=https://www.g2.com/categories/test-management style='font-size: 12px; color: #515159; font-weight: 600'> G2 Grid® for Test Management Tools | Fall 2025 </a> </div>



What teams achieve with Testsigma Test Management



<ul class="wp-block-list"><li>Plan smarter, faster: Map requirements and epics to suites in minutes. The Generator turns produce context into plain-English test cases complete with data, parameters, and steps in seconds.</li><li>Create from context: Build test cases directly from user stories, execution history, or captured flows. Teams go from backlogged items to structured, ready-to-run tests without duplication of effort.</li><li>Bug reporting without the back-and-forth: The Bug Reporter auto-files complete, developer-ready issues steps, replays, environment info straight into Jira or Azure DevOps, so developers get everything they need the first time.</li><li>Two-way Jira integration: Convert Jira stories into test cases instantly, sync runs and results both ways in real time, and log bugs with one click directly inside Jira.</li></ul>



Recognition in Software Testing &amp; Automation Testing



G2’s Fall reports placed Testsigma in the Leader qudrant for Software Testing and Automation Testing, two categories that matter most to modern QA teams today. The recognition reflects how teams are using Testsigma not just to run tests faster, but to open up testing to every role, simplify maintenance and reviews, and modernize the way test cases are created and managed.



<div style="width: 500px; "><iframe src='https://www.g2.com/reports/3745968d-f6d2-446a-adca-538cefea3954/products/testsigma/grid.embed' id='g2-crowd-widget-default' width='500px' height='500px' frameborder='0' scrolling='no' style='border: solid 1px #eaeaea; width:100%;min-height:100%;overflow:hidden;'> </iframe> <a href=https://www.g2.com/categories/automation-testing-tools style='font-size: 12px; color: #515159; font-weight: 600'> G2 Grid® for Automation Testing Tools | Fall 2025 </a> </div>



Why this fueled the G2 results:



The feedback fueling this recognition came directly from real QA teams. They see value in making testing accessible beyond a single automation team with business analysts, SMEs, manual testers, and developers all able to contribute in plain English. Maintenance and reviews are easier with reusable test steps and while AI agents



speed up authoring by generating test cases in seconds. The platform itself provides the enterprise-grade maturity QA leaders expect: secure access controls, seamless Jira/CI/CD integrations, and reliable scale across thousands of environments. This end-to-end solution that accelerates software automation plus a proven platform that unifies teams is what set Testsigma apart in G2’s Fall reports.



<h2 class="wp-block-heading" id="h-what-s-next-compounding-on-the-momentum">What’s Next: Compounding on the Momentum</h2>



The takeaway is simple: Atto now sits at the heart of many Quality Engineering teams, helping them ship faster with confidence, and drive measurable impact. The G2 Fall recognition is a great milestone, but what really matters is this: our AI-first approach is working where it counts, the platform is creating real lift, and delivering more value.



If you’re part of that journey already, thanks for pushing us to lead with real outcomes. If you’re curious, we’d love to show you what having Atto, as your AI-coworker, can be like for your team.<gwmw style="display:none;">



<div class="goto-wrapper">
 
 Try Testsigma today&nbsp; →
 <a href="https://testsigma.com/request-demo" class="goto-link">Book a demo link</a>
 
</div>



<gwmw style="display:none;">



<gwmw style="display:none;">