Selenium drives the browser. Your team does the rest.
Skip building the suite. Pie’s agents write and run the tests. With Selenium, the suite, the waits, the page objects and the grid are your team’s to build and keep running.
Pie is an agentic testing platform whose agents write and run your tests across web, iOS and Android, with no script to write, wait to tune or grid to host.
Selenium is a free, open-source library that drives browsers from Java, Python, C#, JavaScript or Ruby. The suite, the waits and the grid are your team’s to build.
Pie vs Selenium 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 library that drives browsers, with bindings for Java, Python, C#, JavaScript and Ruby.
- Who writes the tests
- Your team, in code. Selenium IDE can record a starting point.
- What a test is
- Code your team structures. Selenium’s docs recommend page objects and explicit waits.
- Where it runs
- Desktop and mobile websites, on your machines or in parallel on a Selenium Grid your team hosts.
- AI help
- Docs and an llms.txt that help coding agents write Selenium code.
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 Selenium test in Python, our translation, written with the explicit waits Selenium’s docs recommend.
import os
from selenium import webdriver
from selenium.webdriver.common.by import By
from selenium.webdriver.support import expected_conditions as EC
from selenium.webdriver.support.ui import Select, WebDriverWait
def test_partly_refunded_invoice_links_to_its_credit_memo():
driver = webdriver.Chrome()
wait = WebDriverWait(driver, 10)
clickable, visible = EC.element_to_be_clickable, EC.visibility_of_element_located
driver.get(os.environ["APP_URL"] + "/login")
driver.find_element(By.ID, "email").send_keys(os.environ["QA_EMAIL"])
driver.find_element(By.ID, "password").send_keys(os.environ["QA_PASSWORD"])
driver.find_element(By.XPATH, "//button[text()='Sign in']").click()
wait.until(clickable((By.LINK_TEXT, "Configure"))).click()
wait.until(clickable((By.XPATH, "//button[text()='Payments']"))).click()
wait.until(clickable((By.LINK_TEXT, "Invoices"))).click()
wait.until(visible((By.XPATH, "//h1[text()='Invoices']")))
driver.find_element(By.XPATH, "//button[text()='Filters']").click()
Select(driver.find_element(By.ID, "refunded")).select_by_visible_text(
"Partly refunded"
)
driver.find_element(By.XPATH, "//button[text()='Apply filters']").click()
wait.until(EC.text_to_be_present_in_element(
(By.CSS_SELECTOR, "[data-testid='invoice-status']"), "Partly refunded"
))
driver.find_element(By.LINK_TEXT, "Open").click()
wait.until(visible((By.XPATH, "//*[text()='Refund amount']")))
memos = driver.find_element(
By.CSS_SELECTOR, "[aria-label='Credit memos against this invoice']"
)
memos.find_element(By.LINK_TEXT, "Open").click()
wait.until(visible((By.XPATH, "//*[text()='Payout method']")))
wait.until(visible((By.XPATH, "//*[text()='Refund issued']")))
driver.back()
driver.quit()
17 locators and 9 waits, 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 locators, no waits. Seven steps anyone on your team could review.
The XPath stops matching, the run goes red, and someone edits the file. Pie re-reads the screen on each run, so a renamed label isn’t a locator edit for your team.
The Pie test is copied word for word from Pie, “tap” and all. The Selenium test is ours, written to match it step for step.
Four reasons to stop maintaining a Selenium suite.
- 01
Free to download, costly to keep
A Selenium suite is paid for in engineer hours: page objects to structure, waits to tune and a Grid to host. In one study, flaky tests alone took at least 2.5% of a team’s productive time. With Pie, your team has no page objects, waits or Grid to keep up.
Source - 02
Everything around the library
Selenium’s docs say it “does not help you write well-architected test suites”. The structure, the page objects, the waits and the grid are your team’s to build. With Pie there is no suite to architect.
Source - 03
“But AI writes Selenium code now”
It does, and the Selenium project publishes docs to help coding agents do it. An agent saves the typing. Your team still reviews, owns and maintains every line. Pie’s tests are plain-English steps, so you have no test code to maintain.
Source - 04
Native apps need a second framework
Selenium automates websites, so a native app means another framework and another suite. Pie tests native iOS and Android apps too, with API and accessibility testing in beta.
Source
The library is free. The suite takes the hours.
Selenium drives the browser, and everything around it is your team’s to build.
| What you’re comparing | Pie | Selenium | 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, structure and repair tests, plus the CI or grid to run them and a second framework for native apps. | 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 code, with the locators and waits each step needs. | Pie |
| When the UI changes | No locators to update. Pie re-reads the screen on every run. | Locators live in your code. Page objects keep the fix in one place, and someone still makes it. | Pie |
| Native iOS and Android | Built in, on the iOS Simulator and the Android Emulator. | Built for desktop and mobile websites. Native apps need another framework, such as Appium. | 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. | A failed test tells your team where it stopped. Triage and the fix are theirs. | Pie |
| License cost | Custom pricing, tailored to your team’s requirements and testing volume. Contact Pie for a quote. | Free and open source. | Selenium |
Which fits your team, Pie or Selenium?
Pick Pie to
- Test more of your app without writing another script.
- Test your native iOS and Android apps as well as your website.
- Give your team back the hours it spends on locators and waits.
- Check your pull requests the way your users will use them.
- Add API and accessibility testing, both in beta.
Pick Selenium if
- Your team has the engineers to build and run the suite around it.
Switch from Selenium one flow at a time
No big rewrite. Your suite keeps 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 tests as Pie covers them
Compare Pie’s results with your Selenium runs, and delete each test 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 suite your team writes and maintains with tests its agents generate by exploring your app.
Selenium costs nothing to license. Stay if your team has the engineers to build and run the suite around it.
The license is. Selenium is open source under Apache 2.0. The 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”, and half the organizations in the World Quality Report 2025-26 name maintenance burden and flaky scripts as a test automation challenge.
Pie’s agents write and run the tests, with no locators for your team to repair.
Selenium is actively maintained, with a new release every few weeks. The question is who pays for the suite around it.
If your team spends more time repairing tests than learning from them, Pie takes that work over.
It can, and the Selenium project publishes docs to help coding agents write current Selenium code. The result is still test code your team reviews, owns and repairs when the UI changes.
Pie’s tests are plain-English steps, so there are no locators or waits to keep in sync.
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.
Flaky tests, setup and reporting. Reviewers on G2 and PeerSpot say timing issues and changing locators make tests flaky unless the framework around Selenium is built well, and that it takes good programming knowledge and has no built-in reporting.
In Pie each run comes with its results, and anyone on the team can read a test or add one in plain English.
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.
Retire the page objects. Keep the coverage.
Book a demo and bring your flakiest flow. We’ll show you the test Pie writes for it, with no waits to tune.
Sources
- Selenium repository. Apache-2.0 license; “A browser automation framework and ecosystem.”github.com/SeleniumHQ/selenium
- Selenium downloads. Language bindings for Java, Python, C#, JavaScript and Ruby, and the current release history.selenium.dev/downloads
- Selenium test practices. Selenium “does not help you write well-architected test suites”; page objects and explicit waits are the recommended structure.selenium.dev/documentation/test_practices · selenium.dev/documentation/test_practices/encouraged/page_object_models · selenium.dev/documentation/webdriver/waits
- Selenium overview and Grid docs. WebDriver is for “desktop and mobile website test automation”; Selenium IDE records tests; Grid runs tests in parallel on machines you host.selenium.dev/documentation/overview · selenium.dev/documentation/grid
- Using AI coding agents with Selenium (Selenium blog, 2026-09-29). Docs, an llms.txt and tested examples for coding agents that write Selenium code.selenium.dev/blog/2026/using-ai-agents-with-selenium
- 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 Selenium.conf.researchr.org/details/icst-2024/icst-2024-industry/1
- World Quality Report 2025-26 (Capgemini, Sogeti, OpenText), Fig 15. 50% cite maintenance burden and flaky scripts as a test automation challenge.capgemini.com/insights/research-library/world-quality-report-2025-26
- PeerSpot, Selenium HQ pros and cons. Summary lists complex setup that needs programming skills, no built-in reporting and no support for desktop applications; reviews dated May and November 2024.peerspot.com/products/selenium-hq-pros-and-cons
- G2, Selenium WebDriver reviews, most recent first. Reviews dated July 18, 2026 (flaky tests from timing and locator changes) and March 18, 2026 (programming knowledge needed, no built-in reporting).g2.com/products/selenium-webdriver/reviews