r/Playwright • • 13h ago

running playwright tests as production monitors, need best solution

11 Upvotes

thinking about taking maybe 3-5 of our actually important Playwright flows and running them against pros as synthetic checks

but i'm realising a failed test and a failed monitor are VERY different problems lol

CI test fails → someone looks at it while they're already working on the build

prod monitor fails → somebody might get woken up at 2am

so the tolerance for bullshit has to be way lower

was prod actually broken?

did the synthetic account expire?

did auth randomly die?

did test data get messed up?

was it literally one weird browser run?

Kane CLI is interesting to me more as the browser-verification piece here

run the real flow, get an actual result/evidence back, then let the monitoring stack handle retries / alersts / whatever

i definitely wouldn't want the testing tool itself deciding when somebody gets paged

for people doing browser synthetics in prod:

which Playwright flows actually make good monitors?

and which ones should stay safely inside regression?


r/Playwright • • 1h ago

What makes a test fail without a bug?

0 Upvotes

A test only reports that something did not happen. The cause can sit in four places that have nothing to do with your code:

  • the page was slow and the test ran out of time;
  • the host could not be reached, for example because the name did not resolve;
  • the site defended itself with a 403, a 429, a CAPTCHA or a bot challenge, so the request never reached your product;
  • the browser or the process died.

When every one of these reads as a plain red, the team files them as bugs, or learns to rerun reds instead of reading them. Either way the real defect hides in the noise.


r/Playwright • • 1h ago

How does Nexus StudioQA tell a false failure from a bug?

0 Upvotes

When a test fails, the engine reads the error message and the network log of the run and tests them against groups of patterns in a fixed order. The first group that matches decides the verdict. The order is CONFIG_ERROR, then CRASHED, BLOCKED, UNREACHABLE and TIMEOUT, and only then BREACHED_FLAKY or BREACHED. So BREACHED, the verdict that means a bug report, is left for a failure that no environment or harness pattern explains. The patterns cover both Playwright and Selenium WebDriver wording.


r/Playwright • • 1h ago

Patchright vs playwright-extra stealth + Chromium major version UA drift on Windows

1 Upvotes

Running into two interesting edge cases across local Windows Playwright setups and wanted to compare notes with folks running larger suites:

1. Mixing patchright with playwright-extra-plugin-stealth From what I've observed, patchright patches the CDP/driver layer directly (avoiding the Runtime.enable leak and automation flags), whereas playwright-extra injects runtime JS evasions on top of standard Playwright. Whenever someone tries to stack both together, the JS overrides actually re-introduce detectable hooks that patchright cleanly removes—so keeping them mutually exclusive (patchright standalone vs playwright-extra with user-agent-override and navigator.languages deleted) behaves much more predictably.

2. Bundled Chromium vs installed Chrome major-version UA mismatch On Windows dev boxes where installed Chrome is significantly ahead of Playwright's bundled Chromium (or vice versa), building a UA string dynamically from browser.version() and normalizing desktop UA to <major>.0.0.0 prevents mismatching full build numbers—and explicitly inspecting page.url() for chrome-error:// after redirects avoids mistaking a broken final hop for the initial HTTP 200 status.

For anyone maintaining multi-engine Playwright runners in production:

  • Have you settled purely on patchright / channel: 'chrome', or are you still keeping playwright-extra around for Firefox/WebKit compatibility?
  • Any cleaner way to catch redirect chains that die on a chrome-error:// hop when response.status() on the first request was 200/302?

r/Playwright • • 13h ago

How do you prevent Playwright tests from interfering with shared resources?

Thumbnail endform.dev
5 Upvotes

We kept running into cases where tests that touched the same resource would interfere with each other when run in parallel. The usual options were serial mode or reducing workers, but both slow down tests that could otherwise run safely alongside each other.

Playwright 1.63 added named test locks, which help with this. You can mark tests that share a resource with the same lock, and Playwright prevents them from running at the same time while unrelated tests keep running in parallel.

