Re: current recommendations for tdd?

NUNit (with testcase attributes), FakeItEasy, NCrunch = awesome


On Wed, Jul 23, 2014 at 9:55 AM, 'Donaldson, John' [email protected]
[testdrivendevelopment] <[email protected]> wrote:

>
>
>  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]
> [testdrivendevelopment] <[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?
>
>
>
>
>     
>



-- 
Thanks,

Roy Osherove

   - *@RoyOsherove* <https://twitter.com/RoyOsherove>
   - Read my new book *Notes to a Software Team Leader
<http://TeamLeadSkills.com>*
   - Or *my new course* about Beautiful Builds
<http://skills.osherove.com/beautiful-builds-and-continuous-delivery-patterns>
and Continuous Delivery
   - +47-96-90-22-15 (Oslo Time)