It's a relatively new term and basically just another "label" for a "type" of testing. An example would be where I'm doing a test that takes a number for input...say your street address...but since I know that the parsing has a ton of code to handle special character like a "+", I try it and every other one I can think of.
Gray box testing is not black or white box. It is gray box, which is why it is not called black or white. [img]/images/graemlins/smile.gif[/img]
Gray box testing - age of? I have known it for at least 32 years despite what wiki says. [img]/images/graemlins/smile.gif[/img]
1. Blackbox testing is functional or non-functional requirement-based. One is testing to show the application-under-test (AUT) functions as required AND show where the AUT does not function properly.
2. Whitebox testing is code implementation-based. One is testing to ensure the code is implemented properly AND where it is not implemented properly.
3. Graybox testing is design-based. System testing includes the concepts of gray box testing when one is addressing or testing the stated or implied design limits. Here is a Link to an example of gray box testing within the performance domain. In this case initial “testing” was gray box testing of the Verification variety. The design limits were being challenged. Subsequent gray box design-based testing of the Validation variety, conducted in the system testing phase proved that the device could not operate at the implied design-limits.
<font color="blue">fahad, is this an interview question? If so, we will have this topic moved to the Software Testing Interview Questions forum toward the bottom of the main page.</font>
Did you mean to say, <font color="blue">"Hit it to know another opinion in addition to those expressed above and at the Google references about black or white..."</font> from one with years experience amounting to less than 1/3 the age of the term "gray box", a term that precedes my IT life?