Git Qa

git-qa

Your test sheet runs itself. You watch, and sign off each case with one key.

git-qa is an open-source human-in-the-loop QA runner. An AI agent works through your test sheet on Android, iPhone, web and desktop apps; you watch the live screen and sign off each case, and the evidence records who verified what. AI agents can also drive it over MCP.

日本語版はこちら / Japanese · Download

[git-qa running a test sheet: cases on the left, the live screen in the middle with the AI pointing at what it found, one-key verdicts on the right]

Left: the cases in your test sheet. Middle: the page, device or app, live, while the AI drives it — the red marker is where it found the expected text. Right: one key per verdict — D pass, F fail. Your handle goes into the evidence when you press it. (The UI is shown in Japanese; it also speaks English.)

When you would reach for it

The release check nobody wants to click through again. You have a 30-row regression sheet for an Android app, a web page and a desktop app. Instead of tapping through it by hand, the AI follows the sheet while you watch the live view and press a key per case. You only stop to look closely where something changed or failed.

"Who actually checked this?" A client, an auditor or your own team asks after an incident. The evidence answers: each case says VERIFIED (a person looked and signed) or AUTO_PASS (the AI passed it, nobody looked), with the name, the time, and the screen at that moment.

An AI agent built the feature — now it should check it, on a real device. Over MCP, Claude Code (or any agent) can screenshot, read the screen, list what can be pressed and tap it, on Android, web, desktop or iPhone. It can run the sheet unattended overnight (--no-ui); in the morning you review the failures. The pass is still yours to give. The server is listed in the official MCP registry as io.github.meta-taro/git-qa; it runs from this clone (there is no npm package).

Try it

1. Download the app from the distribution page (macOS, Windows x64 / ARM64) and install Node 22+
2. Open git-qa. Enter a handle (it goes into the evidence as "who looked"), pick what to look at — an adb device, a web page URL, or a desktop app by name — and a test sheet
3. Start, watch, and press D / F per case

[Picking what to look at: a web page URL, a desktop app by name, or an adb device]

A run, case by case — the AI runs each step (press the button, reopen the page, press it again), you press D, the case turns VERIFIED / qa and the next one starts:

[A run: the AI presses the button and finds the result, reopens the page and finds it reset, presses again; each case is verified with D]

A test sheet is a TSV you can write in any spreadsheet — samples are in sheets/. From source instead: git clone … && pnpm install && pnpm app (see Install).

Why it is built this way

This is not a tool for handing verification to an AI and letting it say "everything passed." When something ships broken, the person is accountable — "the AI did it" is not an answer anyone accepts.

So git-qa splits the work:

• The AI operates the device, the browser, or the desktop app, following a test sheet
• The human watches, and places the verdict with a single keystroke
• The evidence records who saw what, and when

The vocabulary is the point

A plain PASS would collapse the first two into one value. That collapse is exactly what this tool exists to prevent.

You can place VERIFIED without looking. That is a feature, not a hole. The moment you press the key, your handle goes into the evidence. It is a signature, not a lock. There is no anti-cheat machinery — adding it would make a tool that exists to save effort expensive to use.

What it can drive

[git-qa driving a real iPhone: the Clock app opened and the Stopwatch tab tapped through WebDriverAgent, with the AI verdict AUTO_PASS]

A real iPhone, driven through WebDriverAgent: git-qa launched the Clock app and tapped "Stopwatch". The case waits for a person's verdict.

What evidence looks like

One folder per test run. Commit the whole folder if you want the test itself under version control.

<workspace>/  git-qa.json        marks this folder as one test project  sheet.tsv          the test sheet  runs/    20260914-100000/      run.json       verdicts, steps, who placed them and when      case-001/        screen.webp  the screen at the moment the verdict was placed        screen.webm  video of the run — **only when asked for** (`--record`)

Nothing about your machine goes into the evidence: paths are relative to the workspace, so the same run reads the same way on anyone's machine.

Requirements

• Node 22 or newer — required. The app starts a runner process
• adb for Android, a browser for web — only if you use them
• ffmpeg / cwebp — optional. Without them, evidence is kept in the format it was captured in, uncompressed

Install

Download from the distribution page, or run it from source:

git clone https://github.com/meta-taro/git-qa.gitcd git-qapnpm installpnpm app

macOS builds are signed and notarized. Windows builds are not signed — you will see "Windows protected your PC"; check the source before choosing Run.

To see what this machine can actually do — measured, not guessed:

pnpm doctor

The app also states its own version on the start screen ("This git-qa is v0.2.0-beta.20"). Paste that line into bug reports — it decides which build you are talking about. When a newer build exists, the same place says so; git-qa never replaces itself.

Status

Beta. Three products are using it. Rough edges are listed in each release's notes, and nothing fails silently — where a step cannot run, it is recorded as "a person needs to do this," not as a pass.

Bug reports and requests: Issues. Please write them in your own words, right after you hit the problem. Summarizing loses the part that actually hurt.

License

MIT — see LICENSE.