Skip to main content

Difference between Black Box Testing and White Box Testing


          Black Box Testing
                White Box Testing
1
In this testing knowledge of programming is not necessarily essential.
In this form of testing knowledge of programming is must means it is essential.
2
Normally independent software testers are responsible for doing Black Box Testing.
Normally software developers are responsible for doing White Box Testing.
3
In this form of testing Knowledge of implementation is not required.
In this form of testing Implementation knowledge is required.
4
In Black Box Testing, testers may or may not be technically sound.
Normally software developers are involved in this testing, but if it is performed by software testers, then testers should be technically sound.
5
In this sort of testing testers mainly focuses on the functionality of the system.
In this sort of testing developers mainly focuses on the structure means program/code of the system.
6
This testing is done by testers.
This testing is mostly done by developers.
7
This type of testing always focuses on what is performing/ carried out.
This type of testing always focuses on how it is performing/ carried out.
8
In Black Box Testing no knowledge regarding internal logic of code is needed means no need of programming is necessary.
In White Box Testing knowledge regarding internal logic of code is needed means need of programming is mandatory.
9
Other names of this testing include means synonyms of black box testing are testing regarding functionality means Functional testing, Behavioral testing, and Opaque-box/ Closed-box testing that is the reason why in this testing no knowledge of programming is needed.
Other names of this testing include means synonyms of white box testing are testing regarding code means Structural testing, Glass-box/ Clear-box testing, Open-box testing/ Transparent-box testing, Logic-driven testing and Path-oriented testing that is the reason why in this testing knowledge of programming is needed.
10
Black box testing means functional test or external test.
White box testing means structural test or interior test.


Labels:

Comments

Post a Comment

Popular posts from this blog

Difference Between Verification And Validation With Example?

Verification and Validation example is also given just below to this table.                Verification               Validation 1. Verification is a static practice of verifying documents, design, code and program. 1. Validation is a dynamic mechanism of validating and testing the actual product. 2. It does not involve executing the code. 2. It always involves executing the code. 3. It is human based checking of documents and files. 3. It is computer based execution of program. 4.  Verification uses methods like inspections, reviews, walkthroughs, and Desk-checking etc. 4.  Validation uses methods like black box (functional)  testing, gray box testing, and white box (structural) testing etc. 5.  Verification  is to check whether the softwar...
66 comments
Read more

Endurance Testing with Example, Meaning and Definition

Endurance Testing is a type of Performance Testing which is usually used to determine how much a system can sustain the continuous expected load. During the period of Endurance Testing memory utilization is always monitored to detect any potential leaks. In short we can say that judging/studying the memory leak of a server under the period of stability is known as Endurance Testing . Due to its judgment and study on memory leak that is the reason why Endurance Testing is also known by the name Soak Testing . As you know in Endurance Testing memory utilization is monitored so it very important for us to know about memory leak means what it is all about. When memory allocated to objects are not being freed by the system/application than definitely the memory leak occurs. Endurance Testing Example – Real Time Below is given the real time example of Endurance Testing and hope after seen these real time example your knowledge on Endurance Testing should definitely b...
Post a Comment
Read more

Regression Testing with Example and Strategies

Regression Testing is done to ensure that fixed bug does not affect the remaining functionality of the modules and also the functionality of the same module. In short you can say regression testing  is always done to verify that modified code does not break the existing functionality of the application and works within the requirements of the system. Regression Testing Example  For Example there are three Modules in the Project named Admin Module, Personal Information, and Employment Module and suppose bug occurs in the Admin Module like on Admin Module existing User is not able to login with valid login credentials so this is the bug.  Now Testing team sends the above - mentioned Bug to the Development team to fix it and when development team fixes the Bug and hand over to Testing team than testing team checks that fixed bug does not affect the remaining functionality of the other modules (Admin, PI, Employment) and also the functionality of ...
31 comments
Read more