Topic module

Software Testing and Debugging

Build comprehensive final test plans, classify errors and use dry runs, trace tools, breakpoints and watchpoints.

Long-form learning
Concept to Risk to Memory to Check-up

How to study Higher Computing Science

Move from requirements to structured designs, trace code and data precisely, and support every test or evaluation judgement with observable evidence.

Core concepts

Concept 1

A final test plan demonstrates that every functional requirement is met using normal, extreme and exceptional data where relevant.

Exam cue: Map each test directly to a functional requirement and expected result.

Concept 2

Syntax errors break language rules, execution errors occur while running, and logic errors produce incorrect behaviour or output.

Exam cue: Distinguish the observed symptom from the underlying error type.

Concept 3

Dry runs and trace tables expose value changes; breakpoints pause execution and watchpoints monitor selected variables or expressions.

Exam cue: Choose a debugging technique that reveals the suspected value, path or failure point.

Risk pitfalls and guardrails

Listing test data without expected results.

Guardrail: Check route, scope, data type, boundary, loop condition, identifier and expected output before committing to the response.

Calling every wrong answer a syntax error.

Guardrail: Check route, scope, data type, boundary, loop condition, identifier and expected output before committing to the response.

Using one successful test as evidence that all requirements are met.

Guardrail: Check route, scope, data type, boundary, loop condition, identifier and expected output before committing to the response.

Memory anchors

Comprehensive final test plan

It covers every functional requirement with inputs, purpose and expected result.

Syntax error

The code violates the programming language’s grammar.

Execution error

The program starts but encounters a failure while running.

Logic error

The program runs but follows incorrect logic or produces the wrong result.

Breakpoint

Pause execution at a chosen point so program state can be inspected.

Watchpoint

Monitor a selected variable or expression as execution proceeds.

Checkpoint rule

Do the check-up only after you can summarize each concept in one sentence and identify one dangerous pitfall from memory.

Knowledge Check (after reading)

Short check-up to confirm understanding of this module.

Check-up Questions

1-2 question checkpoint

A final test plan should be based primarily on what?

A field accepts integers 1 to 50 inclusive. Which set provides normal, boundary and invalid test data?

Answer all questions to submit.

Next step personalized recommendations

Continue learning

Move forward only after this module is stable.

What is Pass Harbor?

Completely free exam prep for 247 UK exams.

  • Practice questions
  • Flashcards
  • Study guides
  • Mock exams
  • No registration
  • No paywall
  • Start instantly
No more expensive exam prep. Quality study tools should be accessible to everyone.