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.

You know you should have test specs. Nobody has time to write them, and the few that exist were written for a version of the app you retired a year ago.

With read access to your repository and a login to a running environment, our analyst maps your flows from the code, walks each one in the app, and writes specs in your priority order. Every step has an action, the data to use and the expected result.

AI helps draft, but every step is checked in the running app before it is delivered. The code also shows your validation rules, so we add the negative paths people forget.

What's included

  • One 8-hour shift of a named test analyst on your repository and running app
  • Specs for your flows in priority order, each step with action, data and expected result
  • Negative-path specs from your validation rules, up to five per flow
  • Every step verified in the running app; nothing unverified is delivered
  • Delivered as Markdown in a pull request, or as CSV for TestRail, Zephyr, Xray or Qase
  • A coverage note listing flows covered and flows not yet reached

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

Teams who want manual testing but have no written specs, or specs that no longer match the app.

Questions

What access do you need?

Read-only access to the repository and a login to a running test or staging environment. We never need production access to write specs.

How many specs fit in a day?

It depends on the size of your flows. We agree the priority order at the start, write complete specs in that order, and list what was not reached.

Do you use AI on our code?

Yes, to draft specs, using only the files for the flows in scope. Booking this task authorises that under our Terms. Every step is then checked by a person in the running app.

Do you run the specs too?

Not in this task. Book a Manual Testing Day to have them run, or a Playwright Test Suite Day to automate them.

Often booked alongside