I will do playwright or cypress test automation with bdd and ci
Performance and load testing, SLO driven, verify your NFRs, not guess
Informazioni su questo servizio
Tired of flaky tests nobody trusts?
End-to-end test automation and QA automation with Playwright or Cypress: automation testing your team can trust.
Most test suites rot within months: brittle selectors, random red builds, and in the end the team switches the suite off and goes back to manual checks before every release.
I build automation that stays green and stays readable. Playwright or Cypress tests in TypeScript or JavaScript, wired into CI so every pull request is checked automatically.
What's included:
- Page objects or BDD (Gherkin) specs your whole team can read
- Cross-browser runs on Chromium, Firefox and WebKit
- CI pipeline: GitHub Actions, GitLab or Jenkins
- Trace, screenshot and video on every failure
- Repo, a green CI run and a short handover note
Why me?
- 22 years in QA, Full Stack QA and Tech Lead
- Currently building Playwright suites for a US pharmacy platform
- Public BDD framework example in my portfolio
Not sure which package fits? Message me your app and stack, and I'll reply with an honest recommendation.
Applicazione di testing:
Applicazione web
Tecnologia di sviluppo:
Java
•
JavaScript
•
Node.js
•
React
•
TypeScript
Dispositivo:
PC
•
Mac
•
Linux
Il mio portfolio
FAQ
Why should you choose me?
22 years in QA as Full Stack QA and Tech Lead. I'm currently building Playwright suites for a US pharmacy platform. You get tests your team can read and trust, wired into CI, not a fragile script that breaks next sprint.
What's included?
Playwright or Cypress tests in TypeScript or JavaScript, page objects or BDD specs, cross-browser runs, trace, screenshot and video on failure, an HTML report and the full repo. Standard and Premium add a CI pipeline on every pull request.
What's not included?
Writing or fixing your application code, manual exploratory testing, native mobile apps (iOS or Android) and load testing. Test data and accounts come from your side. Ongoing maintenance after delivery can be a separate order.
Which package should I choose?
Basic: 1 core flow, 5 to 8 E2E tests in 1 browser. Standard: 15 to 25 regression tests with page objects, cross-browser and CI. Premium: a full BDD framework with network mocking, accessibility checks, GitHub Actions, docs and a handover call.
Playwright or Cypress, which one should I choose?
For most new projects I recommend Playwright: real cross-browser (incl. Safari engine), parallel runs and great traces. If your team already uses Cypress, I extend and stabilise it instead of rewriting. We decide together on day one.
We already have tests but they are flaky. Can you fix them?
Yes. I find the root causes (timing, test data, shared state, brittle selectors), fix or quarantine them and add retries only where justified. You get a short report of what was wrong and how to keep it from coming back.
Will the tests run in my CI?
Yes. Standard and Premium include a pipeline for GitHub Actions, GitLab CI or Jenkins that runs on every pull request and publishes the HTML report, traces and videos as artifacts. Basic ships with a one-line local run command.
What do you need from me to start?
The app URL (staging is ideal), a test account, the 1 to 3 user flows that matter most, and access to your repo if the tests should live there. If you have no repo yet, I deliver a clean standalone project.
Can my team maintain the tests after you finish?
That is the whole point. Clear naming, page objects or BDD steps, no magic waits, and a README on how to add a new test. You own all the code. Premium includes a handover call with your developers.
Can you also test my API or mobile app?
API: yes, I can add API checks to the suite, or see my separate API testing gig. Mobile web: yes, via Playwright device emulation. Native iOS or Android apps are out of scope for this gig. Message me and we'll find the right fit.

