. NET Testing Framework Advice
I'm aiming to present a unit testing structure right into the mix at my work. We're making use of Visual Studio 2005 (though we might be relocating to 2008 within the next 6 months) and also function largely in C#. If the structure has some sort of IDE assimilation that would certainly be best, yet I'm open to structures that do not have assimilation yet are still reasonably straightforward to ready up. I'm going to get resistance to it somehow, so if I can see to it what I'm pressing isn't a pain in the rear, that would certainly aid my instance.
The noticeable selection from the study I've done so much indicates nUnit, yet I would certainly such as to think of a person that's in fact utilized it prior to advising it to my group.
Has any person around made use of nUnit? If so, exist any kind of challenges or constraints of which I should realize? Exist various other excellent alternatives around? If so, if you've made use of both nUnit at that, I 'd substantially value a suggestion of the toughness and also weak points of them.
I would certainly claim mbUnit additionally, I such as having the ability to run a solitary examination sometimes simply by defining inputs and also result right over the examination function. Dreadful summary of what I suggest so here is a link that shows you what I mean.
NUnit is your best choice. With
TestDriven.NET, you get wonderful assimilation within
VS.NET. (Resharper additionally has a device examination jogger if you're utilizing it).
NUnit it straightforward to make use of and also adheres to a well-known standard. You'll additionally locate a lot of projects/tutorials/guides utilizing it which constantly aids.
Your various other major selection is possibly MBUnit, which is an increasing number of place itself as the
BDD structure of selection (combined with Gallio http://www.gallio.org).
Visual Studio 2008 has actually a constructed in examination task type that operates in a comparable means to NUnit, yet clearly has much tighter assimilation with
Visual Studio (can work on every construct and also reveals the cause a comparable means to the conversion results web page when updating remedy documents), yet it is clearly not as fully grown as NUnit as it's rather new and also I'm not exactly sure concerning just how it takes care of buffooning.
Yet it would certainly deserve checking into when your group relocates to