Automated Testing Glossary

A teacher at a blackboard
A teacher at a blackboard

Automated Testing Glossary

Jul 20, 2023

Common terms in automation testing and what they mean.

A

API (Application Programming Interface)

A set of rules and protocols that allows different software applications to communicate and interact with each other.

API Testing

Testing the functionality, reliability, and security of APIs to ensure they perform as expected and meet the application's requirements.

Acceptance Testing

Evaluating a software application's compliance with business requirements and determining whether it is ready for deployment and use by end-users.

ATDD (Acceptance Test Driven Development)

An approach where acceptance tests are written before the code is developed, helping to ensure the software meets the desired business outcomes.

Accessibility Testing

Evaluating a software application's usability and inclusivity for users with disabilities to ensure it complies with accessibility standards.

Actual Result

The outcome obtained after executing a test case is compared with the expected result to identify any discrepancies.

Ad Hoc Testing

Informal and unplanned testing carried out without predefined test cases, usually used for exploratory testing or quick checks.

Agile Testing

Testing practices integrated into Agile development methodologies, emphasizing continuous testing, collaboration, and frequent feedback.

Automated Testing

Utilizing automated scripts and tools to execute tests, reducing manual effort and enhancing test efficiency and accuracy.

B

Big Bang Testing

A testing approach where all components or modules are tested simultaneously without prior integration testing.

Black Box Testing

Testing a software application's functionality without knowing its internal code or structure.

Bug

A defect or flaw in a software application that causes it to produce incorrect or unexpected results.

C

Canary Testing

A deployment strategy where a new version of the software is tested with a small subset of users before an entire release.

Chaos Testing

Testing a system's ability to withstand unpredictable and adverse conditions to ensure its stability and recovery capabilities.

Change Requests

Formal proposals for alterations or enhancements to a software application's functionality or features.

Code Coverage

A metric that measures the proportion of code lines or branches exercised by test cases.

Code Review

A systematic peer examination of a software codebase to identify defects, security vulnerabilities, and maintainability issues.

Compatibility Testing

Assessing a software application's ability to function correctly across different environments, devices, and configurations.

Concurrency

How many tests can be run simultaneously.

Content Testing

Testing the accuracy, relevance, and integrity of content displayed in a software application.

Continuous Testing

Integrating testing into the continuous integration and continuous delivery (CI/CD) pipeline to ensure rapid and reliable software releases.

Cross Browser Testing

Evaluating a software application's functionality and compatibility across different web browsers.

CSS Selector

A pattern used to identify and select HTML elements on a web page to apply styling or interact with them.

D

Data-Driven Testing

Executing test cases with multiple sets of input data to validate various scenarios and conditions.

Data Flow Testing

Assessing the flow and processing of data within a software application to identify defects and vulnerabilities.

Debugging

The process of identifying and fixing issues and defects in software code.

Defect

An issue or flaw that affects a software application's functionality, performance, or security.

Defect Management

The process of capturing, tracking, and resolving defects discovered during testing.

Deliverable

A product or artifact created during the testing process, such as test plans, test cases, or test reports.

DevOps Testing

Integrating testing into the DevOps culture and practices to ensure seamless collaboration between development and operations teams.

Dynamic Testing

Assessing a software application's behavior and performance during runtime.

E

End-To-End Testing

Evaluating the entire software application's functionality and performance, including all integrated components.

Error

A human mistake or misunderstanding that leads to a defect in a software application.

Error Logs

Recorded information about errors and exceptions that occur during the execution of a software application.

Emulator

Software or hardware that replicates the behavior of another system to facilitate testing.

Execute

Running a test case or test suite to evaluate a software application's behaviour.

Exhaustive Testing

Testing all possible combinations of inputs and scenarios to ensure maximum coverage.

Expected Result

The predefined outcome that a test case should produce is used for comparison with the actual result.

Exploratory Testing

A dynamic and informal testing approach that relies on the tester's intuition and expertise to discover defects.

Extreme Programming

An Agile development methodology that emphasizes continuous feedback, customer collaboration, and incremental development.

F

Flaky App / Site

A software application or website that produces inconsistent and unpredictable results during testing.

Flaky Test

A test that yields different results in different test executions despite no changes in the application's code.

