Home » Insights » From slow automation to fast, repeatable releases
From slow automation to fast, repeatable releases
Jan 29, 2026 Automation , Case study , Quality Assurance, Test automation

This is how an enterprise team rebuilt its existing end-to-end (E2E) automation using Playwright and a continuous integration (CI) pipeline – 140 tests, around 75% faster runs, and far less rerun effort.

The client already had automated tests, but execution was slow and reliability issues meant frequent reruns and manual follow-up were necessary. They needed a modern, scalable end-to-end approach - one that could run predictably in CI, support single sign-on (SSO) environments, and produce actionable reports.

Sollers modernised the client’s test automation by rebuilding it into a reusable Playwright framework and moving execution into a GitHub Actions + AWS pipeline. The goal was to improve speed, stability, and scalability - without increasing operational overheads.

The challenge: faster delivery, same confidence

The client was caught in a familiar loop: regression cycles were too slow, execution depended on local machines, and, when failures occurred, the feedback was neither fast nor clear enough to enable efficient issue resolution. On top of that, they needed to support SSO environments and scale execution without increasing the amount of the manual work required to keep tests stable over time.

Software Quality Assurance

Finding the balance between breadth and depth of testing

CHECK OUR QA OFFER

What we built: a test automation engine, not a test script set

A reusable Playwright E2E framework

To make automation maintainable and scalable, rather than a one-off script set, we delivered a reusable framework with the following outcomes:

  • 140 automated end-to-end tests covering key user journeys and document-driven scenarios
  • A framework designed to be reused across future projects and prepared for further test development
  • A smarter rerun approach that focused on running only failed tests, shortening the feedback loops
  • Reporting that makes failures easier to trace and diagnose

Playwright supports retries and rerunning only the last failed tests, which helps to reduce manual intervention and speed up stabilisation.

CI-first execution with GitHub Actions and AWS

Instead of relying on local machines, we moved the execution process into CI, building a setup that runs reliably on a schedule and on demand. The delivery included:

  • Test runs scheduled every working day using GitHub Actions scheduling
  • AWS infrastructure to execute tests via CI rather than local machines
  • Ephemeral, on-demand agents to scale runs cleanly and securely
  • Reports generated automatically and stored in AWS S3
  • Support for running tests in an SSO environment

Why this design works at enterprise scale

We deliberately opted for a market-proven stack and a framework-driven approach to minimise long-term risk and dependency. Playwright’s popularity and active development make it easier to hire, maintain, and evolve the solution over time, while GitHub Actions enables CI-driven execution and scheduling without tying automation to individual workstations. Using ephemeral execution patterns further reduces contamination between runs and supports secure, repeatable testing in large organisations.

Results that matter

Compared to the previous automated solution, execution time dropped from around340 minutes to around 90 minutes and the effort required for reruns decreased significantly.

  • Around 75% faster automated test execution: 90 minutes vs. 340 minutes (previous automated solution)
  • 140 automated tests delivered in a reusable framework
  • Around 90% less manual work: 2–3 runs vs. 22 runs previously
  • Daily scheduled execution in CI with automated reporting
Retries and “run only failed” workflows were key to reducing manual effort while maintaining fast and actionable feedback.

The next steps

With this setup in place, the client can scale regression coverage without increasing manual effort. They can also shift testing earlier into the delivery process, rely on predictable daily runs, and expand coverage across environments and projects using the same framework. This turns test automation into an asset that grows in value over time instead of a cost that grows with complexity.

Quality at speed - with test automation.

Test automation that speeds up releases - without losing confidence
Build reliable regression and E2E suites that run in CI and give teams fast, actionable feedback.

See our Test Automation Services

Authors of the article

    Martyna Tomica - Head of Quality Assurance

 

    Elżbieta Cebulka-Szulik - Test Automation Engineer

Technology & Market Insights

Automation From slow automation to fast, repeatable releases
Read more
CEO Voices CEO Voices – Interview with Agnès Paquin, CEO of CNP Assurances IARD
Read more
Guidewire QA for Guidewire Cloud migration: a key to stay ahead in a demanding market
Read more
Guidewire Guidewire Cloud migration: faster innovation, lower costs, bigger impact
Read more
guidewire cloud
Cloud, Guidewire How to approach updates on Guidewire Cloud – from release cadence to adoption
Read more
SEE ALL INSIGHTS