Unit tests
Unit tests check small pieces automatically, so a change that breaks something old is caught in seconds rather than weeks.
Python for Kids · Class 10 · Module 7 of 9
Testing and Security
The last two questions before shipping: does it work, and is it safe?
8 sessionsSessions 49–56
4 weeksTypical pace
Intermediate to AppliedLevel
Class 10Python & Coding
The big idea
Students write automated tests that run in seconds, validate every input that crosses a boundary, and handle secrets and permissions properly — including the rule that credentials never belong in source code.
Why it matters
Testing and security are the professional standard, and both are far cheaper to build in than to add afterwards.
Unpacked
What you will actually learn
Three core ideas, each taught with worked examples and then practised until it feels obvious.
Validation
Validation happens wherever data enters the system — forms, files, APIs. Never trust input because it came from your own front end.
Secrets and permissions
Secrets and permissions: keys live in environment variables, not in code; every user gets the least access that lets them do their job.
Did you know?
Scanning tools regularly find thousands of live API keys accidentally published in public repositories every single day.
Common mix-up
“Nobody would bother attacking a school project.” Automated scanners attack everything reachable, indiscriminately, within hours of it going online.
Session by session
Your 8-session journey
Sessions 49–56 of the 72-session year, at two one-hour sessions per week.
- 1
Warm-up and big picture
Where this module fits, what you will build, and a hands-on starter that gets everyone curious about unit tests.
- 2
Unit tests
Guided teaching on unit tests, worked through together with the teacher.
- 3
Unit tests — practice lab
Independent practice, small challenges and one deliberate mistake to diagnose.
- 4
Validation
Guided teaching on validation, building directly on the previous two sessions.
- 5
Validation — practice lab
Applied tasks that combine unit tests and validation in one piece of work.
- 6
Secrets and permissions
Secrets and permissions introduced and practised, completing the toolkit needed for the project.
- 7
Project build
Guided build session for the module project: Application quality audit.
- 8
Test, present and reflect
Finish, test against the checklist, present the work and explain the decisions behind it.
Project lab
Application quality audit
Every module ends with something the student built themselves and can demonstrate. This is the piece that goes into their portfolio and gets explained out loud at the end of session 56.
Try this at home
Audit your own application: list every place data enters, and confirm each one validates. Fix the weakest before reading further.
It is finished when
- It works from start to finish without breaking
- You can explain every part of it in your own words
- You tested it and improved at least one thing afterwards
- Someone else used or understood it without your help
By the end of this module
Students finishing Module 7 can:
- Explain and use unit tests without prompting
- Explain and use validation without prompting
- Explain and use secrets and permissions without prompting
- Build and finish application quality audit
- Test your own work and correct what you find
- Talk an adult through what you made and why
Word bank
The vocabulary introduced here, in plain language:
- unit test
- An automated check on a small piece of code.
- sanitisation
- Cleaning input so it cannot cause harm.
- least privilege
- Granting only the access actually required.
Module challenge
Think you have got this?
0 XPLevel 1 · Curious Beginner
6 quick questions drawn from this module — vocabulary, the project you build, and a myth-or-fact round. Every wrong answer explains itself, so a mistake still teaches you something.
Your child's free trial is one message away.
Tell us your child’s class and what they enjoy. We will suggest the closest program fit—no pressure and no upfront payment.