Quality that
ships with confidence.

MCP as the integration layer

Rather than building brittle point-to-point integrations between tools, MCP provided a structured protocol for connecting multiple systems with consistent context sharing — making the AI layer aware of requirements, test state, and automation results simultaneously.

Maestro as the automation target

Maestro's YAML-based, human-readable syntax made it a natural fit for AI-generated test flows — the output is reviewable and editable by engineers, not a black box.

Engineers in the loop

Generated tests were proposed, not auto-merged. Engineers reviewed and approved flows before they entered the suite, preserving quality control while removing the blank-page burden of writing coverage from scratch.

Cypress over Java + Selenium

I led two structured POCs and ruled out Java + Selenium despite it being the familiar choice. The onboarding complexity didn’t fit a team that included interns, and the verbosity would slow delivery. With multi-brand expansion already anticipated, I chose Cypress and designed the Page Object architecture with that scale explicitly in mind.

Percy over BackstopJS

I identified that functional assertions alone wouldn’t catch visual regressions on a CMS-driven, image-heavy frontend. After evaluating both tools, Percy won on CI/CD integration quality and baseline management reliability.

k6 over JMeter

Performance testing wasn’t on the original roadmap. I identified the gap, made the case for its inclusion, and chose k6 over JMeter for its code-first approach and native fit with our pipeline — JMeter’s GUI-oriented model would have created unnecessary friction.

Deferring Robot Framework rewrite — then migrating at the right time

I spotted structural problems in the existing mobile suite early but assessed that an immediate rewrite would be more disruptive than valuable. I made the deliberate call to hold, and later led the architectural migration to Maestro when the project maturity and team capacity justified it.

OWASP ZAP as a pipeline gate

I integrated ZAP directly into CI/CD so security scans ran automatically on every build, treating security as a continuous delivery concern rather than a last-minute check.