Teaching testing programs with inputs in grade 7 does not have to be complicated. Picture a QA tester designing varied test inputs, including edge cases, to find bugs before software ships. That kind of thinking is exactly what Oklahoma's grade 7 computer science standard 7.AP.PD.03 asks students to practice \u2014 and it is very teachable with the right materials. This post walks through what the standard means, the misconceptions students bring to it, and discussion starters you can use tomorrow, whether you teach in a classroom or at your kitchen table.<\/p>\n
\nTest and refine programs using a variety of student created inputs.\n\u2014 Oklahoma Academic Standards for Computer Science (February 2023)<\/em><\/p>\n<\/blockquote>\n
In plain language: Oklahoma's standard asks seventh graders to test and refine programs using a variety of student created inputs.<\/p>\n
In student-friendly terms, the learning target is: "I can test and refine programs using a variety of student created inputs."<\/strong><\/p>\n
What Students Should Be Able to Do<\/h2>\n
\n
- I can design typical test inputs that reflect normal program use.<\/li>\n
- I can design edge case inputs that test unusual extremes.<\/li>\n
- I can design invalid inputs that test how a program handles bad data.<\/li>\n
- I can refine a program based on what testing reveals.<\/li>\n<\/ul>\n
Along the way, students pick up the working vocabulary of the topic: testing, input, output, typical, edgecase, invalid, boundary, refine, bug, expected, variety, validate.<\/p>\n
Testing Programs With Inputs: Misconceptions to Watch For<\/h2>\n
These are the wrong turns students reliably take with this standard \u2014 knowing them ahead of time is half the lesson plan. Each correction strategy below comes straight from the unit's teacher guide (the paragraph and activity references point into the unit itself).<\/p>\n
1. "Testing a program with one typical input is enough to confirm it works correctly."<\/strong><\/p>\n
Use paragraph 1's key point \u2014 a program can work with one typical input and still have hidden problems revealed only by other kinds of inputs.<\/p>\n
2. "Edge cases and invalid inputs are basically the same thing."<\/strong><\/p>\n
Reference paragraphs 3-4 \u2014 edge cases test unusual extremes that are still technically allowed, while invalid inputs test data that shouldn't be allowed at all.<\/p>\n
3. "Once a bug is fixed, there's no need to test the program again."<\/strong><\/p>\n
Point to paragraph 8 \u2014 retesting after a fix confirms it worked and checks that it didn't accidentally introduce a new problem.<\/p>\n
4. "Refining a program just means making it work for the one specific test case that failed."<\/strong><\/p>\n
Clarify from paragraph 7 \u2014 genuine refining means fixing the root cause so it works for an entire category of similar inputs, not just one case.<\/p>\n
Discussion Starters You Can Use Tomorrow<\/h2>\n
\n
- Why do you think it's easy to forget about edge cases when testing a program you just built?<\/li>\n
- What's an example of a boundary value you might test for a program with a maximum score of 100?<\/li>\n
- Why might a security researcher deliberately test software with unusual or malicious inputs?<\/li>\n<\/ul>\n
Bringing It Home<\/h2>\n
This topic is a natural one for families. One ten-minute activity to try: Together, pick an app or game you both use and try a few unusual inputs together (an empty field, a very long entry) to see how it handles them, and talk about what you notice.<\/p>\n
Where This Leads<\/h2>\n
Students who can test and refine programs using a variety of student created inputs are building skills used every day in QA testing, software engineering, automation test engineering, security research, and computer science education.<\/p>\n\n
See the Unit in Action<\/h2>\n\n