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 automated tests prove the code does what the code says. They do not prove a customer can sign up, pay and get what they paid for, and nobody has clicked through the whole app since the last big release.

Our tester works through your written test specs in your priority order, exactly as written, on the build you name. Every spec ends the day as pass, fail, spec drift, blocked or not reached, with evidence for every failure.

Spec drift is the part most testing services skip. When the software works but no longer matches the spec, we tell you what changed and suggest the edit, so your specs stay worth running. Write your specs with AI from your own code, or have us write them with The Test Spec Builder.

What's included

  • One 8-hour shift of a named tester on one named build, in your priority order
  • A pre-flight check the day before, so the day is not lost to a broken login
  • Every step of every spec reached run exactly as written, on Chrome, Firefox, Edge and Safari, plus a mobile width
  • A result for every spec: pass, fail, spec drift, blocked or not reached, so you know exactly what was covered
  • Defects logged in your tracker with steps, build, browser, severity and screenshots, reproduced three times
  • A spec-drift list with suggested edits, so your specs stay accurate as the app changes
  • An end-of-day report with the next specs in line

How it works

  1. 01

    Book and send access

    Book online with your ABN or NZBN. We tell you exactly what access and material we need; the clock starts once we have it.

  2. 02

    We do the work

    An experienced employee who specialises in this task works through it, and asks before anything outside the scope.

  3. 03

    Delivered with evidence

    You get everything listed on this page, with a written account of what was done.

Before you order

Have these ready so we can start the moment you order. The delivery clock only runs while we have them.

Who it's for

Software teams with written test specs who want a person to run them before every release.

Questions

Do we need test specs first?

Yes. Each step needs an action, any data to use, and the expected result. Write them with AI from your code, or book The Test Spec Builder and we write them from your repo.

What happens when the spec and the software disagree?

If the software is wrong, we log a defect. If it works but differently from the spec, we log spec drift with a suggested edit. You decide which is right; we never edit your specs unless you ask.

Will the tester explore beyond the specs?

No. This day runs what is written, so you know exactly what was covered. Anything that looks broken outside the specs is noted as an observation. For open-ended exploratory testing, book The QA Tester Day.

What if you find no bugs?

Then you have evidence that every spec reached passed on that build, which is what you are paying for. The day is billed the same.

Can we book a day every sprint?

Yes. A standing weekly, fortnightly or per-sprint day keeps the same tester wherever possible, so they already know your app. The Resort Club makes repeat days cheaper.

Often booked alongside