Tested before you see it
A QA agent tests every card in its own worktree before it reaches your Review. When the card passes, QA opens its pull request for you.
QA goes first
When a builder is done, its card moves to Testing and the QA Agent picks it up. QA runs the project’s tests, lint and typecheck, writes tests for what isn’t covered yet, and checks every acceptance criterion. What it checks comes from its starting instructions, which you can change.
Back with a list, or on to you
A card that fails goes back to its builder with a numbered list of what is wrong. A card that passes gets its tests pushed and its pull request opened, and lands in your Review. Nothing reaches you that QA hasn’t seen first.
You review, then merge
You read the pull request on GitHub or Bitbucket Cloud and merge it there, as you always do. GizAi sees the merge, moves the card on to Deploy or Done and removes its worktree. In a project where you allow it, the Team Lead may merge a pull request that QA passed and CI approved. Releases stay yours.
In the docs
docs/features/testing.md on GitHubFAQ
Questions about testing
What if a card keeps failing?
After three rounds back to its builder, GizAi stops the loop. The card goes on hold, marked Needs a decision, and waits for you in the Inbox.
Who pushes the card’s branch?
GizAi does, when a run ends and the branch has commits the remote doesn’t have. It never forces a push. If a push fails, the card goes on hold with the reason.
Can a card skip testing?
Yes. Switch Testing off on the card, and a done answer sends it past the Testing columns, usually straight to Review.
Is a card I build myself tested too?
Yes. When you hand it over, QA tests it the same way, and a failed test sends it back to you.
Install
Get GizAi
One line in a terminal installs GizAi on your computer. It’s free, for Linux, macOS and Windows.
Linux and macOS
curl -fsSL https://gizai.app/install.sh | shWindows · PowerShell
irm https://gizai.app/install.ps1 | iex