NUNIT vs VSTS ?? Which is better ?

[Parag]

Hi,
I am trying to figure out best testing tool for my project. I have
narrowed down my requirements to two tools NUNIT and VSTS unit. But I have
used neither and I have to use only one of them. Hence can someone who has
used them before share his/her experience on them so that I can get a better
idea and make a proper choice ?
Any link or suggestions are also welcome.

Thanks and Regards,
Parag
MTS,Persistent Systems Private Limited

[Peter Rilling]

They both really do the same thing. Here are the reasons that I would
choose NUnit over MSs version.

1) Unit testing in VS can only be done through a high-end version of the
product. If all your developers do not use the team version, then they will
not be able to use the MS testing framework.
2) NUnit has been around for years with a proven track records.
3) NUnit if available for many versions of the framework and also Mono (I
think).
4) NUnit does not couple the testing to just an MS environment.
5) External tools may work better with NUnit such as build systems.
"Parag" <pa************ @persistent.co. in> wrote in message
news:uc******** ******@TK2MSFTN GP10.phx.gbl...

Hi,
I am trying to figure out best testing tool for my project. I have
narrowed down my requirements to two tools NUNIT and VSTS unit. But I have
used neither and I have to use only one of them. Hence can someone who has
used them before share his/her experience on them so that I can get a
better idea and make a proper choice ?
Any link or suggestions are also welcome.

Thanks and Regards,
Parag
MTS,Persistent Systems Private Limited

[William Stacey [MVP]]

I have used both. nunit is nice, but VS test is suit. I use it in the VSDev
version.

--
William Stacey [MVP]

"Parag" <pa************ @persistent.co. in> wrote in message
news:uc******** ******@TK2MSFTN GP10.phx.gbl...
| Hi,
| I am trying to figure out best testing tool for my project. I have
| narrowed down my requirements to two tools NUNIT and VSTS unit. But I have
| used neither and I have to use only one of them. Hence can someone who has
| used them before share his/her experience on them so that I can get a
better
| idea and make a proper choice ?
| Any link or suggestions are also welcome.
|
| Thanks and Regards,
| Parag
| MTS,Persistent Systems Private Limited
|
|

[Cowboy (Gregory A. Beamer) - MVP]

They are pretty equivalent. The VSTS tags are a bit closer to the Attributes
throughout the framework, which is nice. If you are using Team System, I
would go ahead and use VSTS. If not, nUnit is a fine alternative. I use both,
depending on the project location.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

*************** ************
Think Outside the Box!
*************** ************
"Parag" wrote:

Hi,
I am trying to figure out best testing tool for my project. I have
narrowed down my requirements to two tools NUNIT and VSTS unit. But I have
used neither and I have to use only one of them. Hence can someone who has
used them before share his/her experience on them so that I can get a better
idea and make a proper choice ?
Any link or suggestions are also welcome.

Thanks and Regards,
Parag
MTS,Persistent Systems Private Limited

[William Stacey [MVP]]

There are two things that I really like more about VS. Better overall
integration with VS. And you can right-click a method and gen the test stub
automatically. You also get code coverage results with integration to show
what lines where not covered. Not sure what nunit offers today in that
regard.

--
William Stacey [MVP]

"Cowboy (Gregory A. Beamer) - MVP" <No************ @comcast.netNoS pamM> wrote
in message news:AF******** *************** ***********@mic rosoft.com...
| They are pretty equivalent. The VSTS tags are a bit closer to the
Attributes
| throughout the framework, which is nice. If you are using Team System, I
| would go ahead and use VSTS. If not, nUnit is a fine alternative. I use
both,
| depending on the project location.
|
| --
| Gregory A. Beamer
| MVP; MCP: +I, SE, SD, DBA
|
| *************** ************
| Think Outside the Box!
| *************** ************
|
|
| "Parag" wrote:
|
| > Hi,
| > I am trying to figure out best testing tool for my project. I have
| > narrowed down my requirements to two tools NUNIT and VSTS unit. But I
have
| > used neither and I have to use only one of them. Hence can someone who
has
| > used them before share his/her experience on them so that I can get a
better
| > idea and make a proper choice ?
| > Any link or suggestions are also welcome.
| >
| > Thanks and Regards,
| > Parag
| > MTS,Persistent Systems Private Limited
| >
| >
| >

