System testing black box type testing that is based on overall requirement specifications; covers all combined parts of a system. End-to-end testing similar to system testing; the ‘macro’ end of the test scale; involves testing of a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network [...]
Archive for May, 2011
Posted in Uncategorized on May 15, 2011 | Leave a Comment »
Functional testing
Posted in Uncategorized on May 15, 2011 | Leave a Comment »
Functional testing black-box type testing geared to functional requirements of an application; this type of testing should be done by testers. This doesn’t mean that the programmers shouldn’t check that their code works before releasing it (which of course applies to any stage of testing.)
Integration testing
Posted in Uncategorized on May 15, 2011 | Leave a Comment »
Integration testing testing of combined parts of an application to determine if they function together correctly. The ‘parts’ can be code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems.
Incremental integration testing
Posted in Uncategorized on May 15, 2011 | Leave a Comment »
Incremental integration testing continuous testing of an application as new functionality is added; requires that various aspects of an application’s functionality be independent enough to work separately before all parts of the program are completed, or that test drivers be developed as needed; done by programmers or by testers.
Unit testing
Posted in Uncategorized on May 15, 2011 | Leave a Comment »
Unit testing the most ‘micro’ scale of testing; to test particular functions or code modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. Not always easily done unless the application has a well-designed architecture with tight code; may require developing test driver [...]
White box testing
Posted in Uncategorized on May 15, 2011 | Leave a Comment »
White box testing based on knowledge of the internal logic of an application’s code. Tests are based on coverage of code statements, branches, paths, conditions.
Black box testing
Posted in Uncategorized on May 15, 2011 | Leave a Comment »
Black box testing not based on any knowledge of internal design or code. Tests are based on requirements and functionality