On his blog Brandon Savage has a new post reviewing a book from Chris Hartjes, "The Grumpy Programmer's Guide To Building Testable Applications".

When most developers think about books on testing, they think about books that highlight things like "test driven development" or "how to build a test for X." [...] This is not true of Chris Hartjes' book, "The Grumpy Programmer's Guide To Building Testable PHP Applications". When I asked Chris if I could review his book, I expected a step-by-step guide to writing tests. What I got was a step-by-step guide to building an application that COULD be tested. There's a big difference, and it's important to understand the distinction.

He points out that the book provides more about good application structure than who to write the tests for it. It provides a guide to creating modular applications that can be easily pulled apart and tested as well as some practical examples. He also includes a few "wise words" quoted from the book including: "if it's not yours, wrap it up" and "testing is good; testable applications are better."

You can pick up your own copy of the book fron its page on the Leanpub site.