Re: current recommendations for tdd?
"Adam Sroka [email protected] [testdrivendevelopment]" <[email protected]> Tue, 22 Jul 2014 14:00:02 -0700
| Newsgroups | gmane.comp.programming.test-driven-development |
|---|---|
| Message-ID | <CALaPUVevLp2+q4wQCsiTCv=KhXE+0sEP0UX7iGnyT7AKgt0TLA@mail.gmail.com> |
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? > > >