240063 (1) [Avatar] Offline
pg 20. Mocking and Stubbing
For all its strengths Object Oriented Software suffers from an important flow flaw.
A direct result from these flow flaws is that testing OOP software usually needs to cover two levels at once.

pg 21. How to use the code listings
For brevity reasons the book sometimes will point to you to the source code (especially for long and boring Java listings)

pg 23
What you need to take away from this code sample is:

pg 28
See the book "Making Java Groovy" by Manning if you are interested on in any of these cases.

pg 32
This is the main reason that I got interested in Spock in the first place is the fact that it comes with full batteries ...

#C, #D, #E explanations missing from PDF version
Kostis Kapelonis (53) [Avatar] Offline
Thank you very much!

Of course all of these will be fixed. I will mark them for the next MEAP.

The final book will be checked by professional proof-readers so don't worry if the MEAP suffers from this kind of errors (I am not a native speaker)

The problem with annotations is also very important.