Cypress tests what you script. Pie tests what you ship.
Test every flow without waiting for someone to script it. Pie’s agents explore your web, iOS and Android apps and write the tests Cypress needs from your team.
Pie is an agentic testing platform that finds your flows for you. Agents explore your web, iOS and Android apps and write the tests, so coverage doesn’t wait on a spec.
Cypress is a free, open-source test runner for web apps, with a Cloud service for recording, parallel runs and analytics. Your team writes each spec in JavaScript or TypeScript.
Pie vs Cypress at a glance
- What it is
- An agentic testing platform for web, iOS and Android apps.
- Who writes the tests
- Pie’s agents explore your app and generate them. Your team adds the cases that matter in plain English.
- What a test is
- Plain-English steps and checks. No scripts to write, no locators to break.
- Where it runs
- Web apps in a browser. iOS apps on the iOS Simulator, Android apps on the Android Emulator.
- AI help
- The whole product. Agents explore, write and run the tests, and group what they find into issues.
- What it is
- A free, open-source test runner for web apps, with a Cloud service for recording, parallel runs and analytics.
- Who writes the tests
- Your team, in JavaScript or TypeScript. Cypress Studio can record clicks into spec code.
- What a test is
- A spec file of commands and selectors your team keeps in its repo.
- Where it runs
- In a browser, on your machine or your CI. Its docs say native mobile apps can’t run under Cypress.
- AI help
- cy.prompt turns plain-English steps into commands, in beta. Studio AI suggests assertions, also in beta.
One refund check, written twice.
On the right is a real Pie test from a demo billing app we test with. It opens a partly refunded invoice and follows the refund to its credit memo. On the left is the same check as a Cypress spec, our translation, written the way Cypress’s docs suggest.
describe('refund audit', () => {
it('partly refunded invoice links to its credit memo', () => {
cy.visit('/login');
cy.get('#email').type(Cypress.env('QA_EMAIL'));
cy.get('#password').type(Cypress.env('QA_PASSWORD'), { log: false });
cy.contains('button', 'Sign in').click();
cy.contains('a', 'Configure').click();
cy.contains('button', 'Payments').click();
cy.contains('a', 'Invoices').click();
cy.contains('h1', 'Invoices').should('be.visible');
cy.contains('button', 'Filters').click();
cy.get('#refunded').select('Partly refunded');
cy.contains('button', 'Apply filters').click();
cy.get('[data-testid="invoice-status"]').first()
.should('have.text', 'Partly refunded');
cy.contains('a', 'Open').click();
cy.contains('Refund amount').should('be.visible');
cy.get('[aria-label="Credit memos against this invoice"]')
.contains('a', 'Open').click();
cy.contains('Payout method').should('be.visible');
cy.contains('Refund issued').should('be.visible');
cy.go('back');
});
});
17 selectors, and every one is code your team maintains.
Pie test- Enter the account email and password, then tap ‘Sign in’.
- Tap ‘Configure’ on any institute from the instance configuration list to enter its management view.
- Tap the ‘Payments’ dropdown in the sidebar and select ‘Invoices’.
- Tap the ‘Filters’ button, select ‘Partly refunded’ from the Refunded dropdown, and tap ‘Apply filters’.
- Tap ‘Open’ on the first invoice record in the filtered list.
- Scroll down to the ‘Credit memos against this invoice’ section and tap ‘Open’ on the associated credit memo.
- Tap the back button or navigation link to return to the customer’s payments overview.
- The Invoices view is displayed upon selection from the Payments menu.
- The invoice list is filtered to show only invoices with a ‘Partly refunded’ status after applying the filter.
- The detailed view of the selected invoice displays the refund amount and a list of associated credit memos.
- The credit memo details show the payout method and the date the refund was issued.
No selectors. Seven steps anyone on your team could review.
The selector stops matching, the run goes red, and someone edits the spec. Pie re-reads the screen on each run, so a renamed label isn’t a selector edit for your team.
The Pie test is copied word for word from Pie, “tap” and all. The Cypress spec is ours, written to match it step for step.
Four reasons to stop writing a spec for every flow.
- 01
A free app, paid for in hours
The app is free. The bill is your team’s hours, your CI, and a Cloud plan that counts every recorded test. In one study, flaky tests alone took at least 2.5% of a team’s productive time. In Pie, the agents do the writing and the re-running.
Source - 02
Somebody has to write the test first
A Cypress suite covers the flows your team found time to script. Pie’s agents explore your running app and generate the tests, so the flows nobody scripted get tested too.
Source - 03
cy.prompt still ends in a spec
It does. cy.prompt writes commands from plain English. It is in beta, runs in Chromium browsers only and needs a Cloud account. The result is still a spec your team owns. Pie’s tests are plain-English steps with no test code behind them.
Source - 04
The app on your users’ phones
Cypress’s docs say native mobile apps can’t run under it, so iOS and Android mean a second framework and a second suite. Pie tests native iOS and Android apps as well as your web app.
Source
Where your team’s hours go, row by row.
Cypress tests the flows someone found time to script. Pie’s agents find the rest.
| What you’re comparing | Pie | Cypress | Advantage |
|---|---|---|---|
| Cost to run it | No scripts to write and no locators to break, so your team spends those hours on your product. | Your team’s hours to write and repair specs, your own CI to run them, and a Cloud plan billed by recorded test results. | Pie |
| Writing a new test | Agents generate tests by exploring your app. Anyone on your team can add one in plain English. | Your team writes it in JavaScript or TypeScript. Studio records clicks into code, and cy.prompt is in beta. | Pie |
| When the UI changes | No locators to update. Pie re-reads the screen on every run. | Selectors live in your specs. When one stops matching, someone edits the file. | Pie |
| Native iOS and Android | Built in, on the iOS Simulator and the Android Emulator. | Not supported. Cypress tests web apps, including mobile web at a phone-sized viewport. | Pie |
| Fixing the bug | Pie can open a Fix PR with a proposed fix in a repo you connect. Merging it is always your team’s call. | Test Replay lets your team step back through a failed run. Triage and the fix are theirs. | Pie |
| Pull requests | Pie can test your pull requests on a preview URL or a build, and comments on the PR with a GO / NO-GO verdict. | Cloud posts the results of your specs on the pull request, as comments and status checks. | Pie |
| License cost | Custom pricing, tailored to your team’s requirements and testing volume. Contact Pie for a quote. | The app is free and open source. Cloud plans start at $67 a month. | Cypress |
Which fits your team, Pie or Cypress?
Pick Pie to
- Test more of your app without writing another spec.
- Test your iOS and Android apps, not only your web app.
- Give your team back the hours it spends on selectors and flaky runs.
- Check your pull requests the way your users will use them.
- Check your APIs and accessibility along with your UI.
Pick Cypress if
- Your developers have the time to script and maintain each flow.
Switch from Cypress one flow at a time
No big rewrite. Your specs keep running until Pie covers the same flow.
- 1
Send Pie the app
Give Pie a URL for your web app, or an iOS simulator build or an Android APK for mobile. If the app has a login, add a test login through a supported path.
- 2
Let Pie explore
Pie explores your app’s reachable flows and generates tests. You get results in hours, not weeks.
- 3
Add your edge cases
Type the cases only your team knows into Pie Chat in plain English. Pie turns them into tests and runs them with the ones it found.
- 4
Retire specs as Pie covers them
Compare Pie’s results with your Cypress runs, and delete each spec once Pie covers the flow. Connect GitHub or GitLab and Pie can test your pull requests too, given a preview URL or a build for each change.
FAQ
Did we miss a question?
Email us directly →
Yes. Pie replaces the specs your team writes and maintains with tests its agents generate by exploring your app.
The Cypress app is free. Stay if your developers have the time to script each flow.
The Cypress app is free and open source, and Cypress Cloud plans start at $67 a month.
The larger cost is your team’s time. In one study of about 30 developers over five years, flaky tests alone took “at least 2.5% of the productive developer time”.
Pie’s agents write and run the tests, with no selectors for your team to repair.
cy.prompt turns plain-English steps into Cypress commands, and Studio AI suggests assertions while you record. Both are in beta, and cy.prompt runs in Chromium browsers only and needs a Cypress Cloud account.
A person still decides what to test and owns the spec that results. Pie’s agents find the flows by exploring your app, and the tests stay in plain English.
Yes, and both are in beta. Pie runs whole API flows call by call, and checks each screen its tests reach for accessibility problems.
Your UI, API and accessibility testing sit in one place.
Tabs and iframes come up most. Cypress’s docs call iframe support “somewhat limited” and say Cypress cannot drive two browsers at the same time, and G2 reviewers say the same about multiple tabs and windows.
Whichever it is, your developers still own every spec. Pie’s agents write the tests and keep them running.
Whoever owns quality today, such as a QA lead or an engineer who owns releases. Pie does the exploring, writing and re-running, and the owner decides what matters and what counts as a bug.
Anyone on the team, including a product manager, can read a test or add one in plain English.
Pie’s pricing is custom, tailored to your team’s requirements and testing volume.
You buy one product: agents explore your web, iOS and Android apps, write and run the tests, group related findings into issues and can open a Fix PR.
Book a demo, tell us what you ship and how often you release, and we’ll send you a quote.
Ship the app. Leave the specs to Pie.
Book a demo and name a flow nobody has scripted yet. We’ll show you Pie testing it on web and on mobile.
Sources
- Cypress pricing. The app is free and open source; Cloud Starter is free with 500 test results a month, parallelization, Test Replay and pull request comments; Team is $67 a month; extra test results are billed per 1,000. A test result is one recorded run of a single test.cypress.io/pricing
- cy.prompt docs. Beta; end-to-end tests only; Chromium-based browsers only; needs a Cypress Cloud account or record key.docs.cypress.io/api/commands/prompt
- Cypress Studio docs. Studio records your clicks into spec code; Studio AI, in beta, suggests assertions and does not crawl the app.docs.cypress.io/app/guides/cypress-studio
- Cypress FAQ. Native mobile apps cannot run under Cypress; mobile web can be tested at a phone-sized viewport. Tests are written in JavaScript or TypeScript.docs.cypress.io/app/faq
- Why Cypress. Time-travel snapshots, a command log and automatic waiting; component testing for React, Angular, Vue and Svelte.docs.cypress.io/app/get-started/why-cypress
- Cost of Flaky Tests in CI, ICST 2024 industry track. Five years of history, about 30 developers, one commercial project; “at least 2.5% of the productive developer time”. Not specific to Cypress.conf.researchr.org/details/icst-2024/icst-2024-industry/1
- G2, Cypress reviews, most recent first. Review dated April 21, 2026 (multiple tabs and windows, iframes).g2.com/products/cypress/reviews
- Cypress on GitHub, issue 136, “Iframe support”. Opened May 11, 2016; open with 1,045 reactions when read.github.com/cypress-io/cypress/issues/136
- Cypress docs, Trade-offs. “You cannot use Cypress to drive two browsers at the same time.” “iframe support is somewhat limited, but does work.”docs.cypress.io/app/references/trade-offs