Unit tests and parameter validation
Adam Sroka <[email protected]>
| Newsgroups | gmane.comp.programming.test-driven-development |
|---|---|
| Message-ID | <CALaPUVeYS-gBZUF8ZxLrw540T+rJJuh+OA96UgihK8N25d_n+Q@mail.gmail.com> |
IIRC, the terms London and Detroit school were dreamt up on this list as a reaction to the negative reactions to "mockist/statist" terminology. Can't remember who suggested them, but they stuck at least for a while. The reason the top down mock based approach is called London school is that Steve and Nat wrote about it and they live in London. The reason the other approach is called Detroit school is Ron and some of the other early XP guys live in the vicinity. On Monday, October 21, 2013, Josue Barbosa dos Santos wrote: > ** > > > On Sun, Oct 20, 2013 at 4:54 AM, Ron Jeffries <[email protected]> wrote: > >> ** >> And either direction, parameter checking would be rare. As would mocks, >> being as I'm Detroit School and all. >> > > Speaking about Detroit and London Schools, did you read the book Growing > Object Oriented Software Guided by Tests (GOOS) from Steve Freeman an Nat > Price? Just curious. > > -- > Abraços, > Josué > http://twitter.com/josuesantos > > > On Sun, Oct 20, 2013 at 4:54 AM, Ron Jeffries <[email protected]> wrote: > >> ** >> >> >> Hi David, >> >> On Oct 20, 2013, at 2:00 AM, "Parsons, David" <[email protected]> >> wrote: >> >> An interesting discussion. I must admit that it hadn't really occurred to >> me that much parameter validation could be a complete waste of time, so >> thanks for the insight. >> >> It does seem to me that even if you develop 'inside out' you will >> sometimes need to work 'outside in', for example if you are using a mock, >> or if you apply refactorings that extract classes or methods. >> >> >> In fact I generally work "outside-in", with occasional experiments on "I >> wonder whether, if I took this course, I could make such and so happen", >> where I'll build some inside thing. I would save that thing for reference, >> perhaps, but would not expect to use it as is. The experiment would be to >> teach me what's possible and a bit about how to do it. Then I'd let my >> usage of the thing tell me what it wants to be. >> >> And either direction, parameter checking would be rare. As would mocks, >> being as I'm Detroit School and all. >> >> Ron Jeffries >> www.XProgramming.com <http://www.xprogramming.com> >> If it is more than you need, it is waste. -- Andy Seidl >> >> > > > >