Software Development and Project Management
Which describes black-box testing?
- AWithout looking at the internal structure of the program, inputs and expected outputs are determined from the specification to check that it works correctly
- BTest cases are created based on the internal structure of the program, using whether statements and branches have been executed as the criterion
- CUsers finally confirm, in their actual business environment, that the system can be used as required
Show answer and explanation
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.
- A. Correct. Test cases are created from the specification alone and checked through inputs and outputs.
- B. This describes white-box testing.
- C. This describes acceptance testing, which is a test level rather than a way of designing test cases.
Continue: 9 more Software Development and Project Management questions