[John Murray]

While NUnit doesnt offer strong vstudio integration, or coverage there
are a number of 3rd party tools that do this integration .... I
personally prefer TestRunner.

That being said, I really believe that the market positioning of VSTS by
MS puts it out of reach for most independent developers and small
development shops. That being said, IMHO, I personally see NUnit as the
best option.


William Stacey [MVP] wrote:

There are two things that I really like more about VS. Better overall
integration with VS. And you can right-click a method and gen the test stub
automatically. You also get code coverage results with integration to show
what lines where not covered. Not sure what nunit offers today in that
regard.

[Jon Skeet [C# MVP]]

William Stacey [MVP] <wi************ @gmail.com> wrote:

There are two things that I really like more about VS. Better overall
integration with VS. And you can right-click a method and gen the test stub
automatically.
Does it assume a "one test method per concrete method" model though?
That's what Eclipse assumes when you ask it to generate a test skeleton
- and it's almost never what I actually want. (I just start with a bare
test class.)

It's also not useful for true TDD, where the tests come before the code
they're calling.
You also get code coverage results with integration to show
what lines where not covered. Not sure what nunit offers today in that
regard.

You can run NUnit over NCover. I haven't used it much myself, but I've
done enough to know it works.

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

[William Stacey [MVP]]

| That being said, I really believe that the market positioning of VSTS by
| MS puts it out of reach for most independent developers and small
| development shops. That being said, IMHO, I personally see NUnit as the
| best option.

Remember you don't need VSTS to use it. You need at lease VSDev IIRC. I
have VSDev with the MSDN. Am I wrong?

I thought same about NUnit before I really used VS. One day I *forced
myself to use VS for good sized library. I would not go back now.
Different strokes. Code coverage is big.

--
William Stacey [MVP]

[William Stacey [MVP]]

| Does it assume a "one test method per concrete method" model though?
| That's what Eclipse assumes when you ask it to generate a test skeleton
| - and it's almost never what I actually want. (I just start with a bare
| test class.)

Not 100% sure what you mean. By default, if you just have a new class, it
will stub out (pretty nice) each method (w/ overload), constructor and
properties IIRC. And even the private methods if desired. You can then add
any amount of new test methods, delete or change existing ones. You can do
any amount of tests (high, low, range, expected exceptions, etc) inside one
method or break them out as you want. Get nice coverage results, see what
failed. Click on failed tests to jump to that code. Click on uncovered
results to jump to that method and see the uncovered lines in color, etc.
Lot more going on here then just red and green traffic lights.

| It's also not useful for true TDD, where the tests come before the code
| they're calling.

They encourage and support either. Possibly the easiest way is to stub out
your class with exception in the body, then gen your tests over the class.
Then just keep adding code to your class as you go and iterating your tests.
You could also just stub out your tests without any class first, but not
sure how valuable that would be. Its all just code, so you can do what you
want.

| > You also get code coverage results with integration to show
| > what lines where not covered. Not sure what nunit offers today in that
| > regard.
|
| You can run NUnit over NCover. I haven't used it much myself, but I've
| done enough to know it works.

Have nothing against NUnit. I can only suggest trying the test and code
coverage in VS (if you got the MSDN w/ VSDev). I think you will be very
happy with the whole solution.

--
William Stacey [MVP]

[John Murray]

code coverage is available when you use TestRunner and NUnit as well
..... at a fraction of the cost
William Stacey [MVP] wrote:

| That being said, I really believe that the market positioning of VSTS by
| MS puts it out of reach for most independent developers and small
| development shops. That being said, IMHO, I personally see NUnit as the
| best option.

Remember you don't need VSTS to use it. You need at lease VSDev IIRC. I
have VSDev with the MSDN. Am I wrong?

I thought same about NUnit before I really used VS. One day I *forced
myself to use VS for good sized library. I would not go back now.
Different strokes. Code coverage is big.