Kategorien durchsuchen
Entdecken
Fiverr Pro
Deutsch
$
USD
I will reduce regression time with QA automation
QA Automation Engineer
Most QA engineers add more tests. I fix the architecture.
QA Automation Engineer, Playwright specialist – 6 years across SaaS teams. One client: 45-min CI pipeline to 15 min, flake rate from 6% to un...
Über diesen Service
Your team wants automated tests. Nobody knows where to start.
You Google a tutorial, spin up a few tests, three months later: flaky, nobody runs them, project becomes a graveyard. Built without architecture.
My fix: I build your Playwright framework from zero, the right way. Page Object Model. CI ready.
Documented. Your team extends it day one.
Not a tutorial. A production-ready repo with clean architecture, real starter tests, and CI that runs on every push.
WHAT'S INCLUDED
- Playwright project in TypeScript or Python
- Page Object Model architecture
- Starter tests: login, smoke, happy path
- GitHub Actions or GitLab CI workflow
- README + run guide for your team to extend
- ESLint, Prettier, environment config wired up
WHY ME
Six years on SaaS teams. Built test architecture from zero across multiple products. 800+ tests rebuilt for one client. 45-min CI cut to 15 min. Real docs. No lock-in.
I don't sell tutorials. I sell systems.
MESSAGE ME FIRST
Send your stack and what you want covered. One reply: yes I can help, or no and why. No pitch.
Anwendung testen:
Web-Applikation
Gerät:
PC
•
Mac
Mein Portfolio
FAQ
Why should you choose me?
Most QA freelancers sell you tests. I sell you a system your team owns. Six years on SaaS products. One client: 45-min CI to 15 min, flake from 6% to under 1%. No vendor lock-in, full docs, clean code from day one.
What's included?
Production-ready Playwright project with Page Object Model, 3 starter tests (login, smoke, one happy path), CI workflow for GitHub Actions or GitLab, full README, ESLint and Prettier config, and a video walkthrough. Higher tiers add cross-browser, more flows, API tests, and onboarding.
What's not included?
Manual QA, security or penetration testing, mobile native apps (iOS / Android), load testing at 10k+ concurrent users, and tests for features that don't exist yet. If you need those, I'll point you to specialists. I stay focused on web automation that survives.
What tech stacks do you support?
Anything Playwright can drive in a browser: React, Vue, Angular, Next.js, Nuxt, Svelte, Remix, Astro, plus server-rendered apps from Django, Rails, Laravel, .NET, Spring. The framework I build works the same way regardless. Backend language doesn't matter.
TypeScript or Python: which should I choose?
TypeScript if your team writes JS/TS. Python if your team is data-heavy (ML, analytics, backend Python). Default: TypeScript. Better Playwright API, larger community, faster runtime. I'll confirm the right fit on the discovery call.
I have flaky old tests. Should you migrate or replace them?
Usually replace. Migrating bad tests can take longer than rewriting, because the original logic was often wrong (timing, selectors, scope). I review your suite first, decide what to keep and what to throw away, and we align before I touch code.
What if our login uses SSO, OAuth, or 2FA?
All of it is automatable. SSO via storageState injection. OAuth via API token bypass. 2FA via TOTP with a test-only seed, or a non-prod backdoor flag your team controls. I'll pick the cleanest option for your stack on the discovery call.
What happens when our UI changes? Will the tests break?
That is exactly why Page Object Model exists. UI changes touch one selector file, not 50 test files. When your form field id changes, you update the page object, and dependent tests pass again. This is the difference between a framework and a pile of scripts.
Can my team maintain the framework after I leave?
Yes, by design. The README and onboarding doc cover setup, run commands, how to add a new test, how to add a new page object, and how to debug failures. Premium includes a 1-hour live transfer call. I don't sell projects you depend on me for. I sell systems you own.
What if our codebase is messy or our documentation is minimal?
That's the typical state. I have never seen a clean handover in 6 years. I read what's there, ask short questions, and decide on a starting point. You don't need to clean up before sending it to me. The mess IS the problem I'm here to fix.