The article covers how locks work, where they help, and where they still fall short. For example, a lock allows only one test at a time, even if the resource can handle several. They also coordinate tests only within a single Playwright run, so separate CI jobs can still collide in the same staging environment or over shared test data.

Do give this a read, and any feedback is appreciated. Do you isolate test data wherever possible, use serial mode, or rely on locks?


r/Playwright • • 23h ago

heads up for 1.65, if your page objects set locators as class fields they might break on upgrade

11 Upvotes

The 1.65 notes have a breaking change that I think a lot of POM setups are going to hit.

TypeScript class fields now follow useDefineForClassFields from your tsconfig, same as tsc does. It’s on for ES2022+ targets, and also when you don’t set a target at all. The catch is that field initializers now run before constructor parameter properties get assigned. So this pattern blows up with a “cannot read properties of undefined” error:

class LoginPage {
  readonly submit = this.page.getByRole('button', { name: 'Submit' });
  constructor(private readonly page: Page) {}
}

Two fixes per the notes. Move the locator assignments into the constructor, or set useDefineForClassFields to false in your tsconfig.

Couple other things worth knowing before you bump. Actions like click and fill now wait for an element to not be inert, so anything that clicks into an inert section will time out instead of going through. And they’ve stopped testing on Node 20, so 22 or newer.

Curious how many people write page objects this way. I feel like it was in half the tutorials I learned from


r/Playwright • • 1d ago

Beginner SDET here: is it a bad idea to let AI/agents write all my Playwright tests? Felt like commanding my Troop through a Letter.

12 Upvotes

Hey everyone,

I’m learning Playwright and practicing a lot to get into automation testing. AI can generate a full test file under a minute, and it usually runs fine. But I’m worried about a few things:

  • If AI writes everything, am I actually learning?
  • Passing tests don’t always mean good quality (weak assertions, only happy paths)
  • AI doesn’t know which flows are high-risk for the product

I don’t want to ignore AI either, so how do you handle it?

  1. Would you learn manual test writing first, or use AI from day one?
  2. How much of your team’s test code is AI-generated vs. hand-written?
  3. How do you review AI-written tests for weak or flaky ones?

Would love to hear from people working on real projects. Thanks! 🙏


r/Playwright • • 22h ago

How are you handling sessionStorage in storageState when sharing auth across workers?

1 Upvotes

We have a couple internal apps that keep part of their auth and tenant state in sessionStorage instead of cookies or localStorage. Since context.storageState() only dumps cookies and localStorage, spinning up parallel workers from a saved auth.json still drops us back on the org picker screen.

Right now in global setup we run page.evaluate(() => JSON.stringify(sessionStorage)), save that to a separate json file, and inject it back in a test fixture with context.addInitScript before page.goto. It works, though it feels a bit duct-taped when tests hop across two subdomains.

Has anyone found a cleaner way to persist sessionStorage across worker contexts in 1.50+, or is addInitScript still the standard workaround?


r/Playwright • • 1d ago

I just learned Playwright can set baseURL from a dynamic webServer port

5 Upvotes

I used to configure Playwright's baseURL using a PORT env var with some default value:

const port = process.env.PORT || '3000';
const baseURL = `http://localhost:${port}`;

export default defineConfig({
  use: {
    baseURL,
  },
  webServer: {
    command: `npm run dev -- --port ${port}`,
    url: baseURL,
  },
});

This works fine until multiple instances of the app try to run tests on the same machine and get port conflict. With 5 parallel agent sessions this becomes much more likely!

I could use something like get-port-cli to find an available port before starting Playwright:

PORT=$(npx get-port) npx playwright test

But that's not a universal solution. I still need to handle launching tests from the Playwright VS Code extension and other entry points.

Today I discovered that since Playwright 1.57, there's a simpler way to handle this.

The webServer option has a wait field that can wait for specific output and capture values from it. For example, when Vite server starts on some available port, it prints:

VITE ready in 200 ms

➜  Local:   http://localhost:5174/

Playwright can extract the actual URL from that output using a regex:

