A real run
One URL and a Test Login. Eleven Key Features. 277 Tests.
Never start from a blank page again. Pie explored this demo admin app on its own, mapped its key features and wrote these tests. Pick one and read them.
A test Pie wroteA test that turned up a bugA real Pie run on a demo admin app for schools and academies. Your app will differ.
User Authentication
Signing in with an email and password.
3 of the 25 tests Pie wrote
- Sign-in Validation for Blank Password Field
- Verify Navigation from Password Reset Back to Sign In Page
- Graceful Handling of Rapid Multiple Sign-in Requests
One bug it caught
- Expected
- One success message after a reset request.
- Got
- Two identical green banners at once.
Role & Access Management
Permissions and roles across each institute.
3 of the 25 tests Pie wrote
- User Logout and Session Termination Verification
- Modify Role Permissions and Verify Permission Count Increase
- Verify Permissions Filtering and Reset for Coach Role
One bug it caught
- Expected
- Stay on the sign-in page after logging out.
- Got
- Back returns to the signed-in dashboard.
People Management
Staff records, payroll, leave and hiring.
3 of the 25 tests Pie wrote
- Initiate New Payroll Run Process
- Create Leave Policy Category Override
- Verify Staff Directory Search Functionality
One bug it caught
- Expected
- The Coach category listed with the others.
- Got
- Only Instructor is listed.
Staff Communication & Announcements
Announcements and messages to staff.
3 of the 25 tests Pie wrote
- Create and Verify New Announcement
- Validate Mandatory Fields for New Announcement Creation
- Verify Search and Filter Functionality in Announcements
One bug it caught on the way in
- Expected
- Your email filled in after you log out.
- Got
- An empty email field.
Academic Session Management
Scheduling sessions and tracking attendance.
3 of the 25 tests Pie wrote
- Create Teacher Availability Time Slot
- Mark Customer Attendance in Academic Sessions
- Document Notes for Cancelled Academic Session
One bug it caught
- Expected
- A list of teachers to pick from.
- Got
- An empty dropdown, so nobody can add an availability window.
Customer Management
Enrolled members, their details and status.
3 of the 25 tests Pie wrote
- Customize Customer List Column Visibility
- Cancel New Customer Creation via Breadcrumb Navigation
- Export Filtered Customer List by Status
One bug it caught
- Expected
- The table of enrolled customers.
- Got
- The Instance Configuration page.
Business Development
Enquiries, follow-ups and message templates.
3 of the 27 tests Pie wrote
- Create or Edit Outreach Message Templates
- Verify Message Template Preview and Variable Formatting
- Review lead notes via filtered Enquiries in Business Development
One bug it caught
- Expected
- The box stays checked after a refresh.
- Got
- It looks checked, then goes back on refresh.
Payment & Invoice Management
Invoices, orders, payment settings and refunds.
3 of the 25 tests Pie wrote
- Merchant Config Input Validation Test
- Filter Invoices by Customer and Issued Date
- Verify Invoice Refund Audit Trail for Partially Refunded Invoices
One bug it caught
- Expected
- A validation error for a malformed key.
- Got
- It saved !!!@@@### and showed a success banner.
Promotions & Discounts Management
Discount campaigns and coupon codes.
3 of the 25 tests Pie wrote
- Verify Promotion Usage Limits (Total and Per Customer)
- Create Promotion with Extra Sessions Configuration
- Promotions Filtering and Sorting Verification
One bug it caught
- Expected
- “Uses in total” and “Uses per customer” fields.
- Got
- Only the coupon code field.
Events Management
Campus events, schedules and task checklists.
3 of the 25 tests Pie wrote
- Create New Event as Template
- Validation Error for Incomplete Event Task Creation
- Verify Updating Event Task Status and Details
One bug it caught
- Expected
- Picking an institute switches the app to it.
- Got
- The app stays on the default institute.
Reporting & Health Analytics
Revenue, attendance and retention dashboards.
3 of the 25 tests Pie wrote
- Verify Access and Functionality of Business Health Dashboard
- Verify Access and Visibility of Audit Report Logs
- Verify Institutional Performance Overview in Health Reporting
One bug it caught
- Expected
- The Health dashboard.
- Got
- The Instance Configuration page.
What comes back
Pie Logged Out and Pressed Back. The Dashboard Came Back.
Hand your developer a bug they can fix. Pie wrote this test itself, then logged every step with a screenshot, so the fix starts right away.
FailedStep 11 · Pie’s noteBack button returned user to dashboard; assertion 5 failed.
- It should be the sign-in page.Pie writes what it expected next to what it saw, so nobody has to reproduce it.
- Still signed in.Pie had just logged out. One press of Back and the account is open.
Exploring by hand
The First Walk Is on Your Team. Here’s What It Costs.
One QA team told us they spend 10 to 18 hours a week walking through what’s new by hand. Put in your team’s hours to see what that costs.
- hours a month exploring today
- 65
- what that costs a year
- $39,000
Book a demo → In the demo, we’ll work out what Pie takes off it.
What starts it
New App or New Feature. Pie Goes First.
Launch day stops being the first time anyone really uses it. Pie goes through what’s new before your customers do.
-
A New App
A URL or a mobile build, plus a test login. Pie maps the app and writes tests under each key feature.
-
A New Feature
With your repository connected, Pie reads what you merged and writes tests for what’s new, on your schedule or when you ask.
-
One Thing You Want Checked
Describe the test in a sentence. Pie drafts it for your team to confirm.
Pie Writes the Tests
Then it runs them and writes up what broke.
Your team’s call
New Tests Wait for You
Nothing changes in your suites until you accept it.
Who does what
Pie Takes the First Walk. Your Testers Make the Call.
Keep the people who know your product and lose the tedium. Your testers start from a map, so they go straight to what a person sees and an agent won’t.
Pie Takes
- The first walk through the flows it can reach
- Writing the tests, in plain English
- Running them again when you ship
- Writing up what broke, with proof
Your Testers Keep
- Whether it feels right
- What matters to your customers
- The odd cases only your business would hit
- The final call on every bug
The basics
New to Exploratory Testing? Start Here.
Get up to speed in eight short answers, from what it is to where AI fits. The guides go deeper.
Exploratory testing means using an app without a script and deciding what to try next from what you just saw. You learn the app, design the test and run it all at once.
A script checks what someone already thought to check. Exploring finds what nobody wrote down.
Our guide to exploratory testing covers the techniques and when each one fits.
Someone logs out of an admin app and presses Back. The dashboard comes back, still signed in.
No requirement asked for that press. You find it by using the app and asking what happens next, which is the bug Pie caught in the run on this page.
Scripted testing decides the steps first and checks the result. Exploratory testing decides the next step as it goes, from what the last one showed.
Scripts protect what you already know works. Exploring finds out what you didn’t know, and the best finds become scripts. Our guide to manual vs automated testing covers where each one fits.
Ad hoc testing has no plan and usually no notes, so nobody can tell what got covered. Exploratory testing is just as open, with a goal and a record of what you tried and found.
When something is new, like a new app, a new feature or a big redesign. Also after a bug report, because bugs tend to have neighbors.
Once a flow settles, turn what you learned into tests and let regression testing protect it. A test can also walk a whole journey, which is end-to-end testing.
It gives exploring a shape. A tester picks a mission, works for a set time and writes down what they found, so the team can see what got covered.
A bug bash is the group version, with everyone on the app at once. Both take people off other work, so teams save them for what’s new.
It can take the first walk. An agent can use the app, work out what it does, write tests and flag what breaks. Deciding what matters and noticing what feels wrong stay with people.
Pie’s agents explore your app and write the tests, and you make the final call on each bug.
You’re exploring two platforms, more builds and screens that differ by device, plus gestures and permissions a web app doesn’t have.
Pie explores iOS apps on the iOS Simulator (a simulator .app build) and Android apps on the Android Emulator (an .apk). Each run starts from a build instead of a URL.
Our mobile app testing guide covers the rest.
Customers
Faster Releases, Without Breaking What Works.
“As we scale our products and offerings it’s really important to make sure we don’t ship something that breaks the existing experience for our users.”
“After evaluating multiple vendors, Pie was the only solution that consistently executed our most complex end‑to‑end workflows with reliability across builds.”
Security
Yes, Security Will Ask. Here’s What to Tell Them.
- You Pick the Test Account.Pie signs in with the test login you give it. A setup script can call your test API to create the data first.
- We Never Use Your Source Code to Train AI Models.Source code here means the files and code changes in your repositories.
- Logins Reach Pie’s Agents Only While a Test Runs.You keep them in Pie’s credential settings.
- Pie Has a SOC 2 Type 2 Report.Our most recent report is available on request. Data is encrypted in transit.