What program testing types can be thought about?

Sponsored Links:

Black box testing - This type of check does not need any knowledge of internal design or coding. These tests are based on the requirements and functionality.
White Box Testing - This check is based on knowledge of the internal logic of an application code in particular. The check is conducted based on coverage of code statements, paths, conditions.

Unit Testing - the "scale" micro "test, which is mainly used to check the particular functions or code modules. This is normally completed by the programmer, and not by testers, but requires detailed knowledge internal program design and code. Can not easily completed unless the application has a well-designed architecture with tight code; this type may need developing check driver modules or check harnesses.





Functional Testing - This is a check commonly used black-box-directed to verify the functional requirements of an application, this type of testing should be performed by testers.

Proof of Sanity or Smoke testing - This type of testing is completed initially to decide whether a new program version is walking well to accept that evidence of a major hard work. For example, if the new program systems failure in every 5 minutes or corrupting databases, the program may not be in the condition of a "sound" to over out new tests in its current state.

Integration Check - This check is the combination of the "parts" of an application to decide if they work together properly. The 'parts' can be code modules, individual applications, client and server applications on a network, etc. This type of testing is relevant to client / server and distributed systems.

Incremental Integration Testing - This is continuing evidence of a request when a new functionality is added to the existing checks the application functionality by verifying whether it works separately before all parts of the program have been done In this type shall be checked whether the introduction of check drivers or not, this is completed by programmers or testers.

Check Process - This is a kind of black box type testing that is based on overall requirements specifications, covers all parts of a combined process.

Regression Testing - This check is the application again after all the revisions or modifications are made to the program. This is completed mainly at the finish of the life cycle of program development. Highly automated testing tools used for these tests.

End-to-end testing - This is similar to process testing, this involves testing of a complete application environment such as interaction with a database, using the communications network, or interact with other hardware , applications and so on.

UAT (User Acceptance Testing) - This check comes in the final stage and mostly completed on the specifications of the finish user or customer.

Compatibility testing - testing how well the program performs in a particular hardware, program, operating process, network, etc.

Usability Testing - This check is performed to verify the user friendliness of the application. This depends on the targeted finish user or customer provided. User interviews, surveys, video recording of user sessions and other techniques can be used. Developers and testers are usually not appropriate as usability testers.

Comparison testing - This is not to weigh the benefits of the program and the weakness with another competing product. Mutation testing - This is another process for determining whether a set of check information or check cases is useful, regarding the changes in the code or number of errors and retest the original check information or cases to decide if detected the 'mistakes'.