Playwright VS Cypress

The foundational decision is understanding that Playwright is a control library, not a browser. It speaks Chrome DevTools Protocol (CDP) to whatever binary you point it at, and the binary is entirely separate from the library. This distinction is what makes a remote browser service possible.

Repository: https://github.com/microsoft/playwright Documentation: https://playwright.dev/docs/intro License: Apache 2.0 Free Tier: Unlimited (open source; you pay for compute/hosting) Best for: SPAs, client-rendered dashboards, sites that gate content behind click interactions, any page that simply doesn’t exist until JavaScript runs.

Playwright

Starting from Bun v1.3.12, a new experimental API called Bun.Webview was introduced. It enables simple browser automation and can partially replace tools like Playwright. Pretty exciting, so I gave it a try.

Playwright is the recommended choice for new projects, since it is faster than Selenium, has a cleaner async API, and supports Chromium, Firefox, and WebKit.

Extension channel and executablePath now resolve from CLI flags and environment variables (#40572)

How does this compare to Playwwright? It got a similar feature recently [0]

[0] https://github.com/microsoft/playwright/releases/tag/v1.59.0

Each Rendershot worker is a Docker container running an ARQ (Redis-backed) job queue. Jobs come off the queue, get rendered with Playwright, and the resulting bytes are uploaded and the file path written back to Postgres. Concurrency is bounded; the worker fleet scales horizontally — no shared state between workers, just one Chromium process each.

#8683 — Tuning video performance (closed 2021)

The release notes span three versions: v1.56 shipped the agents themselves, v1.58 shipped the token-efficient CLI (playwright-cli), and v1.59 shipped the agent-facing APIs — browser.bind() for MCP interop and page.screencast for video receipts. The naming and the split are what matter — Microsoft built the same architecture I built. They built it better in several specific ways and worse in one.

The project involved heavy use of iframes... and turns out, Cypress has no elegant way of handling those in tests. And guess what? I found this issue dating back to 2016, filled with people also disappointed to find out how hard it is to test iframes.

This is pretty cool - the Jira/Linear integration could save a ton of manual work. How do you handle test data setup and teardown? That's usually where these workflows get messy.

For alternatives in this space, there's qawolf (https://qawolf.com) for similar automated testing workflows, or I'm actually building bug0 (https://bug0.com) which also does AI-powered test automation, still in beta. For the more established players there's always Cypress (https://cypress.io) and Playwright (https://playwright.dev) if you want to stay closer to code, or TestRail (https://testrail.com) + Browserstack (https://browserstack.com) for the enterprise route.

Will definitely try the demo - the acceptance criteria parsing sounds like it could catch a lot of edge cases that usually slip through.

// cypress/support/e2e.js // load and register the grep feature using "require" function // https://github.com/cypress-io/cypress/tree/develop/npm/grep const registerCypressGrep = require('@cypress/grep') registerCypressGrep()

End-to-end tests are better suited for accessibility checks because they closely mimic what users will see and interact with. However, there are some quirks with Cypress, such as handling tab keys to check for focus. You might want to look into cypress-real-events for a potential solution. (Edit: It seems like this issue is finally being considered in Cypress priorities).

Details on the Cypress NPM package can be found here: https://www.npmjs.com/package/cypress

However, starting with version 12, Cypress blocked projects using the 'cypress-cloud' module, impacting these third-party services. SorryCypress now only works with older Cypress versions, while Currents.dev has ended its official support for Cypress. This change has disrupted many teams' testing workflows.

Feature: Web Accessibility Tests Feature: Web Accessibility Tests Scenario Outline: Verify all WCAG Violations Given I am on the "" page And Verify all Accessibility Violations Scenario Outline: Verify P1,P2 WCAG Violations Given I am on the "" page And Verify only P1, P2 issues Examples: | url | | https://google.com | | https://amazon.in | | https://agoda.com | | https://bing.com | | https://cypress.io |

Cypress

In this blog post, we'll explore a Cypress test that replicates this scenario, utilizing the powerful intercept command to manipulate network requests and responses.