Case studies
Results on real projects
We come into very different contexts, with one constant: turning QA into a system that is traceable, maintainable and useful to the business.
MedTech client
Structuring and scaling QA in a MedTech environment
1,500+ test cases in Xray · ~500 API checks · ~250 E2E checks
Planning SaaS
From a critical regression in Excel to ~100 tests run daily
~100 automated tests · Daily CI
German startup
Building the QA function from scratch in a startup
~200 automated tests · 8-month engagement
International SaaS/LMS
Long-term quality engineering on a SaaS platform
1,000+ tests in the suite · 4+ years of collaboration
MedTech client
Structuring and scaling QA in a MedTech environment
Context
The client had a QA team and E2E/API automation, but test management lived on Confluence pages, the frameworks used static data, and the suites had no continuous integration.
What we did
We centralised and migrated more than 1,500 cases to Xray; reworked the Playwright and Karate suites with a more maintainable architecture, Page Object Model and data created and torn down through the API; set up CI in Jenkins with reporting; and left a roadmap of further improvements.
Result
A QA process that is traceable and repeatable, with ~500 API checks in Karate and ~250 E2E checks in Playwright inside a quality ecosystem with test management and CI.
1,500+ test cases in Xray · ~500 API checks · ~250 E2E checks
Stack · Xray · Jira · Playwright · Karate · Jenkins
Planning SaaS
From a critical regression in Excel to ~100 tests run daily
Context
A regression suite that mattered to the product was kept in Excel, and there was no automation at all.
What we did
We turned the priority scenarios into a maintainable Playwright suite, with Page Object Model, data created and cleaned up through the API, and daily CI runs from the start of the project.
Result
Around 100 critical tests moved from being run by hand to automated, recurring feedback, cutting the reliance on manual regression for those flows.
~100 automated tests · Daily CI
Stack · Playwright · Test data via API · CI/CD
German startup
Building the QA function from scratch in a startup
Context
The client had neither a QA team nor a defined quality pipeline.
What we did
We ran an initial audit and defined the QA workflow, brought in Xray and structured manual testing, built E2E automation with Selenium and API automation with REST Assured, wired data preparation to the APIs, set up scheduled and on-push runs with reporting, prepared Postman collections and documented the whole process.
Result
The company went from having no defined QA function to having process, test management, documentation, CI and a base of roughly 200 automated tests.
~200 automated tests · 8-month engagement
Stack · Xray · Selenium · REST Assured · Postman · CI/CD
International SaaS/LMS
Long-term quality engineering on a SaaS platform
Context
A SaaS/LMS platform with several product areas, many integrations and a distributed QA team. On a mature product quality does not rest on a single E2E suite: it takes automation, APIs, integrations, exploratory testing and accessibility together, without losing a useful feedback time.
What we did
We built E2E automation with Playwright inside a suite of over a thousand tests, and API testing with Playwright, Postman and pytest. We tested integrations and asynchronous flows over Pub/Sub, set up CircleCI pipelines for the E2E suites and for the integration tests, migrated test management from Qase to Xray, and joined refinement to define scenarios before anything was built. We added accessibility to the process and evaluated the AI-based features, analysing the results in LangSmith.
Result
A QA practice where exploratory testing, E2E and API automation, integrations, accessibility and AI quality are part of the same delivery cycle. The long collaboration has let coverage and infrastructure grow at the pace of the product.
1,000+ tests in the suite · 4+ years of collaboration
Stack · Playwright · CircleCI · Xray · LangSmith · Postman · pytest
Does your case look like one of these?
In a first 30-minute call we work out which of these you recognise, and where the work would start.
Book a 30-min call