Testing, Evaluation and Mathematical Reasoning
Using planned tests, logical arguments, quantitative evidence and user feedback to debug, assess correctness and evaluate a solution against its specification.
How to study A-level Computer Science
Define the problem and representation, trace the state change, justify the algorithm or architecture, then test the result against requirements, evidence and constraints.
Core concepts
Concept 1
Developmental and final testing use normal, boundary, invalid and stress data with predicted and actual outcomes.
Exam cue: Predict the result before running a test and record enough evidence to reproduce it.
Concept 2
Evaluation judges the solution against requirements, success criteria, user evidence, limitations and realistic improvements.
Exam cue: Link each conclusion to a requirement, test result, user observation or quantitative measure.
Concept 3
Boolean algebra, number bases and algorithm complexity are common mathematical tools and together contribute to the regulated minimum mathematics demand.
Exam cue: Use the board's current project criteria; mark allocations and required evidence differ.
Risk pitfalls and guardrails
Using screenshots of output as the whole test plan.
Guardrail: Do not substitute a memorised definition or generic advantage until you have identified the input, state, stakeholder and constraint in the task.
Calling a solution successful because it compiles.
Guardrail: Do not substitute a memorised definition or generic advantage until you have identified the input, state, stakeholder and constraint in the task.
Listing possible improvements without relating them to evidence or the original purpose.
Guardrail: Do not substitute a memorised definition or generic advantage until you have identified the input, state, stakeholder and constraint in the task.
Memory anchors
Normal Data
Normal data is valid and representative of expected use.
Boundary Data
Boundary data tests values at or immediately around a permitted limit.
Invalid Data
Invalid data deliberately violates a defined input rule.
Debugging
Debugging locates, explains and corrects the cause of observed faults.
Evaluation
Evaluation judges evidence against requirements, limitations and stakeholder needs.
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
What is the purpose of unit testing?
Individually tested modules are connected and their data contracts are exercised together. Which description identifies integration testing?
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.”