From acceptance criteria to test cases
I use Claude to turn acceptance criteria into scenarios ready to automate, including the edge cases that are easy to miss.
QA Automation Engineer. Based in Brazil, open to bringing confidence to teams anywhere in the world.
Software breaks. I build the test suites that bring consistency, so teams can ship big changes with confidence.
Five years in test automation, most of it owning end-to-end coverage for a SOC 2 fintech platform in the US debt-sales market: three production systems, nearly 3,000 automated tests, and the pipelines that ran them every day.
I came to QA from web design and development, so I read a UI the way a designer does and a codebase the way a developer does. AI is part of how I work every day, and I treat what it produces the way I treat any code: as something to test before trusting.
AI speeds up every part of my testing. The final call is always mine.
Modern test automation isn’t just about writing test code. It’s about deciding what deserves trust when machines build alongside us.
I use Claude to turn acceptance criteria into scenarios ready to automate, including the edge cases that are easy to miss.
Every AI-generated test case gets checked against the real requirements, which is also how I find gaps in coverage.
Claude Code alongside Playwright, with Playwright MCP to drive the browser. I review and own every line it writes.
AI reads the failure logs with me to get to the root cause faster, then helps draft clear bug reports.
Things I build for testing and for the people who test.
A dashboard for Cypress and Playwright runs
A test reporting dashboard for Cypress and Playwright. It reads results straight from CI and keeps the history of every run, so after each one a team can see what needs attention, not only what passed and what failed.
A job board built to be tested
A fictional job board I built as a practice target for software testers. Candidates apply to jobs, companies move applicants across a kanban board, and a small course store has a cart, coupons and checkout. Some of it fails on purpose.
| Item | Value | Note |
|---|---|---|
| Admin action (500) | 35% | 2.5–4 s response |
| Checkout (502) | 15% |
4xx client errors 5xx server errors
Vagalume is the target. Next come the test suites that run against it, each in its own public repository, so you can watch them catch the failures Vagalume throws on purpose. New versions of Vagalume will keep adding things to test.
Cypress suite for Vagalume
UI and API tests written in Cypress.
Playwright suite for Vagalume
UI and API tests written in Playwright, with their own set of scenarios.
REST Assured suite for Vagalume
API tests in Java, driven by the OpenAPI contract.
Platform-wide changes the test suite carried the product through.
The whole API layer was replaced. The E2E suite was the safety net that confirmed every flow still behaved the same from the user’s side.
Helped design the components, then kept the regression suite green while every screen moved over to them.
Rebuilt login handling across the suite so tests kept running against the real identity provider.
A visual change touching every page. Combined automated checks with design-QA reviews to catch contrast and layout regressions.
300 Softwares, placed with a US fintech platform
Owned test automation for three production systems on a SOC 2 fintech platform, from test strategy to the daily CI pipelines, with AI built into the workflow.
Built web applications and WordPress sites from Figma to code, with JavaScript on the front end, and did the functional testing that eventually became my job.
Independent; sports photojournalist for Metro and ESPN Brasil
Where my eye for detail comes from. Over those years I was also invited to give several talks.
Lead photographer for the book O Atleticano Vai ao Paraíso, by Fred Melo Paiva Buy