Front-End Testing

Assessing the functionality and user experience of a software application's front-end components.

Functional Integration

Testing the interaction and compatibility of different functional modules within a software application.

Functional Testing

Evaluating a software application's compliance with specified functional requirements.

Future Proof Testing

Ensuring that a software application's design and code can accommodate future changes and requirements.

G,H,I

Glass Box Testing

A testing approach where testers have access to the internal code and structure of the software application.

Incremental Testing

A testing approach where software components or modules are tested and integrated incrementally.

Inspection

A formal review process where stakeholders analyze and assess a software application's quality and compliance with requirements.

Integration Testing

Assessing the interaction and functionality of integrated components or modules within a software application.

Iteration

A repetitive and incremental development cycle in Agile methodologies.

Interface Testing

Evaluating the interactions and data exchanges between different software components or systems.

J,K,L

Localization Testing

Assessing a software application's functionality and user experience for a specific locale or target market.

M

Maintainability

The ease with which a software application can be modified or updated to meet new requirements or fix defects.

Maintenance Testing

Testing a software application after modifications or updates to ensure its continued performance and stability.

Manual Testing

Executing test cases manually without the use of automated testing tools.

N,O

Negative Testing

Evaluating a software application's behavior under conditions of invalid or unexpected inputs.

Non-functional Testing

Assessing a software application's performance, security, usability, and other non-functional aspects.

P

POM (Page Object Model)

A design pattern used in test automation to represent the elements and interactions of web pages.

Performance Indicator

A metric used to evaluate a software application's performance against predefined criteria.

Performance Testing

Assessing a software application's response time, scalability, and stability under different workloads.

Postcondition

The state or conditions expected to exist after the execution of a test case.

Priority

The level of importance assigned to a defect or requirement.

Q

QA Metrics

Quantitative measurements are used to assess the quality and effectiveness of the testing process.

Quality

The degree to which a software application meets specified requirements and user expectations.

Quality Assurance

The process of ensuring that a software application meets quality standards and follows best practices.

Quality Gate

A predetermined criteria or threshold that must be met before a software application can progress to the next development phase.

R

Retesting / Rerunning

Executing previously failed test cases after defects have been fixed to verify their resolution.

Regression Testing

Repeating test cases to ensure that changes or new code do not introduce defects or negatively impact existing functionality.

Release Testing

Evaluating a software application's readiness for deployment and release.

Reliability Testing

Assessing a software application's ability to perform consistently and reliably over time.

S

Sanity Testing

A quick and basic test to verify whether a software application's critical functions are working as expected.

Scalability Testing

Assessing a software application's ability to handle increased workloads and users.

Screenshot Testing

Capturing and comparing screenshots of a software application to identify visual discrepancies.

SEO Testing

Evaluating a website's search engine optimization to improve its visibility and ranking in search results.

Severity

The impact or criticality of a defect on the software application's functionality or user experience.

Shift-Left Testing

Shifting testing activities to occur earlier in the development process to identify and resolve defects sooner.

Smoke Testing

A basic test to ensure that critical functionalities of a software application are functioning before proceeding with detailed testing.

Software Risk Analysis

Identifying and assessing potential risks and their impact on a software application's development and testing.

Software Development Life Cycle

The process and phases involved in developing a software application from concept to deployment.

Software Quality

The overall level of excellence and adherence to requirements in a software application.

Software Quality Management

The process of overseeing and implementing quality measures throughout the software development and testing lifecycle.

Software Testing

The process of evaluating a software application's functionality, performance, and quality to identify defects and ensure it meets requirements.

Software Testing Life Cycle

The phases and activities involved in planning, executing, and managing software testing.

Static Testing

Assessing a software application's code and documentation without executing the program.

Stress Testing

Evaluating a software application's behavior and performance under extreme load conditions.

System Integration Testing

Testing the interaction and compatibility of the entire system, including all integrated components.

T

Test Approach

The overall strategy and guidelines for conducting software testing.

Test Automation

Using automated tools and scripts to execute tests and compare results.

Test Case

A set of preconditions, inputs, and expected outcomes used to validate specific functionality in a software application.

Test Class

A collection of related test cases or test methods.

