"No reason to be shy," I eventually say. "This is an easy question. Any idea? A simple test we could start with. The simplest you can think about." Another pause. "All gutters?" you risk. "That's a start. How would you describe the test case?" "Well..." You don't know what to add. Learning how to write tests is what you're here for, right? You get frustrated. You can tell I notice. I give a hint. "When you want to describe a test case, think of this template." When A is in context X and does Y, B notices Z. "Sometimes, user A and user B are the same person, but it doesn't always happen," I say. You ponder, and give it a try. "When the player is playing bowling and does nothing but gutters... he notices..." You don't know how to finish, and stop. Another hint comes. "Most of the times, A and B are humans... but in some occasions they're bits of a bigger program." There it goes. Of course. "When the function is given a list of gutters as throws, and computes the score, the caller notices the result is 0," you say. Is this the right answer? Go there to discover it. |