QA & Automation · Project-based
QA and test automation so every release ships without surprises
I design the cases that matter, automate regression with Cypress or Playwright and keep it alive in your pipeline. Three years in QA with Stockagile, VHIR and Accenture, on top of almost six in technical roles.
- I reply within 24 h
- No lock-in
- Barcelona · remote
- ES · CA · EN
- home.speccarga con título, H1 y CTA visibles en la primera pantalla
- seo.speccada página tiene un único H1, título y meta description
- legibilidad.specninguna página desborda en horizontal a 320 px
- contact.specun envío instantáneo (bot) no llega a Web3Forms y el mensaje se conserva
- a11y.specenlaces y botones tienen nombre accesible
78 tests · 15 files · mobile and desktop, on every release
Proof
- 3 years in QA
- Stockagile · VHIR · Accenture (UPRO, Red.es)
- Cypress · Playwright · Postman · Docker
- This site ships its own E2E suite
What you get
- Test plan and cases
- E2E suite in your CI
- API collection
- Reports with traceability
- Documentation
Sound familiar?
- Every deployment is scary and gets tested by hand, in a rush, too late.
- Users find the bugs before the team does.
- There are tests, but nobody maintains them and nobody trusts them anymore.
- You need coverage without hiring someone full time.
If any of these situations rings a bell, I can help. Tell me about it →
What's included
- Audit of the current state: risks, coverage and quick wins
- Test plan and cases prioritised by risk
- E2E suite with Cypress or Playwright, integrated in Bitbucket Pipelines, GitHub Actions or your CI
- API testing with Postman when the project calls for it
- Defect reporting and traceability in Jira or your tool
- Documentation so the team can maintain it without me
How we work
Diagnosis
I review the product, the pipeline and what already exists. Out come the risks and a short plan.
Plan
Prioritised cases, suite architecture and acceptance criteria agreed with you.
Automation
I build the suite, wire it into CI and make it stable: no flaky tests, no false positives.
Handover
Report, documentation and a session with the team so the suite stays alive.
Ways of working
No lock-in: per project, hourly or on a monthly basis. Fixed quote after the first conversation.
Fixed-scope project
An E2E suite or an audit with a defined scope and deadline.
Tell me about your product: Fixed-scope projectHourly
A bank of hours for ad-hoc testing, releases or test maintenance.
Tell me about your product: HourlyMonthly retainer
QA embedded in your team a few days a month, with regression and release support.
Tell me about your product: Monthly retainer
Frequently asked questions
Cypress or Playwright?
It depends on your stack and your team. Playwright covers more browsers and works great with TypeScript; Cypress is comfortable for teams already using it. I have built suites with both and recommend whichever gives you less friction.
Do you integrate with my CI?
I have left suites running in Bitbucket Pipelines (at VHIR), where they validated every deployment, and in GitHub Actions (this site), where they run on every change before it goes live. I have worked with Jenkins too, though not in production. If you use another one, I check it before committing.
How long does an E2E suite take?
A first useful block (the critical flows, running in CI) is usually ready in two or three weeks. Then it grows by risk, not by volume.
Do you do manual testing only?
Yes. For launches, apps or sites without a suite, I run exploratory and functional testing with a report and traceability.
Do you work under NDA?
Yes, no problem. I can say who I have worked for, since I was employed at each place, but QA work is internal to the company: that is why I tell what I did and with what, and show no screenshots or data.