Testing & Quality Glossary

Unit Testing — Explained with Examples

Unit testing is a software testing method that verifies individual components or functions in isolation to ensure they work correctly.

Integration Testing — Explained with Examples

Integration testing verifies that different modules or services work together correctly, catching interface mismatches and data flow issues between components.

E2E Testing — Explained with Examples

End-to-end (E2E) testing validates the complete application flow from start to finish, simulating real user scenarios across all system layers.

Mock vs Stub — Explained with Examples

Mocks, stubs, fakes, and spies are test doubles that replace real dependencies in tests, each serving a different purpose in verification and isolation.

Code Coverage — Explained with Examples

Code coverage measures how much of your source code is executed during testing, helping identify untested paths and improve test quality.

Mutation Testing — Explained with Examples

Mutation testing evaluates test quality by introducing small bugs (mutations) into code and checking whether existing tests detect and fail on them.

Smoke Testing — Explained with Examples

Smoke testing is a quick sanity check performed after a deployment to verify that the most critical functions of an application work before deeper testing.

Regression Testing — Explained with Examples

Regression testing re-runs existing test suites after code changes to ensure that new features or fixes don't break previously working functionality.

Static Analysis — Explained with Examples

Static analysis examines source code without executing it to detect bugs, style violations, security vulnerabilities, and code quality issues.

Performance Testing — Explained with Examples

Performance testing evaluates how a system behaves under various load conditions, measuring speed, responsiveness, and stability to identify bottlenecks.

TDD — Explained with Examples

TDD (Test-Driven Development) is a software development process where you write tests before code, following the Red-Green-Refactor cycle.

BDD — Explained with Examples

BDD (Behavior-Driven Development) extends TDD by writing tests in plain language using Given/When/Then scenarios understandable by non-technical stakeholders.