Test Comparison

The process of comparing actual test results with expected results to identify discrepancies.

Test Coverage

The extent to which a software application has been tested is measured by the percentage of code or requirements covered.

Test Id (Selector)

A unique identifier is used to locate and interact with elements in test automation.

Test Infrastructure

The hardware, software, and resources required to conduct testing activities.

TDD (Test-Driven Development)

Writing test cases before writing code, with the aim of guiding development and ensuring testability.

Test Data

The input values and conditions used to execute test cases.

Test Environment

A setup that replicates the production environment for testing purposes.

Test Execution

Running test cases to verify the functionality of a software application.

Test Tool

Software or tool used to perform testing activities, such as test automation or defect tracking.

Test Log

Recording test activities, results, and any issues encountered during testing.

Test Management

Planning, coordinating, and controlling testing activities throughout the project.

Test Observability

The ability to monitor and analyze a software application's behavior during testing.

Test Plan

A document outlining the approach, scope, objectives, and schedule of testing activities.

Test Process

The sequence of activities involved in conducting testing.

Test Process Improvement

Identifying and implementing changes to enhance the testing process and its outcomes.

Test Policy

A formal statement defining the organization's approach to software testing.

Test Pyramid

A testing strategy that prioritizes a large base of unit tests, followed by fewer integration tests and even fewer end-to-end tests.

Test Report

Documentation summarizing the test results and outcomes of testing activities.

Test Runner

Software used to execute automated test cases and manage test suites.

Test Specification

Detailed documentation describing test cases, inputs, and expected outcomes.

Test Strategy

An overall plan for conducting software testing based on project goals and constraints.

Test Suite

A collection of related test cases designed to execute together.

U

User Acceptance Testing

Testing a software application from the end user's perspective to ensure it meets their needs and requirements.

UI Testing

Evaluating the functionality, usability, and responsiveness of a software application's user interface.

Unit Test Framework

A set of tools and conventions for writing and executing unit tests.

Unit Testing

Assessing individual units or components of a software application in isolation.

Use Case

A description of interactions between users and a software application to achieve specific goals.

Use Case Testing

Testing a software application's functionality based on various use case scenarios.

Usability Testing

Evaluating a software application's ease of use and user-friendliness.

V

Visible Text (Selector)

A method of identifying web elements using the visible text they contain.

Validation Testing

Confirming that a software application meets specified requirements and user needs.

Visual Regression

Identifying visual discrepancies and changes between different versions of a software application.

W,X,Y,Z

White Box Testing

Assessing a software application's internal code and structure to validate its functionality and logic.

Web Automation

Automating test execution and validation of web applications.

Web Performance Testing

Evaluating the speed, responsiveness, and efficiency of web applications.

Web Testing

Evaluating the functionality, usability, and compatibility of web applications.

XPath Selector

A method of identifying web elements using their XML Path location.

Common terms in automation testing and what they mean.

A

API (Application Programming Interface)

A set of rules and protocols that allows different software applications to communicate and interact with each other.

API Testing

Testing the functionality, reliability, and security of APIs to ensure they perform as expected and meet the application's requirements.

Acceptance Testing

Evaluating a software application's compliance with business requirements and determining whether it is ready for deployment and use by end-users.

ATDD (Acceptance Test Driven Development)

An approach where acceptance tests are written before the code is developed, helping to ensure the software meets the desired business outcomes.

Accessibility Testing

Evaluating a software application's usability and inclusivity for users with disabilities to ensure it complies with accessibility standards.

Actual Result

The outcome obtained after executing a test case is compared with the expected result to identify any discrepancies.

Ad Hoc Testing

Informal and unplanned testing carried out without predefined test cases, usually used for exploratory testing or quick checks.

Agile Testing

Testing practices integrated into Agile development methodologies, emphasizing continuous testing, collaboration, and frequent feedback.

Automated Testing

Utilizing automated scripts and tools to execute tests, reducing manual effort and enhancing test efficiency and accuracy.

B

Big Bang Testing

A testing approach where all components or modules are tested simultaneously without prior integration testing.

Black Box Testing

Testing a software application's functionality without knowing its internal code or structure.

Bug

A defect or flaw in a software application that causes it to produce incorrect or unexpected results.

