Home > Archive > Extreme Programming > May 2007 > UnitTest++
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Andy Champ 2007-02-18, 7:00 pm |
| I've just seen a post from Phlip, where he says
"And don't use CppUnit. Use UnitTest++, from here:
http://unittest-cpp.sourceforge.net/
Much leaner and cleaner architecture."
I've seen cppunit, and I wasn't that impressed. As MS users, we're
included to VS Team System, purely because it has some nice wizards and
handles all three of our languages - proper C++, Managed C++ and C#.
What do others think?
Phlip, please don't be offended. I suspect you do know what you are
talking about. If I thought you didn't, I wouldn't bother to ask this.
However, I don't *know* you know - IYSWIM.
Andy
| |
| Phlip 2007-02-21, 10:01 pm |
| Andy Champ wrote:
> I've seen cppunit, and I wasn't that impressed. As MS users, we're
> included to VS Team System, purely because it has some nice wizards and
> handles all three of our languages - proper C++, Managed C++ and C#.
>
> What do others think?
Uh, this group is kind'a lean compared to the mailing lists.
I want to know if you can push that Team System outside its envelop. I hope
MS doesn't think that Wizard-Driven Development has value beyond marketing!
The point of UnitTest++ is it's sub-minimal. The test cases and assertions
are reduced almost to a language extension. (Which is the better direction
for TDD research.) So I don't see the need for a Wizard for them, just as I
don't see the need for a Wizard for each 'if' statement.
The code that TDDs UnitTest++ itself is exemplary. If MS's WDD can generate
the same quality of code, great!
--
Phlip
[url]http://www.greencheese.us/Z Land[/url] <-- NOT a blog!!!
| |
|
|
|
|
|
|
|