... 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...
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...
Hi all. There's now quite a few people in this group, some of whom we don't know (or we don't recognise your Yahoo IDs). Time for introductions! Please...
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...
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...
Pdf version 7 july 2009.I created an Eclipse 3.4.2 project for the code of chapter 11 (with JUnit 4.4 on the class path) 1) Class AuctionSniperDriver. A) In...
§1 Unclear conclusions in "Value Types". You write at the end of "Value Types" "We find that the discovery of value types is usually motivated by trying to...
JUnit's version which come with Eclipse 3.4.2 is 4.3. The method assertThat does not exist in the class Assert of JUnit 4.3 but it exists in MatcherAssert....
Many of the SVP reviewers weren't happy with the tests that use of jMock, finding them hard to decipher. I think that a subset of the group is fairly ...
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. ...
"In which we are commissioned to build an application that automatically bids in auctions." -> "We are commissioned to build an application that automatically...
Feedback on this chapter is a bit sparce: By this point review burnout was setting in. We had a bit of trouble with this chapter. On reviewer's comment was "If...
First paragraph: there's a missing comma on one side of 'first' in "When writing unit tests first". From context, I'm guessing it goes after 'tests'. In...
"starting from what our objects need and writing interfaces and further objects" -> "starting from what our objects need and writing interfaces and more...
"rather than having to maintain a mental model of all the code at once, and merging changes back in is never a crisis." -> "rather than having to maintain a...
"If create an Item type in a system, rather than just using String, we can find all the relevant code" -> "If we create an Item type in a system, rather than...
SVP is moving on to other subject matter, but a few of us may stick around here to help. Is there a draft more current that 24 June, and are there areas that...
"The only way for humans to deal with complexity is to avoid it, by working at greater levels of abstraction." -> "The only way for humans to deal with...
The group had some mixed opinions on this chapter. Some questioned whether "issues correct queries" was worth testing, assuming that the third-party ORM had...
"tracking down failures is a tricky when the architecture" -> "tracking down failures is tricky when the architecture" "we prefer to discover those details as...
"We start developing a feature by with the objects that receive input from the end-to-end tests." -> "We start developing a feature with the objects that...
I've just substantially reworked the "Achieving OO Design" chapter. The beginning has been reordered and the whole composition/higher- level stuff has been...
We started putting in little preambles to the example chapters. Do these help? We either need to fill in the rest of the chapters or pull the ones we already...
Hi everybody, especially native US English speakers. In the chapter "Commissioning an Auction Sniper » I found two occurrences of using « agree » as...
The group liked this chapter. The consensus, though, is that this isn't really a special topic, since it's so common (at least to us. We suggest moving it...