Software testing glossary

Your go-to guide for all things QA! From beginner-friendly definitions to in-depth explanations, we’ve got you covered with software testing terms, tools, and techniques to level up your QA game.

New to testing? Try starting with our Term of the Day

A

Accessibility Testing

A type of testing to ensure that applications are usable by people with disabilities to make websites more inclusive.

Agile Methodology

A way of managing projects by breaking them into smaller, more manageable parts. Teams work in short cycles called sprints (1-4 weeks) to plan, build, test, and deliver piece by piece of the project.

Agile Testing

A testing approach aligned with Agile principles, where testing is integrated into every phase of the development lifecycle.

AI Testing

A testing technique that leverages AI/LLMs to improve testing efficiency.

Alpha Testing

A testing type that occurs internally within the development organization to identify and resolve bugs before releasing the product to external users.

API

A set of rules and tools that allows one program to interact with another. It defines how you can request information or services from another system and how that system will respond.

API Mocking

A technique that simulates API responses to test application behavior without relying on a live server.

API Sandbox

A controlled testing environment that replicates API functionality for safe and isolated testing.

API Testing

A testing practice that validates the functionality, reliability, and performance of APIs.

Automated Regression Testing

A testing process that ensures new changes do not negatively impact existing features.

Automation Testing

A testing approach that uses tools and scripts to execute tests, reducing manual effort and time.

Autonomous Testing

A testing method that leverages AI and automation to independently create, run, and analyze tests.

FEATURED TERM

Telecom Testing

A specialized testing process that validates telecom systems, networks, and applications to ensure seamless communication, quality, and reliability across various protocols and devices.

Learn more →

Have a more specific question? Ask our community of 100k testers →

B

BDD Testing

A testing approach that uses behavior-driven development to align tests with business goals by writing scenarios in plain language, ensuring clarity and collaboration among developers, testers, and stakeholders.

Black Box Testing

A method that tests software functionality without knowledge of its internal code, focusing solely on inputs and expected outputs to identify issues from the user’s perspective.

Boundary Value Analysis

A test design technique that targets the edge values of input ranges, where defects are most likely to occur, ensuring effective coverage with minimal test cases.

Bug

A flaw or error in software that causes incorrect or unexpected behavior, requiring identification, prioritization, and resolution within the defect lifecycle.

C

Chaos Testing

A testing practice that intentionally disrupts system components, simulating real-world failures to uncover weaknesses and ensure system resilience under unpredictable conditions.

CI/CD

A development practice combining Continuous Integration (merging code frequently) and Continuous Delivery (automated deployment) to streamline software release cycles and improve quality.

CI/CD Pipeline

An automated workflow that builds, tests, and deploys code changes efficiently, enabling rapid feedback, consistent deployments, and smoother collaboration across teams.

Cross Browser Testing

A process that verifies application functionality, performance, and appearance across multiple browsers, devices, and operating systems to ensure a seamless user experience.

Cucumber Testing

A behavior-driven testing approach using the Cucumber tool to write executable test cases in Gherkin syntax, making test scenarios easy to understand for all stakeholders.

D

Database Testing

A testing process that validates database integrity, schema, queries, and data consistency to ensure accurate, secure, and high-performance interactions with software systems.

Desktop Testing

A method that tests desktop applications for functionality, usability, and performance across operating systems, ensuring reliability in standalone environments.

DevOps Implementation

A strategic process that integrates development and operations teams, automating workflows, improving collaboration, and accelerating software delivery cycles.

DevOps Lifecycle

A series of phases—planning, development, testing, deployment, and monitoring—that ensures continuous improvement and faster delivery of reliable software.

DevTestOps

A methodology combining development, testing, and operations into a unified process, enabling faster feedback and continuous testing within agile software delivery.

DevTestOps Orchestration

A practice that automates and coordinates DevTestOps workflows, streamlining testing, improving collaboration, and enhancing test coverage across agile teams.

E

End-to-End Testing

A testing approach that validates the complete workflow of an application, ensuring all integrated components work together as expected from start to finish.

