I agree. It is silly for MS to not have included the testing framework with
all versions. In my opinion, it is these business decision that might make
people choose not to use their testing framework. The last thing that a
company needs to wonder if the version they have has all the bells and
whistles. Also, companies may allow their developers to work from home who
may have their own copy of VS.NET. Most likely the individual will not be
shelling out thousands for the IDE, but they still want unit testing. Why
go through the hassle when nUnit has a proven track record and is free for
all IDE and framework versions.
"Jon Skeet [C# MVP]" <sk***@pobox.com> wrote in message
news:MP************************@msnews.microsoft.c om...
Patrik Löwendahl [C# MVP] <pa**************@home.se> wrote:
The unit testing tools are only a part of Team System for System
Developers
and Team System for Testers. If you don't have either versions, you can
still
get an integrated experience by using NUnit and TestDriven.NET.
Indeed. It's as if MS believe that unless you're part of a large
enterprise development team, you don't need to do unit testing - or at
least that it's not very important.
<rant>
The silly thing is that I don't think it would have cost them *any*
sales of VSTS to include unit testing in Pro (or even Express, if I had
any say about it). No-one's going to make a purchasing decision based
on whether they can use the MS unit testing framework or whether they
have to use NUnit. MS could have taken huge amounts of unit testing
mind-share off NUnit in one fell swoop. From one I've seen of their
testing UI, I'm glad they didn't, mind you.
Still, it's not like any free IDEs have integrated unit testing, is it?
Eclipse doesn't have it, does it? Oh, wait a minute...
</rant>
--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog:
http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too
