Also see Michael Feathers' response to Coplien via Twitter: http://michaelfeathers.typepad.com/michael_feathers_blog/2008/06/the-flawed-theo.html / https://twitter.com/mfeathers/statuses/441598005515669504
On Fri, Mar 7, 2014 at 9:53 AM, David Gerard <[email protected]> wrote: > On 7 March 2014 15:13, Chris McMahon <[email protected]> wrote: > > > This process is something that I think would be of great interest to a > > variety of teams: > > * When to throw away old tests > > * When to create new tests (TDD style, before writing the code that > > satisfies the test?) > > * When to refactor existing tests > > * At what point do you make these decisions? > > I'd like to encourage you to discuss your approaches along these lines, > > because I think it would be of great interest across all the WMF dev > teams. > > > This essay has been going around. There's a lot to it IMO. > > http://www.rbcs-us.com/documents/Why-Most-Unit-Testing-is-Waste.pdf > > tl;dr "unit test" is another word for "assert". Now, *acceptance* tests ... > > > - d. > > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
