Loading ...
Sorry, an error occurred while loading the content.

156797RE: [XP] TDD/unit testing in a team without unit testing

Expand Messages
  • Lukasz Szyrmer
    Jan 12, 2012
    • 0 Attachment

      Thanks for the Mikado method reference, as I wasn't aware of that one. Looks fantastic, because it seems to address the business payoff of using TDD while refactoring (i.e. not adding new features). I'm concerned about spending a lot of time (more importantly convincing others to spend lots of their time) on something that ends up proving largely what I already know, so hopefully that will clear things up a bit.


      Linedata Limited
      Registered Office: 85 Gracechurch St., London, EC3V 0AA
      Registered in England and Wales No 3475006 VAT Reg No 710 3140 03

      From: extremeprogramming@yahoogroups.com [mailto:extremeprogramming@yahoogroups.com] On Behalf Of George Dinwiddie
      Sent: 11 January 2012 19:12
      To: extremeprogramming@yahoogroups.com
      Subject: Re: [XP] TDD/unit testing in a team without unit testing
      Importance: High


      On 1/11/12 9:28 AM, Chris Hulan wrote:
      > Don't know if it will help sell your team on unit tests,
      > but Michael Feathers' _Working Effectively with Legacy Code_ is the bible for
      > how to add tests to existing code with minimum disruption.

      I second Chris' recommendation of WELC and suggest you pair it with the
      Mikado Method (http://mikadomethod.wordpress.com/book/)

      - George

      * George Dinwiddie * http://blog.gdinwiddie.com
      Software Development http://www.idiacomputing.com
      Consultant and Coach http://www.agilemaryland.org

      [Non-text portions of this message have been removed]
    • Show all 10 messages in this topic