WebdriverIO gives you one API. Pie gives you the tests.

Get the tests, with nothing to maintain. With WebdriverIO, every spec, selector and page object behind its API is your team’s to write and repair.

Pie

Pie is an agentic testing platform whose agents write and run your web, iOS and Android tests, with no specs, page objects or Appium setup for your team to maintain.

WebdriverIO

WebdriverIO is a free, open-source test framework for Node.js that automates browsers, mobile apps and desktop apps. Your team writes the specs in JavaScript or TypeScript.

The basics

Pie vs WebdriverIO at a glance

PieAgentic testing platform
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.
WebdriverIOOpen-source test framework
What it is
A free, open-source test framework for Node.js that automates browsers, mobile apps and desktop apps.
Who writes the tests
Your team, in JavaScript or TypeScript, with Mocha, Jasmine or Cucumber.
What a test is
A spec file of selectors and commands, usually behind page objects your team maintains.
Where it runs
In Chrome, Firefox, Safari and Edge, and on mobile through Appium. The machines, or the cloud you rent, are yours to bring.
AI help
An MCP server that drives browsers and apps, a session CLI that exports the steps as a test, and an act command that needs a model your team supplies.
The same test, both ways

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 WebdriverIO spec, our translation, using WebdriverIO’s selectors and its Mocha runner.

WebdriverIO specrefund-audit.e2e.ts
import { browser, $, $$, expect } from '@wdio/globals';

describe('refund audit', () => {
  it('links a partly refunded invoice to its credit memo', async () => {
    await browser.url('/login');
    await $('#email').setValue(process.env.QA_EMAIL);
    await $('#password').setValue(process.env.QA_PASSWORD);
    await $('button=Sign in').click();

    await $$('=Configure')[0].click();
    await $('button=Payments').click();
    await $('=Invoices').click();
    await expect($('h1')).toHaveText('Invoices');

    await $('button=Filters').click();
    await $('#refunded').selectByAttribute('value', 'partly-refunded');
    await $('button=Apply filters').click();
    await expect($$('[data-testid="invoice-status"]')[0])
      .toHaveText('Partly refunded');

    await $$('=Open')[0].click();
    await expect($('dt=Refund amount')).toBeDisplayed();

    await $('[aria-label="Credit memos against this invoice"]')
      .$('=Open').click();
    await expect($('dt=Payout method')).toBeDisplayed();
    await expect($('dt=Refund issued')).toBeDisplayed();
    await browser.back();
  });
});

17 selectors, in a spec your team writes and keeps passing.

Pie test
Steps
  1. Enter the account email and password, then tap ‘Sign in’.
  2. Tap ‘Configure’ on any institute from the instance configuration list to enter its management view.
  3. Tap the ‘Payments’ dropdown in the sidebar and select ‘Invoices’.
  4. Tap the ‘Filters’ button, select ‘Partly refunded’ from the Refunded dropdown, and tap ‘Apply filters’.
  5. Tap ‘Open’ on the first invoice record in the filtered list.
  6. Scroll down to the ‘Credit memos against this invoice’ section and tap ‘Open’ on the associated credit memo.
  7. Tap the back button or navigation link to return to the customer’s payments overview.
Checks
  • 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.

Now rename ‘Filters’ to ‘Filter’.

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 WebdriverIO spec is ours, written to match it step for step.

Where they differ

Four reasons to hand the spec writing to agents.

  1. 01

    One API, and your team writes every line behind it

    WebdriverIO’s docs recommend page objects, so a redesign means updating the page object. The page object is still a file your team wrote and has to keep current. Pie’s tests are plain-English steps with no selectors underneath.

    Source
  2. 02

    Free framework, full-time upkeep

    WebdriverIO has no license fee. A suite costs the hours to write each spec and keep the page objects behind it current. In one study, flaky tests alone took at least 2.5% of a team’s productive time. Pie’s agents take those hours on.

    Source
  3. 03

    Mobile means building an Appium setup

    WebdriverIO reaches phones through Appium. Your team installs Appium and its drivers, Android Studio for Android, and a Mac with Xcode for iOS. Pie takes an iOS simulator build or an Android APK and starts testing.

    Source
  4. 04

    AI that drives the browser, not the checks

    WebdriverIO’s act command turns a plain-language instruction into steps using a model your team supplies, and its docs say act doesn’t assert. Pie’s agents explore your app, write the checks and group what they find into issues.

    Source
Side by side

Specs your team writes, or tests agents write.

WebdriverIO gives your team one API for browsers, phones and desktop apps. Pie’s agents write the tests.

What you’re comparingPieWebdriverIOAdvantage
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 each spec and page object and repair them, plus your own CI or a rented cloud. Pie
Getting started Give Pie your app’s URL, or upload an iOS simulator build or an Android APK. You get results in hours, not weeks. Run the setup wizard, pick a framework, write a config file, then write your first spec. 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. Pie
When the UI changes No locators to update. Pie re-reads the screen on every run. Selectors live in your specs and page objects. When one stops matching, someone edits the file. Pie
Native iOS and Android Built in, on the iOS Simulator and the Android Emulator. Through Appium, which your team installs and maintains with its drivers and SDKs. Pie
Fixing the bug Pie groups related findings into issues, and can open a Fix PR in a repo you connect. Merging it is always your team’s call. Reporters and traces show what failed. Your team reads them and files the bug. 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. Specs run inside your CI job on each commit, with sharding across jobs. Both
License cost Custom pricing, tailored to your team’s requirements and testing volume. Contact Pie for a quote. Free and open source, under the MIT license. No paid tier. WebdriverIO
Desktop apps Pie tests web, iOS and Android apps. Electron, Tauri, macOS and Windows apps. WebdriverIO
The exception

