Frequently Asked Questions (FAQs)

Here are answers to some common questions that will help new and experienced users leverage the platform better.

How do I get started with Pie?

Getting started with Pie is straightforward. Schedule a personalized demo with our team to see how Pie’s autonomous testing platform works with your specific applications and QA challenges. During the demo, we’ll demonstrate our AI-native testing capabilities and show you exactly how Pie can transform your testing workflow from manual to autonomous.

What do I need for my very first test run?

• For a web app: Just the URL
• For a mobile app: A zipped .app (iOS Simulator) or .apk (Android) file
• If login is required: Have a set of test credentials ready

How long does it take to see results?

For most applications, your first comprehensive report—including a Readiness Score and a list of issues—will be ready within 15–30 minutes of starting a run.

Do I have to write test scripts?

No. Pie’s AI agents autonomously generate hundreds of test cases by exploring your app just like a real user would.
For specific or complex scenarios, use the Pie Test Assistant to create a new test using a plain English prompt—no code required.

How do I test a specific user flow that the AI might miss?

Use the Pie Test Assistant.
Write a prompt in plain English (e.g., “Log in, go to settings, and change the notification preferences”).
The AI will generate and validate the test case for you.

How do I get the bug reports into my team’s workflow?

Use our one-click Jira integration to push any issue directly into your Jira project.
This creates a pre-filled ticket with all necessary details.
You can also integrate Pie into your CI/CD pipeline to trigger runs automatically.

What happens if I dismiss an issue by mistake?

Dismissed issues aren’t gone forever.
You can find them in the “Resolved” tab within the issues section.
Click “Restore” to move the issue back to your active list.

What’s the difference between a “Finding” and an “Issue”?

• Finding: A single, raw instance of a potential bug detected in a specific test
• Issue: A curated, deduplicated report created by grouping related findings into one actionable root cause

This means you get one report per unique bug, not hundreds of duplicate alerts.

How do “Self-Healing Tests” actually work?

Instead of relying on brittle code selectors (like a specific button ID), Pie’s tests are based on the AI’s contextual understanding of your app, stored in an application model.
If a button’s text or ID changes, the AI still identifies it by position, function, and context.
This allows tests to heal themselves and run without manual updates.

How is the Readiness Score calculated?

The score starts at 100% for every test run.
It is reduced by a set amount for each approved critical issue found.
This makes the score a true reflection of release-blocking bugs, giving you a clear and reliable signal for go/no-go decisions.