Black box testing
|
Grey box testing
|
White box testing
|
The internal working of an application is not required to be known.
|
Limited or partial knowledge
|
Full knowledge of the application
|
Performed by end users and also by testers and developers
|
Performed by end users and also by testers and developers
|
Performed by developers
|
This is the least time consuming and exhaustive
|
partly time-consuming and exhaustive
|
Most of the time consuming and exhaustive
|
Testing is based on external expectations-internal behaviour of the application is unknown
|
Testing is done on the basis of high-level database diagrams and data flow diagram
|
Internal working are fully known and the tester can design test data accordingly
|
This can only be done by trial and error method
|
data domains and internal boundaries can be tested, if they know
|
data domains and internal boundaries can be tested, if they know
|
Not suited to algorithm testing
|
Not suited to algorithm testing
|
suited for algorithm testing
|
Testing output, Without knowing the process that led to it
|
Testing code and output
|
Testing the code
|
Advantages and disadvantages of white and black box methods
Black box testing
|
White box testing
|
|
benefits
|
*fits big code.
*There is no need to access the code.
* No need to be a developer or programmer
* A clear separation between the user and the developer
|
*Knowing the code makes better planning of testing
*Maximum coverage of test
|
disadvantage
|
* Accuracy test damaged due to the poor knowledge that the examiner have
* Low coverage. The testing only the black box.
|
*Sometimes there is no need for going down so deeply
*there is no need to qualifications people.
|
No comments:
Post a Comment