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

Archive

Articles

47 guides on automation frameworks, API testing, CI pipelines, and the process habits that make quality teams trusted.

2026 · updated entries marked

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

Cypress "failed because this element is detached from the DOM": The Messages That Replaced It, and the Fixes

"cy.click() failed because this element is detached from the DOM" no longer exists: Cypress 12.0.0 replaced it with two messages about the page updating. We reproduced both in Cypress 16.1.1, on Sauce Demo and on two one-file local pages: chained actions, a wrapped element kept too long, and a button that disappeared while covered. Why the alias the error suggests failed for a button that changed, and why Cypress could click a button replaced every 20 ms.

cypress · automation · tutorial

9 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

Selenium "stale element reference: stale element not found": What Replaced the Element, and How to Fix It

StaleElementReferenceException reproduced on Sauce Demo with Selenium 4.49.0: a Select reused after sorting, and an Add to cart button clicked twice. Why the product names didn't go stale but silently kept the old order, why a catch-and-retry around the same WebElement failed every attempt, what a retry around a fresh lookup actually did, and a Chrome password check that made clicks disappear.

selenium · java · automation

9 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

Black-Box Testing Techniques: 4 Examples on One Checkout

Choose between equivalence partitioning, boundary value analysis, decision tables, and state transitions using one checkout. Compare the tests each produces, then try the matching generator or practice questions.

test cases · tutorial · manual testing

9 MIN

Updated

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

Defect Leakage, Escape Rate, DRE and DDP: One Fraction, Four Names

The four common defect metrics that compare bugs found before and after a release are one fraction under different names. This guide gives the formulas with their sources, shows how a different denominator changes the answer, explains the time window, puts the often-quoted 85% average in context, and shows when a change between releases is real.

quality metrics · release · process

7 MIN

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

SQL for Testers: Four Checks That Find the Data Bugs a Screen Hides

A hands-on guide to checking a database the way a tester checks a screen. Load a small shop database with seeded data bugs, write a query that returns the rows breaking each rule, and see why the first version of each query often finds nothing.

sql · test data · 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

Acceptance Criteria vs Definition of Done: What Each One Is For

The two are constantly confused, and teams pay for it twice: quality rules copied into every story, or skipped entirely because everyone assumed they were somewhere else. This guide separates them, shows what belongs in each, and turns a Definition of Done into checks a pipeline enforces.

acceptance criteria · definition of done · process

8 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

AI Wrote Part of the Sprint. Who Owns the Defects?

The measured quality gap in AI-generated code is real but narrower than the headline, and it is not the interesting part. The interesting part is that review, testing, and traceability all assume the author understood what they wrote — and a product owner is the person who can put a name against each story before that assumption stops holding.

ai · code quality · product owner

6 MIN

Definition of Ready: Training Wheels or Anti-Pattern?

A Definition of Ready stops half-formed work entering a sprint, and it also turns collaboration into a hand-off with an acceptance gate. Both are true. This guide covers when it helps, the failure mode that makes practitioners call it an anti-pattern, and the diagnostics that tell you which one you have.

definition of ready · process · product owner

6 MIN

Go or No-Go: The Questions to Ask Before You Release

How to run a go/no-go decision that can genuinely say no: one named owner instead of a group vote, evidence gathered before the meeting, criteria with thresholds written in advance, every accepted risk carrying an owner and an expiry, and escaped defects measured afterwards to correct the criteria.

release · product owner · process

8 MIN

Updated

How to Write Acceptance Criteria a Tester Can't Misread

Acceptance criteria decide what gets built and what gets tested. This guide covers the eight properties that make a criterion checkable, with a real story rewritten from a score of 48 to 100 in our acceptance criteria grader, and the questions each rewrite answered before the sprint instead of during it.

acceptance criteria · requirements · product owner

11 MIN

Updated

Reading Quality From the Support Queue

Support data is the earliest external signal that a release went wrong, and most of it gets read as a support-team scorecard instead. This guide separates the metrics that say something about the product from the ones that say something about the queue, and gives a weekly routine for turning volume into defects.

quality metrics · product owner · support

7 MIN

The European Accessibility Act: What It Requires of Your Checkout

Accessibility stopped being a nice-to-have in June 2025. This guide covers who the European Accessibility Act applies to, which standard it points at, what enforcement has actually looked like in France, why overlay widgets do not count, and five checks a product owner can run on their own checkout in fifteen minutes.

accessibility · compliance · product owner

7 MIN

Load Testing for Beginners with k6: Smoke, Load, and Finding the Limit

A hands-on introduction to load testing with k6. Start a tiny shop API locally, check it works for one user, prove it meets a response-time goal under steady load, then add users until it doesn't. Includes an exercise with an answer key.

performance testing · k6 · api testing

15 MIN

The npm Worm Targets Your Test Pipeline: Hardening Playwright CI After Shai-Hulud

What the keyv and Bitwarden CLI attacks did to CI runners and AI coding agent config files, which defenses we verified on real npm versions (including one that npm 10 silently ignores), and a pull request check for files that run code on folder open.

ci cd · security · github actions

9 MIN

Updated

2025 · updated entries marked

API Testing for Beginners: Postman and Playwright Examples

A hands-on introduction to API testing: explore an API with curl, write a Postman collection and run it with Newman, then write the same checks in Playwright. Uses a public practice API whose real responses include a few surprises.

api testing · postman · rest

10 MIN

Updated

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

How to Run Automated Tests in CI/CD with GitHub Actions: From One Job to Shards

A practical path to tests in CI: the GitHub Actions workflow Playwright generates and what each line does, the additions a real project needs (taken from this site's pipeline), and how to shard a slow suite and merge the results into one report.

ci cd · automation · github actions

9 MIN

Updated

How to Write Effective Test Cases: Worked Examples on a Real Checkout Form

A practical guide to test cases: what to include, three techniques for choosing inputs, ten real cases for a checkout form with the results we observed, and how the cases become an automated test. Three of the ten raised questions the form's requirements don't answer.

qa · test cases · process

9 MIN

Updated

How to Write High-Quality Bug Reports

We found a real bug in a practice shop and wrote it up two ways. The difference between 20 and 100 points is steps, expected versus actual, environment, reproducibility, and evidence. Each part is explained with the exact lines from the report.

qa · bug reporting · process

8 MIN

Updated

Manual vs Automated Testing: What Each One Caught on the Same Demo Shop

A concrete comparison instead of a debate: which bugs on a deliberately broken demo shop an automated suite caught, which ones a person caught, and a short set of questions for deciding what to automate next.

qa · manual testing · automation

5 MIN

Updated

QA Engineer Skills Roadmap: What to Learn, in What Order, and How to Prove It

Ten skills for testers, in the order they build on each other: test design, bug reporting, exploratory testing, API testing, one UI framework, Git and CI, test data and SQL, debugging failures, accessibility, and working with AI assistants. Each comes with a free project that proves you can do it.

qa career · skills · automation

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

What Is Software Testing? A Beginner's Guide With a Hands-On Exercise

A plain-language introduction for new testers: what testing is and isn't, seven principles every tester should know, the main levels and types, and a practice session on a deliberately buggy demo shop with a list of real bugs to check your findings against.

qa · software testing · beginner

6 MIN

Updated