Testing Feedback and Documentation
Grade 7 | Computer Science | Unit 03
Teacher's Guide
Learning objectives
- Explain Test case and Documentation in the context of this lesson.
- Use the worked example to answer the three practice questions with supporting reasoning.
- Complete the activity, evaluate its result, and identify one limitation or possible improvement.
Prerequisites: Basic reading and arithmetic; no previous subject study is assumed.
Suggested time: Three to five 45-minute sessions, including activity development and review. Language units need brief repeated spoken practice between sessions.
Teaching sequence
- Introduce: Present the title as a question or problem. Ask learners what they notice and record two initial ideas without treating them as established facts.
- Explain: Read the concept section and teach the two vocabulary items. Ask learners to paraphrase the distinction between them using a concrete example.
- Model: Work through the example. Identify given information, assumptions, and the reason for the result or interpretation. Use a teacher's spoken model for language pronunciation.
- Apply: Complete the activity individually or in pairs. Require a draft, a check against the task, and a brief revision. Discuss why different justified responses may be acceptable.
- Retrieve and evaluate: Answer practice and vocabulary questions independently; use the answer key for feedback. Finish with the reflection and an activity rubric.
Assessment and differentiation
The companion CSV contains five retrieval entries: two vocabulary questions and three practice questions. Award one point per accurate answer, accepting equivalent wording that preserves the meaning. Language answers may be oral or written according to the goal. Revisit missed concepts rather than using the score as the only measure of learning.
Assess the activity separately with four criteria, each scored 0-2: correct use of lesson concepts; clear evidence or reasoning; completion of the task requirements; and a useful revision or acknowledged limitation. A 0 indicates missing or unsupported work, 1 indicates partial achievement, and 2 indicates clear achievement. Accept multiple designs, interpretations, and decisions when their reasons meet the criteria.
Support learners with a word bank, annotated example, smaller first step, or partner rehearsal. Extend by changing one assumption or constraint and asking how the result would change. Use invented personal details in financial and social tasks. Optional school character discussion can connect honesty, respect, cooperation, and stewardship to the activity; assess the subject knowledge and reasoning separately.
Student Worksheet
Concept and helping material
Testing compares actual behavior with expected behavior for specified cases. A failed test is useful evidence for improvement. Ordinary, boundary, and invalid inputs exercise different situations. Documentation explains purpose, use, and assumptions so someone else can understand a program.
Vocabulary
- Test case: A specified input and its expected result.
- Documentation: Information explaining a program's purpose, operation, or design.
Worked example
A fictional score checker accepts numbers from 0 to 100. Test 50, 0, 100, -1, and a word; decide expected behavior before running each test.
Investigation or design task
Write a test table for a paper score-checking algorithm. Include ordinary, boundary, and invalid cases, revise one defect, and add usage instructions.
Record your work: State the goal; show your drawing, dialogue, calculation, data, or argument; explain one choice; and describe one check or revision. Identify a limitation rather than claiming your work proves more than it does.
Practice
- Why test 0 and 100 in the example?
- Should a failed test be hidden?
- Why decide expected results before running tests?
Vocabulary retrieval
- Define Test case.
- Define Documentation.
Reflection
Choose one answer or activity decision. Explain the evidence, calculation, language pattern, or reasoning that supports it. Describe one change of context or assumption that could change your conclusion.
Answer Key
- They are valid boundary values.
- No. It identifies behavior to investigate and improve.
- It avoids treating whatever happens as correct after the fact.
Vocabulary answers are the definitions above and appear in the CSV. Activity and reflection responses vary; use the teacher rubric and require specific reasoning tied to the task. A different supported interpretation is acceptable where the question allows it.
Source Reference
Everything You Need to Ace Computer Science and Coding in One Big Fat Notebook, PDF viewer pages 79,84,104 (1-based). Conceptual background; the examples, calculations, questions, and activities here are original adaptations. These pages were inspected in the supplied file; viewer numbering may differ from printed numbering. No source worksheets or illustrations are reproduced.