locked
Test-Driven Development in Microsoft.NET RRS feed

All replies

  • As a slight aside, I was wondering if you include unit tests in your continuous integration and if so what method do you use to distinguish between a test that has genuinely failed as opposed to one that you expect to fail ala TDD - or as someone said, 'deferred its success' Wink


    Tuesday, July 29, 2008 9:03 PM
  • I am not fanatically TDD, but I do use NUnit to test as I think everyone should. It is debatable to a lot of folks as to the extent some go with TDD.

     

    It's a good methodology, I recommend using tests, recommend refactoring. Pair programming is very helpful.

     

    Just think of it in terms of that, a methodology that can help, but don't go over board with it.

    Tuesday, July 29, 2008 9:11 PM
  • I used NUnit until Microsoft integrated a testing framework into the Visual Studio IDE;

     

    http://msdn.microsoft.com/en-us/library/ms379625(VS.80).aspx

     

    NMock is useful for removing dependancies on external resources (databases for example);

     

    http://www.nmock.org/

     

    I agree that in most environements TDD is a useful practise and everyone should give pair programming a try as my experiences of this have been good as well.

     

    Wednesday, July 30, 2008 9:59 AM
  • Thanks G Moore!

     

    Wednesday, July 30, 2008 1:10 PM
  • I still use NUnit with TestDriven.net to integrate it into the IDE, I found it easier to use when you're testing in a stand-alone mode. For mocking I prefer TypeMock.

     

    I've never formally done pair-programming I'm still not sure about it, but I won't knock it till I've tried it.

     

     

    Wednesday, July 30, 2008 4:56 PM
  • Thanks for the input pkr2000!

    Wednesday, July 30, 2008 5:42 PM