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

Dry run tracing

301.13 Testing

Practise exam questions

Testing — Note 3 of 6

Step through manually.

What you need to know

A dry run means stepping through code line by line on paper, recording variable values in a trace table. This helps find logic errors without running the program.

What to know

  • Create columns for each variable
  • Add a row for each line that changes a value
  • Include the output column for print statements
  • Follow loops iteration by iteration

Code examples

Dry run this code
python
x = 1
for i in range(3):
    x = x * 2
print(x)
# Trace: x=1 → x=2 → x=4 → x=8
# Output: 8
← Previous noteTest data types301.13 TestingNext note →Expected vs actual301.13 Testing

Back to Testing

Specification notes for programming are in Paper 2.

Testing

Note 3 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).