growing-oo-software-guided-by-tests at Yahoo! Groups

Source code for the book

hrvojep — Wed, 04 Nov 2009 08:01:27 GMT

Hi, I bought the book and want to work on the examples from the Sniper Auction, where is the source code for the book? Cheers h.

Re: state machine diagram

Nat Pryce — Thu, 03 Sep 2009 16:40:28 GMT

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

Re: state machine diagram

George Dinwiddie — Wed, 02 Sep 2009 19:35:04 GMT

Yes, the text makes that clear. Perhaps the picture is not as confusing to other people as it is to me. - George ... -- ... * George Dinwiddie *

Re: state machine diagram (was: [TDD] incomplete vs broken)

Nat Pryce — Wed, 02 Sep 2009 18:18:59 GMT

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

Re: state machine diagram (was: [TDD] incomplete vs broken)

Steve Freeman — Wed, 02 Sep 2009 09:10:05 GMT

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

state machine diagram (was: [TDD] incomplete vs broken)

George Dinwiddie — Tue, 01 Sep 2009 16:20:24 GMT

... 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

Re: What is the current status

Pete Keller — Mon, 17 Aug 2009 18:32:25 GMT

... Sounds like a Christmas present to me. 8) Thanks Pete

Re: What is the current status

nat_pryce — Mon, 17 Aug 2009 17:11:56 GMT

... It will be out in November. --Nat

What is the current status

Pete Keller — Thu, 13 Aug 2009 19:24:44 GMT

When will we see it in print? Thanks Pete

Re: Minor typo in chapter 8 - Building on Third-Party Code

Steve Freeman — Thu, 06 Aug 2009 13:43:16 GMT

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

Minor typo in chapter 8 - Building on Third-Party Code

Pietro Di Bello — Wed, 05 Aug 2009 12:28:22 GMT

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

Re: Introductions

Pietro Di Bello — Wed, 05 Aug 2009 12:15:52 GMT

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

Typos in Chapter 1

Pietro Di Bello — Wed, 05 Aug 2009 12:09:21 GMT

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

Re: one last opinion.

aman kohli — Tue, 04 Aug 2009 16:16:39 GMT

... what looks good on the screen, does not necessarily look good on the page. -- ak

Re: one last opinion.

Russ Rufer — Tue, 04 Aug 2009 15:51:51 GMT

Another vote for "emphasises neither". Slight preference. My second choice would be "emphasises only class names." It *looks* nice, but I wonder how to