I will migrate your cypress or selenium tests to playwright
QA Lead Playwright, TypeScript, Test Automation
About this Gig
Playwright is faster, more reliable, and free of the limitations teams hit with Cypress (iframes, multi-tab, cross-browser) and Selenium (speed, flakiness). If your suite is holding you back, I'll migrate it properly.
I'm a QA Lead with 11+ years in automation I've built and maintained large suites in all three frameworks, so nothing gets lost in translation:
- Full migration to Playwright + TypeScript with page-object architecture
- Equivalent or better coverage verified test-by-test
- Faster suite: parallel execution and auto-waiting replace sleeps and retries
- CI pipeline updated (GitHub Actions, GitLab, Jenkins)
- Side-by-side comparison report: runtime, pass rate, coverage
What I need: repo access and a way to run your current suite (or CI logs).
Suites vary a lot message me with your test count and framework version for an exact quote. The packages cover typical sizes.
Testing application:
Web application
Development technology:
Java
•
JavaScript
•
TypeScript
Device:
PC
•
Mac
•
Linux
FAQ
Why Playwright over Cypress?
Free parallelisation, all three browser engines, better iframe/tab/multi-origin handling, faster runs.
Will we lose any coverage?
No. The comparison report maps every original test to its migrated equivalent.
Our tests are in Java (Selenium). Does that matter?
No — I work in both Java and TypeScript. The language switch is part of the migration.

