Browse categories
Explore
Fiverr Pro
English
$
USD
Valeriia M is unavailable until Aug 8, 2026
You can still contact the seller.
I will do QA automation for web mobile apps and API using playwright selenium cypress
Ukraine
I speak English, Ukrainian, Russian
2 orders completed
QA Engineer, Manual Automation Testing, Web, Mobile, API
I’m a QA Engineer specializing in manual and automation testing for web, mobile, and API products. I help teams release stable software by running functional, regression, smoke, exploratory, and UI te...
About this Gig
Tired of manually re-testing features after every release?
As a QA Automation Engineer / SDET, I build reliable automated testing frameworks for Web, Mobile, and API. I catch regressions before production saving hours of repetitive manual QA on every deployment.
️ What I Deliver:
- Web & Mobile E2E Testing: Automated flows using Playwright, Cypress, Selenium WebDriver, and Appium (for Android & iOS).
- API Automation: Verification of REST APIs with Postman, Swagger / OpenAPI, and Rest Assured.
- Scalable Frameworks: Page Object Model (POM) & BDD (Cucumber, Pytest) written in Python, JavaScript, or TypeScript.
- CI/CD Pipeline Setup: Automated execution via GitHub Actions, GitLab CI, Jenkins, and Docker.
- Reports & Management: Allure Report outputs (with pass/fail logs & screenshots) synced with Jira, TestRail, or Xray.
- Cloud Execution: Cross-browser testing on BrowserStack or Sauce Labs.
Tools & Tech Stack: Playwright | Selenium | Cypress | Appium | Python | JS/TS | Pytest | Cucumber | Postman | Rest Assured | Jenkins | GitHub Actions | GitLab CI | Docker | Allure Report | Jira | TestRail
Please contact me before ordering with your app details (staging/demo access) and target flows Ill conf
Testing application:
Website
Device:
PC
•
iPhone
•
Android mobile phone
My Portfolio
FAQ
Which automation framework do you recommend — Selenium, Cypress, or Playwright?
It depends on your stack. Playwright and Cypress are faster to set up and great for modern JS/TS apps; Selenium has broader language/browser support and works well for legacy or cross-language projects.
Do I need to provide access to my source code?
No — I test through the UI like a real user would, so a working URL (staging or demo) with test credentials is enough. Source code access can help for deeper integration but isn't required.
Can you integrate the tests into our CI/CD pipeline?
Yes, included in the Premium package (GitHub Actions), and available as an add-on on Basic/Standard.
What if my app doesn't have a staging environment?
That's fine — we can test against a demo account on production as long as it won't affect real user data, or you can set up a simple staging build; happy to advise on the safest approach.
Do you write documentation so our team can maintain the tests?
Yes, included from the Standard package up — clear setup instructions and comments so your developers can run and extend the suite without me.