C

Canary Testing

A deployment strategy where a new version of the software is tested with a small subset of users before an entire release.

Chaos Testing

Testing a system's ability to withstand unpredictable and adverse conditions to ensure its stability and recovery capabilities.

Change Requests

Formal proposals for alterations or enhancements to a software application's functionality or features.

Code Coverage

A metric that measures the proportion of code lines or branches exercised by test cases.

Code Review

A systematic peer examination of a software codebase to identify defects, security vulnerabilities, and maintainability issues.

Compatibility Testing

Assessing a software application's ability to function correctly across different environments, devices, and configurations.

Concurrency

How many tests can be run simultaneously.

Content Testing

Testing the accuracy, relevance, and integrity of content displayed in a software application.

Continuous Testing

Integrating testing into the continuous integration and continuous delivery (CI/CD) pipeline to ensure rapid and reliable software releases.

Cross Browser Testing

Evaluating a software application's functionality and compatibility across different web browsers.

CSS Selector

A pattern used to identify and select HTML elements on a web page to apply styling or interact with them.

D

Data-Driven Testing

Executing test cases with multiple sets of input data to validate various scenarios and conditions.

Data Flow Testing

Assessing the flow and processing of data within a software application to identify defects and vulnerabilities.

Debugging

The process of identifying and fixing issues and defects in software code.

Defect

An issue or flaw that affects a software application's functionality, performance, or security.

Defect Management

The process of capturing, tracking, and resolving defects discovered during testing.

Deliverable

A product or artifact created during the testing process, such as test plans, test cases, or test reports.

DevOps Testing

Integrating testing into the DevOps culture and practices to ensure seamless collaboration between development and operations teams.

Dynamic Testing

Assessing a software application's behavior and performance during runtime.

E

End-To-End Testing

Evaluating the entire software application's functionality and performance, including all integrated components.

Error

A human mistake or misunderstanding that leads to a defect in a software application.

Error Logs

Recorded information about errors and exceptions that occur during the execution of a software application.

Emulator

Software or hardware that replicates the behavior of another system to facilitate testing.

Execute

Running a test case or test suite to evaluate a software application's behaviour.

Exhaustive Testing

Testing all possible combinations of inputs and scenarios to ensure maximum coverage.

Expected Result

The predefined outcome that a test case should produce is used for comparison with the actual result.

Exploratory Testing

A dynamic and informal testing approach that relies on the tester's intuition and expertise to discover defects.

Extreme Programming

An Agile development methodology that emphasizes continuous feedback, customer collaboration, and incremental development.

F

Flaky App / Site

A software application or website that produces inconsistent and unpredictable results during testing.

Flaky Test

A test that yields different results in different test executions despite no changes in the application's code.

Front-End Testing

Assessing the functionality and user experience of a software application's front-end components.

Functional Integration

Testing the interaction and compatibility of different functional modules within a software application.

Functional Testing

Evaluating a software application's compliance with specified functional requirements.

Future Proof Testing

Ensuring that a software application's design and code can accommodate future changes and requirements.

G,H,I

Glass Box Testing

A testing approach where testers have access to the internal code and structure of the software application.

Incremental Testing

A testing approach where software components or modules are tested and integrated incrementally.

Inspection

A formal review process where stakeholders analyze and assess a software application's quality and compliance with requirements.

Integration Testing

Assessing the interaction and functionality of integrated components or modules within a software application.

Iteration

A repetitive and incremental development cycle in Agile methodologies.

Interface Testing

Evaluating the interactions and data exchanges between different software components or systems.

J,K,L

Localization Testing

Assessing a software application's functionality and user experience for a specific locale or target market.

M

Maintainability

The ease with which a software application can be modified or updated to meet new requirements or fix defects.

Maintenance Testing

Testing a software application after modifications or updates to ensure its continued performance and stability.

Manual Testing

Executing test cases manually without the use of automated testing tools.

N,O

Negative Testing

Evaluating a software application's behavior under conditions of invalid or unexpected inputs.

Non-functional Testing

Assessing a software application's performance, security, usability, and other non-functional aspects.

P

POM (Page Object Model)

A design pattern used in test automation to represent the elements and interactions of web pages.

