- Black-Box Testing
- White-Box Testing
- Grey-Box Testing
|
Black-Box
Testing
|
White-Box
Testing
|
Grey-Box
Testing
|
|---|---|---|
|
The internal
workings of an application need not be known.
|
Tester has
full knowledge of the internal workings of the application.
|
The tester
has limited knowledge of the internal workings of the application.
|
|
Also known
as closed-box testing, data-driven testing, or functional testing.
|
Also known
as clear-box testing, structural testing, or code-based testing.
|
Also known
as translucent testing, as the tester has limited knowledge of the
insides of the application.
|
|
Performed by
end-users and also by testers and developers.
|
Normally
done by testers and developers.
|
Performed by
end-users and also by testers and developers.
|
|
Testing is
based on external expectations - Internal behavior of the
application is unknown.
|
Internal
workings are fully known and the tester can design test data
accordingly.
|
Testing is
done on the basis of high-level database diagrams and data flow
diagrams.
|
|
It is
exhaustive and the least time-consuming.
|
The most
exhaustive and time-consuming type of testing.
|
Partly
time-consuming and exhaustive.
|
|
Not suited
for algorithm testing.
|
Suited for
algorithm testing.
|
Not suited
for algorithm testing.
|
|
This can
only be done by trial-and-error method.
|
Data domains
and internal boundaries can be better tested.
|
Data domains
and internal boundaries can be tested, if known.
|
No comments:
Post a Comment