Continuous System Test

The Kanban system helped us see that we needed to do system test continuously (well, regularly at least), instead of saving it until the end. The test team resisted this initially, since system test takes time and it felt inefficient to do it more than once in the release cycle. But that is an illusion. It may seem more effective to do test only at the end, but if we include bug-fixing time in the equation, it is significantly less effective.

Here’s what testing at the end typically looks like in a two-month release cycle:

images/Bugs/Late-testing-compressed.png

And here is what it typically looks like if we do it more often:

We can’t test the whole system ...

Get Lean from the Trenches now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.