Skip to content
Independent guides for QA & test automationRSSEditorial policy
QA Vibes

Topic

Playwright

21 articles tagged “playwright”.

Playwright "page.goto: net::ERR_ABORTED; maybe frame was detached?": What Aborted the Navigation

Playwright's "page.goto: net::ERR_ABORTED", reproduced nine ways on a one-file local app and run in Chromium, Firefox and WebKit: a 204 response, two navigations at once, a test timeout, a page closed mid-load, route.abort() and a removed iframe. Why a download now says "Download is starting" instead, where the "maybe frame was detached?" suffix comes from, and the fix for each cause.

playwright · automation · tutorial

15 MIN

Element Click Intercepted: "Other element would receive the click" in Selenium, and "intercepts pointer events" in Playwright

One overlay, two tools: Sauce Demo's slide-out menu covers the product images, and clicking one fails in Selenium with ElementClickInterceptedException and in Playwright with a timeout whose call log says "intercepts pointer events". Why elementToBeClickable doesn't help, why closing the menu and clicking at once was flaky in Selenium and not in Playwright, and why force and JavaScript clicks are the wrong fix.

selenium · playwright · automation

12 MIN

Playwright "Element is not attached to the DOM": When Locators Avoid It, and When They Don't

"Element is not attached to the DOM" reproduced on Sauce Demo with element handles, and measured on a local page that replaces its button every 20 to 1,000 ms. Locator clicks never threw it, but timed out when the page re-rendered faster than they could act. locator.screenshot() and scrollIntoViewIfNeeded() threw it even at one re-render a second. What to use instead, measured.

playwright · automation · tutorial

11 MIN

Playwright "Executable doesn't exist": Why the Browser Revision in the Path Changed, and How to Fix It

"browserType.launch: Executable doesn't exist" reproduced by upgrading Playwright from 1.63.0 to 1.64.0 with one browser cache: the path asks for chromium_headless_shell-1248 and the cache holds 1243. Where that revision comes from, what npx playwright install removes, why installing browsers before npm ci gets the wrong revision, and which CI and Docker setups avoid it.

playwright · automation · ci cd

7 MIN

Playwright "Target page, context or browser has been closed": What Closed It, and How to Fix It

Playwright's "Target page, context or browser has been closed", reproduced on a one-file local app: a closed context, a popup that closes itself, a page kept between tests, and a script that closes the browser too early. Why a missing await in Playwright Test shows "Test ended." instead, why an assertion on a closed page says "Received: undefined", and the fixes for each.

playwright · automation · tutorial

12 MIN

Playwright Strict Mode Violation: Why a Locator Resolved to 2 Elements, and How to Fix It

Playwright's strict mode violation, reproduced four ways on Sauce Demo and this site's practice shop: six identical buttons, two equal prices, a substring match, and a hidden alert added by Next.js. How to read the error, why it fails immediately instead of retrying, how to fix each case, and why .first() is usually the wrong fix.

playwright · automation · tutorial

9 MIN

Playwright Timeout Errors: Which Timeout Fired, and What to Change

Playwright has seven timeouts and they fail with different messages. We triggered each one against a deliberately slow local app: the 5-second expect timeout, the 30-second test timeout and the misleading net::ERR_ABORTED that follows it, actions with no limit of their own, navigation, hooks, the global timeout and the webServer start-up. How to tell from the first line which one fired, and what to change instead of raising every limit.

playwright · automation · tutorial

15 MIN

Sauce Demo Error Messages: What Each One Means and How to Test It

A reference for the error messages on Sauce Demo, the practice shop testers automate first. Each message with its exact text, the input that triggers it, and where it sits on the page, the checkout errors problem_user and error_user cause, the alerts and page errors a test never sees unless it listens, and a Playwright spec with its real output.

playwright · test cases · tutorial

12 MIN

Azure DevOps: Publish Playwright Results and Import Test Cases

Publish Playwright's JUnit XML with PublishTestResults@2, including runs with failed tests. Troubleshoot an empty Tests tab, then use the separate CSV workflow to import manual test cases into Azure Test Plans.

azure devops · ci cd · playwright

11 MIN

Updated

API Test Cases: 34 Positive and Negative Cases, Run Against a Real API

A catalogue of API test cases where every case was sent to a real API. 34 requests to Restful Booker, grouped by endpoint, with what a well-behaved API should return and what this one did, followed by a Playwright spec that checks the contract and records the known defects.

api testing · test cases · playwright

12 MIN

Updated

Page Object Model vs Fixtures in Playwright: One Suite Written Three Ways

Should you use page objects, fixtures, or plain hooks in Playwright? We wrote the same three Sauce Demo tests all three ways, ran them, and measured the differences: how much code each needs, how many places a locator lives, where a failure points when a locator breaks, and what a beforeEach does to a test that doesn't need it.

playwright · automation · tutorial

8 MIN

Test Cases for a Login Page: 22 Cases, Run Against a Real Login

A login page test case list where every case was run. 22 cases against Sauce Demo, grouped by what they protect, with the error text the site actually showed, the cases a practice site can't answer, and a data-driven Playwright spec with its real output.

test cases · playwright · tutorial

11 MIN

Updated

Accessibility Testing with axe and a Keyboard: What Each One Catches

A hands-on introduction to accessibility testing. Scan a page with axe, read a violation properly, see the same bug in the accessibility tree and in your locators, then find out why a keyboard pass misses it entirely. Includes an exercise with an answer key.

accessibility · playwright · automation

9 MIN

Cypress vs Playwright vs Selenium: The Same Test in All Three, Timed

One test (log in, add a product, check the cart badge) written in Cypress, Playwright, and Selenium against the same public demo shop. How the code differs, how long each run took, what broke during setup, and which framework fits which team.

cypress · playwright · selenium

7 MIN

Updated

UI Test Automation Mistakes: Seven We Reproduced on a Demo Shop

A fixed wait that added up to five seconds to a test, an assertion that passed for text that doesn't exist, a click on the wrong product, and a dialog listener that froze the page. Each mistake is reproduced with real output, and each has a fix.

ui automation · best practices · cypress

8 MIN

Updated