I will develop a playwright selenium and cypress test automation framework
Senior QA Automation Engineer, Playwright, Selenium and API Testing
Über diesen Service
Manual regression testing doesn't scale every new feature means re-testing everything that came before, and it only gets slower as your product grows.
I'm a QA Automation Engineer with 5+ years of professional testing experience, including hands-on work migrating test suites from Selenium to Playwright for faster, more reliable automation. I'll build you a clean, maintainable test automation framework using the Page Object Model design pattern, so your test suite stays easy to extend as your product changes.
What you get:
- A structured automation framework (Playwright, Selenium, or Cypress your choice, or my recommendation based on your stack)
- Page Object Model architecture for maintainable, reusable test code
- Cross-browser coverage where applicable
- Clear HTML test reports after every run
- Optional CI/CD integration so tests run automatically on every build
What I need from you: access to your web app (staging preferred), a list of the user flows you want covered, and your existing test repo if this is a migration or extension rather than a build from scratch.
Not included: manual exploratory testing or one-off bug hunting see my QA Testing gig for that. This gig is specifically for
Anwendung testen:
Website
Entwicklungstechnologie:
Java
•
JavaScript
•
Perl
•
Python
•
TypeScript
Gerät:
PC
•
Linux
•
iPhone
•
Android-Mobiltelefon
•
Windows Phone
Mein Portfolio
FAQ
What is the Page Object Model, and why does it matter?
It's a design pattern that separates your test logic from your page structure, so when your UI changes, you update one file instead of rewriting dozens of tests. It's the difference between a framework that lasts and one you throw away in 3 months.
Can you migrate our existing Selenium suite to Playwright?
Yes — I've done this professionally. I'll assess your current suite first and give you a clear picture of what carries over directly versus what needs rebuilding.
Do you write tests from scratch or work with an existing framework?
Both — tell me which in your project brief, and I'll scope accordingly.
Which framework should I choose: Playwright, Selenium, or Cypress?
If you're unsure, tell me your tech stack and browser requirements and I'll recommend one — Playwright is usually my default for new projects due to speed and reliability.
Do I get the source code?
Yes, full framework source code is yours, delivered via GitHub repo or a zip file.
Can this integrate with our CI/CD pipeline?
Yes, available as an extra or included in Premium — I primarily work with GitHub Actions.
What if my app doesn't have a staging environment?
A local build or a shared dev environment works too — just make sure I can reach it.
Do you test APIs as part of this?
UI automation is the core of this gig; API test integration is available as an add-on or included in Premium.
How do you handle test data and login credentials?
Share them securely (not in the public order chat) — I'll ask for these via the requirements form after you order.
Do you sign NDAs?
Yes, happy to sign a standard NDA before receiving repo or environment access.