Top

Week 13

In this week's content we will be looking at programming test evidence: finding defects and explaining fixes through a realistic Level 3 IT context. You will be required to test a small safe Python program, identify logic defects and communicate the evidence and required corrections professionally.

Steps to complete:
1. Predict expected results for normal, boundary and invalid test cases.
2. Read the supplied loan-tracker functions and connect each section to a client requirement.
3. Run or manually trace the supplied tests and complete actual-result and pass/fail fields.
4. Explain the cause and user impact of each failed test without merely saying “the code is wrong”.
5. Write a 350-word test report containing evidence, proposed fixes and retest priorities.
6. Rewrite one technical defect explanation in plain English for library staff.

By the end of the session you should have a completed test log, defect analysis and technical-plus-client-facing evaluation.

Week 13 Student Resource Pack


Last Updated
2026-09-14 09:21:05

English and Maths

English

code reading; evidence; cause/effect explanation; formal report writing; adapting technical register.


Maths


Stretch and Challenge

Stretch and Challenge


Homework

Homework


Equality and Diversity Calendar
How to's

How to's Coverage





Links to Learning Outcomes

Links to Assessment Criteria

AQA AO1, AO4, AO5, AO6: interpret evidence, evaluate success, explain defects precisely and adapt language to audience.

Unit 4: Programming — C: develop and test a software solution; testing, refinement and evaluation against requirements.

 


Files that support this week


| | | | |

Next

Prev