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.

AI-Assisted Test Case Generation

Automatically generates test cases to enhance coverage and ensure traceability to business requirements.

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.

Automated Test Suite

An automated test suite is one configured to run at specific time intervals or triggered by certain conditions.

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

Manual Testing

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

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.

Big Bang integration testing

An approach where all components are integrated simultaneously and tested as a whole system, often leading to complex debugging.

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.

Bottom-up integration testing

An integration testing approach where lower-level modules are tested first, and higher-level modules are integrated step by step.

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.

Built-in Keyword

A predefined function in Katalon Studio that can be used to create test scripts.

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.

Checkpoint

Checkpoint is the snapshot of test data taken at a specific time. A checkpoint is used to verify whether the current state of the data source is different from its previous state.

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 Integrations

Integrate Katalon projects into CI/CD pipelines.

CI/CD Pipeline

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

Cloud-Based Test Execution Environment

Equipped with common browsers and operating systems.

Collaboration Features

Version control, shared test artifacts, and integration with ALM tools.

Conditional Statement

A control structure that executes a set of instructions based on a condition.

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.

Cross-Browser and OS Testing

Execute tests on most standard browsers and operating systems on the cloud.

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.

Custom Keyword

A user-defined function in Katalon Studio that can be used to create test scripts.

D

Data Binding

The data binding feature allows you to bind test data files with the variables defined in the test case and dynamically run tests with the bound test data. In Katalon Studio, you can perform data binding at the test suite level and the test case level.

Data-driven testing

A testing method where the same test case is run multiple times with different input data sets to validate the system’s behavior under various conditions.

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.

Desktop Web Testing

TestCloud supports desktop browser testing across multiple browsers on Windows, macOS and Linux. The desktop test environments include: Chrome, Chrome (headless), Edge Chromium, Firefox, Firefox (headless), Safari (macOS only) and IE (Windows only).

Device Farm

A collection of physical devices maintained by Katalon TestCloud for test execution.

Device Log

Logs captured from the test device during execution to help identify issues related to the device's configuration.

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

Emulator

A tool that replicates both the behavior and internal functionality of a system or component, allowing testing as if on the original hardware or environment.

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.

Exception Handling Statement

In Katalon Studio, a statement refers to a line of code or instruction written in a test script (Groovy or Java syntax) that performs an action, defines a condition, or executes logic during test execution.

Execution Profile

A set of configurations that determine how a test case is executed.

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

Front end testing

Testing focused on the user interface and user interactions to ensure the application behaves as expected.

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.

Global Variable

A variable that can be accessed from any test case or test suite in a project.

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.

GUI testing

Testing the graphical interface of an application to ensure visual elements and user interactions function as intended.

I

Integration Testing

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

K

Katalon Runtime Engine

Katalon Runtime Engine (KRE) is the test execution add-on of Katalon Studio. Katalon Runtime Engine allows you to execute automation tests in CLI mode. It can be used in a variety of scenarios, such as scheduling your tests, integrating with CI/CD system, or bundling your tests to execute in virtual containers like Docker.

Keywords

Predefined functions in Katalon Studio that can be used to create test scripts. They can be either built-in or custom.

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.

Live Testing

The process of testing a software application in a real-world environment, typically with real users, to identify any issues or bugs that may not have been detected during earlier testing phases.

Local Testing

The process of testing a software application on a local machine or environment, typically to ensure that it functions correctly before being deployed to a production environment.

Local Variable

A variable that can only be accessed within the test case or test suite where it is defined.

Log-viewer

After executing a test case, Katalon Studio provides you with comprehensive execution logs in the Log Viewer. You can quickly investigate the logs to pinpoint the root causes of any issue and correct the test execution with Debug utilities.

Loop

A control structure that repeats a set of instructions until a specific condition is met.

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

Manage Test Suites

A collection of test cases that are intended to be executed as a group.

Manual Mobile Testing

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

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 Native App Testing

The process of testing mobile applications that are developed specifically for a particular mobile platform, such as iOS or Android.

Mobile Testing

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

Mobile Web Testinng

TestCloud mobile browser testing supports built-in browser for each OS. The mobile test environments include built-in browser of each operating system (OS): Safari for iOS and Chrome for Android.

