Vaïk Duhautois

QA Engineer with a developer background, I design test automation with a development-oriented approach: solid architecture, reusable patterns, native integration into CI/CD. This dual dev/QA culture naturally led me to take ownership of DevOps topics and build end-to-end foundations from scratch — now materialized in my Reticle project (see below).

My proximity to functional QA teams allowed me to evolve into a Lead QA role, involved in both automation processes and manual QA — from defining acceptance criteria to test strategy.

--

My Reticle project solves a recurring problem: the time lost bootstrapping a foundation before writing the first test. Three turnkey E2E frameworks — Selenium (Java), Playwright, and Cypress (TypeScript) — share a common architecture: Page Object Model, 25+ typed elements, YAML config, data providers, and Allure reporting. You import it as a dependency and start writing tests immediately.

A complete web app complements the chain: an interactive overlay on the target site, visual element scanning, one-click Page Object generation, integrated exploratory QA phase, allowing bug reporting while preparing the automated test foundation. Ongoing work on network interception will enable automatic capture of API exchanges to feed API tests or mocked acceptance tests.

Result:

explore → map → generate → test — what would take 3 to 4 months is done in one week.