Equivalence Class Partitioning

A test design technique that divides input data into partitions to reduce test cases while maintaining coverage by selecting representative values for each group.

Exploratory Testing

A hands-on testing approach where testers simultaneously design, execute, and adapt test cases based on their experience and real-time observations to uncover hidden defects.

F

Functional Testing

A testing process that verifies each function of an application against specified requirements to ensure correct output based on given inputs.

G

Geolocation Testing

A testing method that evaluates application behavior based on user location data, ensuring features like localization, navigation, and geo-specific content work accurately.

GraphQL

A query language for APIs that enables efficient data retrieval by allowing clients to specify exactly what data they need, reducing over-fetching and under-fetching issues.

GraphQL Testing

A testing process that validates GraphQL queries, mutations, and schema to ensure accurate, secure, and performant API interactions.

I

Integration Testing

A testing phase that ensures seamless communication and data flow between integrated modules or components within a system.

L

Live Testing

A testing practice that involves executing tests on a live or real-time environment to evaluate application performance, behavior, and functionality under actual conditions.

Low-Code Testing

A testing approach that leverages low-code tools to simplify test automation, allowing users with minimal coding expertise to create, run, and maintain tests efficiently.

M

Manual Mobile Testing

A testing process where testers manually evaluate mobile applications on real devices to identify issues related to functionality, usability, and performance.

Manual Testing

A testing process performed manually without automation tools, where testers validate software functionality by executing test cases step-by-step.

Microservices

An architectural style that structures applications as a collection of small, independent services, each focused on a specific function, enabling scalability and flexibility.

Mobile Cloud Testing

A testing method that uses cloud-based platforms to evaluate mobile applications across diverse devices, operating systems, and networks without physical infrastructure.

Mobile Testing

A process that tests mobile applications for functionality, usability, performance, and compatibility across various devices, operating systems, and network conditions.

O

Omnichannel Testing

A testing approach that ensures a seamless user experience across multiple channels—web, mobile, and other platforms—by validating consistent functionality and performance.

P

Penetration Testing

A security testing method that simulates cyberattacks to identify vulnerabilities in software systems, ensuring systems are protected against real-world threats.

Performance Testing

A testing process that evaluates software responsiveness, speed, and stability under normal and peak conditions to ensure optimal performance.

Q

QA / Quality Assurance

A proactive process focused on improving software quality by establishing standards, processes, and testing practices throughout the development lifecycle.

R

Regression Testing

A testing process that ensures recent changes in the code do not break existing functionality, verifying software stability after updates or fixes.

S

Sanity Testing

A focused testing approach that quickly verifies specific bug fixes or minor changes to confirm the software works as expected before further testing.

Shift Left Testing

A testing strategy that involves starting testing earlier in the development process to catch defects sooner, reduce costs, and accelerate delivery.

Shift Right Testing

A testing approach that focuses on validating software quality in production environments by monitoring, testing, and gathering feedback post-deployment.

Soak Testing

A performance testing method that evaluates system stability and resource usage over prolonged periods under sustained load to detect potential issues like memory leaks.

Software Testing

A process that verifies and validates software functionality, performance, and quality to ensure it meets user requirements and works as intended.

Software Testing Life Cycle

A systematic process that defines phases—planning, design, execution, reporting, and closure—to ensure thorough and organized software testing.

Synthetic Monitoring

A proactive monitoring technique that uses automated scripts to simulate user behavior, testing application availability and performance around the clock.

T

TDD

Test-Driven Development (TDD) is a software development methodology where tests are written before code, ensuring functionality aligns with requirements and reducing defects early in the process.

Test Case Management

The process of organizing, creating, and maintaining test cases to ensure comprehensive coverage, efficient execution, and traceability throughout the testing lifecycle.

Test Data Management

A strategy for creating, managing, and maintaining high-quality, relevant, and secure test data to support efficient testing and compliance with regulations.

Test Environment

A controlled setup, including hardware, software, and configurations, that replicates production environments for accurate and reliable software testing.

