Software Testing Approaches: A Comprehensive Guide | SSCP Exam

Software Testing Approaches

Prev Question Next Question

Question

Which of the following statements pertaining to software testing approaches is correct?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

C.

A bottom-up approach to testing begins testing of atomic units, such as programs or modules, and works upwards until a complete system testing has taken place.

It allows errors in critical modules to be found early.

A top-down approach allows for early detection of interface errors and raises confidence in the system, as programmers and users actually see a working system.

White box testing is predicated on a close examination of procedural detail.

Black box testing examines some aspect of the system with little regard for the internal logical structure of the software.

Source: Information Systems Audit and Control Association, Certified Information Systems Auditor 2002 review manual, Chapter 6: Business Application System Development, Acquisition, Implementation and Maintenance (page 300)

Top Down Testing: An approach to integration testing where the component at the top of the component hierarchy is tested first, with lower level components being simulated by stubs.

Tested components are then used to test lower level components.

The process is repeated until the lowest level components have been tested.

Bottom Up Testing: An approach to integration testing where the lowest level components are tested first, then used to facilitate the testing of higher level components.

The process is repeated until the component at the top of the hierarchy is tested.

Black Box Testing: Testing based on an analysis of the specification of a piece of software without reference to its internal workings.

The goal is to test how well the component conforms to the published requirements for the component.

A. A bottom-up approach allows interface errors to be detected earlier. In a bottom-up testing approach, individual modules of the software are tested first, and then they are combined to test the larger software components. This approach allows interface errors to be detected earlier because the individual modules are tested first and their interface with other modules can be tested during the integration phase.

B. A top-down approach allows errors in critical modules to be detected earlier. In a top-down testing approach, the software is tested from the highest level modules down to the lowest level modules. This approach allows errors in critical modules to be detected earlier because the higher level modules are tested first and if they are faulty, then it will be identified at an early stage.

C. The test plan and results should be retained as part of the system's permanent documentation. The test plan and results should be retained as part of the system's permanent documentation for several reasons. First, it helps to ensure that testing is repeatable and consistent across different environments. Second, it provides a historical record of the testing process and results, which can be useful for future testing or for addressing any issues that arise. Finally, it is often required as part of regulatory or compliance standards.

D. Black box testing is predicated on a close examination of procedural detail. Black box testing is a testing approach where the software is tested without any knowledge of the internal workings of the software. The tester only interacts with the software's inputs and outputs, and does not have any knowledge of the internal code. Therefore, black box testing is not predicated on a close examination of procedural detail, but rather on the understanding of the software's behavior and its specifications.

In summary, the correct statement is: A. A bottom-up approach allows interface errors to be detected earlier.