The Pie Documentation
Pie Loop

Pie Loop

Your PR merged. Pie tests it, finds the regression, and surfaces a fix suggestion — with a plain-English explanation and before/after screenshots — before your team’s next standup.

Pie Loop runs when your team ships. It reads what changed, tests the affected flows, and validates every bug against your source code. No false positives in your inbox. No test logs to dig through. Just a clear fix suggestion in the issue panel, ready to act on.

How It Works

  1. Reads the diff. Pie analyzes what changed and identifies which flows in your app are affected.
  2. Tests like a user. AI agents navigate those flows — clicking, filling forms, completing the journeys real users take.
  3. Validates every finding. Each bug gets cross-referenced against your source code. No false positives reach you.
  4. Surfaces a fix. For every confirmed bug, Pie writes a suggested fix and surfaces it in the issue detail panel — with the code change, a plain-English explanation, and before/after screenshots.
  5. Updates Coverage Stories. The run folds into your week’s Coverage Story: what shipped, what Pie tested, what it found.

No test runs to schedule. No results to triage. No tickets to file.

Use Cases

Catch regressions before production. Pie Loop tests every change. Developers get a fix suggestion with before/after screenshots, not a bug report filed two weeks later.

Weekly quality pulse for engineering leads. Coverage Stories give you a plain-English view of what shipped, what broke, and what got fixed. No test logs, no digging through run history.

Know exactly what’s covered. Coverage Stories give you a running view of which flows Pie tested on every run — so you always know what’s covered and what isn’t.

Best Practices

Start with one repository. Get Coverage Stories flowing for one repo before expanding. Your team will develop a feel for the results before relying on them at scale.

Check Coverage Stories regularly. Engineering leads who keep Coverage Stories in their weekly routine catch regressions before customers do. It takes two minutes and replaces a meeting.

Act on what you find. Fix suggestions come with the code change, before/after screenshots, and a plain-English explanation. Dismissing an issue is equally valid — it teaches Pie what your app intentionally does.

Need Help?

How-To: Read Your Test & Issue ReportsConnect Pie Bot