Testing - Black Box
Email this Mix
Slide 1 - Designing Black Box Tests
- Emerson Murphy-Hill
- Creative Commons Attribution 4.0 License.
- Material Produced by NCSU Software Engineering Faculty.
Slide 2 - Planning a Black Box Test Case
Slide 3 - Important Consideration for Black Box Test Planning
- Look at requirements/problem statement to generate.
- Test cases need to be traceable to a requirement.
- You must write the repeatable test case so anyone on the team can run the exact test case and get the exact same result/sequence of events.
- The inputs must be very specific.
- Example: “Students who receive a grade of 70 or higher pass the exam.”
- Correct test cases: Grade = 80; Grade =20
- Incorrect test cases: “input a passing grade” “input a failing grade”
- The expected results must be very specific. “Pass” “Fail”
Slide 4 - Important Consideration for Black Box Test Planning (cont.)
- Run the simplest test case first – or you won’t know if the test case failed because basic functionality doesn’t work or if the hard stuff doesn’t work.
- Plan the simplest test to test the failure that you are looking for. If the test case fails, you don’t want to have to work *too* hard to re-run the test when the code is (supposedly) fixed.
Slide 5 - Tests of Customer Requirements
- Ensure each customer requirement is tested at least once
- Start with most-used success path (i.e. “happy path”)
- Continue with other success paths
- Also test failure paths that contain intentional errors that should fail predictably and gracefully (i.e. expected points of user failure)