Performance Indicator

A metric used to evaluate a software application's performance against predefined criteria.

Performance Testing

Assessing a software application's response time, scalability, and stability under different workloads.

Postcondition

The state or conditions expected to exist after the execution of a test case.

Priority

The level of importance assigned to a defect or requirement.

Q

QA Metrics

Quantitative measurements are used to assess the quality and effectiveness of the testing process.

Quality

The degree to which a software application meets specified requirements and user expectations.

Quality Assurance

The process of ensuring that a software application meets quality standards and follows best practices.

Quality Gate

A predetermined criteria or threshold that must be met before a software application can progress to the next development phase.

R

Retesting / Rerunning

Executing previously failed test cases after defects have been fixed to verify their resolution.

Regression Testing

Repeating test cases to ensure that changes or new code do not introduce defects or negatively impact existing functionality.

Release Testing

Evaluating a software application's readiness for deployment and release.

Reliability Testing

Assessing a software application's ability to perform consistently and reliably over time.

S

Sanity Testing

A quick and basic test to verify whether a software application's critical functions are working as expected.

Scalability Testing

Assessing a software application's ability to handle increased workloads and users.

Screenshot Testing

Capturing and comparing screenshots of a software application to identify visual discrepancies.

SEO Testing

Evaluating a website's search engine optimization to improve its visibility and ranking in search results.

Severity

The impact or criticality of a defect on the software application's functionality or user experience.

Shift-Left Testing

Shifting testing activities to occur earlier in the development process to identify and resolve defects sooner.

Smoke Testing

A basic test to ensure that critical functionalities of a software application are functioning before proceeding with detailed testing.

Software Risk Analysis

Identifying and assessing potential risks and their impact on a software application's development and testing.

Software Development Life Cycle

The process and phases involved in developing a software application from concept to deployment.

Software Quality

The overall level of excellence and adherence to requirements in a software application.

Software Quality Management

The process of overseeing and implementing quality measures throughout the software development and testing lifecycle.

Software Testing

The process of evaluating a software application's functionality, performance, and quality to identify defects and ensure it meets requirements.

Software Testing Life Cycle

The phases and activities involved in planning, executing, and managing software testing.

Static Testing

Assessing a software application's code and documentation without executing the program.

Stress Testing

Evaluating a software application's behavior and performance under extreme load conditions.

System Integration Testing

Testing the interaction and compatibility of the entire system, including all integrated components.

T

Test Approach

The overall strategy and guidelines for conducting software testing.

Test Automation

Using automated tools and scripts to execute tests and compare results.

Test Case

A set of preconditions, inputs, and expected outcomes used to validate specific functionality in a software application.

Test Class

A collection of related test cases or test methods.

Test Comparison

The process of comparing actual test results with expected results to identify discrepancies.

Test Coverage

The extent to which a software application has been tested is measured by the percentage of code or requirements covered.

Test Id (Selector)

A unique identifier is used to locate and interact with elements in test automation.

Test Infrastructure

The hardware, software, and resources required to conduct testing activities.

TDD (Test-Driven Development)

Writing test cases before writing code, with the aim of guiding development and ensuring testability.

Test Data

The input values and conditions used to execute test cases.

Test Environment

A setup that replicates the production environment for testing purposes.

Test Execution

Running test cases to verify the functionality of a software application.

Test Tool

Software or tool used to perform testing activities, such as test automation or defect tracking.

Test Log

Recording test activities, results, and any issues encountered during testing.

Test Management

Planning, coordinating, and controlling testing activities throughout the project.

Test Observability

The ability to monitor and analyze a software application's behavior during testing.

Test Plan

A document outlining the approach, scope, objectives, and schedule of testing activities.

Test Process

The sequence of activities involved in conducting testing.

Test Process Improvement

Identifying and implementing changes to enhance the testing process and its outcomes.

Test Policy

A formal statement defining the organization's approach to software testing.

Test Pyramid

A testing strategy that prioritizes a large base of unit tests, followed by fewer integration tests and even fewer end-to-end tests.

Test Report

Documentation summarizing the test results and outcomes of testing activities.

Test Runner

Software used to execute automated test cases and manage test suites.

Test Specification

