Re: Three Law of TDD - to strictly follow, or not?
"Kaleb Pederson [email protected] [testdrivendevelopment]" <[email protected]> Thu, 28 Aug 2014 09:14:34 -0600
| Newsgroups | gmane.comp.programming.test-driven-development |
|---|---|
| Message-ID | <CAF4m_uXgXgv_7tuGLoTX9cL=aXgDrpwFhBvn1TRtNvJB82sTqg@mail.gmail.com> |
On Thu, Aug 28, 2014 at 8:38 AM, 'Donaldson, John' [email protected] [testdrivendevelopment] <[email protected]> wrote: > If you insist (as an earlier poster did) that you first write an assert, > then you would avoid this “compilation only” worry (as long as your assert > is non-trivial). I remember seeing that post but I forgot to respond -- that's a good idea that I've never tried. Done properly that should provide the necessary guarantees. Thanks for re-pointing that out. --Kaleb