DRY vs WET | Arlo Being Bloody StupidWrite Explicit Tests – Following WET just asks “What is each test attempting to say? How could we say that most clearly?” An awesome example on re-writing a test into a much, much better one. It also demonstrates well that writing a good test is an iterative and challenging task – but the result is absolutely worth the effort.
In improve this we take a look at a reader submitted test, user interface, story or block of code and we try and improve it, without context, explaining what we did as we went.
In this issue Anand has sent us a cucumber test that he’s asked us to improve.