Detailed documentation describing test cases, inputs, and expected outcomes.

Test Strategy

An overall plan for conducting software testing based on project goals and constraints.

Test Suite

A collection of related test cases designed to execute together.

U

User Acceptance Testing

Testing a software application from the end user's perspective to ensure it meets their needs and requirements.

UI Testing

Evaluating the functionality, usability, and responsiveness of a software application's user interface.

Unit Test Framework

A set of tools and conventions for writing and executing unit tests.

Unit Testing

Assessing individual units or components of a software application in isolation.

Use Case

A description of interactions between users and a software application to achieve specific goals.

Use Case Testing

Testing a software application's functionality based on various use case scenarios.

Usability Testing

Evaluating a software application's ease of use and user-friendliness.

V

Visible Text (Selector)

A method of identifying web elements using the visible text they contain.

Validation Testing

Confirming that a software application meets specified requirements and user needs.

Visual Regression

Identifying visual discrepancies and changes between different versions of a software application.

W,X,Y,Z

White Box Testing

Assessing a software application's internal code and structure to validate its functionality and logic.

Web Automation

Automating test execution and validation of web applications.

Web Performance Testing

Evaluating the speed, responsiveness, and efficiency of web applications.

Web Testing

Evaluating the functionality, usability, and compatibility of web applications.

XPath Selector

A method of identifying web elements using their XML Path location.

Common terms in automation testing and what they mean.

A

API (Application Programming Interface)

A set of rules and protocols that allows different software applications to communicate and interact with each other.

API Testing

Testing the functionality, reliability, and security of APIs to ensure they perform as expected and meet the application's requirements.

Acceptance Testing

Evaluating a software application's compliance with business requirements and determining whether it is ready for deployment and use by end-users.

ATDD (Acceptance Test Driven Development)

An approach where acceptance tests are written before the code is developed, helping to ensure the software meets the desired business outcomes.

Accessibility Testing

Evaluating a software application's usability and inclusivity for users with disabilities to ensure it complies with accessibility standards.

Actual Result

The outcome obtained after executing a test case is compared with the expected result to identify any discrepancies.

Ad Hoc Testing

Informal and unplanned testing carried out without predefined test cases, usually used for exploratory testing or quick checks.

Agile Testing

Testing practices integrated into Agile development methodologies, emphasizing continuous testing, collaboration, and frequent feedback.

Automated Testing

Utilizing automated scripts and tools to execute tests, reducing manual effort and enhancing test efficiency and accuracy.

B

Big Bang Testing

A testing approach where all components or modules are tested simultaneously without prior integration testing.

Black Box Testing

Testing a software application's functionality without knowing its internal code or structure.

Bug

A defect or flaw in a software application that causes it to produce incorrect or unexpected results.

C

Canary Testing

A deployment strategy where a new version of the software is tested with a small subset of users before an entire release.

Chaos Testing

Testing a system's ability to withstand unpredictable and adverse conditions to ensure its stability and recovery capabilities.

Change Requests

Formal proposals for alterations or enhancements to a software application's functionality or features.

Code Coverage

A metric that measures the proportion of code lines or branches exercised by test cases.

Code Review

A systematic peer examination of a software codebase to identify defects, security vulnerabilities, and maintainability issues.

Compatibility Testing

Assessing a software application's ability to function correctly across different environments, devices, and configurations.

Concurrency

How many tests can be run simultaneously.

Content Testing

Testing the accuracy, relevance, and integrity of content displayed in a software application.

Continuous Testing

Integrating testing into the continuous integration and continuous delivery (CI/CD) pipeline to ensure rapid and reliable software releases.

Cross Browser Testing

Evaluating a software application's functionality and compatibility across different web browsers.

CSS Selector

A pattern used to identify and select HTML elements on a web page to apply styling or interact with them.

D

Data-Driven Testing

Executing test cases with multiple sets of input data to validate various scenarios and conditions.

Data Flow Testing

Assessing the flow and processing of data within a software application to identify defects and vulnerabilities.

Debugging

The process of identifying and fixing issues and defects in software code.

Defect

An issue or flaw that affects a software application's functionality, performance, or security.

Defect Management

The process of capturing, tracking, and resolving defects discovered during testing.

