Glossary
The terms and labels Pie uses in the app and in these docs, each linked to the page that covers it. Bold text is a UI label, exactly as the app shows it.
Screens and labels
Sidebar labels, in the order the app lists them.
| Label | What it is |
|---|
| Test Cases | Every test case for the app, with a detail view for each. Includes the PR scan inbox filter. |
| Test Suites | Named groups of test cases you run together. See Organize tests into suites. |
| Run History | Every run, with its result, tests and step screenshots. See Read a run. |
| Loop | The page that lists your Loops and holds Coverage Stories. |
| Issues | The deduplicated bugs Pie found and confirmed, in Open, Resolved and Rejected tabs. See Triage issues. |
| Builds | Uploaded mobile builds. Web apps don’t show this screen. |
| Pie Media Service | Opens the Upload item dialog, where you add media files that Pie can use as mock media objects. |
| Pie Canvas | The screen where you author a test inside a live run. It shows once the app has a run. |
| Chat | The in-app assistant. |
| Settings | Team Management, Credentials Manager, API Keys, App Instructions, Integrations, Scripts, Run Schedules and Notifications, plus other settings these docs don’t cover. Narrow screens show a shorter set. See Set up and admin. |
Loop, Pie Bot, PR scan, Chat and Canvas
These names are easy to mix up. Each one is a different thing.
| Term | What it is | Where you find it |
|---|
| Loop | The sidebar page where you manage Loops and read Coverage Stories. | Sidebar |
| A Loop, or Loops | A scheduler object: one or more suites plus a trigger. A trigger is a schedule, a new build (mobile apps only) or an API call. See Loops. | Loop page |
| Pie Bot | The GitHub app that tests your pull requests. You install it with Install Pie PR Bot. See Connect GitHub or GitLab. | Settings > Integrations |
| PR scan | A setting inside a Loop. Each time the Loop runs, it reads the pull requests merged in the scan period, writes tests for what’s new and revises the tests those changes touch. New tests land in the PR scan inbox. See PR scan. | Inside a Loop |
| Chat | A conversation with Pie in the app, for creating tests, exploring edge cases, understanding a flow and checking a run. See Ask Pie in Chat. | Sidebar |
| Pie Canvas | The screen where you author a test inside a live run. It needs at least one run. | Sidebar |
| Pie Loop | The feature that runs your suites on a schedule, on a new build or from your CI. You create Loops on the Loop page. See Create a Loop. | Loop page |
Building and running tests
| Term | Meaning |
|---|
| Discovery | The exploration where Pie maps your app and builds its key features and starting test cases. |
| Key feature | A core area of your app that Pie discovers and you can prioritize. Also called a group. Each test case belongs to one. |
| Test case | One test: a title, a prompt or steps, and assertions. |
| Test suite | A named group of test cases that you run together. An empty suite can’t run. |
| Run | One execution of test cases against a build (mobile) or a URL (web). A run produces results and findings. |
| Build | A mobile app binary you upload: an .apk for Android, a zipped simulator .app for iOS. |
| Assertion | A check inside a test case that a condition is true. Example: “Verify the user is on the dashboard screen.” |
| Credential | A stored test login. Refer to it in a step as @{name}. See Manage credentials. |
| Execution script | A shell command Pie runs during a test. Refer to it as #{name}. See Use execution scripts. |
| App Instructions | Standing guidance for the whole app, including how to sign in, saved in Settings. A suite’s own instructions replace them for that suite. See Save app instructions. |
| Coverage scan | A scan that reads the changes merged in a window and generates tests for the behavior those changes could have broken. New tests are held for review. See Run a coverage scan. |
| Coverage Stories | A plain-English weekly account of what shipped, what Pie tested and what it found, built when Pie publishes a coverage scan for that week. See Coverage Stories. |
| Self-healing test | A test written as intent, which Pie re-reads against the screen on every run, so it can adapt when the interface changes. A big redesign can still break tests until their steps are regenerated. |
| Contextual model | Pie’s structured map of your app’s screens, elements, features and their relationships. |
Results and triage
| Term | Meaning |
|---|
| Finding | One raw instance of a potential bug, detected in a specific test. |
| Issue | A deduplicated report that groups related findings into one root cause. Issues are tracked across runs. |
| Acknowledge | Accept an issue as real. The button on the issue is Track it. You can create a ticket in your tracker at the same time. |
| Resolved | An issue marked as valid and fixed, with Mark as resolved. |
| Rejected | An issue you dismissed as Not a real issue. |
| Auto-Fix | The panel on an issue. Its Fix button has Pie check that the issue is a real bug, then open a PR with a proposed fix for your team to review. See Triage issues. |
| Investigate an app issue | A sheet on Issues where you describe a problem you saw. Pie creates an issue and tries to reproduce it. |
| Readiness Score | A score that starts at 100% and drops with each issue, by severity: Critical 8, High 5, Medium 2, Low 1. It never goes below 50%, and resolved and rejected issues don’t count. 90 to 100 is stable, 70 to 89 needs caution, and below 70 is a blocker. The app labels the bands Ready to Launch, Needs Attention and Not Ready Yet. |
| Severity | The technical impact of a bug. A crash is critical. |
| Priority | The urgency of fixing a bug from a business view. A typo on the homepage can be low severity and high priority. |
Agents and automation
| Term | Meaning |
|---|
| AI agent | The software that explores your app, runs tests and analyzes results. |
| MCP | Model Context Protocol, a standard way for an AI agent to call tools. Pie’s MCP server lets an agent run tests, read results and triage issues. See Connect your agent. |
| API key | A secret that authenticates your agent, CI pipeline or scripts as your app. See Create an API key. |
| CI/CD | Continuous integration and continuous deployment: merging changes often and releasing them automatically. See Trigger from CI. |
Testing terms
| Term | Meaning |
|---|
| Push, Probe, Patch, Pass | The four steps every change goes through: a PR or a build gives Pie something to test, you fix what broke with Auto-Fix, your coding agent or your tracker, and Pie re-checks until the change passes. See How Pie works. |
| Bug (defect) | A flaw in the app that produces an incorrect or unexpected result. |
| End-to-end (E2E) testing | Testing a workflow from start to finish, the way a user moves through it. |
| Functional testing | Testing that features work as specified: does this feature do what it should? |
| Regression testing | Re-running tests to confirm that recent changes haven’t broken working features. |
| Smoke testing | A short set of tests on a new build to confirm its most critical paths work. A failed smoke test usually rejects the build. |
| Usability testing | Testing how easy and intuitive the app is for a user. |