8. A Well‐Tested Solution
Standard: 2‐AP‐17: Systematically test and refine programs using a range of test cases
Looking back at your work to preserve the moss, you notice how the parts seem to fit together. First, you built a prototype to map out the best route to discover the moss in its hiding place. Then, you built a gate for it and a password strategy so that a user equipped with the proper password would gain access. You also discovered how ants communicate with each other in their own secret code to inform their community about where the patches of moss lie throughout the forest. What if you could bring these parts all together into one larger solution to create a robust strategy to safeguard the rare glowing moss for all future generations?
“It's a lot to think about,” admits your Guide when you mention this idea. “What if one part doesn't work well? Will everything else then fail? It seems like you should stop to think about all the things that might fail and build a plan to test them. By having a plan, you make sure that all the parts of the system work together.”
“I'll build a testing plan!” you say, agreeing that this is an interesting idea. You start looking at the ways that testing can help you think about your projects as part of a larger system of parts that all need to fit together.
Get Computer Science for Kids now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
