Posts Tagged ‘Gray Box Testing’

Hi guys,

I found these some important concepts for any tester to know. So sharing with you all –

Black Box Testing – These tests are based on requirements and functionality, not based on any knowledge of internal design or code.
Tester has to test just the input and expected/actual output.
Synonyms for Black-box include: behavioral, functional, opaque-box, and closed-box.

White Box Testing – These are based on knowledge of the internal logic of an application’s code. Tests are based on coverage of code statements, branches, paths, and conditions. For conducting these tests, tester should have the knowledge and access to internal code, algorithms and software designs.
Synonyms for white-box include: structural, glass-box and clear-box.

Gray Box Testing – It is a software testing technique that uses a combination of black box testing and white box testing. Gray box testing is not black box testing, because the tester does know some of the internal workings of the software under test. In gray box testing, the tester uses the internal code, algorithms for creating the Test Cases, one takes a black box approach in applying inputs to the software under test and observing the outputs.

Gray box testing is a powerful idea. The concept is simple; if one knows something about how the product works on the inside, one can test it better, even from the outside. Gray box testing is not to be confused with white box testing; i.e. a testing approach that attempts to cover the internals of the product in detail. Gray box testing is a test strategy based partly on internals. The testing approach is known as gray box testing, when one does have some knowledge, but not the full knowledge of the internals of the product one is testing.



Read Full Post »