Black box Testing
|
White box Testing
|
Software
testing method performed without the knowledge of internal code or structure
|
Software
testing method with the knowledge of internal code or structure
|
It
is carried out by software testers
|
It
is carried out by developers
|
Implementation
knowledge of the software is not required
|
Implementation
knowledge of the software is required
|
Programming
language such knowledge C,C++, Java is not required
|
Programming
language knowledge such as C, C++, Java is required
|
It
is performed at higher levels of testing
E.g.
System, User acceptance testing
|
It
is performed at lower levels of testing
E.g.
Unit testing, Integration testing
|
Black
box testing means functional or external testing
|
White
box testing means structural or interior testing
|
Basic
for test cases is Requirement Specification document
|
Basic
for test cases is Detailed Design document
|
It
mainly focuses on the functionality of the software or application
|
It
mainly focuses on the code or program of the software
|
It
focuses on What software does?
|
It focuses
on How software works or performs?
|
The
objective of testing is what the module or software is intended to do?
|
The
objective of testing is How module or software works?
|
It
only covers the testing of input values and desired output values
|
It
covers the actual calculation logic used to calculate the desired output
values
|
Showing posts with label Top 10 differences between black box and white box Testing. Show all posts
Showing posts with label Top 10 differences between black box and white box Testing. Show all posts
Sunday, 20 September 2015
Top 10 differences between Black box and White box Testing
Subscribe to:
Posts (Atom)