Deliverable

A product or artifact created during the testing process, such as test plans, test cases, or test reports.

DevOps Testing

Integrating testing into the DevOps culture and practices to ensure seamless collaboration between development and operations teams.

Dynamic Testing

Assessing a software application's behavior and performance during runtime.

E

End-To-End Testing

Evaluating the entire software application's functionality and performance, including all integrated components.

Error

A human mistake or misunderstanding that leads to a defect in a software application.

Error Logs

Recorded information about errors and exceptions that occur during the execution of a software application.

Emulator

Software or hardware that replicates the behavior of another system to facilitate testing.

Execute

Running a test case or test suite to evaluate a software application's behaviour.

Exhaustive Testing

Testing all possible combinations of inputs and scenarios to ensure maximum coverage.

Expected Result

The predefined outcome that a test case should produce is used for comparison with the actual result.

Exploratory Testing

A dynamic and informal testing approach that relies on the tester's intuition and expertise to discover defects.

Extreme Programming

An Agile development methodology that emphasizes continuous feedback, customer collaboration, and incremental development.

F

Flaky App / Site

A software application or website that produces inconsistent and unpredictable results during testing.

Flaky Test

A test that yields different results in different test executions despite no changes in the application's code.

Front-End Testing

Assessing the functionality and user experience of a software application's front-end components.

Functional Integration

Testing the interaction and compatibility of different functional modules within a software application.

Functional Testing

Evaluating a software application's compliance with specified functional requirements.

Future Proof Testing

Ensuring that a software application's design and code can accommodate future changes and requirements.

G,H,I

Glass Box Testing

A testing approach where testers have access to the internal code and structure of the software application.

Incremental Testing

A testing approach where software components or modules are tested and integrated incrementally.

Inspection

A formal review process where stakeholders analyze and assess a software application's quality and compliance with requirements.

Integration Testing

Assessing the interaction and functionality of integrated components or modules within a software application.

Iteration

A repetitive and incremental development cycle in Agile methodologies.

Interface Testing

Evaluating the interactions and data exchanges between different software components or systems.

J,K,L

Localization Testing

Assessing a software application's functionality and user experience for a specific locale or target market.

M

Maintainability

The ease with which a software application can be modified or updated to meet new requirements or fix defects.

Maintenance Testing

Testing a software application after modifications or updates to ensure its continued performance and stability.

Manual Testing

Executing test cases manually without the use of automated testing tools.

N,O

Negative Testing

Evaluating a software application's behavior under conditions of invalid or unexpected inputs.

Non-functional Testing

Assessing a software application's performance, security, usability, and other non-functional aspects.

P

POM (Page Object Model)

A design pattern used in test automation to represent the elements and interactions of web pages.

Performance Indicator

A metric used to evaluate a software application's performance against predefined criteria.

Performance Testing

Assessing a software application's response time, scalability, and stability under different workloads.

Postcondition

The state or conditions expected to exist after the execution of a test case.

Priority

The level of importance assigned to a defect or requirement.

Q

QA Metrics

Quantitative measurements are used to assess the quality and effectiveness of the testing process.

Quality

The degree to which a software application meets specified requirements and user expectations.

Quality Assurance

The process of ensuring that a software application meets quality standards and follows best practices.

Quality Gate

A predetermined criteria or threshold that must be met before a software application can progress to the next development phase.

R

Retesting / Rerunning

Executing previously failed test cases after defects have been fixed to verify their resolution.

Regression Testing

Repeating test cases to ensure that changes or new code do not introduce defects or negatively impact existing functionality.

Release Testing

Evaluating a software application's readiness for deployment and release.

Reliability Testing

Assessing a software application's ability to perform consistently and reliably over time.

S

Sanity Testing

A quick and basic test to verify whether a software application's critical functions are working as expected.

Scalability Testing

Assessing a software application's ability to handle increased workloads and users.

Screenshot Testing

Capturing and comparing screenshots of a software application to identify visual discrepancies.

SEO Testing

Evaluating a website's search engine optimization to improve its visibility and ranking in search results.

Severity

The impact or criticality of a defect on the software application's functionality or user experience.

Shift-Left Testing

