Skip to navigation Skip to main content

The Software Testing Glossary That Doesn't Put You to Sleep

Basic Terms and Definitions

Let’s be honest: Most testing glossaries read like robot dictionaries. You scan three terms, your eyes glaze over, and suddenly you’re checking cat videos.

Not this one.

After years in QA trenches, I’ve curated only the terms that actually matter – with battle-tested examples and β€œwhy you should care” insights. Bookmark this as your go-to cheat sheet when:

  • Your PM says β€œJust run some ad hoc tests”
  • A dev argues β€œIt’s not a bug, it’s an anomaly!”
  • You need to explain regression testing to your CEO

Ready to speak fluent QA? Let’s dive in.


πŸ” The Bug Lifecycle: From β€œOops” to β€œFixed”

(Know these to win every bug debate)

Term What It Really Means Real-World Example
Bug Code’s β€œoops” moment Submit $0 payment β†’ Order processes anyway
Defect Fancy word for bug (corporate likes this) Login fails for users with apostrophes in passwords (O’Conner)
Anomaly Unexpected behavior with no spec App displays negative loading times
Fault Hidden landmine in code if (age > 120) misses 121+ users
Failure When landmine explodes 121-year-old user crashes retirement portal
Blocker β€œDrop everything!” bug Checkout page 500 error

🚨 Pro Tip: Track bug β†’ defect β†’ anomaly ratios. High anomalies? Your specs are vague.


πŸ§ͺ Testing Types Decoded

(Cut through the jargon jungle)

The Core 4

  1. Unit Testing
    • What: Testing code snippets in isolation
    • Example: Does calculateTax(10000) return $2200?
    • Tools: JUnit, pytest, Mocha
  2. Integration Testing
    • What: Do modules play nice together?
    • Example: User creation β†’ Email trigger β†’ DB update
    • Gotcha: 80% of β€œit works on my machine” fails happen here
  3. Regression Testing
    • What: Did new code break old stuff?
    • Example: After font update, print function outputs gibberish
    • Pro Move: Automate this (Selenium, Cypress)
  4. Exploratory Testing
    • What: Structured curiosity
    • Example: β€œWhat if I upload a 10GB .txt file?”
    • Secret: Best bugs found during coffee-fueled sessions

Special Forces

| Type | When to Use | Killer Question |
|β€”β€”|β€”β€”β€”β€”-|β€”β€”β€”β€”β€”-|
| Smoke Test | After deployment | β€œDoes the app even launch?” |
| Performance Test | Before Black Friday | β€œWill it handle 10k concurrent users?” |
| Security Test | Always | β€œCan hackers steal DB via login form?” |
| Usability Test | UI changes | β€œCan Grandma complete checkout in <2 mins?” |

More Testing Flavors

| Term | Real QA Translation | Why Care |
|β€”β€”|β€”β€”β€”β€”β€”β€”β€”|β€”β€”β€”-|
| Alpha Testing | Internal dogfooding | Catch embarrassment before customers see it |
| Beta Testing | Public trial by fire | Find edge cases only users discover |
| Black-box Testing | User-mode investigation | Simulate real user behavior |
| White-box Testing | Code-level autopsy | Find why it broke, not just that it broke |
| Ad hoc Testing | Unplanned bug hunting | Great for last-minute sanity checks |


Security Testing Arsenal

(Before hackers ruin your week)

Attack Vectors

| Term | What Happens | Real Case |
|β€”β€”|————–|———–|
| SQL Injection | ' OR 1=1-- exposes databases | 42% of web apps vulnerable (OWASP) |
| DDoS Attack | Fake traffic tsunami | 2016 Dyn attack killed Twitter/Netflix |
| Zero-Day | Unpatched hole only hackers know | Log4j chaos |
| Phishing | β€œDear User, reset password!” | 36% of breaches start here (Verizon) |
| Ransomware | Encrypts data + demands Bitcoin | Colonial Pipeline $4.4M payout |

Defense Strategies

| Term | How It Protects You | Implementation Tip |
|β€”β€”|β€”β€”β€”β€”β€”β€”β€”|β€”β€”β€”β€”β€”β€”β€”|
| Penetration Testing | Ethical hacking simulation | Hire outsiders - they think like criminals |
| Sanitization | Input field bodyguard | Always validate AND sanitize user inputs |
| CIA Triad | Security holy trinity | Balance Confidentiality, Integrity, Availability |
| Bug Bounty | Crowdsourced security | Offer $500+ for critical vulnerabilities |

Golden Rule: Treat every input field like a loaded gun - always sanitize.


Performance & Automation Terms

(Where β€œslow” isn’t a metric)

Speed Metrics

| Term | Measures | Passing Grade |
|β€”β€”|β€”β€”β€”-|β€”β€”β€”β€”β€”|
| Throughput | Transactions/second | E-commerce: β‰₯50 TPS |
| Latency | Click β†’ response time | >2s = 53% mobile bounce (Google) |
| The 5 Nines | Uptime % | 99.999% = 5 mins downtime/year |

Automation Essentials

| Term | What It Solves | Tools |
|β€”β€”|β€”β€”β€”β€”β€”-|β€”β€”-|
| DRY Principle | Duplicate test scripts | Page Object Models |
| Test Pyramid | Unbalanced coverage | mermaid graph TD A[70% Unit]-->B[20% API]-->C[10% UI] |
| CI/CD Pipeline | β€œWorks on my machine” syndrome | Jenkins, GitLab CI |
| Test Double | Testing in isolation | Mocks, Stubs, Fakes |


QA Process & Methodology

(The frameworks that keep you sane)

Workflow Essentials

| Term | Why It Matters | Pro Tip |
|β€”β€”|β€”β€”β€”β€”β€”-|β€”β€”β€”|
| TDD (Test-Driven Dev) | Code confidence from day 1 | Write test before writing function |
| Shift Left | Catch bugs early | Include QA in sprint planning |
| Traceability Matrix | Prove test coverage | Map test cases β†’ requirements |
| Blue/Green Deploy | Zero-downtime updates | Route 5% traffic to new version first |

Defect Management

| Term | Meaning | Priority Guide |
|β€”β€”|β€”β€”β€”|β€”β€”β€”β€”β€”-|
| Blocker | Showstopper bug | Fix immediately! |
| Critical | Major function broken | Fix before release |
| Major | Annoying but workaround exists | Schedule next sprint |
| Heisenbug | Disappears when debugging | Add logging before attempting fix |


The Ultimate QA Cheat Sheet

Must-Know Acronyms

| KPI | Key Performance Indicator |
| SLA | Service Level Agreement |
| UAT | User Acceptance Testing |
| MTTR | Mean Time To Repair |
| DDoS | Distributed Denial of Service |

Jargon Decoder Ring

| Term | Translation |
|β€”β€”|β€”β€”β€”β€”-|
| Canary Release | Test new version on 5% users |
| Happy Path | Ideal user workflow |
| Legacy Code | Untested spaghetti code |
| Smoke Test | β€œDoes it turn on?” check |

Pro Formulas

```plaintext Risk Score = Probability Γ— Impact Test Coverage = (Tested Requirements / Total Requirements) Γ— 100 MTBF = Total Uptime / Number of Failures

How to Use This Glossary

  1. New to QA? Learn the Core 4 testing types first
  2. Prepping for release? Audit your performance/security terms
  3. In a bug debate? Pull precise definitions from section 1

πŸ” Want the full checklist? β†’ Download my QA Terminology Playbook (free PDF)


Enjoy !!! See Yaaa, Next.

Cover

Share: X (Twitter) Facebook LinkedIn