Testing Glossary
A comprehensive guide to software testing, QA, and beta testing terminology.
A
A/B Testing
A method of comparing two versions of a product or feature to determine which performs better with users.
Alpha Testing
An internal testing phase conducted by the development team before releasing software to external users.
B
Beta Testing
A pre-release testing phase where real users evaluate software in real-world conditions to find bugs and provide feedback.
Beta Testing Metrics
Quantitative and qualitative measurements used to evaluate the success and effectiveness of a beta testing program.
Bug Report
A documented account of a software defect, including steps to reproduce, expected behavior, and actual behavior.
C
Canary Release
A deployment strategy that rolls out changes to a small subset of users before a full release to detect issues early.
Churn Rate
The percentage of users or customers who stop using a product within a given time period.
Closed Beta
A beta testing phase restricted to a selected group of invited users, often used to gather targeted feedback.
Cohort Analysis
A method of grouping users by shared characteristics or signup date to track how their behavior changes over time.
Continuous Integration (CI)
A development practice where code changes are automatically built, tested, and merged into a shared repository multiple times a day.
Crash Report
An automatically generated log capturing technical details when software unexpectedly stops functioning.
D
Defect Lifecycle
The series of stages a software bug goes through from discovery to resolution, including reporting, triaging, fixing, and verification.
Dogfooding
The practice of a company using its own product internally before releasing it to customers.
E
Early Access
A release model where users can access and use a product before its official launch, often in exchange for feedback.
Edge Case
An unusual or extreme scenario that occurs at the boundaries of expected input or usage conditions.
End-to-End Testing
A testing method that validates an entire application workflow from start to finish, simulating real user scenarios.
Exploratory Testing
An unscripted testing approach where testers simultaneously learn, design, and execute tests based on their understanding of the system.
F
Feature Flag
A toggle mechanism that allows teams to enable or disable features in production without deploying new code.
Feature Request
A user suggestion for new functionality or improvements to an existing product.
Feedback Loop
A continuous cycle of collecting user input, analyzing it, making improvements, and measuring the impact of those changes.
Freemium
A business model where a product offers basic features for free while charging for premium features or enhanced functionality.
Functional Testing
Testing that verifies each function of a software application operates according to its specified requirements.
O
Onboarding
The process of guiding new users through a product's core features and helping them reach their first moment of value.
Open Beta
A beta testing phase available to all users without restrictions, typically used to stress-test software at scale.
P
Performance Testing
Testing that evaluates the speed, responsiveness, and stability of a software application under various conditions.
Product-Market Fit
The point at which a product satisfies a strong market demand and users consistently choose it over alternatives.
R
Regression Testing
Re-running existing tests after code changes to ensure that previously working features have not been broken.
Release Candidate
A software version that is potentially ready for final release, pending the outcome of last-stage testing.
Reproducibility
The ability to consistently recreate a software bug or issue using the same steps and conditions.
Retention Rate
The percentage of users who continue using a product over a given time period, indicating how well the product sustains engagement.
S
Service-Level Agreement (SLA)
A formal commitment between a service provider and a customer that defines expected performance standards, uptime guarantees, and remedies for failures.
Session Recording
A tool that captures user interactions with a product, including clicks, scrolls, and navigation patterns, for analysis.
Severity vs Priority
Severity measures how much a bug impacts functionality, while priority determines the order in which it should be fixed.
Smoke Testing
A quick, preliminary test that checks whether the most critical functions of a software build work before deeper testing begins.
Soft Launch
A limited release of a product to a small audience to test real-world performance before a full public launch.
Staging Environment
A pre-production server setup that mirrors the live environment, used for final testing before deployment.
T
Technical Debt
The accumulated cost of shortcuts, workarounds, and deferred maintenance in a codebase that makes future changes harder and slower.
Test Case
A documented set of conditions, inputs, and expected results used to verify that a specific feature or function works correctly.
Test Coverage
A metric that measures the percentage of code or functionality exercised by a test suite.
Test Environment
A configured setup of hardware, software, and network conditions where testing is performed.
Test Plan
A document outlining the scope, approach, resources, and schedule for testing activities on a software project.
U
Unit Testing
Testing individual components or functions of code in isolation to verify they produce the expected output.
Usability Testing
Evaluating a product by observing real users as they attempt to complete tasks, measuring ease of use and user satisfaction.
User Acceptance Testing (UAT)
The final testing phase where end users verify that a software system meets their business requirements before go-live.