testing

I’m an avid believer in testing - TDD helps drive design, and having a test suite available to verify behaviour while maintaining an application is worth a million bucks. However, even the most complete unit test suite still doesn’t guarantee that the integration between different components is perfectly done, nor does it test the value a system delivers from a user perspective. Does a feature really do what a user expects it to do? [Read More]

I’ll say it once more - it’s not worth it. Let it go. Your aim should be at about 70% code coverage - as long as you know in your hearts heart that you have tested that you should have. What’s vitally important (and which is the whole reason why I run coverage tools in the first place), is not the warm, fuzzy feeling I get in my tummy when I see a high number - it’s the easy identification of untested code and pathways that yield value in this regard. [Read More]

I’m one of the converted in terms of test-driven development. One of the main “aha” moments for me is not to write unit tests - it’s writing testable code. Any code that’s testable is sure to be of a higher quality and easier to maintain than typical spaghetti code. That brings me to the second part of the title - mocks. The art of mocking objects have taken off over the last couple of years. [Read More]