Python that can fail a test
Functions, lists, and a test that is allowed to go red.
- Write a function and a test for it
- Explain why a test failed
- Keep names clear enough for a mentor to read
They make: A small tool (shop, quiz, or timer) with tests.
GCC · UAE · KSA · Qatar · Kuwait · Engineered for the Few.
GCC · GST / AST
Ages 11–14
Ages 11–14 write Python, games, and websites — with tests a mentor can actually fail.
Class
1 : 4 · 4 children
When
GST / AST evenings
They leave with
A website running on their laptop
11–14s who are ready to build things a parent can open — a site, a game, a small robot sim. Prior code helps; it is not required.
They leave the sandbox. A page has to open in a browser. A game has gravity. A test can fail for a real reason. Same tiny class: four kids, one engineer.
Class 1
New piece: a page, a jump, a sensor.
Class 2
Mentor tries to break it. They fix what broke.
Show
Twelve minutes, no slides. Parents can watch.
Functions, lists, and a test that is allowed to go red.
They make: A small tool (shop, quiz, or timer) with tests.
HTML, CSS, a little JavaScript. The homework is a live page.
They make: My Portfolio — a personal site on localhost they can show.
Velocity, jump, a way to lose. Pretty pixels are not enough.
They make: Sky Hopper — a side-scroller they wrote.
Sensors in, motors out. Green means go. Red means stop.
They make: Color Rover — floor colour changes what the rover does.
Personal website
A real page that opens in a browser: name, photo, three projects, a contact line. Parents can open the link.
Python game
Tap to hop through gaps. Gravity pulls down, space jumps, a pipe ends the run. A game they wrote — not a clone they downloaded.
Robot challenge
A rover that reads the floor colour: green means go, red means stop, blue means turn. Code that moves something.
Ready when you are
We’ll check App Builders is the right fit for their age and what they like to make.