Shifting testing activities to occur earlier in the development process to identify and resolve defects sooner.

Smoke Testing

A basic test to ensure that critical functionalities of a software application are functioning before proceeding with detailed testing.

Software Risk Analysis

Identifying and assessing potential risks and their impact on a software application's development and testing.

Software Development Life Cycle

The process and phases involved in developing a software application from concept to deployment.

Software Quality

The overall level of excellence and adherence to requirements in a software application.

Software Quality Management

The process of overseeing and implementing quality measures throughout the software development and testing lifecycle.

Software Testing

The process of evaluating a software application's functionality, performance, and quality to identify defects and ensure it meets requirements.

Software Testing Life Cycle

The phases and activities involved in planning, executing, and managing software testing.

Static Testing

Assessing a software application's code and documentation without executing the program.

Stress Testing

Evaluating a software application's behavior and performance under extreme load conditions.

System Integration Testing

Testing the interaction and compatibility of the entire system, including all integrated components.

T

Test Approach

The overall strategy and guidelines for conducting software testing.

Test Automation

Using automated tools and scripts to execute tests and compare results.

Test Case

A set of preconditions, inputs, and expected outcomes used to validate specific functionality in a software application.

Test Class

A collection of related test cases or test methods.

Test Comparison

The process of comparing actual test results with expected results to identify discrepancies.

Test Coverage

The extent to which a software application has been tested is measured by the percentage of code or requirements covered.

Test Id (Selector)

A unique identifier is used to locate and interact with elements in test automation.

Test Infrastructure

The hardware, software, and resources required to conduct testing activities.

TDD (Test-Driven Development)

Writing test cases before writing code, with the aim of guiding development and ensuring testability.

Test Data

The input values and conditions used to execute test cases.

Test Environment

A setup that replicates the production environment for testing purposes.

Test Execution

Running test cases to verify the functionality of a software application.

Test Tool

Software or tool used to perform testing activities, such as test automation or defect tracking.

Test Log

Recording test activities, results, and any issues encountered during testing.

Test Management

Planning, coordinating, and controlling testing activities throughout the project.

Test Observability

The ability to monitor and analyze a software application's behavior during testing.

Test Plan

A document outlining the approach, scope, objectives, and schedule of testing activities.

Test Process

The sequence of activities involved in conducting testing.

Test Process Improvement

Identifying and implementing changes to enhance the testing process and its outcomes.

Test Policy

A formal statement defining the organization's approach to software testing.

Test Pyramid

A testing strategy that prioritizes a large base of unit tests, followed by fewer integration tests and even fewer end-to-end tests.

Test Report

Documentation summarizing the test results and outcomes of testing activities.

Test Runner

Software used to execute automated test cases and manage test suites.

Test Specification

Detailed documentation describing test cases, inputs, and expected outcomes.

Test Strategy

An overall plan for conducting software testing based on project goals and constraints.

Test Suite

A collection of related test cases designed to execute together.

U

User Acceptance Testing

Testing a software application from the end user's perspective to ensure it meets their needs and requirements.

UI Testing

Evaluating the functionality, usability, and responsiveness of a software application's user interface.

Unit Test Framework

A set of tools and conventions for writing and executing unit tests.

Unit Testing

Assessing individual units or components of a software application in isolation.

Use Case

A description of interactions between users and a software application to achieve specific goals.

Use Case Testing

Testing a software application's functionality based on various use case scenarios.

Usability Testing

Evaluating a software application's ease of use and user-friendliness.

V

Visible Text (Selector)

A method of identifying web elements using the visible text they contain.

Validation Testing

Confirming that a software application meets specified requirements and user needs.

Visual Regression

Identifying visual discrepancies and changes between different versions of a software application.

W,X,Y,Z

White Box Testing

Assessing a software application's internal code and structure to validate its functionality and logic.

Web Automation

Automating test execution and validation of web applications.

Web Performance Testing

Evaluating the speed, responsiveness, and efficiency of web applications.

Web Testing

Evaluating the functionality, usability, and compatibility of web applications.

XPath Selector

A method of identifying web elements using their XML Path location.

Now give these buttons a good test 😜

Want Better Automation Tests?

Want Better Automation Tests?

High-quality test coverage with reliable test automation.