Skip to topic
    ← Back to course topics

    Describe the approach to testing — OCR A-Level Computer Science

    Describe the approach to testing explained

    This statement asks you to name the test data you will use during iterative development and after development is complete, then justify each choice.

    Read the full explanation

    Identify means stating specific data values, such as a boundary value, not describing testing in general. Justify means explaining why each set is useful: it should link to a requirement or success criterion from your analysis, test a rule at its limits, or check that bad input is rejected. Iterative development data targets the feature added at each stage. Post development data covers the whole solution against all requirements. Label each set by phase so the choice is clear.

    Your focus

    1. Identify a set of normal, boundary, and erroneous test data for an iterative development stage.
    2. Justify each chosen data set by linking it to a specific requirement.
    3. Select post development test data that covers the whole solution.

    Describe the approach to testing exam tips

    Marking Points
    • Names specific test data for the iterative development phase, giving actual values rather than general categories.
    • Names specific test data for the post development phase, covering the complete solution.
    • Links each justification to a requirement or success criterion from the analysis.
    • Explains how a chosen value tests a validation rule at its limit, such as a boundary value.
    • Includes data expected to be rejected and explains how the program should handle it.
    • Labels each test data set by phase so the examiner can see which phase it supports.
    Examiner Tips
    • 💡Record each test data set in a table with columns for phase, input, reason, and expected result so every item is easy to check.
    • 💡Make at least one justification refer directly to a numbered requirement from your analysis.
    • 💡Check that post development data includes normal, boundary, erroneous, and extreme cases where they apply to your solution.
    Common Mistakes
    • Describes testing methods in general without listing any actual test values; name the specific data and its expected result.
    • Gives a justification such as 'it is a good test' without saying what it checks; state the requirement or rule being tested.
    • Uses one data set for both phases without explanation; separate the sets or justify why the same data serves both phases.
    • Includes only valid data, so erroneous input is never tested; add data that should be rejected and explain the expected outcome.