Computing · Year 3

Active learning ideas

Testing and Refining Programs

Active learning works for testing and refining programs because debugging requires hands-on practice with real code and immediate feedback. Students develop debugging habits faster when they test sequences themselves, see errors in real time, and refine code iteratively rather than relying only on explanations.

• National Curriculum Attainment Targets
• KS2: Computing - Programming
• KS2: Computing - Debugging

• 25–45 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Think-Pair-Share
• 30 min · Pairs

Pair Swap: Bug Hunt

Students create a simple sprite program, then swap with a partner. Partners use a checklist to test inputs like clicks or keys, note errors such as stuck loops, and suggest one fix. Pairs discuss and refine before swapping back for final tests.

Design a testing plan to ensure a program works correctly.

Facilitation Tip

During Pair Swap: Bug Hunt, assign clear roles like tester and recorder to keep discussions focused on evidence-based observations rather than opinions.

What to look for

Provide students with a simple sprite program (e.g., a sprite moving across the screen). Ask them to write down two specific things they would test to ensure it works correctly and one potential bug they might look for.

• Understand
• Apply
• Analyze
• Self-Awareness
• Relationship Skills

Activity 02

• Stations Rotation
• 45 min · Small Groups

Stations Rotation: Test Scenarios

Set up stations with programs facing challenges: maze navigation, color changes, sound triggers. Small groups test each using planned inputs, record bugs on sticky notes, rotate, and propose group refinements at the end.

Critique a peer's program and suggest improvements.

Facilitation Tip

In Station Rotation: Test Scenarios, circulate with a checklist to ensure students try edge cases like extreme inputs or rapid clicks before moving on.

What to look for

Students swap programs with a partner. Instruct them to run the program three times, trying slightly different actions each time. Then, they should write down one thing they liked about the program and one specific suggestion for improvement, referencing a particular sprite action or event.

• Remember
• Understand
• Apply
• Analyze
• Self-Management
• Relationship Skills

Activity 03

• Think-Pair-Share
• 35 min · Whole Class

Iteration Cycles: Whole Class Challenge

Display a shared sprite program on the board. Class tests as a group with volunteer inputs, votes on errors, teacher codes fixes live. Students then apply the cycle to their own programs individually.

Explain how iterative testing leads to a more robust program.

Facilitation Tip

For Iteration Cycles: Whole Class Challenge, model how to pause and ask reflective questions like 'Why did that happen?' after each test run.

What to look for

Observe students as they test their programs. Ask questions like: 'What are you testing right now?', 'What did you expect to happen?', 'What happened instead?', and 'How will you fix that?'

• Understand
• Apply
• Analyze
• Self-Awareness
• Relationship Skills

Activity 04

• Think-Pair-Share
• 25 min · Individual

Testing Plan Builder: Individual Draft

Students draft a testing plan for their program on paper: list inputs, expected outputs, pass/fail criteria. They test alone, refine, then share plans in pairs for peer validation and tweaks.

Design a testing plan to ensure a program works correctly.

Facilitation Tip

Use Testing Plan Builder: Individual Draft to require students to name at least one edge case in their plan before they write any code.

What to look for

Provide students with a simple sprite program (e.g., a sprite moving across the screen). Ask them to write down two specific things they would test to ensure it works correctly and one potential bug they might look for.

• Understand
• Apply
• Analyze
• Self-Awareness
• Relationship Skills

A few notes on teaching this unit

Approach this topic by modeling systematic testing with think-alouds, showing how to vary inputs intentionally and record outcomes. Avoid rushing to fix errors before students have explored multiple scenarios themselves. Research shows that students learn debugging best when they experience the process repeatedly, not just once. Emphasize small, testable changes over complete rewrites to build persistence and confidence.

Successful learning looks like students creating specific test plans, running programs multiple times with varied inputs, identifying bugs, and making targeted code adjustments. They should articulate what they tested, what went wrong, and how they fixed it with confidence.

---

Watch Out for These Misconceptions

• During Pair Swap: Bug Hunt, watch for students who declare a program 'perfect' after one test run.

  Have partners run the program again with different inputs, like moving the sprite quickly or slowly, and compare notes before deciding it works.

• During Iteration Cycles: Whole Class Challenge, watch for students who erase large sections of code when they find a bug.

  Prompt them to isolate the issue by testing step-by-step, like commenting out one block at a time to see what changes the outcome.

• During Station Rotation: Test Scenarios, watch for students who test only typical inputs and miss edge cases.

  Ask groups to brainstorm 'what if' scenarios together, like what happens if the sprite starts in an unexpected position, before testing.

---

Methods used in this brief

• Think-Pair-Share
• Stations Rotation