Depending on how soon you want 1.8.0 to be, here is a list of feature
that are simple to implement:
1) CPPUNIT_TEST_EXCEPTION( method, ExceptionType)
2) CPPUNIT_TEST_FAIL( method )
3) add a flag to TestFailure distinguishing error/failure, retain only
one collection to store result
(see other mail)
4) CPPUNIT_TEST_SUITE_NAMED_REGISTRATION( TestFixtureType, SuiteName ) :
register the fixture's suite in a suite of the specified name.
5) Qt TestRunner (I've got it working, need feedback and help to use
TMAKE to build a library instead of an application)
6) ASSERT_EQUAL support for two differents compatible types
1 & 2) are already done (need to be integrated & documented though).
3) is a bit of work, but not much.
4) only really need the macro declaration & documentation
5) need some collaborative work, meaning unpredicatable amount of
time...
6) need to find suitable traits. Probably some discussion there...
Those are mostly simple stuff that hinder me, and other I guess, when I
use CppUnit...
Baptiste.
---
Baptiste Lepilleur <gai...@fr...> http://gaiacrtn.free.fr/index.html
Author of The Text Reformatter, a tool for fanfiction readers and writers.
Language: English, French (Well, I'm French).
|
