💚

Beginner-Friendly Topic

Take your time - it's perfectly normal to re-read this topic 2-3 times. Try the interactive code editor below to run code yourself. Use the Q&A section to check your understanding before moving on. You've got this! 🚀

Testing Terminology & Glossary

Professional testers speak a precise language. Knowing the correct terminology is essential for communicating clearly with developers, product managers, and stakeholders - and for SDET job interviews. This topic covers the 20 most important testing terms you will encounter every single day.

20 min•By Priygop Team•Updated 2026

Core Testing Terminology

Bug / Defect / Fault: A flaw in the software that causes incorrect behavior. 'Bug' is informal; 'defect' is formal in documentation.
Error: A human mistake made by a developer or analyst (e.g., misunderstanding a requirement).
Failure: The observable incorrect behavior when the software runs - the symptom caused by a defect.
Test Case: A documented set of conditions to verify a specific behavior (inputs, steps, expected result).
Test Suite: A collection of related test cases grouped together (e.g., 'Login Test Suite').
Test Plan: A document describing the scope, approach, resources, and schedule for testing activities.
Test Oracle: The source used to determine whether the actual result matches expected result (spec, previous version, domain expert).
Regression Testing: Re-running tests after code changes to ensure existing functionality isn't broken.
Smoke Testing: A quick, shallow test run to verify the basic functions work before deeper testing begins.
Sanity Testing: A narrow, focused test after a specific fix to confirm it works without running the full suite.
Test Coverage: The degree to which the tests exercise the software (code coverage, requirement coverage, branch coverage).
Flaky Test: A test that passes and fails intermittently without code changes - a reliability problem.
Test Harness: The collection of software + test data + configuration used to run tests.
Mock / Stub / Spy: Test doubles that replace real dependencies (mock = verifiable fake, stub = returns preset values, spy = records interactions).
SUT (System Under Test): The component or system being tested.
UAT (User Acceptance Testing): Final validation by actual users that the system meets business needs.
Entry Criteria: The preconditions that must be met before testing begins.
Exit Criteria: The conditions that define when testing is complete (e.g., 0 critical open bugs, 95% test pass rate).
Severity: The technical impact of a bug on the system (Critical, Major, Minor, Trivial).
Priority: The business urgency of fixing a bug (High, Medium, Low - set by product/business).

Try It - Bug Report Writer

Try It - Bug Report WriterHTML

HTML Editor

✓ ValidTab = 2 spaces

