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

156794Re: [XP] TDD/unit testing in a team without unit testing

Expand Messages
  • james@renaissancesoftware.net
    Jan 11, 2012
    • 0 Attachment
      Hello Luke

      I just wrote a blogpost about why manual test is unsustainable. It is not a article about TDD though it might give some insight into the need for automated tests. The other recomendations people made on the list are good ones.


      There are lot's of good reasons to do TDD. The most compelling one for new people in my opinion is defect prevention. Here's an article about that


      I've got some other articles onTDD that might help make a case to get some people to try TDD.

      thanks, James

      James Grenning Author of TDD for Embedded C
      www.renaissancesoftware.net http://pragprog.com/titles/jgade/

      On Jan 11, 2012, at 4:45 AM, Lukasz Szyrmer wrote:

      > Hi all,
      > Just wondering if anyone might have some experience with or know of some good resources on doing TDD within a team that doesn't feel strongly about automated testing. Ron Jeffries mentions such a concept in passing in his book Extreme Programming Adventures in C#.
      > Generally speaking, I can see the benefits of unit testing. We do some interface level-behavioural testing, particularly where it's easy, but I'm not sure if we're really getting the benefit from our efforts.
      > We already have a CI environment which builds on every check-in, and this is quite useful. On some of our programs, tests are somewhat hard to write, as most of our desktop programs are traditional desktop (Borland) C++ apps with windows UIs, so there isn't a separation of concerns like with MVVM in WPF for example.
      > In particular, is there a good way of writing tests against one class without being too disruptive for the project? Are there any intermediate steps possible? For example, are there any easy ways to unit test a specific fragile class? Is this just an issue of figuring out how to apply dependency injection in this context? Does it make sense to pull the class out context?
      > I realize it would be good to get everyone on board with TDD on one hand, and lower-level unit testing on the other, but it's hard to sell if I have little experience with it.
      > Luke
      > Linedata Limited
      > Registered Office: 85 Gracechurch St., London, EC3V 0AA
      > Registered in England and Wales No 3475006 VAT Reg No 710 3140 03
      > [Non-text portions of this message have been removed]

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