Read Coverage Stories
Coverage Stories describe the pull requests your team merged in plain words: what changed, what Pie tested and what broke. They’re on the Loop page, grouped by week.
Before you start
- Connect your repository to Pie. See Connect GitHub or GitLab.
- Run a Loop on your merged pull requests. See Create a Loop.
- Check that a coverage scan covering the week you want to read is published. Pie builds a week’s stories when it publishes a coverage scan that covers that week, not after each run.
Open Coverage Stories
In the sidebar, select Loop, then open the Coverage Stories tab. Each week starts with its totals: PRs, Flows tested, Issues and Fixes merged.
Read a story
Each story covers a set of PRs merged that week, with a title and a short summary. A story can contain:
- Issues caught: the bugs Pie found. Each shows its severity (Critical, High, Medium or Low) and, when Pie can trace it, the PR it was found in.
- Test coverage: how many flows Pie tested for the change, split into new and re-run tests.
- PRs scanned: every PR in the story, each linked to your repository.
- Screenshots of the features the story covers.
Findings Pie couldn’t tie to a PR are in a separate Other findings this week card.
Open an issue
Select an issue to see what the test expected and what the app did, under Expected vs observed. When Pie has prepared a fix, you’ll also see Fix applied (a summary of the fix), Code diff (the change) and PR conversation (the comments on the fix).
Check the fix status
Each issue with a fix carries one of three statuses:
| Status | What it means |
|---|---|
| Fix ready | Pie prepared a fix, and no PR is open for it yet |
| Fix open | The fix is open as a PR, linked from the issue |
| Fix merged | The fix PR was merged |
What you’ll see
Beside the weekly feed, All-time impact and Issues vs fixes show the trend across weeks: which weeks had regressions, which were clean and whether fixes keep pace with issues. To go back to an earlier week, use Jump to week.
Common uses
- A quality check across the team: read the week’s totals and story summaries. You don’t need to open individual test results.
- Checking your own change: find the story that holds your PR and open the issue it introduced. Read what was expected, what happened and, when there is one, the fix.