The QA Tester Day
A full day of one QA tester, on the dates you book, so your customers stop being the people who find your bugs. Up to 40 cases run against one named build, every fault written up with steps a developer can follow.
Your developers test what they just built, which is the one thing they are worst at seeing. So the regression nobody looked for reaches a customer, and you find out from a support ticket on a Friday.
Each day you book is one full working day with a QA tester. You choose the shape of the day and they work one named build of your product: your written test specs run step by step, exploratory sessions hunting the edge cases a script cannot reach, and every fault raised in your own tracker with the environment, the steps, the severity and the evidence attached. Book a series of dates, one before each release if you like, and we keep the same tester wherever we can, so they arrive knowing your product and where it tends to break.
We sell the testing and the record of it, never a bug count. A day that runs your cases and finds nothing is a delivered day, billed like any other, and the report shows exactly what was covered so you can act on a clean result instead of wondering about it. Book one day, or as many as your releases need.
What's included
One full working day (8 hours) of one QA tester, on a date you book
Up to 40 scripted cases run against one named build, or six timed exploratory sessions, or a mix, your call each day
Faults raised in your own tracker with steps, environment, severity and evidence, so developers fix instead of decipher
Fixes retested against the build they landed in, and the neighbouring behaviour checked with them
Your written specs checked as they run: where the app works but no longer matches a step, you get a screenshot and a one-line edit to bring the spec up to date, kept out of the bug count
A written coverage record at the end of every day: what was tested, what was found, what carries over
As many days as you need, booked one at a time or as a series, with the same tester kept across a series wherever we can
Before you order
Have these ready so we can start the moment you order. The delivery clock only runs while we have them.
A test or staging environment we can reach (not production), and a way to tell which build is deployed, such as a version page or a version number on screen
A login for each role we need to test, created for our tester's email, plus any test data those journeys need
An invite for our tester into your bug tracker: Jira, Linear, GitHub Issues, GitLab, Azure DevOps or Shortcut
Your written test specs or test-management tool if you have them, or the user stories we should test from
Your five to ten most important user journeys, and a weekday at least three working days ahead with the working hours you want
How it works
Book it — pay the fixed price and tell us the target environment. No scoping call first.
We deliver — an experienced specialist runs our standard workflow for this exact task. You can watch progress and message them in the portal.
Hand-off — you get the deliverables, the documentation, a rollback snapshot, and a walkthrough if you want one.
Who does it
A salaried Support Resort specialist with more than ten years in the field, working from a runbook we've been refining since 2003 — supervised by senior management, never a marketplace contractor. You'll see who is assigned and can message them about this task directly in your portal.
FAQ
Ask about this task
Our assistant knows the scope document and runbook behind this service. Ask what's covered, what isn't, or whether it's the right task for your situation.
Answers come from our published scope documents. Prefer a person? Switch to the "Email us" tab — a senior manager replies personally, usually the same weekday.
Related services
The Test Spec Builder
A test analyst reads your code with AI, checks each step in your running app, and writes manual test specs your testers, or ours, can follow without asking questions.
The Playwright Test Suite Day
A test automation engineer spends a day turning the flows you choose into Playwright tests, written by hand or drafted with AI, and hands you a pull request of tests that passed three runs in a row.
The Front-End Developer Day
One full day of a senior front-end developer clearing the queue nobody schedules: designs built, tablet layouts repaired, and the CSS four people have patched put back in order.
The Accessibility Alignment
One page design tested against all 55 Level A and AA criteria in WCAG 2.2, with a keyboard and a screen reader as well as a scanner, then fixed and handed back with a sheet showing what happened to every one.