Pete, a developer, writes an application. Jane, the security analyst, knows some things about the overall application but does not have all the details. Jane needs to
review the software before it is released to production. Which of the following reviews should Jane conduct?

A.
Gray Box Testing

B.
Black Box Testing

C.
Business Impact Analysis

D.
White Box Testing

Explanation:
Gray box testing, also called gray box analysis, is a strategy for software debugging in which the tester has limited knowledge of the internal details of the program.
A gray box is a device, program or system whose workings are partially understood. Gray box testing can be contrasted with black box testing, a scenario in which
the tester has no knowledge or access to the internal workings of a program, or white box testing, a scenario in which the internal particulars are fully known. Gray
box testing is commonly used in penetration tests.
Gray box testing is considered to be non-intrusive and unbiased because it does not require that the tester have access to the source code. With respect to internal
processes, gray box testing treats a program as a black box that must be analyzed from the outside. During a gray box test, the person may know how the system
components interact but not have detailed knowledge about internal program functions and operation. A clear distinction exists between the developer and the
tester, thereby minimizing the risk of personnel conflicts.
Incorrect Answers:
B: Black-box testing is a method of software testing that examines the functionality of an application without peering into its internal structures or workings. This
method of test can be applied to virtually every level of software testing: unit, integration, system and acceptance. It typically comprises most if not all higher level
testing, but can also dominate unit testing as well. Specific knowledge of the application’s code/internal structure and programming knowledge in general is not
required. The tester is aware of what the software is supposed to do but is not aware of how it does it. For instance, the tester is aware that a particular input
returns a certain, invariable output but is not aware of how the software produces the output in the first place. In this question, the tester has some knowledge of the
application. Therefore, this answer is incorrect.
C: A Business Impact Analysis is the analysis of the impact an event will have on the business. As an example in terms of IT, a Business Impact Analysis could
describe the effect of a server failure. A Business Impact Analysis is not used to describe the testing of an application.
Therefore, this answer is incorrect.
D: White-box testing (also known as clear box testing, glass box testing, transparent box testing, and structural testing) is a method of testing software that tests
internal structures or workings of an application, as opposed to its functionality (i.e. black-box testing). In white-box testing an internal perspective of the system, as
well as programming skills, are used to design test cases. The tester chooses inputs to exercise paths through the code and determine the appropriate outputs.
This is analogous to testing nodes in a circuit, e.g. in-circuit testing (ICT). White-box testing can be applied at the unit, integration and system levels of the software
testing process. Although traditional testers tended to think of white-box testing as being done at the unit level, it is used for integration and system testing more
frequently today. It can test paths within a unit, paths between units during integration, and between subsystems during a systemlevel test.
In this question, the tester has some knowledge of the application but not the detailed knowledge required for a white-box test. Therefore, this answer is incorrect.

http://searchsoftwarequality.techtarget.com/definition/gray-box http://en.wikipedia.org/wiki/Black-box_testing
http://en.wikipedia.org/wiki/White-box_testing