CppUnit 2.0 is a full rewrite. I've already done much work on it (based on
all my experience on enhancing CppUnit). The resulting core is a lot more
cleaner/flexible than the current version CppUnit.
I'll try to put it online with some rationale when I have more time. I'm
currently focusing on getting the first automated refactoring to work on
Refactoring Assistant (http://cpptool.sf.net), so this will have to wait a
bit.
Concerning the dependency features, I have a hard time seeing how this can
be done and remain practical. Does JUnit provides something like that ?
Why do you need to document the Unit Test ? Isn't the method name enough ?
Baptiste.
----- Original Message -----
From: "Philippe Lavoie" <phi...@ca...>
To: "Gary Granger" <gr...@at...>;
<cpp...@li...>
Sent: Wednesday, October 30, 2002 3:39 PM
Subject: [Cppunit-devel] What's next for cppunit?
Hi,
I'm just wondering if there are any planned new features for a 2.0
release of cppunit.
The list is pretty quiet and cppunit does a great job.
I think most comments are about the documentation.
Personnaly, my only issue is with the integration with Visual Studio
.NET (it would be nice to have something that helps create the skeleton
of a test case for you, but hey. Copy/paste works too ;)
Any missing feature that are being worked on? I'm adding ideas below
just to get a discussion started :)
- TestCase dependencies, in some cases if test case A fails, no
other should be run as they will all fail. Maybe just set there results
to D (dependency failure).
- TestCase documentation, I use doxygen to view the test case
documentation. But it would be nice to use the XML output option with a
verbose setting to get at least a short line of what the test is about.
May the source be with you.
Phil
|
