Documentation StudioOps Production
StudioOps

QA & Playtest

Builds, bugs, per-build tests, playtests and a status report.

What it is

QA & Playtest logs every build someone plays and links it to a milestone. Bugs carry a severity (Blocker, Major, Minor, Cosmetic), who handles them and a status that only ends when verified in the next build; the ones still open are flagged as carried over. Test cases come from the Blueprint's QA nodes and, if the project goes to console, from its requirements: on each build you mark Pass, Fail, Blocked or N/A, and a failure becomes a bug already linked. Playtests record how many players and what kind (no personal data), whether it's fun from 1 to 5 and where they got stuck or bored, with quick capture from your phone; every finding becomes a bug or goes to "Not yet". Each build has its summary, a ready-for-milestone signal and a status report to send your publisher.

What it solves

Bugs live in a chat or a spreadsheet and nobody knows which are still open.
Every bug with severity, owner and build; the unfixed ones carry over to the next build on their own.
"We tested it" doesn't say what was tested.
Test cases from the Blueprint and console, with Pass/Fail per build: "46 of 50 passing".
What happened in the playtest is forgotten the next day.
You take notes from your phone while they play and every finding becomes a bug or a saved idea.

Tutorial: how to use it

  1. 1
    Log the build

    Name, date, platforms and the milestone it's for.

  2. 2
    Run the tests

    Mark each case; a failure opens the bug already filled in.

  3. 3
    Run the playtest

    How many players, whether it's fun and what you saw, from your phone.

  4. 4
    Send the report

    The build's bugs, tests, playtest and risks, ready to copy or print.

Shortcuts & tips

  • On your phone, "Note while they play": pick Stuck, Bored, Liked or Other, type and press Enter.
  • Pressing the same result again on a test sets it back to "not run".
  • A fixed bug can only be verified in a later build.
  • If the project uses Console, its requirements show up as tests; turn them off with one button.

How it connects