Testing to inform development — OCR A-Level Computer Science
Testing to inform development explained
Testing to inform development covers 2 specification points, including (a) Provide annotated evidence for testing at… and (b) Provide annotated evidence of any remedial….
Read the full explanation
Open a point below for its explanation and revision guidance.
(a) Provide annotated evidence for testing at each stage justifying the reason for the test.
Provide asks for evidence, so the submission must contain the test records and their annotations, not a general account of testing. Under section 3.3.2, each test at each stage of the programming project should show the solution's state at that point and feed the next change. Annotate each test with its purpose, input data, expected result, actual result and the development action that followed. Justifying the reason for the test means stating why it was run at that point, such as checking a new validation routine immediately after adding it. A test chosen only because it passes gives weak evidence; one that probes a known risk shows deliberate, traceable decisions.
(b) Provide annotated evidence of any remedial actions taken justifying the decision made.
This criterion asks you to provide annotated evidence of any remedial actions you took during development, and to justify the decision behind each one. A remedial action is a change made after a test showed the solution did not behave as intended, such as correcting a validation rule. For each action, record the failing test, the expected and actual results, the change made and a retest showing the fix worked. Annotations should explain in your own words what each screenshot shows, so the evidence supports your reasoning. The justification must explain why this response was right, for example why a range check was tightened rather than hiding the error. Cover every remedial action, not only the most significant.
Your focus
- Produce a test record for each development stage of a programming project.
- Justify the reason for each test by linking it to a specific change, risk or requirement.
- Explain the development action that followed each test result.
Show all 6 objectives
- Identify a failing test and the remedial action it prompted.
- Produce annotated evidence showing the expected and actual result before and after a change.
- Justify a remedial decision by referring to the observed test result.
Testing to inform development exam tips
Marking Points
- Includes a test record for each development stage, not only the final stage.
- Annotates each test with its purpose, the data used, and the expected and actual results.
- States the reason for each test, linked to a specific change, risk or requirement at that stage.
- Shows the development action taken after each test result, including unchanged code where a test passed.
- Selects tests that probe known risks, such as boundary values or invalid input.
- Identifies each remedial action taken, including minor changes, rather than only the largest one.
- Shows the failing test that prompted each change, together with the expected and actual results.
- Shows the code or design change made, and a retest showing the outcome after the change.
- Annotates each piece of evidence in the learner's own words, explaining what it demonstrates.
- Gives a justification that explains why this response was appropriate for the problem found.
Examiner Tips
- 💡Keep a test log with one row per test showing stage, purpose, data, expected result and actual result.
- 💡After each failed test, write the change made and the later test that confirmed the fix.
- 💡Before submission, check that every development stage has at least one annotated test with a stated reason.
- 💡Keep a dated log of each test, failure, change and retest as you go, so the order of events is clear.
- 💡Write each annotation as a short statement of what the evidence proves, not a copy of the output.
- 💡Before submitting, check that every remedial action you recorded has a justification beside it.
Common Mistakes
- Presents one end-of-project test log; record tests at each stage so the progression is visible.
- Lists tests without stating why each was run; add the stage-specific reason beside the test.
- Records only passing results; include failures and the resulting changes because they show development.
- Uses tests that duplicate earlier ones without a new purpose; choose a test that answers a new question at that stage.
- Lists remedial actions without linking them to a failing test; each action needs the evidence that prompted it.
- Presents screenshots with no annotation; add a note stating what each one shows and why it matters.
- Justifies a change by saying it fixed the error; explain why this response, rather than an alternative, was the appropriate choice.