How MindK cut their regression cycle to about an hour.

The challenge: Regression ran manually, not on automated tests.

The team’s testing was mostly manual. APIs got checked in Postman. A little Playwright covered a part of automation, depending on the project.

The team was five people: four manual testers and one engineer who could write automation code. That split was the problem. Regression is the same checks, run again and again, and the people who knew the product best couldn’t automate any of it.

Code-based automation was slow to build and slower to keep alive.

MindK already tried the code route. It was writing tests in a framework, and it would keep doing so. But every test took an engineer’s time to build, and more time to fix whenever the app changed.

What the team wanted was specific. A tool where "everyone can write tests easily", that cut the time a framework takes, and that didn’t turn into a maintenance job of its own.

Why Testsigma: A tool the manual testers could run themselves.

MindK ran a short trial on the client project with Testsigma. The reason it stuck with them how manual testers could also build automated tests themselves.

How they got there: Automating priority scenarios, not everything.

MindK didn’t throw out its code automation. It split the work. The manual testers took the regression scenarios into Testsigma. The automation engineer kept the checks that needed code: reading emails, text messages and PDFs.

The team didn’t chase a coverage number. It worked through what mattered most and stopped there. In a short span, the team’s top-priority scenarios were in Testsigma.

A schedule run that fits 100 deploys a day.

The client’s test environments take a lot of builds. Running the whole suite on every one made no sense. So the team runs regression on a daily schedule against the client’s servers, plus a short sanity check before bigger releases.

The result: Regression runs every day, and the testers do other work.

The change is what they get to do while the tests run. A regression plan that runs every day in about an hour and a quarter. It’s down from about a full day of manually executing the regression suite.

One engineer owns the suite, the rest test new features.

The automation suite now needs only one person, not five. Dmytro Rudenko, a QA engineer who built most of the test cases, maintains it and runs it. He decides what gets automated next.

That freed the rest of the team for work that can’t be automated yet: the new features coming through every sprint.

What’s next

The regression suite is the base. The next step for MindK is testing at the pace the client ships.