Test Plans
Computer Science: OCR GCSE, topic 2.3.10
Test Plans
It is important to make sure that tests are planned carefully. So, as many bugs as possible are fixed before deployment.

Test plans
- Test plans make sure that testing is effective by detailing:
- Exactly which tests will be performed.
- What test data will be used.
- What the system's intended outcome should be.
- A test plan should be created before development.
- A test plan is part of the design stage.
- Testing should cover all of the success criteria of the project.

Expected results
- Expected results are a key concept of a test plan.
- A programmer should know how the program is expected to behave and what the expected output should be.
- The actual result can then be compared to the expected result.
- The comparison determines whether the test was successful, unsuccessful or partially successful.
Test yourself on Test Plans
A test plan says a program should display 10. The program runs and displays 10. What does this result show?
A test's actual result is close to the expected result in a test plan, but does not match it exactly. What does this result show?
As a minimum, what should tests cover?
What should be included in a test plan?
A team plans which tests to run and what result to expect before coding starts. In which stage of development does this happen?