Flaky Playwright Tests: Find the Cause, Fix It, Prove It's Fixed
A field guide to flaky Playwright tests, organised by the error you are staring at, with a loop that proves the fix holds.
Engineering
The Blendra Blog
Practical guides for QA engineers, SDETs, and developers building reliable Playwright test automation and CI pipelines.
Featured
Latest articles
Playwright Locators: A Ranked Guide to Selectors That Survive Redesigns
A ranked guide to Playwright locators, with the way each one breaks and how to narrow a locator that matches too much.
Playwright Codegen: Record a Test, Then Make It Maintainable
How to get the most out of Playwright codegen, and the five refactors that turn a recorded script into a test you can keep.
Playwright Authentication: Log In Once and Reuse It Safely
Four ways to handle login in Playwright, when each one breaks, and how to keep credentials and state files out of git.
Playwright Sharding: Split Your Suite Across CI Machines
Workers, fullyParallel and shards are three different knobs. When to use each, with complete GitHub Actions and GitLab CI configs.
Playwright Assertions: Web-First Checks That Actually Prove Something
The Playwright assertions worth knowing, the ones that pass no matter what, and how to check values that change on every run.
Playwright with pytest: A Practical pytest-playwright Setup
From an empty folder to a CI-ready Playwright Python suite with pytest, with every file shown and every command tested.
Playwright Page Object Model: When It Helps, When It Hurts, and How to Wire It with Fixtures
A small, honest page object model for Playwright, wired in with fixtures, and the patterns that make page objects worse than none.
Cypress vs Playwright in 2026: A Factual Comparison with the Same Test in Both
A dated, checkable comparison of Cypress and Playwright, built around one test written in both, with where each tool genuinely wins.
How to Write Test Cases That a Person Can Run and a Test Can Prove
A test case template with a fully worked example, built so every expected result is something a person can see and a test can assert.
Playwright Network Mocking: page.route, HAR Replay and When Not to Mock
How to use page.route to create states your real backend won't give you on demand, and where mocking makes an end-to-end test lie.
Playwright Trace Viewer: Find Why a Test Failed in CI
Set up traces in CI, get them out of a failed job, and read them in five steps to find the real cause of a failure.
Playwright Auto-Waiting: What It Waits For and When You Still Have to Wait
Playwright waits for a lot, but not for everything. Here is the exact list, and what to do for the rest.
data-testid Best Practices: Naming, Ownership and Shipping to Production
Test ids make selectors boring in the best way. A naming scheme, an ownership rule and the production question, answered.
Playwright Test Data: Seed, Isolate and Clean Up Without Flakes
Patterns for creating, isolating and cleaning up test data in Playwright so parallel tests stop colliding.
Playwright Environment Variables: baseURL, Secrets and Several Environments
One config for local, staging and production runs, with secrets that never land in the repo or the test file.
Playwright in GitLab CI: Docker Image, Reports and Parallel Jobs
A complete .gitlab-ci.yml for Playwright, with the image, caching, test reports and sharding explained line by line.
Migrate from Cypress to Playwright: Command Map, Plan and Pitfalls
A command-by-command map from Cypress to Playwright, plus a migration plan that keeps CI green while you switch.
Selenium to Playwright Migration: A Step-by-Step Plan
How to move from Selenium to Playwright one flow at a time, with a mapping table for waits, locators and assertions.
Playwright Visual Testing with toHaveScreenshot: Stable Snapshots in CI
Visual comparisons that don't fail on every font change: baselines, masks, thresholds and the CI setup that keeps them stable.