Redesigning asserts as a printer.
When a test case fails, what kinds of things help you to work out what’s happened? Note down some ideas.
Explain what a printer is in the context of approval testing. Perhaps show the ones for Supermarket Receipt or TicTacToe.
Explain the idea of a storyboard - where a test prints the state after ‘arrange’, then print out what the ‘act’ step is, as well as printing the final state. Some tests will have multiple ‘act’ steps and print the state after each one.
There is a starting position for the Vending Machine Kata with one test case. First convert the assertions to an approval test. (Do this as a demo, then ask them to do the same for themselves). Then introduce new functionality into the vending machine feature by feature. Either do this for yourself or merge in the feature branches provided. As you develop the code, extend your printer to test the new functionality.
What have you learnt about printer design? How much detail should you include?