Modernising quality engineering at a UK property-technology company.

Challenge

Reapit’s product teams needed faster, more comprehensive feedback on the quality of their changes. QA was moving from a predominantly manual approach towards modern Quality Engineering, while supporting an established product estate across the UK and EMEA.

Baseline

The legacy desktop automation framework used TestArchitect, with regression execution taking around 15 hours. That made each complete run a lengthy feedback cycle. Alongside desktop modernisation, we needed systematic API coverage and a more consistent approach to automation across teams.

My role

As Head of QA for the UK and EMEA, I owned the regional quality strategy and led distributed QA leads, working with engineering leadership and aligning our approach with the wider global organisation.

I set the modernisation priorities, guided tooling and resourcing decisions, and worked with QA leads and engineers to turn the strategy into working frameworks and broader coverage. Delivery was a team effort: my responsibility was to establish the direction, support the people delivering it, and keep the work focused on measurable improvements.

During my time at Reapit, I also received the Rising Star Award at the company’s Global Kick-Off.

Intervention

Modernised desktop automation

We migrated the legacy TestArchitect framework to FlaUI. This was the central automation improvement: regression execution fell from approximately 15 hours to 1–2 hours, giving teams results within a much shorter feedback cycle.

Established comprehensive API endpoint coverage

We introduced an API testing framework using Playwright and extended automated coverage to 100% of endpoints. This added a dedicated layer of service-level verification alongside desktop testing.

Strengthened the regional Quality Engineering approach

I worked with QA leads across the UK and EMEA to establish shared direction for automation, tooling and quality practices, aligned with the wider global strategy. This included mentoring QA leaders and advising engineering leadership on capability, investment and resourcing.

Made coverage more useful for release decisions

Alongside framework modernisation, we connected automated checks to the requirements and risks they covered and reported coverage by product area. This helped teams explain what had been verified and identify where further testing was needed.

Evidence

The clearest outcome was faster regression feedback, supported by comprehensive API endpoint coverage and a more consistent approach to Quality Engineering across distributed teams.

Starting point

About 15 hours

End point

1–2 hours

Results

Desktop automation

Migrated from TestArchitect to FlaUI

Regression execution

Reduced from 15 hours to 1–2 hours

Execution-time reduction

Approximately 87–93%

API automation

Introduced a Playwright API testing framework

API endpoint coverage

Reached 100%

Quality leadership

Established shared direction across UK and EMEA QA teams

Unit

Execution time of one complete automated regression run

Scope

The desktop regression suite: on TestArchitect before the migration, on FlaUI after it.

My contribution

I owned the regional quality strategy, set the modernisation priorities, guided tooling and resourcing decisions, and worked with QA leads and engineers to turn the strategy into working frameworks and broader coverage. Delivery was a team effort.

Caveat. The timing improvement refers to regression execution, rather than the full release process. The API figure describes endpoint coverage; it does not imply that every input, permission combination or failure scenario was covered.

Limitations

Faster regression execution and 100% endpoint coverage are not, on their own, evidence that fewer defects reached customers, and this page makes no such claim. Reporting coverage by product area is described as a delivered practice; no figure is published for it.