White Box Vs Black Box Testing
White Box Testing
- The application is tested at the source code level.
- Testing for loops, if-else statements etc., are part of white-box testing.
- Done by testers and developers.
Black Box Testing
- It tests how the software behaves as a whole and analyzes client requirement specifications.
- Usually done with those who have no knowledge of the actual code.
- Done by end-users, testers and developers.
Black Box Testing: It verifies that the requirements are met and examines the functionality of an application.
White Box Testing: High granularity.
Black Box Testing: Low granularity when compared with white box testing.
Black Box Testing: It is also known as closed box, functional testing.
Black Box Testing: This is done by end-users, testers and developers.
Black Box Testing: It is suited only for business domain testing.
Black Box Testing: Algorithm testing is not considered suitable for black box testing.
·Basis for Test Cases
Black Box Testing: The test case is built around requirements and specifications.
Black Box Testing: For performing black box testing, programming skills are not required. It is done with those who usually have no knowledge of the actual code.
Black Box Testing: Maintenance is easier.
Black Box Testing: It’s difficult to design test cases in black box testing.
Black Box Testing: Takes less time when compared with White Box.
Black Box Testing: It is applied during the later stages of testing.
Black Box Testing: It attempts to find the following errors:
- initialization errors
- incorrect functions error
- database access errors
- Unit testing, and
- Integration Testing.
- Acceptance Testing, and
- System Testing
Black Box Testing: Implementation Knowledge is not necessary for black box testing.
·Selection of Test Cases
Black Box Testing: It is based on the selection of sample test cases.
Black Box Testing: Tests how the software behaves as a whole, so internal structure is not known.
- Control flow testing
- Data flow testing
- Branch testing
- Path testing
- Statement coverage
- Decision coverage
Black Box Testing techniques:
- Decision table testing
- All-pairs testing
- Equivalence partitioning
- Boundary value analysis
- Cause–effect graph
- Error guessing
Find our Selenium 3.0 Training Online Classroom training classes in top cities:
|Selenium 3.0 Training||12 Jan -10 Feb 2019, Weekend batch||Your City||View Details|
|Selenium 3.0 Training||2 Mar -31 Mar 2019, Weekend batch||Your City||View Details|
Recommended articles for you
The Scope Of Software TestingArticle
Testing Your Way To Success: How To Build A Career In Softwa...Article
How to Test your Website?Article