Agenda

  1. Warm-up: Predict the Output — what happens when somebody types “seven” into a box expecting 7?
  2. Break each other’s programs, kindly: The Bad Input Hunt
  3. Back to Testing and Debugging — a test plan is just a written list of what you are afraid of
  4. Write the test plan you will run with your client, including what you expect each case to do before you try it
  5. Log it in your Code Journal

Things to do before our next class

  • Milestone: test your program with your client — beside them, not for them — and write down everything they did that you did not expect.