Black‐Box Testing
Thomas J. Ostrand
Abstract
Thomas J. Ostrand
Abstract
Abstract Black‐box testing of software is any method of generating testcases that is independent of the software's internal structure. Since black‐box testing is always based, either directly or indirectly, on the software's specification, it is also called specification‐based testing . The simplest concept of black‐box testing is that the tester examines the program's specification and chooses test cases that exercise all its externally visible functions. In selecting these black‐box tests, the tester considers the program's purpose, the sets of possible inputs and expected outputs, possible ways in which the program might fail, and possible uses of the program. The art of testing consists of approaching each of these sources of tests in an organized way, and in using whichever sources are most appropriate for the particular software and its intended use. Various specific types of black‐box testing are model‐based testing , scenario‐based testing , data‐based testing , statistical testing , and (a special case of the latter two approaches) random testing , all of these types are discussed. Other terms sometimes used as synonyms for black‐box testing are functional testing and behavioral testing . The rationale for these usages is that black‐box tests are based on the function or behavior to be performed by the software, not its structure or design. However, because of the multiple meanings possible for function , these terms are potentially misleading.
OpenAlex reports 8 citations for this work. Citation counts describe recorded attention and do not establish research quality.
A contribution statement is not available in the OpenAlex record.
Method details are not available in the OpenAlex metadata.
Findings are not separately available in the OpenAlex metadata.
Limitations are not available in the OpenAlex metadata.
Application details are not available in the OpenAlex metadata.
Abstract Black‐box testing of software is any method of generating testcases that is independent of the software's internal structure. Since black‐box testing is always based, either directly or indirectly, on the software's specification, it is also called specification‐based testing . The simplest concept of black‐box testing is that the tester examines the program's specification and chooses test cases that exercise all its externally visible functions. In selecting these black‐box tests, the tester considers the program's purpose, the sets of possible inputs and expected outputs, possible ways in which the program might fail, and possible uses of the program. The art of testing consists of approaching each of these sources of tests in an organized way, and in using whichever sources are most appropriate for the particular software and its intended use. Various specific types of black‐box testing are model‐based testing , scenario‐based testing , data‐based testing , statistical testing , and (a special case of the latter two approaches) random testing , all of these types are discussed. Other terms sometimes used as synonyms for black‐box testing are functional testing and behavioral testing . The rationale for these usages is that black‐box tests are based on the function or behavior to be performed by the software, not its structure or design. However, because of the multiple meanings possible for function , these terms are potentially misleading.
Key concepts: White-box testing, Black-box testing, Black box, Non-regression testing, Keyword-driven testing, Manual testing, Orthogonal array testing, Computer science