For those wondering about the status of his book, "Zend Framework: Survive The Deep End", Padraic Brady has posted an update of where he's at.

Since the rumor mill has been active a while, I confirm two chapters of the book will be released this week. [...] To kick off a new spell of book updates, the next Chapter will be "A Simple Hello World Example", with an Appendix titled "Virtual Hosts On Apache 2". The following Chapter approximately one week later will be an introduction to the application to be built for most of the first half of the book.

He notes that, while normal print books usually have schedules, self-publishing is a bit more flexible. He does want to assure the readers of the book that work is actively being done and the chapters will keep coming.

On the PHP in Action blog, despite some agreement with Padraic Brady on his one behavior, one assertion method for writing unit tests, Dagfinn Reiersol still has his reservations.

Pádraic maintains that one assertion per test is a rule that should always be followed unless there is a specific good reason to break it. I prefer it as a guideline, as does Robert C. Martin in the book Clean Code. The reference is not intended as an appeal to authority to "prove" that I’m right. I’m just making the point that I think this reflects the current state of the art, which is not necessarily perfect, of course.

Dagfinn talks about behavior-driven development and illustrates how a two assertions could be combined into one but that the end result "isn't very pretty" - and that's just testing two proterties of a single object. Imagine what would happen if things got more complex.