Different types of Testing




Properties Black Box Grey Box White Box
Process Gives input to the system and checks the output of the system without bothering to know to how the output is generated (Checks Functionality) Tests the output as well as process carried out to generate the output. Gives the input to the system and checks how the system processes the input to generate output. (Checks system performance)
Based on External Specification Knowledge of the algorithm, interval states, architecture or other high level descriptions of program behavior Detailed design and knowledge of the internal logic of an application’s code
Access to/Knowledge of structure Tester has no access/Knowledge Tester has limited access/Knowledge which includes documentation of data structures and algorithm used. Tester has complete access/Knowledge
Performed by End users (User acceptance testing), testers and developers End users (User acceptance testing), testers and developers Testers and developers
Resources and Time usage Least exhaustive and time consuming Partly exhaustive and time consuming Most exhaustive and time Consuming
Algorithm Testing Not Suited Not Suited Suited
Suitable for Functional or business/ domain testing Functional or business/ domain testing but in more depth All
Testing of data domain and internal boundaries Not possible. Tests only by trial and error Possible if known Must be done
Opacity of Testing Opaque Translucent Transparent
Programming Knowledge Not Required Some idea is required Required
Implementation Knowledge Not Required Some idea is required Required
Tools Required Automated scanning tools and manual penetration testing Automated scanning tools and manual penetration testing Specialized knowledge and tools like debugger and source code analysis
Levels to which it can be applied Unit, integration, system and acceptance Unit, integration, system and acceptance Unit, integration and system
Granularity Low Medium High

 

Share This:
Facebooktwittergoogle_plusredditpinterestlinkedintumblr