Automated unit tester

  • Thread starter Thread starter David Dvali
  • Start date Start date
Tim said:
Another useful tip is if you use NUnit, you'll be pleases when VS2005 comes
out in 3 months as it has an NUnit clone built in.
Click to expand...

ROFL. I think this is the funniest thing I've heard anybody say about
Team System :-)



Oliver Sturm
 
Tim Haughton said:
Another useful tip is if you use NUnit, you'll be pleases when VS2005 comes
out in 3 months as it has an NUnit clone built in.
Click to expand...

As far as I'm aware, that's only for Team System - i.e. the really
expensive edition. Apparently MS think that mere professionals don't
use unit tests :(

(Things may have changed, of course - and it would be nice if they did.
I can't see unit testing on the beta 2 of VS 2005 Professional Edition
though.)
 
Oliver Sturm said:
The "NUnit clone" bit :-)
Click to expand...

why not go whole hog and just say it includes a clone of NUnit which in
itself is a clone of JUnit.

Its not like NUnit was a brilliant individual accomplishment.
 
Daniel,
Wasn't the original xUnit implemented in SmallTalk?

Kent Beck's book "Test-Driven Development" has an implementation in Python.

I don't consider the Unit Test feature of Team System an NUnit clone as much
as yet another implementation of a TDD platform. Don't get me wrong I do
like the Unit Test feature of Team System....

I do like the leveraging of Generics in the Unit Test feature of Team
System.

Jay

message |
| | > Tim Haughton wrote:
| >
| >> The NUnit bit? Or the bit about MS releasing in 3 months? ;�)
| >
| > The "NUnit clone" bit :-)
|
| why not go whole hog and just say it includes a clone of NUnit which in
| itself is a clone of JUnit.
|
| Its not like NUnit was a brilliant individual accomplishment.
|
|
 
Jay B. Harlow said:
Daniel,
Wasn't the original xUnit implemented in SmallTalk?
Click to expand...

I'm not sure off hand, actualy, but still the silliness remains: calling
something a clone of something that is a clone of something that is probably
a clone of something.
I don't consider the Unit Test feature of Team System an NUnit clone as
much
as yet another implementation of a TDD platform. Don't get me wrong I do
like the Unit Test feature of Team System....
Click to expand...

Neither do I, honestly. I like Team System's approach a bit better. Better
integration, mostly, but some of the features it offers were nice.
 
Jon Skeet said:
As far as I'm aware, that's only for Team System - i.e. the really
expensive edition. Apparently MS think that mere professionals don't
use unit tests :(
Click to expand...

OK now your confusing me. I was convinced I had not installed Team System,
I'll have to check when I get back to base.

MS also think that only architects use UML too.

--
Regards,

Tim Haughton

Agitek
http://agitek.co.uk
http://blogitek.com/timhaughton
 
Daniel said:
why not go whole hog and just say it includes a clone of NUnit which in
itself is a clone of JUnit.

Its not like NUnit was a brilliant individual accomplishment.
Click to expand...

The thing I was laughing about was merely that I'm sure Microsoft won't
like anybody calling an important part of their flagship product for
developers a clone of something.

And personally, I wouldn't call an implementation of a concept in
another language a clone - at least not in the negative sense that the
word somehow implies. Sure, NUnit may not have been a brilliant
individual accomplishment, but it was necessary work done well (at least
in v2) on the .NET platform.


Oliver Sturm
 
Oliver Sturm said:
The thing I was laughing about was merely that I'm sure Microsoft won't
like anybody calling an important part of their flagship product for
developers a clone of something.
Click to expand...

Normally I think you'd be right. But in this case, Microsoft *want* it to be
seen as an NUnit clone to speed people's transition from NUnit. And I've
been told by more than one person at MS that this is so.

I know that Jim Newkirk was working on a conversion tool, wonder if that's
done yet.

--
Regards,

Tim Haughton

Agitek
http://agitek.co.uk
http://blogitek.com/timhaughton
 
Tim said:
Normally I think you'd be right. But in this case, Microsoft *want* it to be
seen as an NUnit clone to speed people's transition from NUnit. And I've
been told by more than one person at MS that this is so.
Click to expand...

Okay, I believe you ;-) Still, "clone" has that funny sound to it: it
says that the clone is a copy, nothing more and nothing less than the
source, right? I don't think it's going to be long until MS starts
telling us that their implementation has bells and whistles that are not
in NUnit - so it's not a clone, after all, and I'm sure they'll find
that distinction important.
I know that Jim Newkirk was working on a conversion tool, wonder if that's
done yet.
Click to expand...

I've read about that, but I haven't had a look.



Oliver Sturm
 
Daniel O'Connell said:
why not go whole hog and just say it includes a clone of NUnit which in
itself is a clone of JUnit.
Click to expand...

NUnit v1 was a JUnit clone. v2 moved beyond JUnit. But that's like saying
that C# is 75% Java, 10% C++ and 15% VB. But wait, Java is 50% C++, and C++
is 35% C. Everything can be reduced to intrinsics, would it have added
anything to the thread? (note - I made these figures up). My calling it an
NUnit clone wasn't in any way intended as a criticism.
Its not like NUnit was a brilliant individual accomplishment.
Click to expand...

NUnit was a good community accomplishment. Good software developers writing
good software for developers.

--
Regards,

Tim Haughton

Agitek
http://agitek.co.uk
http://blogitek.com/timhaughton
 
Tim Haughton said:
NUnit v1 was a JUnit clone. v2 moved beyond JUnit. But that's like saying
that C# is 75% Java, 10% C++ and 15% VB. But wait, Java is 50% C++, and
C++
is 35% C. Everything can be reduced to intrinsics, would it have added
anything to the thread? (note - I made these figures up). My calling it an
NUnit clone wasn't in any way intended as a criticism.
Click to expand...

Hench why I never responded to you, but the poster who made a point about it
being funny. I'm not sure how it was humorous, considering calling it a
clone is pretty inaccurate to begin with, and calling it a clone of a clone
that was a clone of another clone would have been funny, but calling it a
clone on its own..nah. At best that comes off as is a neutral comment, at
worst a jab.
NUnit was a good community accomplishment. Good software developers
writing
good software for developers.
Click to expand...

Yes it was, although there were some disappointing things about it. I don't
put NUnit in the "Great" pile that some stuff goes into, merely passable.
 
Back
Top