@pyrmont For me, it helps to write a happy path test case first. Make it pass, then write a few things that should obviously fail with bad input. Helps make sure I always have a test for something.
@wa9ace I think I'd like to get there. My issue at the moment is that I rarely understand well enough the 'shape' (for want of a better word) the code and so writing tests feels like putting the cart before the horse.
A Mastodon instance for Rubyists & friends