Re: Test-driven development

Hi,

I have used both JUnit and NUnit and fornd them very helpful... They
are good for unit testing the modules and u can check that nothing has
broken by the new changes introduced in your code .

Infact, I would like to add this in good programming practices... this
is reduces time and effort put in on discovering that there was some
bug introduced by some minor change in a method.

.

Relevant Pages

  • Re: VS 2005 Pro and Unit Tests etc.
    ... nessasarily monetory. ... MS ripped the idea from the OS community - quite a great hypocrisy ... > NUnit is based on JUnit, so I guess the JUnit authors got ripped off, too? ...
    (microsoft.public.vsnet.general)
  • Re: JUnit et al approach - criticisms
    ... Keep in mind, JUnit are just unit testing frameworks and as such can be used in may ways. ... TDD uses unit tests as a means of capturing the design that we create, much like UML diagrams capture design. ...
    (comp.lang.java.programmer)
  • Re: unit testing in vs.net 2005?
    ... > and Team System for Testers. ... > get an integrated experience by using NUnit and TestDriven.NET. ... sales of VSTS to include unit testing in Pro (or even Express, ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: unit testing in vs.net 2005?
    ... it is these business decision that might make ... people choose not to use their testing framework. ... shelling out thousands for the IDE, but they still want unit testing. ... > get an integrated experience by using NUnit and TestDriven.NET. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: TypeInitializationException / forcing all static ctors to run on startup
    ... MbUnit, but I don't know that that's any more suitable for small ... Once you've used NUnit a few times, you'll think nothing of using it, ... I consider TWO types of unit testing, ... implying no run-time unit testing. ...
    (microsoft.public.dotnet.languages.csharp)