qaping

QA your game every patch, without doing the testing

Your coding agent reads each patch, decides what it puts at risk, and hands the build to real human playtesters. You get back a sentence and a verdict — with the session on video — before you ship.

Set up qapingHow it works

you ▸run QA on this patch

agentdiff touches saves and the pause menu — 2 checks affected

agentbuild published, playtest rounds filed. working on…

agentverdict: old saves no longer load. issue filed, video at 04:12

How it works

You ask. The rest is the agent's job.

  1. Install one command

    npx @qaping/cli setup connects qaping to Claude Code, Cursor, or Codex — the same agent you already build with.

  2. Your agent writes QA-PLAN.md

    Ask it to set up QA. It reads your repo and drafts a committed checklist of what your game can't afford to break — saves that must load, the first boss, the settings screen. You edit it like any other file.

  3. Every patch, humans test what needs judgment

    The agent reads the diff, picks the checks that patch touches, publishes the build, and files playtest rounds with real people from the pingfusi reviewer pool. Verdicts, questionnaire answers, and full session video land on your PR — issues filed and timestamped to the footage.

Checks don't stay expensive

When a check has settled — same result, patch after patch — your agent promotes it into a plain code test in your repo, free to run on every PR. Replaying recorded sessions on a machine is in pilot, not self-serve yet. Human rounds stay for what only judgment can answer: feel, readability, whether the boss is actually fun.

Set up in under a minute

qaping is an MCP server your coding agent calls. One command wires it up.

  1. Run one command

    Type it in your terminal, or in Claude Code, Cursor, or Codex. It sets everything up for you.

    npx @qaping/cli setup

  2. Approve the sign-in

    Sign in when prompted.

  3. Ask for QA

    Your agent authors QA-PLAN.md from your repo. From then on, “run QA” is the whole workflow.

    set up QA for my game. use qaping

Pricing

Pay for a playtester's time, per round. No subscription.

Start free

$0

20 credits when you sign up — enough for your first patch check.

Then per round

  • 2 credits per minute of a playtester's time, at 15¢ per credit
  • A default 10-minute patch check is 20 credits — $3
  • Checks promoted into your repo's code tests run free, forever

Run QA on your next patch

One command to set up. The free credits are enough for your first patch check.

Set up qaping