Discover published sets by community

Purpose: To validate each individual unit of the software performs as designed. Applied: Typically during the development phase.

Purpose: To check the data flow and interaction between integrated modules. Applied: After unit testing, before system testing.

Purpose: To ensure that the application is usable by people with disabilities. Applied: Ideally throughout the development process.

Purpose: To identify all possible issues before releasing the product to real users. Applied: At the end of the development process, before beta testing.

Purpose: To determine the behavior of the system at peak load times. Applied: Before the production to evaluate performance.

Purpose: To check the software behavior under different regional settings. Applied: After the system testing, before the release in a particular locale.

Purpose: To confirm that recent changes or additions haven't broken any existing functionality. Applied: After any change or bug fix.

Purpose: To discover defects by exploring the app without predefined tests. Applied: Usually in the early stages of testing or when there is no detailed specification.

Purpose: To ensure the application works as expected on different devices, OS versions, and screen sizes. Applied: During the later stages of development.

Purpose: To get real user feedback from target audience. Applied: After alpha testing, before the final product release.

Purpose: To evaluate the application's user interface and user experience. Applied: Throughout the development lifecycle.

Purpose: Validate the complete and fully integrated software system. Applied: After integration testing.

Purpose: To determine the responsiveness, reliability, and scalability under a given workload. Applied: After the system is deemed stable.

Purpose: To verify the software meets business requirements. Applied: Before the product release to market.