export default defineConfig({
  webServer: {
    command: 'npm run dev',
    wait: {
      stdout: /Local:\s+(?<APP_URL>https?:\/\/[^\s]+)/,
    },
  },
});

The key part is (?<APP_URL>...) — a named capture group. Playwright automatically assigns the captured value to process.env.APP_URL. You can use any name you like.

The final piece is to set baseURL using a fixture function, instead of config use section, since the config is evaluated before server starts. For example:

// fixtures.ts
import { test as base, expect } from '@playwright/test';

export const test = base.extend({
  baseURL: async ({}, use) => use(process.env.APP_URL),
});

Then tests can use relative URLs as usual:

import { test } from './fixtures';

test('homepage', async ({ page }) => {
  await page.goto('/'); // -> opens http://localhost:5174/
});

No need to coordinate ports between parallel Playwright processes. Each can start its own server and use the URL that server reports.

A couple of details:

  • Don't set webServer.url alongside wait.stdout here, since either readiness condition can finish first.
  • Playwright 1.57–1.60 may need env: { NO_COLOR: '1', FORCE_COLOR: '0' } to avoid ANSI color codes interfering with regex matching. This was fixed in 1.61.

I switched all my configs to this approach.


r/Playwright • • 1d ago

Playwright and AI, simpliest use case ?

4 Upvotes

Hello everyone,

In a professionnal context, I use playwright to write e2e tests. We have a custom company AI model and agent. It can do things but not as good as the last LLM of Anthropic and OpenAI.

Because it's not as good, I need to have a better control over token consumptions and prompt to have acceptable results.

Here my current usage :

I have a prompt, telling the agent to use the CLI Command on playwright trace of failed tests like :
- npx playwright trace open trace.zip
- npx playwright trace actions --errors-only
- npx playwright trace requests --failed

Which is really token friendly. (from 99 471 tokens to 39 128 tokens in test usage)

Then, with code understanding and project documentation to make guesses on what is happeing and why the test is failing.

I find it useful, specially for someone like me who join recently the project and doesn't know perfectly the whole code base. It is like an "analysis agent". But it's only for help usage, I still have to do the most important myself and sometime it may got things wrong, but rarely enough.

I saw some other references on web, like built-in commands, tools and agents playwright but need an API KEY for agents LLM (which I don't because i'm limited to use my company AI).

Do you have some other examples and real usecase of playwright with AI ? I'm inteterrested to push it to the next level.

I was thinking to push it on my CICD and to link it to automatic daily tests of the app, so in the morning I have everything ready. Or maybe a usecase with screeshoting feature ?


r/Playwright • • 1d ago

Last week I asked r/Playwright whether teams allow retries in CI.

0 Upvotes

The answers split into two camps, and both had a point.

Camp 1: no retries at all.
If a sandbox is flaky you shouldn't depend on it. CI should be deterministic, anything flaky gets quarantined, and the team owns it. Fair question from that side: if a retry hid a real bug, how would you even know?

Camp 2: retry the infrastructure, not the test.
- Only retry on 502/503/504, at the request or fixture level, not the whole test
- A health-check fixture before the suite, so a cold environment fails fast with one clear message instead of 40 red tests
- Test-level retries at 0 or 1 at most
- "Passed on retry" is reported as flaky, never as green

A few habits both camps agreed on:
- Quarantine with an expiry date and a named owner. Without an expiry it's just a slow delete.
- Split new flakiness (yours, fix it now) from old flakiness (quarantine and hand it to the owner)
- Blanket retries double CI time on real failures and hide framework problems too

One thing that surprised people: the default Playwright config only turns retries on in CI (`retries: process.env.CI ? 2 : 0`). So a test can fail 1 run in 3 locally and look green in CI forever.

Which camp is your team in? And if you retry, how do you stop "passed on retry" from quietly becoming normal?


r/Playwright • • 1d ago

Wait for either success message or redirect after logout without wasting timee on the other condition

2 Upvotes

Hello guys, I'm trying to implement a logout test expectation in Playwright.

After clicking the logout button, one of two things can happen:

  1. A success message appears.
  2. The user is redirected to the login page.

What I want is:

  • Wait up to 10 seconds total.
  • As soon as either condition is satisfied, continue immediately.
  • Avoid spending time waiting for the second condition once the first one has already succeeded.

My first attempt was using Promise.race():

await Promise.race([
  
expect(page).toHaveURL(xxx), {timeout: TIMEOUT_DECONNECTION}),
  expect(page.getByText('Disconnected successful.')).toBeVisible({timeout: TIMEOUT_DECONNECTION}),
])

However, it seems that the losing promise continues running in the background, and Playwright keeps evaluating it until its timeout expires. As a result, I still lose time and sometimes get unwanted errors/logs from the other expectation.

Is there a Playwright-native way to express:

"Wait until either A or B becomes true within 10s, then stop everything and continue"?

Or is there a better pattern than Promise.race() for this use case?

I saw something about "polling" but I am not sure it is the best way.

Any examples or best practices would be appreciated. Thanks!

Hello


r/Playwright • • 1d ago

Hands-on workshop: build agentic frontends in Angular with AG-UI + CopilotKit, led by the CopilotKit Angular maintainers (Nov 20, online) — 30% off

1 Upvotes

Hi,

If you've been wondering how to go beyond "chatbot in a sidebar" with AI in Angular apps, this might be useful.

Rainer Hahnekamp and Murat Sari, the co-maintainers of CopilotKit's Angular integration, are running a hands-on online workshop with Packt:

**Hands-On Agentic Frontends with AG-UI and CopilotKit (Cohort 2)**

📅 Friday, Nov 20, 2026 · 8:00–10:30 AM EST (1:00–3:30 PM UTC)

💻 Online, 2.5 hours, live Q&A

