Abstract

                        Black Box Testing is used when code of the module is not available. Black box testing treats the system as a “black-box”, so it doesn’t explicitly use knowledge of the internal structure or code. Or in other words the Test engineer need not know the internal working of the “Black box” or application. In such situations appropriate priorities can be given to different test cases, so that the quality of software is not compromised, if testing is to be stopped prematurely. This paper briefly sketches a general strategy for black-box testing, different methods involved and the advantages and disadvantages associated with them. The study of this paper would be beneficial to both researchers and practitioners alike in having an understanding of black box testing.

Keywords:   Black-Box Testing, White-Box Testing, Equivalence Class Portioning, Boundary Value Analysis, Decision Table.