Revise Computing
Revision notesQuestionsFor schools
Log inStart revising free
Revision notesQuestionsFor schoolsLog in
GCSE Computer Science/Supplementary programming practice/Testing

Test tables

301.13 Testing

Practise exam questions

Testing — Note 5 of 6

Complete provided test tables.

What you need to know

A test table documents each test with columns for: test number, input data, data type (normal/boundary/erroneous), expected output, actual output, and pass/fail.

What to know

  • Include test number, input, type, expected, actual, pass/fail
  • Cover normal, boundary, and erroneous data
  • Fill in expected BEFORE running the test
  • A complete table proves the program was thoroughly tested

Code examples

Test table example
python
# | Test | Input | Type      | Expected | Actual | P/F |
# |  1   |  50   | Normal    | "Pass"   | "Pass" |  P  |
# |  2   |  49   | Boundary  | "Fail"   | "Fail" |  P  |
# |  3   | "abc" | Erroneous | Error msg| Crash  |  F  |
← Previous noteExpected vs actual301.13 TestingNext note →Debugging301.13 Testing

Back to Testing

Specification notes for programming are in Paper 2.

Testing

Note 5 of 6

  1. 1Why test?
  2. 2Test data types
  3. 3Dry run tracing
  4. 4Expected vs actual
  5. 5Test tables
  6. 6Debugging
Topic overview

© 2026 Revise Computing · revisecomputing.co.uk

Privacy noticeTermsContact

Revise Computing is an independent revision resource. It is not affiliated with, or endorsed by, OCR (Oxford Cambridge and RSA Examinations).