Ping Pong programming

​​ When doing TDD one idea we’ve used successfully is to follow these steps:

• Write the smallest amount of a test required to make it fail. This could even be a compilation failure.
• Then write no more of the production code required to make that test pass.

“Ping Pong development” while pairing programming is to follow these steps once and then swap who is driving and who is navigating (read more about driver/nagivator pairing in one of my previous blogs)

This is enjoyable, helps to promote following “red”, “green, “refactor” and helps reduce keyboard hogging

Hope this helps