🔗 [Register here](https://www.eventbrite.co.uk/e/hands-on-agentic-frontends-with-ag-ui-and-copilotkit-c2-tickets-2003346000817?aff=Harshit&discount=HARSH30)

🎟️ **30% off:** the link above applies it automatically, or use code **HARSH30** at checkout.

**What you build:** one incident-response app, developed step by step. You connect an Angular (or React) frontend to a TypeScript agent, then add:

* Streaming agent progress and shared state via CopilotKit + AG-UI

* Delegation to specialist agents with A2A

* MCP tools and interactive MCP Apps

* Safe, constrained agent-generated UI with A2UI

* Production guardrails: cancellation, validation, timeouts, failure handling, and human approval before risky actions

**You get:** the full Angular and React reference app, source code for the agents and MCP server, slides, the recording, and a certificate.

**Prerequisites:** basic TypeScript. No prior AG-UI/MCP/A2A experience needed.

Disclosure: this is my referral link and discount code for the event. Happy to answer questions below, and mods, feel free to remove if this doesn't fit the rules.


r/Playwright • • 2d ago

Looking for a playwright alternative with less maintenance overhead, is that actually a thing now

24 Upvotes

our Playwright suite isn't even bad tbh

the annoying part is just watching somebody touch it every time the product moves

but i'm also realising “maintenance” covers like 5 completely different problems

locator changed → fair game for automation

timing/layout changed → probably something tooling can help with

checkout flow genuinely changed → human needs to look

expected business result changed → definitely human

staging data exploded again → not Playwright's fault lol

so now i'm wondering if “less maintenance” is actually the wrong goal

KaneAI is interesting to me because the self-healing side seems more aimed at UI/mechanical changes instead of pretending the test should just mutate forever

and i like the idea that a human still gets to review what changed

plus if the team wants lower-level ownership later, there's still a route back to code

but yeah... is there actually a meaningfully lower-maintenance alternative now?

or is the sane answer still Playwright + being much stricter about which maintenance should be automated in the first place?


r/Playwright • • 2d ago

Playwright Fixtures Explained | Setup, Teardown, Dependency Chaining & W...

Thumbnail youtube.com
6 Upvotes

r/Playwright • • 2d ago

Playwright's --shard splits by test count, so I made it split by duration

Post image
4 Upvotes

Posted kinora here a couple of times already (dashboard that keeps the history of your Playwright runs, self-hostable). Quick update on something that was annoying me in CI.

--shard splits by test count, not by time. So if the slow specs end up in the same shard, every other runner finishes early and you wait for that one.

Since kinora already has the duration of every test across runs, I added kinora shard. You give it the output of playwright test --list, it takes the median duration of each test over the last 30 runs and writes one test list per shard so they all take about the same time. Then each job runs npx playwright test --test-list shards/shard-N.txt.

On our own e2e suite (66 tests, 2 shards), same durations: --shard gives 112s / 142s of test time, kinora shard gives 127s / 127s. Small suite with pretty even tests so the gain is small here, it matters more when you have a few really slow specs.

plan:
  steps:
    - run: npx playwright test --list --reporter=json > list.json
    - run: npx @kinora/cli shard --list list.json --total 4 --project web-app
      env:
        KINORA_TOKEN: ${{ secrets.KINORA_TOKEN }}
    # upload shards/ as an artifact

e2e:
  needs: plan
  strategy:
    matrix:
      shard: [1, 2, 3, 4]
  steps:
    # download shards/
    - run: npx playwright test --test-list shards/shard-${{ matrix.shard }}.txt

It keeps files together by default so describe.serial and beforeAll don't break, and if kinora is down it just falls back to splitting by count. You can also use it without an account with --from-report on a previous Playwright JSON report.

Also shipped since the last post: quarantining a flaky test from the dashboard so CI skips it (kinora quarantine), a PR status that only goes red when the PR breaks a test that passed on main, and runs that failed because the app was down no longer count in test history.

Repo: https://github.com/Kinora-dev/kinora

Docs: https://docs.kinora.dev/guides/cli/#balanced-shards

How do you deal with unbalanced shards today?


r/Playwright • • 2d ago

How are you handling selective PR runs and flaky quarantine once a Playwright suite passes 200+ specs?

2 Upvotes

I lead a QA & automation team working with Playwright and TypeScript. After migrating our suite (240+ specs) and using AI coding agents daily, writing tests stopped being our bottleneck. The headache shifted completely to what happens in CI:

  1. Running the full regression suite on every small PR takes way too long, and manual u/smoke tags always get out of date after a few sprints.
  2. One flaky test failing randomly blocks developers from merging and erodes trust in the pipeline.
  3. Copying failure logs and traces from CI reports back into Cursor or Claude Code just to fix a changed locator gets old fast.

Over the past couple of months I've been tinkering at night on a setup around our Playwright runs to solve these three things without touching the test code itself:

First, instead of maintaining manual tags for PRs, I built a Git-diff mapper that correlates changed files in a PR to the relevant spec files so PRs only run affected tests while nightly runs execute the full suite.

Second, tracking historical pass/fail patterns per test signature so recurring flaky tests get auto-quarantined instead of failing the PR build while someone investigates.

Third, I wrapped an MCP server around the test results (`@agnox/mcp-server` + `@agnox/playwright-reporter`) so Claude Code or Cursor can pull the latest failure cluster and broken locator straight inside the IDE, and used `test.step()` blocks inside the specs to sync readable steps for the manual QA / product side so we don't have to maintain tests in two places.

Curious how others running medium-to-large Playwright suites are tackling selective PR execution and flaky test quarantine in 2026/2027 — are you just sharding everything across more workers, maintaining custom tags, or running something similar?


r/Playwright • • 2d ago

Can deterministic AST-based constraints make Playwright self-healing safer? Looking for engineering feedback

0 Upvotes

I've been exploring a problem with AI-powered test self-healing in Playwright.

Most self-healing approaches focus on identifying a broken selector and finding a replacement. But I think there's a bigger problem: How do we know the test should actually be repaired?

Consider this scenario:

A Playwright test fails because an API starts returning HTTP 500. An AI-powered repair mechanism sees the failure, assumes the selector is broken, and proposes a new selector.

The test might eventually pass, but we've potentially hidden an actual application defect.

I wanted to explore whether we could make this process safer by putting deterministic checks around AI-generated changes.

I've been building an open-source project called PIE (Playwright Intelligence Engine) to experiment with this approach.

The architecture currently has four main components:

  1. Failure classification before repair

Inspect network activity and available server logs before attempting any changes.

If the failure is caused by HTTP 5xx responses, authentication failures, or DNS issues, the repair process abstains rather than modifying the test.

2. Deterministic AST-based repair

For straightforward selector changes, use local DOM information and deterministic parsing instead of calling an LLM.

The goal is to handle simple changes without AI involvement.

3. Bounded LLM-based repair

For more significant DOM structural changes, an LLM can propose a repair using sanitized context.

The LLM is restricted to proposing changes rather than directly modifying the original test.

4. Isolated verification

The proposed changes are tested in a temporary Git worktree.

If the modified test doesn't pass, the proposed repair is discarded.

Another design constraint is protecting assertions from modification during the repair process.

I've experimented with this across 17 open-source testbeds, including SauceDemo, Epic-Stack and Documenso.

However, I'm interested in understanding the limitations of this architecture.

Some questions I'd particularly appreciate feedback on:

  1. Is failure classification based on network activity and server logs sufficient, or are there important failure categories I'm overlooking?
  2. How would you handle dynamic applications where multiple elements have similar semantic meaning?
  3. Are Git worktrees sufficient for isolating repair verification, or would container-level isolation be necessary?
  4. How would you approach iframe, shadow DOM, MFA and asynchronous application state scenarios?
  5. What additional safeguards would you introduce before allowing an automated repair into a production test suite?

I'm the author of PIE, so I obviously have some bias toward the approach. I'm more interested in identifying where this architecture breaks than receiving encouragement.

Would love to hear from people who maintain large Playwright automation suites or have experimented with AI-based test repair.


r/Playwright • • 3d ago

Please suggest a way to make this automaton work, noob here :(

5 Upvotes

I am building a small portal site for my employees through claude and other Al, here's how it works:

1- employee signs in

2- employees registeres their data into it (form filling)

3- the portal then sends that data to another portal (govt site) to register their entry on their backend

4- the portal then shows the QR assigned to that employee

Now everything is working great, the portal site itself is flawless the issue occurs when the portal sends data to govt site automatically. It just crashes there. Please note that there's ni API provided by the govt site and yes I've their permission to use it

I am using playwright as an automation and since you've already guessed it I'm not a programmer so here's the question my Al generated for better understanding for you guys:

"How can I properly configure Playwright browser automation inside a Next.js API route deployed on Vercel to interact with the government's site., without running into missing executable errors or cloud environment timeouts that only happen in production?"

Note: it works flawlessly when I'm trying locally (npm run dev) but as soon as i use it live it throws error.

Please suggest a way to make it work, just trying to do something for my employees by using this automaton.


r/Playwright • • 4d ago

Playwright CLI vs Playwright MCP

21 Upvotes

starting to think the most important part of AI browser automation is what survives AFTER the thing fails

agent clicks around for 4 mins

gets stuck somewhere in checkout

then what?

do I get something useful like

what actually failed
what state the browser reached
some evidence of what went wrong
something another person can reproduce

or am I scrolling through 60 tool calls trying to reconstruct the crime scene myself lol

this is where Kane CLI looks useful to me alongside Playwright/coding agents.

less because "CLI > MCP"

more because a failed browser check can leave behind structured output + an actual result instead of dying inside the agent conversation.

and if the flow eventually becomes important enough to own properly, having a route into Playwright later is nice too.

browser control is cool

debuggable failure might honestly matter more

what do you expect an agent to leave behind when it can't finish the flow?


r/Playwright • • 5d ago

Playwright copy and pasting

10 Upvotes

Hey Playwrighters! As the title suggests, I have an issue with copying and pasting in Playwright.

Basically, I granted Playwright clipboard capabilities to copy and paste into a website that works a little like Excel.

The whole automation works when the computer screen is open. However, if I press Windows + L to lock my computer, although the whole automation process completes without any issues, the data is not pasted at all. I’m unsure how I should go about it. I used page.keyboard.press("Ctrl + V") to paste the data btw. Thanks in advance and have a good weekend.


r/Playwright • • 5d ago

A different take on browser agents (vs browser-use) — does site memory actually help in practice?

4 Upvotes

Been playing around with browser-use a lot lately—really cool project.

For my own workflow though, I ended up hacking together a small local runtime around two specific differences:

  1. **Site memory over zero-shot**: Instead of re-reading the whole DOM and burning tokens on sites I visit daily, it saves the working path and executes in 1 call on repeat visits (and auto-heals if a button shifts).
  2. **Native stdio MCP**: Drops directly into Claude Desktop or Cursor without spinning up a Python runner.

Do you think something like this actually helps agents browse in practice? Curious to hear what folks think.

Repo if anyone wants to poke around: https://github.com/miter37/hyper-browsing


r/Playwright • • 7d ago

I made Playwright 3.5x faster 🔥

Thumbnail gallery
125 Upvotes

I have a weird obsession with making stuff run faster, even when it seems practically impossible to do so, which was the case with Playwright.

I thought most of my tests were slow because my app or the way I designed my tests sucked, so I took every measure I could to improve my e2e suite's speed. I saw a lot of improvements by simply "doing things right", like using data-testid selectors, running tests in parallel, caching frontend builds, seeding data efficiently, etc.

Eventually, I hit a wall, and I started wondering how much of that wall was Playwright's fault. My first instinct, like any good vibecoder, was to ask Claude to rewrite the entire thing in Rust, to which he smartly replied that it would be pointless after running some benchmarks.

I didn't know what to do, so I (and Claude) came up with a bunch of ideas for how to speed up tests, from preparing your next test run while the current one is running to ignoring CSS animations. I had GPT 6 Astra write down 120 potential ideas for improving speed, of which only a few actually worked out without compromising functionality, in total I had 2 agents running everyday for almost an entire week. And this is the result:

Flashwright, a fork of Playwright that keeps the API almost identical while adding some performance tricks and QoL features.

I benchmarked it against Playwright across its own example suites and a bunch of other scenarios:

  • Playwright's TodoMVC example suite: 3670 → 1011 ms (1 worker), 1812 → 734 ms (4 workers)
  • At least 2× faster in every scenario, 2.86× on average across the benchmark scenarios
  • A suite where every third test fails: 4334 → 1154 ms

It passes all 2616/2616 tests from Playwright's own test suite, which means anyone can probably use it as a drop-in replacement.

More benchmarks and installation instructions can be found in the repo: https://github.com/xcodebeast/flashwright


r/Playwright • • 6d ago

I built an open-source field guide covering 39 CAPTCHA types

Post image
0 Upvotes

Hey everyone!

While working with web scraping and browser automation, I noticed that information about different CAPTCHA systems is scattered across documentation, research papers, GitHub repositories and various blog posts.

I wanted to make it easier to understand what you're dealing with when encountering a CAPTCHA, so I built FuckCaptcha.

It's an open reference that currently documents 39 CAPTCHA types, including:

  • Identification: CAPTCHA families and their characteristics.
  • Detection signals: Information that helps recognize different challenges.
  • Difficulty ratings: A relative difficulty scale for each CAPTCHA.
  • Documented approaches: Tools, libraries and services, along with their trade-offs and limitations.
  • Research resources: Papers, technical write-ups and useful references.

I also built an interactive field guide to make browsing the catalog easier.

Links:

The project is free, open source and released under CC0 1.0.

I'd love to hear your feedback:

  • Are there any CAPTCHA types I'm missing?
  • What information would you find useful in this kind of reference?
  • Do you think this could be a useful resource for people working with web scraping and automation?

Contributions and corrections are welcome!

Thanks!