RE: current recommendations for tdd?
"'Donaldson, John' [email protected] [testdrivendevelopment]" <[email protected]> Wed, 23 Jul 2014 07:55:49 +0000
| Newsgroups | gmane.comp.programming.test-driven-development |
|---|---|
| Message-ID | <716D07F3CBA94244A0922E7A99837C3A24557BAD@G5W2731.americas.hpqcorp.net> |
Yes, NUnit is wonderful and Moq. If you’re using Visual Studio the built-in unit test framework is reasonable and well-integrated. And then add – ReSharper. John D. From: [email protected] [mailto:[email protected]] Sent: 22 July 2014 23:00 To: [email protected] Subject: Re: [TDD] current recommendations for tdd? TDD, or at least the ideas behind it, is a lot older than that. NUnit and SpecFlow are both pretty awesome. There are also a number of good mock tools: NSubstitute, Rhino, Moq, etc. You should play with a few to find a style that suits you. On Tuesday, July 22, 2014, [email protected]<mailto:[email protected]> [testdrivendevelopment] <[email protected]<mailto:[email protected]>> wrote: Hello, I was curious about the current state of TDD. Obviously, it's 10+ years old at this point. I wanted to find out which practices and tools are currently favored for TDD. I'm guessing that these may have evolved a bit over the years. I'm a .NET developer. I prefer simple design for unit test implementation. I prefer to use free tools for unit testing. Which practices and tools would you use/recommend if starting a new .NET project from scratch today?