<!DOCTYPE html>
<html>
<head>
<style>
  body { font-family: 'Segoe UI', sans-serif; padding: 20px; background: #f0f4ff; }
  h2 { color: #3730a3; }
  .card { background: white; padding: 24px; border-radius: 12px; box-shadow: 0 2px 10px rgba(0,0,0,0.1); max-width: 600px; }
  label { font-weight: 600; color: #374151; display: block; margin: 10px 0 4px; font-size: 13px; }
  input, select, textarea { width: 100%; padding: 8px 10px; border: 2px solid #e5e7eb; border-radius: 6px; font-size: 14px; box-sizing: border-box; }
  textarea { height: 60px; resize: vertical; }
  .row { display: grid; grid-template-columns: 1fr 1fr; gap: 12px; }
  button { background: #3730a3; color: white; border: none; padding: 10px 24px; border-radius: 6px; cursor: pointer; font-size: 14px; margin-top: 14px; }
  button:hover { background: #164e35; }
  .report { background: #eef2ff; border: 1px solid #c7d2fe; border-radius: 8px; padding: 16px; margin-top: 16px; font-family: monospace; font-size: 13px; line-height: 2; display: none; }
  .label { color: #3730a3; font-weight: bold; }
  .critical { color: #dc2626; } .major { color: #ea580c; } .minor { color: #ca8a04; } .trivial { color: #16a34a; }
  .high { color: #dc2626; } .medium { color: #d97706; } .low { color: #16a34a; }
</style>
</head>
<body>
<div class="card">
  <h2>🐛 Bug Report Writer</h2>
  <p>Fill in the fields to generate a professional bug report.</p>
  <label>Bug Title</label>
  <input id="title" placeholder="e.g. Login fails with valid credentials on Firefox" />
  <label>Steps to Reproduce</label>
  <textarea id="steps" placeholder="1. Go to login page&#10;2. Enter valid email&#10;3. Enter correct password&#10;4. Click Login"></textarea>
  <label>Expected Result</label>
  <input id="expected" placeholder="e.g. User is redirected to dashboard" />
  <label>Actual Result</label>
  <input id="actual" placeholder="e.g. Error message: 'Invalid credentials' appears" />
  <label>Environment</label>
  <input id="env" placeholder="e.g. Chrome 121, macOS Sonoma, Staging" />
  <div class="row">
    <div>
      <label>Severity</label>
      <select id="severity">
        <option value="critical">🔴 Critical</option>
        <option value="major">🟠 Major</option>
        <option value="minor" selected>🟡 Minor</option>
        <option value="trivial">🟢 Trivial</option>
      </select>
    </div>
    <div>
      <label>Priority</label>
      <select id="priority">
        <option value="high">High</option>
        <option value="medium" selected>Medium</option>
        <option value="low">Low</option>
      </select>
    </div>
  </div>
  <button onclick="generate()">🖨️ Generate Bug Report</button>
  <div class="report" id="report"></div>
</div>
<script>
  let bugCount = 1;
  function generate() {
    const id = "BUG-" + String(bugCount++).padStart(4, "0");
    const title = document.getElementById("title").value || "Untitled Bug";
    const steps = document.getElementById("steps").value || "1. Reproducing step";
    const expected = document.getElementById("expected").value || "Expected behavior";
    const actual = document.getElementById("actual").value || "Actual behavior";
    const env = document.getElementById("env").value || "Not specified";
    const sev = document.getElementById("severity").value;
    const pri = document.getElementById("priority").value;
    const sevLabel = {critical:"🔴 Critical",major:"🟠 Major",minor:"🟡 Minor",trivial:"🟢 Trivial"}[sev];
    const priLabel = {high:"⬆ High",medium:"➡ Medium",low:"⬇ Low"}[pri];
    const r = document.getElementById("report");
    r.style.display = "block";
    r.innerHTML = '<span class="label">Bug ID:</span>      ' + id + '\n' +
      '<span class="label">Title:</span>        ' + title + '\n' +
      '<span class="label">Severity:</span>     <span class="' + sev + '">' + sevLabel + '</span>\n' +
      '<span class="label">Priority:</span>     <span class="' + pri + '">' + priLabel + '</span>\n' +
      '<span class="label">Environment:</span>  ' + env + '\n' +
      '<span class="label">Steps:</span>\n' + steps.split("\n").map(s => "  " + s).join("\n") + '\n' +
      '<span class="label">Expected:</span>     ' + expected + '\n' +
      '<span class="label">Actual:</span>       ' + actual + '\n' +
      '<span class="label">Status:</span>       🆕 New';
  }
</script>
</body>
</html>

<!DOCTYPE html>
<html>
<head>
<style>
  body { font-family: 'Segoe UI', sans-serif; padding: 20px; background: #f0f4ff; }
  h2 { color: #3730a3; }
  .card { background: white; padding: 24px; border-radius: 12px; box-shadow: 0 2px 10px rgba(0,0,0,0.1); max-width: 600px; }
  label { font-weight: 600; color: #374151; display: block; margin: 10px 0 4px; font-size: 13px; }
  input, select, textarea { width: 100%; padding: 8px 10px; border: 2px solid #e5e7eb; border-radius: 6px; font-size: 14px; box-sizing: border-box; }
  textarea { height: 60px; resize: vertical; }
  .row { display: grid; grid-template-columns: 1fr 1fr; gap: 12px; }
  button { background: #3730a3; color: white; border: none; padding: 10px 24px; border-radius: 6px; cursor: pointer; font-size: 14px; margin-top: 14px; }
  button:hover { background: #164e35; }
  .report { background: #eef2ff; border: 1px solid #c7d2fe; border-radius: 8px; padding: 16px; margin-top: 16px; font-family: monospace; font-size: 13px; line-height: 2; display: none; }
  .label { color: #3730a3; font-weight: bold; }
  .critical { color: #dc2626; } .major { color: #ea580c; } .minor { color: #ca8a04; } .trivial { color: #16a34a; }
  .high { color: #dc2626; } .medium { color: #d97706; } .low { color: #16a34a; }
</style>
</head>
<body>
<div class="card">
  <h2>🐛 Bug Report Writer</h2>
  <p>Fill in the fields to generate a professional bug report.</p>
  <label>Bug Title</label>
  <input id="title" placeholder="e.g. Login fails with valid credentials on Firefox" />
  <label>Steps to Reproduce</label>
  <textarea id="steps" placeholder="1. Go to login page&#10;2. Enter valid email&#10;3. Enter correct password&#10;4. Click Login"></textarea>
  <label>Expected Result</label>
  <input id="expected" placeholder="e.g. User is redirected to dashboard" />
  <label>Actual Result</label>
  <input id="actual" placeholder="e.g. Error message: 'Invalid credentials' appears" />
  <label>Environment</label>
  <input id="env" placeholder="e.g. Chrome 121, macOS Sonoma, Staging" />
  <div class="row">
    <div>
      <label>Severity</label>
      <select id="severity">
        <option value="critical">🔴 Critical</option>
        <option value="major">🟠 Major</option>
        <option value="minor" selected>🟡 Minor</option>
        <option value="trivial">🟢 Trivial</option>
      </select>
    </div>
    <div>
      <label>Priority</label>
      <select id="priority">
        <option value="high">High</option>
        <option value="medium" selected>Medium</option>
        <option value="low">Low</option>
      </select>
    </div>
  </div>
  <button onclick="generate()">🖨️ Generate Bug Report</button>
  <div class="report" id="report"></div>
</div>
<script>
  let bugCount = 1;
  function generate() {
    const id = "BUG-" + String(bugCount++).padStart(4, "0");
    const title = document.getElementById("title").value || "Untitled Bug";
    const steps = document.getElementById("steps").value || "1. Reproducing step";
    const expected = document.getElementById("expected").value || "Expected behavior";
    const actual = document.getElementById("actual").value || "Actual behavior";
    const env = document.getElementById("env").value || "Not specified";
    const sev = document.getElementById("severity").value;
    const pri = document.getElementById("priority").value;
    const sevLabel = {critical:"🔴 Critical",major:"🟠 Major",minor:"🟡 Minor",trivial:"🟢 Trivial"}[sev];
    const priLabel = {high:"⬆ High",medium:"➡ Medium",low:"⬇ Low"}[pri];
    const r = document.getElementById("report");
    r.style.display = "block";
    r.innerHTML = '<span class="label">Bug ID:</span>      ' + id + '\n' +
      '<span class="label">Title:</span>        ' + title + '\n' +
      '<span class="label">Severity:</span>     <span class="' + sev + '">' + sevLabel + '</span>\n' +
      '<span class="label">Priority:</span>     <span class="' + pri + '">' + priLabel + '</span>\n' +
      '<span class="label">Environment:</span>  ' + env + '\n' +
      '<span class="label">Steps:</span>\n' + steps.split("\n").map(s => "  " + s).join("\n") + '\n' +
      '<span class="label">Expected:</span>     ' + expected + '\n' +
      '<span class="label">Actual:</span>       ' + actual + '\n' +
      '<span class="label">Status:</span>       🆕 New';
  }
</script>
</body>
</html>

Result

Click ▶ Run to see the result

Edit the code on the left, then click Run (Ctrl+Enter)

HTML|83 lines|4346 chars|✓ Valid syntax

UTF-8

Quick Quiz - Testing Terminology

Common Mistakes

Using 'bug', 'defect', 'error', 'failure' interchangeably - in formal contexts they mean different things; imprecise language causes miscommunication.
Confusing Severity and Priority - a cosmetic logo bug is Low Severity but could be High Priority before a product launch; a data corruption bug is Critical Severity but Low Priority on a deprecated module.
Calling every test that fails 'flaky' - a consistently failing test has a real bug; a flaky test has non-deterministic behavior. Distinguish them.
Writing test cases without a test oracle - without knowing what the expected result IS, you cannot determine pass or fail.

Tip

Practice Testing Terminology Glossary in small, isolated examples before integrating into larger projects. Breaking concepts into small experiments builds genuine understanding faster than reading alone.

Diagram

Loading diagram…

Technical diagram.

Practice Task

Note

Practice Task - (1) Write a working example of Testing Terminology Glossary from scratch without looking at notes. (2) Modify it to handle an edge case (empty input, null value, or error state). (3) Share your solution in the Priygop community for feedback.

Common Mistake

Warning

A common mistake with Testing Terminology Glossary is skipping edge case testing - empty inputs, null values, and unexpected data types. Always validate boundary conditions to write robust, production-ready software testing code.

Key Takeaways

Professional testers speak a precise language.
Bug / Defect / Fault: A flaw in the software that causes incorrect behavior. 'Bug' is informal; 'defect' is formal in documentation.
Error: A human mistake made by a developer or analyst (e.g., misunderstanding a requirement).
Failure: The observable incorrect behavior when the software runs - the symptom caused by a defect.

Next Module

Topics in This Module

Testing Terminology & Glossary

20 min•By Priygop Team•Updated 2026

Core Testing Terminology

Bug / Defect / Fault: A flaw in the software that causes incorrect behavior. 'Bug' is informal; 'defect' is formal in documentation.

Error: A human mistake made by a developer or analyst (e.g., misunderstanding a requirement).

Failure: The observable incorrect behavior when the software runs - the symptom caused by a defect.

Test Case: A documented set of conditions to verify a specific behavior (inputs, steps, expected result).

Test Suite: A collection of related test cases grouped together (e.g., 'Login Test Suite').

Test Plan: A document describing the scope, approach, resources, and schedule for testing activities.

Test Oracle: The source used to determine whether the actual result matches expected result (spec, previous version, domain expert).

Regression Testing: Re-running tests after code changes to ensure existing functionality isn't broken.

Smoke Testing: A quick, shallow test run to verify the basic functions work before deeper testing begins.

Sanity Testing: A narrow, focused test after a specific fix to confirm it works without running the full suite.

Test Coverage: The degree to which the tests exercise the software (code coverage, requirement coverage, branch coverage).

Flaky Test: A test that passes and fails intermittently without code changes - a reliability problem.

Test Harness: The collection of software + test data + configuration used to run tests.

Mock / Stub / Spy: Test doubles that replace real dependencies (mock = verifiable fake, stub = returns preset values, spy = records interactions).

SUT (System Under Test): The component or system being tested.

UAT (User Acceptance Testing): Final validation by actual users that the system meets business needs.

Entry Criteria: The preconditions that must be met before testing begins.

Exit Criteria: The conditions that define when testing is complete (e.g., 0 critical open bugs, 95% test pass rate).

Severity: The technical impact of a bug on the system (Critical, Major, Minor, Trivial).

Priority: The business urgency of fixing a bug (High, Medium, Low - set by product/business).

Try It - Bug Report Writer

Try It - Bug Report WriterHTML

HTML Editor

✓ ValidTab = 2 spaces

<!DOCTYPE html>
<html>
<head>
<style>
  body { font-family: 'Segoe UI', sans-serif; padding: 20px; background: #f0f4ff; }
  h2 { color: #3730a3; }
  .card { background: white; padding: 24px; border-radius: 12px; box-shadow: 0 2px 10px rgba(0,0,0,0.1); max-width: 600px; }
  label { font-weight: 600; color: #374151; display: block; margin: 10px 0 4px; font-size: 13px; }
  input, select, textarea { width: 100%; padding: 8px 10px; border: 2px solid #e5e7eb; border-radius: 6px; font-size: 14px; box-sizing: border-box; }
  textarea { height: 60px; resize: vertical; }
  .row { display: grid; grid-template-columns: 1fr 1fr; gap: 12px; }
  button { background: #3730a3; color: white; border: none; padding: 10px 24px; border-radius: 6px; cursor: pointer; font-size: 14px; margin-top: 14px; }
  button:hover { background: #164e35; }
  .report { background: #eef2ff; border: 1px solid #c7d2fe; border-radius: 8px; padding: 16px; margin-top: 16px; font-family: monospace; font-size: 13px; line-height: 2; display: none; }
  .label { color: #3730a3; font-weight: bold; }
  .critical { color: #dc2626; } .major { color: #ea580c; } .minor { color: #ca8a04; } .trivial { color: #16a34a; }
  .high { color: #dc2626; } .medium { color: #d97706; } .low { color: #16a34a; }
</style>
</head>
<body>
<div class="card">
  <h2>🐛 Bug Report Writer</h2>
  <p>Fill in the fields to generate a professional bug report.</p>
  <label>Bug Title</label>
  <input id="title" placeholder="e.g. Login fails with valid credentials on Firefox" />
  <label>Steps to Reproduce</label>
  <textarea id="steps" placeholder="1. Go to login page&#10;2. Enter valid email&#10;3. Enter correct password&#10;4. Click Login"></textarea>
  <label>Expected Result</label>
  <input id="expected" placeholder="e.g. User is redirected to dashboard" />
  <label>Actual Result</label>
  <input id="actual" placeholder="e.g. Error message: 'Invalid credentials' appears" />
  <label>Environment</label>
  <input id="env" placeholder="e.g. Chrome 121, macOS Sonoma, Staging" />
  <div class="row">
    <div>
      <label>Severity</label>
      <select id="severity">
        <option value="critical">🔴 Critical</option>
        <option value="major">🟠 Major</option>
        <option value="minor" selected>🟡 Minor</option>
        <option value="trivial">🟢 Trivial</option>
      </select>
    </div>
    <div>
      <label>Priority</label>
      <select id="priority">
        <option value="high">High</option>
        <option value="medium" selected>Medium</option>
        <option value="low">Low</option>
      </select>
    </div>
  </div>
  <button onclick="generate()">🖨️ Generate Bug Report</button>
  <div class="report" id="report"></div>
</div>
<script>
  let bugCount = 1;
  function generate() {
    const id = "BUG-" + String(bugCount++).padStart(4, "0");
    const title = document.getElementById("title").value || "Untitled Bug";
    const steps = document.getElementById("steps").value || "1. Reproducing step";
    const expected = document.getElementById("expected").value || "Expected behavior";
    const actual = document.getElementById("actual").value || "Actual behavior";
    const env = document.getElementById("env").value || "Not specified";
    const sev = document.getElementById("severity").value;
    const pri = document.getElementById("priority").value;
    const sevLabel = {critical:"🔴 Critical",major:"🟠 Major",minor:"🟡 Minor",trivial:"🟢 Trivial"}[sev];
    const priLabel = {high:"⬆ High",medium:"➡ Medium",low:"⬇ Low"}[pri];
    const r = document.getElementById("report");
    r.style.display = "block";
    r.innerHTML = '<span class="label">Bug ID:</span>      ' + id + '\n' +
      '<span class="label">Title:</span>        ' + title + '\n' +
      '<span class="label">Severity:</span>     <span class="' + sev + '">' + sevLabel + '</span>\n' +
      '<span class="label">Priority:</span>     <span class="' + pri + '">' + priLabel + '</span>\n' +
      '<span class="label">Environment:</span>  ' + env + '\n' +
      '<span class="label">Steps:</span>\n' + steps.split("\n").map(s => "  " + s).join("\n") + '\n' +
      '<span class="label">Expected:</span>     ' + expected + '\n' +
      '<span class="label">Actual:</span>       ' + actual + '\n' +
      '<span class="label">Status:</span>       🆕 New';
  }
</script>
</body>
</html>

Result

Click ▶ Run to see the result

Edit the code on the left, then click Run (Ctrl+Enter)

HTML|83 lines|4346 chars|✓ Valid syntax

UTF-8

Quick Quiz - Testing Terminology

Common Mistakes

Using 'bug', 'defect', 'error', 'failure' interchangeably - in formal contexts they mean different things; imprecise language causes miscommunication.

Confusing Severity and Priority - a cosmetic logo bug is Low Severity but could be High Priority before a product launch; a data corruption bug is Critical Severity but Low Priority on a deprecated module.

Calling every test that fails 'flaky' - a consistently failing test has a real bug; a flaky test has non-deterministic behavior. Distinguish them.

Writing test cases without a test oracle - without knowing what the expected result IS, you cannot determine pass or fail.

Tip

Diagram

Loading diagram…

Technical diagram.

Topics in This Module