What is white-box Integration Testing and its differences
between Black box-Integration testing?
Answers were Sorted based on User's Feedback
Answer / sushree sangeeta das
white box testing is based on internal logic of an
application.Test are based on coverage of code
statement,branches,paths and condition.But in black box
testing,it is not based on any knowledge of internal design
or code.In black box testing tester can be non technical.
Is This Answer Correct ? | 15 Yes | 2 No |
Answer / viji
white box texting:
1.It is structural testing
2.coding and logic is needed here
3.Developers do the coding
4.otherwise called open source testing or clearbox testing
Divided into 3 coverage:Statement,Conditional,Decision
Black box testing:
1.it is functional testing
2.No Coding or logic is needed.
3.SRS is required
Combination of white box and black box is called grey box
testing.
Divided into Equilanence partioning,Boundary value,Error
guessing
Is This Answer Correct ? | 6 Yes | 2 No |
Answer / renu
white box testing is applicable at integration level of
testing for testing the units(small piece of code) during
integration .
Blackbox testing is also applicable at integration level of
testing.
I dont the exact difference between those two.
Is This Answer Correct ? | 4 Yes | 2 No |
Answer / bharti
White box testing is code based whereas black box testing
in requirements based.
Is This Answer Correct ? | 3 Yes | 1 No |
Actually there is no concept of White-box integration
testing and black box- integration testing but we can keep
this in this scenario if it has to be explain ...like below
Integration testing techniques are
1. Top-Down
2. Bottom-up
3. sandwich / hybrid
and in integration we club one module to other module and
check the connectivity which is a functional technique, and
sometime if one module is ready and other module is not
ready to move to third module we take help of developers for
developing a small piece of code which we call it as stub
and driver. Stub and driver is a small link that connected
from one module to other module so it is called white box.
SInce we need both white box technique and black box
technique it is called Grey Box testing
Integration testing is a grey box.
Since we are using stub and drivers in integration we can
call it as white-box integration testing and
since we are using black box technique in integration we can
call it as black box integration testing.
Hope this will help you to understand
Is This Answer Correct ? | 3 Yes | 1 No |
Answer / nishtha
white box integration testing is the testing in which two
or more modules or units combine together and get tested
while black box testing is the type of testing in which no
knowledge of internal logics and code is required.
only concern abt functionality of software focused on the
testing for requirements of work product, so in white box
integration testing means two or more functions are combine
together to get tested against the functional
specifications in order to check for normal and abnormal
behavior of the system.
Is This Answer Correct ? | 0 Yes | 1 No |
what is mean by configuration managaement.. explain with example ?
Name three types of tests that should NOT be automated.
what is difference between regression & retesting?
.In languages testing, what is the fixed part and changing part?
what is Negative testing and what It?s Purpose?
what is the call-pair testing? there is any length for Test case?
Hi Friends, I have completed 3 rounds of an Interview with HR discussion also and got Offer letter from Cognizant, but after in 30 min they send one more email like Offer is on Hold, and its not valid... Could you please guide me any one , Can i expect Offer again from Cognizant or Can i drop the hopes ?.
What do you do in this application?
Here is the scenario. We have web app. in ASP.NET, server is IIS and database is SQL server2005. The application is used in healthcare industry. I am going to get realtime data from healthcare company to test. I need to perform back end testing. If someone can help me understand how i can start back end testing.
Can any1 tell me suppose u r doing manual testing on unix platform with Shell Script, then how it is done? How u r implementing it & what is the use of Shell scripting on Manual Testing?
What if an organization is growing so fast that fixed testing processes are impossible? What to do in such situations?
What is the difference between test case, test suite, test script, test scenario & test plan?