Tebugging
    Sign Up Free

    Glossary

    QA and AI testing glossary

    Short, plain definitions of the terms QA teams use most, from AI QA agents and agentic testing to regression and flaky tests.

    Agentic testing
    Agentic testing is an approach where AI agents plan and perform testing steps toward a goal, such as "verify checkout works", instead of only following a fixed script. The agent decides which actions to take and reports what it found.
    AI QA agent
    An AI QA agent is software that uses AI models to carry out quality assurance tasks with limited human input: reading requirements or an application, proposing test scenarios, creating and running tests, and explaining the results. A person reviews its suggestions and decides what matters.
    AI-powered testing
    AI-powered testing uses artificial intelligence to help plan, create, run and analyze software tests, for example by suggesting test scenarios, drafting test cases or grouping and explaining failures.
    What is AI-powered web testing? →
    Cypress
    Cypress is an open-source end-to-end testing framework for web applications, written in JavaScript, that runs tests inside the browser and offers interactive, time-travel debugging.
    Edge case
    An edge case is an input or situation at the limits of what a feature expects, such as an empty field, a very long name, an expired link or a lost network connection.
    End-to-end (E2E) testing
    End-to-end testing checks a complete user flow through the real application, from the user interface through the backend and back, for example signing up and completing a purchase.
    Exploratory testing
    Exploratory testing is unscripted testing where a tester learns the application, designs tests and runs them at the same time, using judgment to find unexpected problems.
    Flaky test
    A flaky test passes and fails on different runs without any change to the code. Common causes are timing problems, shared test data, unstable selectors and slow external services.
    Playwright
    Playwright is an open-source browser automation and testing framework from Microsoft that drives Chromium, Firefox and WebKit, with built-in auto-waiting and a trace viewer.
    Regression testing
    Regression testing re-runs existing tests after a change to confirm that features which worked before still work. It is the type of testing that benefits most from automation.
    Retesting
    Retesting checks that a specific bug has been fixed by repeating the test that found it. Regression testing, by contrast, checks that the fix did not break anything else.
    Selenium
    Selenium is an open-source project for automating web browsers. Its WebDriver API is a W3C standard and it supports many programming languages and browsers.
    Tebugging vs Selenium →
    Self-healing test
    A self-healing test can recover when the application changes in small ways, typically by finding an element through another attribute when its original selector no longer matches, and then reporting the change.
    Shift-left testing
    Shift-left testing means testing earlier in the development process, for example reviewing requirements for testability and running automated tests on every pull request.
    Smoke testing
    Smoke testing is a quick, shallow check of the most important functions (can users log in, does the main page load) to decide whether a build is stable enough for deeper testing.
    Test automation framework
    A test automation framework is a library and set of conventions for writing and running automated tests in code, such as Selenium, Playwright or Cypress for web applications.
    Test case
    A test case is a single, specific check with preconditions, steps, test data and an expected result. It either passes or fails.
    Test case management
    Test case management is organizing test cases, plans and results in one place so a team can see what is covered, what was run and what failed.
    Test coverage
    Test coverage describes how much of an application's features, requirements or code is exercised by tests. High coverage of critical user flows matters more than a high overall percentage.
    Test plan
    A test plan is a document that describes what will be tested in a release, how, when, by whom, and the criteria for starting and finishing testing.
    How to write a test plan →
    Test scenario
    A test scenario is a one-line description of something to verify, such as "user resets a forgotten password". One scenario usually becomes several test cases.
    Test strategy
    A test strategy is the long-term, organization- or product-level approach to testing: which test levels and types are used, tools, environments and quality goals. Individual test plans follow it.
    Test suite
    A test suite is a group of test cases that are run together, for example all checkout tests or the full regression suite.

    Tebugging

    Plan, run and analyze your web tests with AI.

    Start on the free plan. No credit card required.

    Start Testing Free