Skip to content
Independent guides for QA & test automationRSSEditorial policy
QA Vibes
Free · 5 minutes · no sign-upWould your AI-generated tests catch these bugs? Try the challenge →

test cases · from our own pipeline

Black-Box Test Design Techniques, Applied to One Real Checkout

The four black-box techniques in the ISTQB Foundation syllabus, applied to one checkout on this site's practice shop, with every result checked by a test. Each technique asks a different question, and the state transition model found something none of the others could: a URL that skips the details form.

QA Vibes Editorial8 minTested with Playwright 1.63.0

Latest

All articles →

  1. Azure DevOps for Testers: Publishing Playwright Results and Importing Test Cases

    10 MIN · azure devops

  2. Updated

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

    12 MIN · api testing

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

    7 MIN · quality metrics

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

    8 MIN · playwright

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

    8 MIN · sql

Practice · the free challenge

Would your AI-generated tests catch these bugs?

Inspect a passing test suite. Find what it misses. Improve it with the AI tools you already use.

Try the free challenge

More practice

Practice lab →
  • Playwright practice lab

    Run your own suite against a shop with ten seeded bugs and see which ones it catches.

  • Why did this test pass?

    Three case files from recorded runs: predict, diagnose, repair.

  • SQL lab

    Write SQL checks against a shop database with seeded bad rows.

  • Test design questions

    Boundary values, partitions, decision tables and state transitions, every answer explained.

All free and ad-free. Nothing to install to start.

The workbench

Free tools. No sign-up. Nothing leaves your browser.

Open the workbench →

Playwright test reviewer

Paste a test. Get the questions a careful reviewer would ask — fixed waits, missing awaits, assertions that can never fail — each mapped to its ESLint rule.

HIGH   L9   Fixed wait (waitForTimeout)
HIGH   L11  Missing await
MED    L5   Waiting for networkidle
LOW    L6   CSS or XPath locator
Review a test

Bug report grader

Paste a defect report and see what a developer will ask for before they can fix it. Ten weighted checks, severity and priority, Jira export.

✓ Steps to reproduce     20/20
✓ Expected vs actual     15/15
✗ Evidence attached       0/15
! Tone                    5/10
  Score                  78/100
Grade a report

Start here

QA Foundations, in 5 parts

≈ 38 minutes end to endOr follow the full QA roadmap →Or rate what you can already show →

  1. 01

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

    6 MIN

  2. 02

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

    8 MIN

  3. 03

    How to Write High-Quality Bug Reports

    8 MIN

  4. 04

    Understanding the Test Pyramid: What the Published Numbers Actually Say

    7 MIN

  5. 05

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

    9 MIN

Not an engineer?

Quality for product owners

You do not run the tests, and you decide most of what they will find: the criteria, the definition of done, the release call, and what happens to what got through. Same material, organised by the question you arrived with.

Open the product owner hub →

Browse by topic

automation16playwright13tutorial10process8qa8product owner7ci cd6test cases6case study5accessibility3ai3api testing3devops3manual testing3quality metrics3selenium3

Tools we reference most

All 28 →
PlaywrightMicrosoft's end-to-end framework with auto-waiting, isolated browser contexts, a trace viewer, and built-in parallelism across Chromium, Firefox, and WebKit.Open source
CypressJavaScript testing framework that runs alongside your app, with time-travel debugging, network stubbing, and component testing.Open source
SeleniumThe W3C WebDriver reference implementation, with bindings for Java, Python, C#, JavaScript, and Ruby, plus Grid for distributed runs.Open source
BrowserStackCloud of real desktop browsers and mobile devices for manual and automated testing, with Selenium, Playwright, Cypress, and Appium support.Free trial

How this site works

Dated, not evergreen

Every article shows when it was published, when it was last updated, and what changed. Articles whose steps we ran say which versions they were tested with.

Checked, then cited

Every code sample is syntax-checked in CI, complete Java examples are compiled, and Playwright examples must pass our own test reviewer. Articles end with links to official documentation.

Corrections in public

Spotted something wrong? Every article has a report link, and the fix appears in that article’s revision history.