Computing · Year 3

Active learning ideas

Testing and Refining Databases

Active testing helps Year 3 students move beyond creating a branching database to recognizing how real-world variety affects performance. When students physically trace paths and swap projects, they see firsthand where their yes/no questions succeed or fail with different items.

• National Curriculum Attainment Targets
• KS2: Computing - Data and Information
• KS2: Computing - Information Technology

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

Activity 01

• Outdoor Investigation Session
• 35 min · Pairs

Peer Swap Testing: Database Challenges

Pairs create five test items from a class list, swap databases with another pair, and trace each item through the questions. They note successes, failures, and reasons on a feedback sheet. Pairs then reconvene to discuss fixes before retesting.

Design a testing plan to ensure a database never leads to the wrong result.

Facilitation Tip

During Peer Swap Testing, circulate with a timer and call out when partners have one minute left to agree on one shared suggestion.

What to look for

Provide students with a printed branching database created by a classmate. Ask them to test it with three different items (one common, one unusual, one that might not fit). Students should record the path taken for each item and write one specific suggestion for improvement, such as rewording a question or adding a new category.

• Remember
• Understand
• Analyze
• Social Awareness
• Self-Awareness
• Decision-Making

Activity 02

• Outdoor Investigation Session
• 45 min · Small Groups

Bug Hunt Relay: Group Refinement

Small groups receive flawed sample databases. One student tests an item and passes to the next for diagnosis; the group brainstorms improvements. Rotate roles twice, then vote on the best refinements to implement.

Critique a peer's database and suggest improvements for accuracy.

Facilitation Tip

For Bug Hunt Relay, give each group a colored marker so their fixes stand out on the printed database sheet.

What to look for

Present students with a short, incomplete branching database on a whiteboard or shared screen. Ask them to identify one 'dead end' or 'ambiguous question' and explain why it is a problem. Then, ask them to suggest one question that could be added to resolve the issue.

• Remember
• Understand
• Analyze
• Social Awareness
• Self-Awareness
• Decision-Making

Activity 03

• Outdoor Investigation Session
• 30 min · Whole Class

Edge Case Workshop: Whole Class Critique

Display three peer databases on the board or screen. Class votes on test items that might fail, traces paths together, and suggests category expansions. Update one database live as a model for individual refinements.

Explain how to handle an item that doesn't fit existing database categories.

Facilitation Tip

In the Edge Case Workshop, place the most unusual item in the middle of the circle so every voice is needed to classify it.

What to look for

Give each student a card with an item (e.g., 'a bat', 'a chair', 'a cloud'). Ask them to write down the first question they would ask in a branching database to start classifying this item. Then, ask them to describe one challenge they might face if this item didn't fit neatly into the existing categories.

• Remember
• Understand
• Analyze
• Social Awareness
• Self-Awareness
• Decision-Making

Activity 04

• Outdoor Investigation Session
• 25 min · Individual

Solo Debug then Share: Personal Polish

Individuals test their own database with 10 varied inputs, logging errors. In pairs, they share logs and refine one question each before whole-class demos of key fixes.

Design a testing plan to ensure a database never leads to the wrong result.

What to look for

Provide students with a printed branching database created by a classmate. Ask them to test it with three different items (one common, one unusual, one that might not fit). Students should record the path taken for each item and write one specific suggestion for improvement, such as rewording a question or adding a new category.

• Remember
• Understand
• Analyze
• Social Awareness
• Self-Awareness
• Decision-Making

A few notes on teaching this unit

Start with a brief mini-lesson on why one friend’s test items may not work for another. Model tracing a path aloud while pointing to each question, then invite students to mimic the process in pairs. Research shows that physically stepping through the tree builds stronger logical reasoning than abstract discussion alone.

By the end of the sequence, every student will have identified unclear questions, fixed dead ends, and improved a classmate’s project. You’ll hear them explain their fixes using terms like ‘ambiguous’ and ‘edge case’ with confidence.

---

Watch Out for These Misconceptions

• During Peer Swap Testing, students assume their partner’s database will work perfectly if it sorts the items they brought from home.

  Hand each tester a set of three unfamiliar items—one that clearly fits, one that doesn’t, and one that sits on the edge—then ask them to trace the path aloud and explain where the tree breaks.

• During Bug Hunt Relay, students think every error requires deleting the whole branch.

  Prompt groups to circle only the problematic question, draw a small arrow to a new question they could insert, and label it ‘add branch’ before making any cuts.

• During Solo Debug then Share, students feel embarrassed to admit their tree has a dead end.

  Encourage them to write the problem in red on the back of the sheet, then swap with a partner for targeted help; the red mark becomes a starting point for collaboration rather than a source of shame.

---

Methods used in this brief

• Outdoor Investigation Session