O

Object Repository

Object Repository is a folder structure within your Katalon project that contains Test Objects. Each test object represents a UI element (like a button, text field, link, etc.) and contains information about how to locate that element on a web, mobile, or desktop application.

Object Spy

A utility in Katalon Studio that allows users to inspect and gather information about UI elements.

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.

Pesticide paradox

The principle that repeatedly executing the same test cases will eventually stop revealing new defects, requiring regular test case updates.

Q

QA / Quality Assurance

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

QA process

A structured set of activities designed to ensure quality across software development, including standards, audits, and continuous improvement.

R

Recorder

A utility in Katalon Studio that allows users to create automated test scripts by recording interactions with the application under test.

Recorder and Spy Utilities

Generate automated test cases by interacting with the application under test.

Regression Test Suite

A regression test suite is a collection of regression test cases that share certain characteristics.

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.

Scalability

Addresses scalability issues due to cost and time constraints in setting up physical labs.

Search Test Cases

A series of conditions or events to determine whether an application or software system is working according to expectations.

Self-Healing

A feature in Katalon Studio that automatically repairs broken tests caused by minor changes in the application under test.

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.

Simulator

A tool that mimics the behavior of a real system or component for testing purposes, without replicating the exact internal workings.

Smart Wait

A function in Katalon Studio that allows tests to wait for certain conditions to be met before proceeding.

Smoke testing

A preliminary test run to verify that the basic and critical functionalities of a software build are working correctly.

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 data generation

The process of creating artificial data that mimics real data for safe and controlled testing scenarios.

Synthetic Monitoring

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

System UI

Interface elements provided by the system or platform, such as navigation bars or system dialogs, that interact with the application.

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.

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.

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 coverage techniques

Methods to measure how much of the software has been tested. Examples include code coverage, requirements coverage, and risk-based coverage.

Test Data

Input data used in test cases to produce the expected result.

Test Data Centralization

Oversee team productivity and product quality status.

Test Data File

A file that contains test data for data-driven testing.

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 failure analysis

The investigation and analysis of failed tests to determine the root cause of defects or issues in the application or environment.

Test Infrastructure

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

Test Listeners

An event-based interface that allows customization of test case execution.

Test Maintenance

Methods to handle errors during test execution and fix tests to stay up-to-date with code changes.

Test management

The process of planning, controlling, and tracking the testing efforts, including test case creation, execution, and defect management.

Test Object

A representation of a UI element in the application under test.

Test orchestration

The coordinated execution of automated test suites across environments and systems, often integrated with CI/CD pipelines.

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 reporting

The process of documenting and presenting test results, including metrics like pass/fail rates, defect counts, and execution time.

Test scenario

A high-level description of a functionality or business process to be tested, typically derived from requirements or user stories.

Test Scripts

A test script is an automation script written specifically to automate the steps of a test case.

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.

TestCloud

A cloud-based test execution service provided by Katalon that allows users to run automated tests on a variety of devices and platforms.

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.

TestOps

Katalon TestOps is a modern, comprehensive quality management platform that enables teams to easily and efficiently test, launch, and optimize the best digital experiences. It provides capabilities that allow test automation teams to collaborate, manage, scale, and continuously improve testing operations.

Top-down integration testing

An integration testing approach where top-level modules are tested first, with lower-level modules progressively integrated using stubs.

TrueTest

Katalon TrueTest is an add-on AI-augmented test automation solution that automatically discovers, models, generates, and maintains user-journey test cases. TrueTest provides a streamlined test generation process, saving time and improving testing efficiency.

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.

V

Verification Point

In Katalon Studio, a Verification Point refers to a specific step in a test case where the actual outcome of the application is compared against the expected result to determine whether the test passes or fails.

Visual Testing

Visual testing is an automated process used to verify the user interface (UI) of web and mobile applications, ensuring that the application appears to end users exactly as intended.

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 product

Clear

Studio

TestCloud

TestOps

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

K

L

M

O

P

Q

R

S

T

U

V

W

By letter

A

B

C

D

E

F

G

I

K

L

M

O

P

Q

R

S

T

U

V

W

By product

Clear

Studio

TestCloud

TestOps

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

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