Hire Automation Testers
An automated test suite is software, and it decays like software. Tests that fail at random get re-run until they pass, then muted, then ignored, and after a while the green tick in the pipeline tells nobody anything. Our automation testers spend as much time repairing that trust as they do writing new checks.
The person you hire works inside your repository and your pipeline, and answers to you. Where it is practical they write tests in the language your developers already use, so the suite does not become an island that only one person can maintain.
Test automation jobs we take on
Nearly every automation request is one of the six below, or a mix of them. If yours looks different, send it and we will say whether we can do it.
Browser tests for the journeys that pay
Sign-up, login, checkout, the forms that bring in enquiries. Written in Playwright or Cypress against stable selectors such as roles and test IDs, so a renamed CSS class does not break forty tests at once.
API and contract tests
Checks that call your endpoints directly: status codes, response schemas, authentication failures, pagination limits. They finish in seconds and catch many regressions before a browser is opened.
Repairing a flaky suite
Finding out why a test passes on one run and fails on the next. The usual causes are fixed sleeps, shared test data, tests that depend on running order, and animations. Each is fixed at the cause, not hidden behind a retry.
Wiring tests into the pipeline
Running the suite on every pull request in GitHub Actions, GitLab CI or Jenkins, split across parallel workers. Traces, screenshots and video are kept for failed runs so a developer can see what happened without reproducing it.
Moving off an old framework
Migrating a Selenium or Protractor suite to a current tool in stages. We port the tests that still earn their place, delete the ones that duplicate each other, and keep both suites running until the new one covers the same ground.
Test data and environments
Seed scripts, factories and API calls that put the application into a known state before each test and tidy up afterwards. Without this, everything else on the list stays unreliable.
Frameworks and runners in daily use
The right tool is usually the one your developers can read and maintain. These are the ones our testers work with.
- Browser
- PlaywrightCypressSelenium WebDriverWebdriverIO
- Mobile
- AppiumDetoxEspressoXCUITest
- API
- PostmanNewmanREST AssuredSupertestPact
- Load
- k6JMeterLocust
- Pipelines
- GitHub ActionsGitLab CIJenkinsAzure PipelinesDocker
- Languages
- TypeScriptJavaScriptPythonJavaC#
Choosing the level of automation tester
Writing a test that passes is easy. The levels differ in whether the person knows which tests are worth writing, and at which layer.
Junior
Adds tests to a framework that already exists, following the patterns in the repository. Can turn a written test case into a working script and mend a broken selector. Needs review on test design.
Choose when: a framework and conventions are in place and someone senior reviews pull requests.
Mid-level
Decides what to cover at which layer, builds page objects or fixtures that others can reuse, and keeps the run time under control. Traces a failure to its cause before raising it.
Choose when: the product is under active development and you want coverage to grow sprint by sprint.
Senior
Sets the test strategy: what is automated, what stays manual, what runs on each commit and what runs nightly. Builds the framework from an empty folder and teaches developers to write tests themselves.
Choose when: there is no automation yet, or the existing suite is slow, unreliable and nobody trusts it.
From your brief to a test running in the pipeline
Tell us what needs testing
Send the type of application, the framework your developers use, and whether any automated tests exist today. Access to a staging environment is worth more than a document.
Meet the tester we put forward
We send the profile of one named person and you interview them directly. If they are not right for the work, tell us and we suggest another.
One contained piece of work
Begin with a single flow, for example automating login and one purchase. It shows you how the person writes and explains tests before you agree to anything longer.
A steady weekly cycle
Tests are committed to your repository and tasks live in your tracker. Each week you receive a short note on what was covered and what is stuck. Invoicing is monthly.
The published rate for test automation
Our rates are published. Pick the role and move the sliders for an indicative budget.
Rate card
| Role | Hourly | Monthly* |
|---|---|---|
| Frontend / WordPress | $30 | $4,800 |
| Backend / API | $32 | $5,120 |
| Full-stack | $35 | $5,600 |
| Mobile (React Native / Flutter) | $35 | $5,600 |
| DevOps / Cloud | $40 | $6,400 |
| AI / Automation engineer | $45 | $7,200 |
| QA / Test engineer | $25 | $4,000 |
| UI / UX design | $28 | $4,480 |
*160 hrs/month full-time. Rates are indicative for planning, in USD (other currencies are converted at an indicative rate), and depend on seniority, contract length and timezone overlap. Longer engagements and multi-role teams are discounted — ask.
Will this arrangement suit your team?
We are a good choice when
- Your team releases often and manual regression runs are holding each release back.
- You have a suite already, but it fails at random and people have stopped reading the results.
- Your developers would write tests if someone set up the framework and the pipeline first.
- You are an agency and want automated checks on client projects without employing a tester.
Look elsewhere when
- The product is a prototype whose screens change every week. Automating it now means rewriting the tests every week too.
- You expect automation to replace all manual testing. A script checks what it was told to check and nothing else.
- You need a tester physically present at your site.
- You want a one-off review lasting a few hours. The smallest engagement we offer is 40 hours a month.
Questions automation testers hear first
Playwright, Cypress or Selenium: which should we use?
It depends on what you already have. For a new suite on a web application we usually suggest Playwright, because it drives Chromium, Firefox and WebKit from one API and waits for elements without extra code. If your team has a working Cypress or Selenium suite, keeping it is often cheaper than switching.
How much of our testing can be automated?
Stable, repeated checks automate well: regression paths, API behaviour, form validation. New features, visual judgement and usability are better tested by a person. We will say which is which for your product, and we will not quote a coverage percentage before seeing it.
Will the tests slow down our pipeline?
They can if nobody manages them. We keep fast API and component checks on every pull request, run the longer browser suite on parallel workers, and move slow or rarely useful tests to a nightly run.
Can one person do both manual and automated testing?
Yes, and on a small product that is often the sensible arrangement. The tester explores new features by hand, then automates the checks worth repeating. Tell us the split you expect so we propose someone comfortable with both.
Who keeps the test suite if we stop?
You keep all of it. Every script, fixture and pipeline file sits in your own repository from the first day, so there is nothing to hand back. The agreement sets out ownership and confidentiality before any work begins.
What happens if the tester leaves or is unwell?
We put forward a new tester and the choice is yours again, as it was at the start. The framework, the test data scripts and the run instructions are in your repository, so the new tester starts from the code and not from memory.
Describe what you need tested
A few lines will do: what the application is, which tools your developers use, and whether any tests run automatically today. We reply within one business day.