Recovery Testing

Alpha Testing

Alpha Testing is a type of acceptance testing done in the presence of customer at the developer's site. The customer performs the test in an environment similar to the actual working environment for the software.

Beta Testing

Type of acceptance testing done by the customer in a live application of the software at the end user's site in an environment not controlled by the developer.

Ad hoc Testing

Ad hoc testing is testing in which the focus is not only on planned test case execution, but also on unplanned testing.

Sanity Testing

Sanity Testing is a narrow regression test that focuses on one or a few areas of functionality. Usually unscripted, it is used to determine if a small section of the application is still working after a minor change has been made. One has to verify whether requirements are met or not, checking all basic functionality are working properly.

Smoke Testing

Smoke Testing is testing all areas of the application without getting into too many details. It is scripted, either using a written set of tests or automated tests. Smoke testing is conducted to ensure whether the most crucial functions of a program are working. It is designed to touch every part of the application in a cursory way.

End To End Testing

Testing the application starting from scratch to the end after integrating all the modules.

Monkey Testing

Monkey testing simulates the behaviour of monkey jumping from one tree to another in search of a better fruit assuming that all fruits are similar. It is the automated testing done randomly without typical user specifications. The use of monkey testing is to simulate how customers will use the software in real time.

Retesting

After any change is made to the application, testing only the particular module and not the entire application is called retesting.

Regression Testing

Testing done to ensure that enhancements or defect fixes made to the software works properly and does not affect existing functionality. Compared to retesting, regression testing is testing the entire module to ensure that changes made in particular module do not affect previously working modules.

Compatibility Testing

Testing conducted on the application to evaluate the application's compatibility with the computing environment.

Positive Testing

Positive testing is testing done to verify known test conditions.

Negative Testing

Negative testing is testing the application for improper conditions and invalid inputs.

Grey Box Testing

Grey Box testing refers to the technique of testing a system with limited knowledge of the internals of the system. It involves having access to internal data structures and algorithms for the purpose of designing test cases, but testing at the user or black box level.