Black-Box Test Planning
Black box testing, which is also called functional or system testing, ignores the internals of the program and instead focuses on the inputs and the expected results of the program as defined by the requirements. The tester treats the program as a “black box”; the program implementation that generates the program output is unknown. The tester identifies the expected program output from the requirements and can compare the actual output with the expected output.
TASK: Black-Box Test Plan
We are completing the black box test plan prior to the design because, as discussed in the testing lecture earlier this semester, the black box tests should only be based on your requirements and should work independent of design. You currently know the program input and output based on the requirements you documented. How exactly the user will interact with the system/program will come out of the design; you can be general with this for now. The Actual Results column of the black box test plan will remain blank for now until you have implemented your software. Discussion and formal documentation will be done in your team’s report file.
TASK: Reflection
Once you have completed the black-box test plan task, each student should individually complete the reflection on black-box testing.
Additional Resources
- Slides TODO: Add links to resources (in _data/comprehensive-exercise.yml)
- Other Resources TODO: Add links to resources (in _data/comprehensive-exercise.yml)