QA & Testing Glossary
Plain-English definitions of the QA and software testing terms that come up most — with links to deeper guides where you want the full picture.
A
- Assertion
- A check inside a test that verifies an expected outcome — for example, that a confirmation message appeared. A test without meaningful assertions runs code but proves nothing.
- Auto-waiting
- A framework feature that automatically waits for an element to be visible, stable, and actionable before interacting with it, eliminating the timing races that cause most flaky tests.Learn more
B
- Browser context
- An isolated browser session with its own cookies, storage, and cache — like a fresh incognito window — used to keep tests independent of one another without relaunching the browser.Learn more
C
- CI/CD
- Continuous integration / continuous delivery: the automated pipeline that builds and tests your code on every change. Running tests here catches broken journeys before they reach production.Learn more
- Codegen
- Playwright's built-in recorder that watches you click through your app and generates ready-to-run test code with resilient selectors — a fast way to scaffold a test.Learn more
- Cypress
- A popular open-source end-to-end testing framework that runs inside the browser, known for its polished interactive developer experience.Learn more
E
- End-to-end (E2E) testing
- Testing that drives the real application through a complete user journey across the frontend, backend, and database — the closest automated proxy for real user experience.Learn more
- Exploratory testing
- Unscripted, human-driven testing where the tester simultaneously designs and executes tests, using discoveries to guide the next action. Finds bugs that scripted tests cannot because it adapts to surprises.Learn more
F
- Fixture
- A reusable piece of test setup — such as a logged-in user or seeded data — that provides a consistent starting state so tests are isolated and repeatable.Learn more
- Flaky test
- A test that passes and fails on the same code without any change. Flakiness erodes trust in the whole suite and is usually caused by timing, shared state, or brittle selectors.Learn more
- Flow
- A single automated script that covers one complete user journey end to end. Flows prove a feature actually works, unlike fragmented tests that check isolated pieces.Learn more
H
- Headless browser
- A browser running without a visible window. Headless mode is faster and is the default for running tests in CI; headed mode is useful for watching or debugging a test locally.Learn more
I
- Integration testing
- Testing that verifies two or more components work together — such as an API and a database — usually without driving the full user interface.Learn more
L
- Locator
- A resilient, re-evaluated description of how to find an element on a page. Playwright locators carry built-in auto-waiting, making them more reliable than one-time element references.Learn more
M
- Managed QA
- A service model where an external team builds, runs, and maintains your automated test suite, delivering pass/fail results without your team owning the maintenance.Learn more
- Mocking
- Replacing a real dependency — such as a third-party API — with a controlled stand-in during testing, so tests stay fast, deterministic, and independent of outside services.Learn more
P
- Page Object Model
- A design pattern that wraps the locators and actions for a page in a reusable object, keeping tests readable and reducing the work needed when the UI changes.Learn more
- Parallelization
- Running multiple tests at the same time across workers or machines (also called sharding) to cut total run time. Isolated tests are a prerequisite for safe parallel execution.Learn more
- Playwright
- A free, open-source framework from Microsoft for automating browsers to test web apps, known for reliable, fast cross-browser tests and built-in auto-waiting.Learn more
R
- Regression testing
- Re-running a broad set of tests to confirm that recent changes did not break existing functionality. Broader and deeper than smoke testing.Learn more
S
- Selector
- The string that describes how to find an element, such as a role, text, or CSS query. User-facing selectors are far more durable than ones tied to styling.Learn more
- Selenium
- The long-standing open-source browser automation framework that predates Playwright and Cypress, still widely used for legacy and broad browser coverage.Learn more
- Self-healing tests
- Tests that automatically adapt to minor UI changes — for example, by finding an element a new way when its selector changes — reducing maintenance and false failures.Learn more
- Smoke testing
- A small, fast set of checks on the most critical paths to confirm a build is stable enough to test further or deploy. Your early-warning system.Learn more
T
- Test coverage
- A measure of how much of your code or features your tests exercise, often a percentage. Useful for finding gaps, but a high number does not guarantee quality.Learn more
- Test isolation
- The principle that each test starts from a clean, independent state with no dependency on other tests. Isolation prevents one test's side effects from causing another test to fail.Learn more
- Test pyramid
- A model for structuring automated testing: a large base of fast unit tests, a middle layer of integration tests, and a small top layer of slower end-to-end tests. Balances speed, cost, and coverage confidence.Learn more
- Test runner
- The tool that discovers, executes, and reports on your tests — handling parallelism, retries, and results. Playwright includes its own test runner.Learn more
- Test suite
- A collection of tests grouped together, often by feature or area. A healthy suite is fast, reliable, and focused on meaningful journeys rather than sheer count.Learn more
- Trace
- A complete recording of a test run — DOM snapshots, network activity, console logs, and screenshots — that lets you replay exactly what happened at the moment of failure.Learn more
U
- Unit testing
- Testing a single function or component in isolation. Fast and precise, but unable to confirm that the whole system works together.Learn more
- User acceptance testing (UAT)
- The final testing phase before release, where stakeholders or users verify that the software meets business requirements and is fit for purpose. Distinct from functional testing, UAT validates intent, not just behavior.Learn more
- User journey
- The sequence of steps a real user takes to accomplish a goal, such as signing up or checking out. Mapping critical journeys defines what is most worth testing.Learn more
V
- Vendor lock-in
- When tests are trapped in a proprietary format you cannot export or run elsewhere. Standard, exportable code (like plain Playwright) avoids it so you truly own your tests.Learn more
- Visual regression testing
- A testing technique that takes screenshots of an application and compares them against a stored baseline to detect unintended visual changes. Playwright includes built-in screenshot assertion support.Learn more
W
- WebKit
- The browser engine behind Safari. Playwright bundles WebKit so you can test Safari behavior on any operating system, including Windows and Linux.Learn more
See modern QA in action
Everything we write about is what we build and run every day. Book a demo and we'll show you flow-based Playwright coverage on your own codebase.