A testing approach that determines inputs and expected outputs from the specification alone, without looking at the internal structure of the program. Its techniques include equivalence partitioning, boundary value analysis and decision tables.
Japanese name: ブラックボックステスト
Black-box testing appears in 1 practice question across 1 topic, including Software Development and Project Management.
Answer: A. Without looking at the internal structure of the program, inputs and expected outputs are determined from the specification to check that it works correctly
Black-box testing treats the test object as a box whose contents cannot be seen and creates test cases from the specification alone; its techniques include equivalence partitioning, boundary value analysis, cause-effect graphs and decision tables. It is good at finding functions that are in the specification but not implemented, but it cannot tell whether a particular path in the implementation has been exercised. Creating tests based on internal structure and using coverage as the criterion is white-box testing. The final confirmation by users is acceptance testing, which is the name of a test level.
Black-box testing treats the test object as a box whose contents cannot be seen and creates test cases from the specification alone; its techniques include equivalence partitioning, boundary value analysis, cause-effect graphs and decision tables.
Which describes black-box testing?As an Amazon Associate I earn from qualifying purchases.
Equivalence partitioning Boundary value analysis White-box testing Agile development Branch coverage CI/CD (continuous integration and continuous delivery) Critical path method (CPM) Earned value management (EVM) Scrum SLA (service level agreement)