Have you ever carefully crafted a set of tests, only to later discover that subtle issues still slipped through? Or maybe you’ve wondered if your tests are truly validating the important behaviours, especially in those tricky edge cases. We can sometimes be lulled into a false sense of security: if our tests pass, our code must be solid. But what if there was a way to find those missing edge cases and evaluate the quality of our tests?

In java, the only thing I’ll do in a constructor is assign a parameter to a field. Sounds strict? Let me explain.

We have had some new starters within the test team at LMAX over the past year. Here are their thoughts of their first year.

What started as a simple bug reported soon caused a pair of developers to question maths itself.

The best thing coverage can tell you is that code is unused, and should therefore be deleted.