Program testing worksheets for Grade 4 Computer Science help students compare what a program should do with what actually happens. In Testing Expected and Actual Program Outcomes, a rabbit-game example gives students a clear reason to examine results: a character can respond to a key press while still moving in the wrong direction.

The lesson focuses on a practical question: does the observed behavior match the plan? Students follow Maya as she records her expectations, notices a movement problem, changes an instruction, and checks the game again. This concrete example connects programming fundamentals to careful observation and decisions supported by evidence.

Follow the evidence in Maya’s game

The space key should make the rabbit jump once, while the right arrow key should move it one step right. The first jump works as expected, but the movement goes left. Students examine why these results provide different evidence about the game’s behavior.

After the instruction changes, Maya checks both controls. This introduces the importance of checking that the corrected movement works while the jump still behaves correctly. Repeated tests address consistency, and different inputs reveal how the program responds under more than one condition. Students also consider why a single successful result cannot establish that every part works.

What you receive and how students respond

• A student worksheet with a dialogue, definition matching, a cloze passage, diagram labeling, and a reading passage about testing a rabbit game.
• Multiple-choice questions, true-or-false statements, short answers, and an extended response that move from identifying information to explaining the testing process.
• A separate PDF Teacher Guide containing Learning Objectives, Teaching Tips, Discussion Questions, and Common Mistakes.

The vocabulary includes expected outcome, actual result, testing, and evaluation. A recorded table connects the key pressed with the planned behavior and observed result, helping students interpret evidence rather than judge the game from a general impression.

Use it to make testing decisions visible

Introduce the case during a programming lesson, then have students complete the written tasks independently or discuss their reasoning with a partner. Bring the class together to compare explanations of the movement error and the purpose of the later checks. The extended response provides an opportunity to explain the sequence from initial expectations to evaluation.

This computer science practice gives teachers a specific basis for discussing debugging and program evaluation. Students must explain how observations support an improvement, making their reasoning visible beyond simply identifying whether a result is correct.