← Back to work

Case study

Test Automation Architect · QA Strategy Lead

Apr 2023 – Feb 2025

Enterprise Software · Regulatory Technology

ERS

Two back-to-back engagements with ERS — first establishing the QA strategy and automation framework on the Core project, then leading the Cyprus rollout with multi-country deployment and a framework migration from Playwright/TypeScript to Cypress/JavaScript.

−orders of magnitude

Regression runtime

2 back-to-back

Engagements

Multiple

Countries deployed

Overview

ERS — the European regulatory and registry platform — brought me in as the QA strategy lead for two consecutive initiatives. The Core project came first (foundational framework). The Cyprus rollout followed (multi-country deployment with a framework re-platform mid-flight).

ERS Core — Test Automation Architect (Apr 2023 – Jan 2024)

Established the overall QA strategy and automation framework from scratch.

  • Built a Cypress + JavaScript automation framework tailored to the Angular frontend and .NET Core backend
  • Reduced smoke and regression runtimes by multiple orders of magnitude through architectural refactoring and smarter parallelization
  • Integrated automated tests into Azure DevOps CI/CD pipelines for continuous validation on every merge
  • Authored test cases covering registry functionalities, UX routes, and form validations
  • Worked with cross-functional teams on detailed test documentation and comprehensive reporting

ERS Cyprus — Test Automation Architect (Jan 2024 – Feb 2025)

Led the Cyprus-specific rollout, including a mid-engagement framework migration.

  • Established initial automation using Playwright with TypeScript
  • Transitioned the framework to Cypress with JavaScript mid-project to align with the organization’s evolving standards — without disrupting delivery
  • Incorporated Azure DevOps workflows with aligned requirements and detailed test plans
  • Successfully deployed across multiple countries, each with localized validation needs

Why it matters

Two distinct engagements, back-to-back, each with different technical constraints. Reducing regression times by orders of magnitude isn’t a one-time win — it’s what happens when someone takes the time to understand what the pipeline is actually doing versus what it’s supposed to do. And re-platforming mid-engagement without slipping delivery is what “senior” actually means.