Ver categorias
Explorar
Fiverr Pro
Português
$
USD
I will build e2e test automation for your saas apps
SaaS E2E QA Automation Engineer
I build Playwright & Appium test suites that run on every deployment, so your team ships faster without manual regression cycles.
What I deliver:
- Playwright web automation (login, CRUD, multi-step...
Sobre este Serviço
Is your SaaS app tested manually every release? That's slow, error-prone, and doesn't scale.
I build professional E2E test automation suites that run automatically catching regressions before your users do.
WHAT I AUTOMATE
-Login, signup, and auth flows
-Dashboard and CRUD operations
-Form validation and error states
-Multi-step user journeys
-API + UI interaction flows
-Mobile app flows (Appium) Premium
-Cross-browser testing (Chromium, Firefox, WebKit)
-CI/CD pipeline integration (GitHub Actions)
TOOLS I USE
-Playwright (web automation)
-Appium (Android & iOS mobile)
-Page Object Model architecture
-HTML test reports with pass/fail breakdown
WHAT YOU GET
-Basic Up to 10 test cases, clean Playwright suite, HTML report
-Standard Up to 30 TCs, POM structure, CI pipeline, multi-browser
-Premium 50+ TCs, web + mobile (Appium), full documentation
All code is clean, commented, and structured so your dev team can extend it after delivery.
Message me before ordering if you have a large or complex application I'll confirm scope first.
Aplicação de teste:
Software
Tecnologia de desenvolvimento:
JAVA
•
JavaScript
•
Python
•
TypeScript
Dispositivo:
PC
•
iPhone
•
Celular Android
•
Windows Phone
Meu portfólio
Perguntas frequentes
Which framework do you use and why Playwright over Selenium?
I use Playwright for web automation and Appium for mobile. Playwright is faster, more reliable, and has built-in auto-waiting which eliminates most flaky test issues that plague Selenium suites. It also supports Chromium, Firefox, and WebKit out of the box. For mobile apps, Appium is the industry st
Do you need access to my codebase?
No. I only need access to your running application — a staging or test environment URL is enough for web testing. For mobile, I need the APK (Android) or IPA (iOS) file. I never require production access or source code.
What do the delivered test files look like?
You receive a clean GitHub repository (or zipped folder) with tests organised using Page Object Model, a configuration file, a README with setup instructions, and an HTML report from the last test run. Your developers can clone it, run it, and extend it without any handholding.
Can you integrate the tests into our existing CI/CD pipeline?
Yes — Standard and Premium packages include GitHub Actions integration. If you use GitLab CI, Bitbucket Pipelines, or Jenkins, message me before ordering and I'll confirm compatibility. The pipeline runs your full test suite on every push and emails results automatically.
What if my app changes after delivery and tests break?
Minor UI changes (selector updates, text changes) are covered under the revision policy. For larger app redesigns or new features added after delivery, I offer a maintenance package — message me and I'll quote based on scope. The POM architecture I use is specifically designed to make updates fast a
