QA Glossary

Definition:

A type of testing conducted to determine whether a system meets the requirements and is ready for delivery.

Example:

Running a final set of tests against the system to confirm that the software functions as expected before release.

Best practices:

Definition:

An initial phase of testing conducted by internal teams before releasing the product to external users.

Example:

In-house testers running tests on an early version of the software to identify bugs and usability issues.

Best practices:

Definition:

Using software tools to execute pre-scripted tests on an application before it is released into production.

Example:

Automating regression tests to quickly validate that new code changes haven’t broken existing functionality.

Best practices:

Definition:

A phase of testing where a product is released to a limited audience outside the development team to identify bugs and gather user feedback.

Example:

Releasing a new app version to a select group of users who provide feedback on performance and usability.

Best practices:

Definition:

Testing a system without any knowledge of its internal workings; focuses on inputs and expected outputs.

Example:

Testing a login function by entering different usernames and passwords to see if the system responds correctly.

Best practices:

Definition:

The process of capturing, reporting, and managing defects in software during the development and testing phases.

Example:

Using a bug report software to log defects and track their status until resolution.

Best practices:

Definition:

A software development practice where developers frequently integrate code changes into a shared repository, followed by automated builds and tests.

Example:

Developers push code changes multiple times a day, and the CI server automatically runs tests to catch issues early.

Best practices:

Definition:

A testing approach that validates the complete functionality of an application, including the integration of all components from start to finish.

Example:

Testing an e-commerce site by completing a full purchase flow from product search to checkout and payment confirmation.

Best practices:

Definition:

An informal testing approach where testers actively explore the application to identify defects based on their intuition and experience.

Example:

Manually navigating a newly developed feature to identify any unexpected behaviors or errors.

Best practices:

Definition:

Testing individual components together to ensure they work correctly as a group.

Example:

Testing the interaction between a web application\'92s front-end and back-end APIs.

Best practices:

Definition:

A type of performance testing that determines how a system behaves under expected and peak loads.

Example:

Testing an e-commerce website by simulating thousands of users checking out simultaneously.

Best practices:

Definition:

A security testing method used to identify vulnerabilities in a system by simulating an attack.

Example:

Testing a web application for SQL injection vulnerabilities by attempting unauthorized data access.

Best practices:

Definition:

A testing technique to determine how a system performs in terms of responsiveness and stability under various conditions.

Example:

Measuring how quickly a web page loads under different levels of user traffic.

Best practices:

Definition:

Testing existing functionality to ensure that recent code changes have not introduced new bugs.

Example:

Running a suite of tests after a bug fix to confirm that other functionalities remain intact.

Best practices:

Definition:

A preliminary test to check the basic functionality of an application before conducting more detailed testing.

Example:

After a new build, verifying that the application starts, navigates between screens, and performs basic functions without crashing.

Best practices:

Definition:

Testing how a system behaves under extreme conditions, often beyond its normal operational capacity.

Example:

Overloading a web server to determine its breaking point and recovery time.

Best practices:

Definition:

A set of conditions or variables used to determine if a system under test meets requirements.

Example:

A test case for a login feature might include inputs for valid and invalid usernames and passwords.

Best practices:

Definition:

The process of creating, managing, and maintaining data necessary for software testing.

Example:

Generating realistic test data for validating user workflows in an application.

Best practices:

Definition:

A configured environment used for testing, including hardware, software, and network settings that mimic production as closely as possible.

Example:

Setting up a staging server with the same configurations as the live server to test new features.

Best practices:

Definition:

Testing individual components of software in isolation to ensure they work as expected.

Example:

Testing a single function in a codebase, like a calculation method, to ensure it returns the correct result.

Best practices:

Definition:

Testing how easily end-users can interact with a software product, focusing on the user experience.

Example:

Observing users as they navigate an app to identify areas of confusion or difficulty.

Best practices:

Definition:

The final phase of testing where end-users validate the functionality before the system goes live.

Example:

A group of end-users testing a new feature to confirm it meets their needs and expectations.

Best practices:

Definition:

An automated process that scans software for known security vulnerabilities.

Example:

Running a vulnerability scan to identify outdated libraries that may pose security risks.

Best practices:

Definition:

Testing based on an understanding of the internal structure, logic, and design of the application.

Example:

Testing individual code paths in a function to ensure they execute correctly under different conditions.

Best practices: