You Climbed the Test Pyramid. Now Eat a Custard Slice.

Martin Fowler's Test Pyramid has served the industry well for years. It tells you which types of tests to write (unit, integration, end-to-end) and roughly how many of each. The pyramid is intuitive: a wide base of fast unit tests, a narrower middle of integration tests, and a thin top of slow end-to-end tests. To … Continue reading You Climbed the Test Pyramid. Now Eat a Custard Slice.

Why I prefer a Test Contract to a Test Plan

Some context... I firmly believe that quality really is everyone's responsibility. In order for that to become something practical and useful, the things we do have to be easily accessible to everyone, regardless of their background. Sometimes that means we have to simplify and abstract away the actual complexities of practices and techniques, particularly around … Continue reading Why I prefer a Test Contract to a Test Plan

Is it possible to improve the impact of our Testing by simplifying it?

I admire the simplicity of TDD. Red, Green, Refactor. Write a test, see it fail. Write some code, see the test pass. Refactor your code, the test should still be green. It's simple to describe and a simple concept to understand. Except it's not simple. I rarely practice TDD by myself these days, but I … Continue reading Is it possible to improve the impact of our Testing by simplifying it?

We have no evidence to suggest we shouldn’t release

"We have no evidence to suggest we shouldn’t release." I sometimes use this statement or a variation of it, when asked if something we’re testing is ready to ship. For me it succinctly describes the current state of our knowledge of the software under test. A longer form could read “We have completed all of … Continue reading We have no evidence to suggest we shouldn’t release