Pdf version 7 july 2009.I created an Eclipse 3.4.2 project for the code of chapter 11. I have a Vista, French version, and the French keyboard on my laptop. ...
Feel free to submit a keyboard layout file as a patch. I don't know what a French layout looks like or have any way of testing one. --Nat www.natpryce.com On...
We'll have to think about this. Don't forget that our intention is to have the code available for download and browsing by the time of publication. S....
... To make the code "as just before Failing And Passing the Test, page 88" compilable, Eclipse proposes me the minimal version public class Main { public...
... Yes. That reporting code is still in a branch. We haven't had time to merge it into head -- you know why:) ... That was our intention. We use this material...
Nat and I can't agree on some of the code highlighting, so we need some other opinions. The question is whether class/method highlighting (using bold) is...
I prefer the last one - emphasising only the important bits. Having class and method names in bold is actually the opposite of the convention in Eclipse where...
I prefer option D) other :-) We are all use to syntax highlighting. I can not think of an editor that does not offer it. The reason this exists across the...
Another vote for "emphasises neither". Slight preference. My second choice would be "emphasises only class names." It *looks* nice, but I wonder how to...
Hi all, I think I've found two typos in chapter 1. In the Testing End-to-End paragraph, the last statement is:The result is a more difficult release cycle than...
Hi, I'm Pietro Di Bello, I'm a senior sw engineer, programming mainly in Java (since 1999). I follow and practice eXtreme Programming and Agile Methods since...
Other minor typo in Chapter 8. Building on Third-Party Code, paragraph "Only Mock Types That You Own": To develop against *an* third-party API... Seems to me...
Thanks for helping out. I should point out that the on-line version is rather out of date and we've nearly finished copy editing. Sorry for not being clearer ...
... Irrespective of the quibbling on the TDD list, I saw the diagram http://www.mockobjects.com/book/figures/listening-to-tests.png and found it a little...
the intention is that sometimes you have to refactor a broken test to make the error messages meaningful before making it pass. Unfortunately, I think it's too...
Actually the intention is that while trying to write a test you sometimes have to go back and refactor (on green -- hence the green arc) to get the code into a...
Maybe the internal arc should loop from "refactor" back to "refactor", approaching but not quite reaching the "write a failing test" node. Although that is...