When the app runs on the desktop

You test desktop apps

WebdriverIO automates Electron, Tauri, macOS and Windows apps as well as browsers. Pie tests web, iOS and Android apps.

Source
Who should pick which

Which fits your team, Pie or WebdriverIO?

Pick Pie to

  • Test more of your app without writing another spec.
  • Cover web, iOS and Android with no Appium setup to build.
  • Give your team back the hours it spends on selectors and flaky runs.
  • Check your pull requests the way your users will use them.
  • Find accessibility problems on the screens your tests reach, in beta.

Pick WebdriverIO if

  • You test Electron, Tauri, macOS or Windows apps.
Getting started

Switch from WebdriverIO one flow at a time

No big rewrite. Your specs keep running until Pie covers the same flow.

  1. 1

    Point Pie at your app

    Give Pie your web app’s URL, or an iOS simulator build or an Android APK. If the app has a login, add a test login through a supported path.

  2. 2

    Let Pie explore

    Pie explores your app’s reachable flows and generates tests. You get results in hours, not weeks.

  3. 3

    Add your edge cases

    Type the cases only your team knows into Pie Chat in plain English. Pie explores each flow, drafts the test and runs it once you confirm.

  4. 4

    Retire specs as Pie covers them

    Compare Pie’s results with your WebdriverIO runs, and delete each spec and page object once Pie covers the flow.

FAQ

Did we miss a question?
Email us directly →

Is Pie a WebdriverIO alternative?

Yes, for web, iOS and Android apps. Pie replaces the specs your team writes and maintains with tests its agents generate by exploring your app.

Stay on WebdriverIO if you test desktop apps such as Electron or Tauri.

Is WebdriverIO free?

Yes. WebdriverIO is open source under the MIT license, with no paid tier.

The cost is your team’s time to write the specs and keep them passing, plus the CI or cloud they run on.

Pie’s agents write and run the tests instead.

Can WebdriverIO test mobile apps?

Yes, through Appium. Your team installs Appium and the drivers for each platform, with Android Studio for Android and a Mac with Xcode for iOS simulators.

Pie tests native iOS apps on the iOS Simulator and Android apps on the Android Emulator, from a build you upload. Real devices are available on demand.

Does WebdriverIO have AI features?

Yes. WebdriverIO ships an MCP server that lets an AI assistant drive browsers and apps, and an act command that turns a plain-language instruction into steps using a model your team supplies. Both help a person author a test.

Pie’s agents explore your app and generate the tests and their checks.

Does Pie test APIs and accessibility too?

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.

How do I move from WebdriverIO to Pie?
One flow at a time. Give Pie your app’s URL or a build, let it generate tests, and type your edge cases into Pie Chat. Keep your WebdriverIO specs running until Pie covers the same flow, then retire them.
Who on my team runs Pie?

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.

What does Pie cost?

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.

Get the tests without writing the specs.

Book a demo and bring the flow your specs keep breaking on. We’ll show you Pie covering it, with no page object behind it.

Sources

  1. WebdriverIO docs, Why WebdriverIO. One API for web, mobile and desktop apps; not a vendor product, with no paid tier and no feature gates; a project of the OpenJS Foundation.webdriver.io/docs/why-webdriverio
  2. WebdriverIO docs, Getting Started, and the v10 release post. Desktop targets include Electron, Tauri and macOS apps; v10 adds native macOS and Windows apps through the wdio session CLI.webdriver.io/docs/gettingstarted · webdriver.io/blog/2026/10/05/webdriverio-v10-release
  3. WebdriverIO on GitHub. MIT license; “Next-gen browser and mobile automation test framework for Node.js”.github.com/webdriverio/webdriverio
  4. WebdriverIO docs, Selectors and Page Object Pattern. CSS, text, XPath, accessibility-name and role selectors; page objects recommended so a UI change is made in one place.webdriver.io/docs/selectors · webdriver.io/docs/pageobjects
  5. WebdriverIO docs, Getting Started and Testrunner. A setup wizard with Mocha, Jasmine or Cucumber, and a runner configured in wdio.conf.ts.webdriver.io/docs/gettingstarted · webdriver.io/docs/testrunner
  6. WebdriverIO docs, Mobile. Mobile automation runs through Appium, with the UiAutomator2 and XCUITest drivers, Android Studio and its SDK, and macOS with Xcode for iOS simulators.webdriver.io/docs/platforms/mobile
  7. WebdriverIO docs, MCP and AI service. An MCP server lets an AI assistant drive browsers and apps; browser.act() sends an instruction to a model your team configures, caches the steps, and does not assert.webdriver.io/docs/mcp · webdriver.io/docs/ai-service
  8. 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 WebdriverIO.conf.researchr.org/details/icst-2024/icst-2024-industry/1