ITPEC FE Morning October 2018 Question 49
ITPEC FE Morning October 2018 — Question 49 of 80
Black Box Testing — testing based only on input/output without examining internal code.
Black box testing treats the program as an opaque box: test cases are derived from specifications, not source code.
Why (a) is correct:
- Since internal code is never examined, redundant code cannot be detected — this is a known limitation of black box testing
Why not others:
- (b) — test data volume growing with branch/module count relates to white box testing, where internal paths drive test design
- (c) — verifying whether "the necessary part is executed" requires inspecting internal structure → white box
- (d) — instruction and branch coverage rates are white box metrics (statement coverage, branch coverage)
Key rule: Black box = specification-based (equivalence partitioning, boundary value analysis). White box = structure-based (statement/branch/path coverage).
AI-generated — may contain errors
The original exam layout is preserved in the image so diagrams, formulas, tables, and code remain accurate.
This question comes from an official ITPEC past paper. ITPEC Practice is an independent study tool and is not affiliated with ITPEC. See the official FE past-paper collection or Report an issue.