Build
01New Test automation work from requirement to production: end-to-end tests for signup, checkout and the flows that make money; Mobile UI tests on real devices and emulators; Suites that run in CI on every pull request.
QA and testing · 5 technologies
Test automation — the regression suite that runs itself.
Manual testing does not scale with every release. I build automated end-to-end suites with Playwright or Cypress for the web and Appium or Maestro for mobile, wire them into CI, and keep them fast enough that developers actually run them.
- Technologies
- Selenium · Cypress · Playwright · Appium · Maestro
- Support
- Build · fix and maintain · upgrade and migrate · audit and advise
- Typical
- End-to-end tests for signup, checkout and the flows that make money
- Pricing
- Fixed price, or hourly from $10 by stack
- Team
- Me, plus a vetted team of 50+ for larger builds, 90% with 10+ years' experience
- Start
- Usually within one working day of agreeing the scope
01 — What I do with Test automation
build, fix, upgrade, audit
Fix and maintain
02The usual problems in existing Test automation systems: flaky tests everyone ignores, a suite that takes an hour, and no coverage of the checkout.
Upgrade and migrate
03Selenium to Playwright, brittle selectors to resilient ones, nightly runs to per-change runs.
Audit and advise
04A code, security, performance and SEO audit of your Test automation system, with a written plan you can act on with or without me.
02 — Technologies
what each one is for
Selenium
Maintaining and migrating existing suites.
Cypress
Developer-friendly browser tests.
Playwright
My default: fast, reliable, multi-browser.
Appium
Cross-platform mobile automation.
Maestro
Simple, readable mobile UI flows.
03 — Typical projects
what people usually ask for
Test automation work
that actually gets ordered.
Three shapes most Test automation engagements take. Yours may be a fourth; describe it and I will tell you honestly whether it fits.
- End-to-end tests for signup, checkout and the flows that make money
- Mobile UI tests on real devices and emulators
- Suites that run in CI on every pull request
04 — Questions
about Test automation work
How many tests do we need?
Fewer than you think. Cover the flows that earn money or break trust first. Ten reliable tests beat two hundred flaky ones.
Can tests run before every deploy?
Yes, in GitHub Actions, GitLab CI or Jenkins, blocking the deploy when something fails.
How is Test automation work priced?
A fixed price for a defined scope, or hourly from $10 depending on the stack, always with a written estimate before any work starts.
How do we start?
Send a short description of what exists and what you need. You get a reply within one working day with questions, then a scope or an estimate.
06 — Start
describe the Test automation project
Got a Test automation project?
Tell me what exists, what you need, and the deadline if there is one. I reply within one working day with questions, then a scope or an estimate.
Ahmedabad, India · IST (UTC+5:30) · --:-- IST · Mon–Fri 09:00–18:00 IST · US & EU overlap daily