Test Execution

The process of running test cases, logging results, and identifying defects to validate software functionality, performance, and quality.

Test Infrastructure

The foundational setup of tools, systems, and environments required to support effective testing, ensuring efficiency, scalability, and reliability.

Test Plan

A detailed document outlining the testing scope, objectives, resources, schedule, and deliverables to ensure structured and effective test execution.

Test Pyramid

A testing strategy that emphasizes a balanced mix of unit tests, integration tests, and UI tests to achieve efficiency, reliability, and faster feedback.

Test Report

A summary document providing insights into test results, defects, and overall software quality, helping stakeholders make informed decisions.

Test Strategy

A high-level document that defines the testing approach, tools, scope, and objectives to ensure consistent and effective testing practices.

Test Suite Management

The process of organizing and managing groups of related test cases to streamline test execution and ensure efficient test coverage.

Testing Center of Excellence

A centralized framework that standardizes testing practices, tools, and processes to improve software quality, efficiency, and collaboration across teams.

TestOps

An approach that integrates testing into CI/CD pipelines, combining test automation, infrastructure, and monitoring to optimize software quality and delivery.

U

UI Testing

A testing process that verifies user interface elements—buttons, menus, and visuals—function correctly and provide a seamless, intuitive user experience.

Unit Testing

A testing method that focuses on validating individual components or functions in isolation to ensure they work as expected and produce correct results.

User Acceptance Testing

The final testing phase where real users validate whether the software meets business requirements and is ready for deployment.

W

Web Application Development

The process of designing, building, and deploying web-based applications that address user needs, combining front-end, back-end, and testing practices.

Web Testing

A process that evaluates web applications for functionality, performance, security, and compatibility across different browsers and devices.

White Box Testing

A testing method that examines the internal structure, logic, and code of an application to ensure accuracy, security, and optimal performance.

Oops! We couldn’t find that term.

But don’t worry—our glossary is constantly growing.
Try a different search term, or let us know what you were looking for!

By category

Clear

API

Desktop

Mobile

QA Concepts and Best Practices

Software Development Methodologies

Test Automation and Tools

Test Management and Reporting

Testing Types

Web

By letter

A

B

C

D

E

F

G

I

L

M

O

P

Q

R

S

T

U

W

Frequently asked questions

What is the Software Testing Glossary?

+

The Software Testing Glossary is a comprehensive collection of key terms and definitions related to software testing, automation, methodologies, and tools. We extracted these definitions from the ISTBQ, making it a quick reference guide for beginners and experts alike to understand testing concepts clearly.

Each of these terms is linked to a highly detailed article on Katalon Blog where you can learn more about the term.

This glossary is designed for software developers, testers, QA professionals, project managers, and anyone involved in software development and testing. It’s also helpful for students or newcomers to the industry looking to familiarize themselves with testing terminology.

What kind of terms are included in the glossary?

+

The glossary includes a wide range of terms, such as:

• Testing methodologies (e.g., black-box testing, regression testing).
• Types of testing (e.g., functional, non-functional, unit testing).
• Automation tools and frameworks (e.g., Selenium, Appium).
• Key industry concepts (e.g., CI/CD, Agile testing).

How do I use this glossary?

+

Our glossary is arranged alphabetically. You can use it the same way you use a dictionary: jump to the initial letter of the term you want to search for and then scroll down to the definition. You can also filter by category.

The Katalon Software Testing Glossary is also helpful for training, onboarding, or preparing for certifications and interviews in the software testing field. If you want to dive deeper, there’s always the Katalon Blog with well-researched and insightful articles.

Is the glossary updated regularly?

+

Yes, the glossary is continuously updated to reflect the latest trends, tools, and methodologies in the software testing industry.

Can I suggest new terms to add to the glossary?

+

Absolutely! If you think a term or concept is missing, simply use this form to suggest new terms to include on this page.

Secure your competitive advantage in the QA field

Join our Academy to expand your knowledge and earn certificates that kickstart your QA career.

Join Katalon Academy