Skip to topic
    ← Back to course topics

    Testing to inform evaluation — OCR A-Level Computer Science

    Testing to inform evaluation explained

    Testing to inform evaluation covers 2 specification points, including (a) Provide annotated evidence of testing the… and (b) Provide annotated evidence of usability….

    Read the full explanation

    Open a point below for its explanation and revision guidance.

    (a) Provide annotated evidence of testing the solution of robustness at the end of the development process.

    This criterion asks you to provide annotated evidence of testing the solution for robustness at the end of the development process. Robustness means the program keeps behaving sensibly when given invalid, unexpected or extreme input, rather than crashing or giving wrong output. Test the final version after development is complete, using invalid and boundary values for each input. For each test, record the input, the expected outcome, the actual outcome and a screenshot, then annotate what the evidence shows about how the program handled the bad input. A list of ticks is not enough, because the annotation must explain the behaviour observed.

    (b) Provide annotated evidence of usability testing (user feedback).

    Provide means you must supply the evidence in your project, not describe it from memory. Usability testing checks whether real users can complete tasks with your solution easily. User feedback is what testers say or do during and after those tasks. Evidence should show who tested, which tasks they attempted, what they said or did, and how you recorded it. Annotated means each item carries a short label explaining what it shows and what you changed as a result. For example, a dated screenshot of a tester missing the save button, annotated with the tester's comment and the interface change made in response. Link each item to the success criterion it tests.

    Your focus

    1. Select invalid, extreme and boundary inputs for each input of the final solution.
    2. Record expected and actual outcomes for each robustness test.
    3. Annotate evidence to explain how the solution handled erroneous input.
    Show all 6 objectives
    1. Collect annotated user feedback from a usability test of your solution.
    2. Label each evidence item with what it shows and the action taken in response.
    3. Link each piece of feedback to a usability success criterion from your analysis.

    Testing to inform evaluation exam tips

    Marking Points
    • Tests the final version of the solution rather than an earlier prototype.
    • Uses invalid, extreme and boundary inputs that test how the solution handles unexpected data.
    • Records the input, expected outcome and actual outcome for each test.
    • Annotates each screenshot to explain how the solution behaved with the bad input.
    • Explains whether the solution kept working sensibly or failed, and why that matters for robustness.
    • Includes evidence gathered from real users rather than from the developer testing their own solution.
    • Records who tested, the tasks attempted and the date or version of the solution tested for each item.
    • Presents user feedback in the testers' own words, quoted or paraphrased accurately.
    • Annotates each item to explain what it shows about usability and what action followed.
    • Links each piece of evidence to the relevant usability success criterion from the analysis.
    Examiner Tips
    • 💡Plan a test table before testing, listing each input, its type and the expected result.
    • 💡Capture screenshots that show both the input entered and the output produced.
    • 💡Write each annotation as a sentence explaining what the evidence shows about robustness.
    • 💡Record feedback as soon as each test ends, noting the tester's role and the date, so the evidence can be referenced accurately later.
    • 💡Annotate each screenshot or log with one or two sentences stating what it shows and the change it led to.
    • 💡Use a table that links each usability success criterion to the feedback item and the resulting change.
    Common Mistakes
    • Tests only typical valid data, which does not show robustness; include invalid and boundary values for each input.
    • Uses a tick list without annotation; explain what the output shows about the program's behaviour.
    • Presents evidence from an early prototype, which does not meet the end-of-development requirement; retest the final version.
    • Presents a single summary sentence such as users found it easy, with no source; include the actual feedback and who gave it.
    • Attaches screenshots or logs without annotation, leaving the examiner to infer the point; add a label stating what each item shows.
    • Mixes the developer's own opinions with user feedback; keep tester comments separate and clearly labelled.