RE: [Cppunit-devel] What's NEW?

[Summerwill, B. <BSu...@eu...>]

>> We might also want to include an "expected change" section somewhere:
>> - include directory structure revision

I've seen this referred to a few times.  What revision is planned to the
include
directory structure?


Cheers,
Bob





-----Original Message-----
From: Baptiste Lepilleur [mailto:bl...@cl...]
Sent: 23 September 2001 19:59
To: Cpp Unit Develpment Mailing List
Subject: Re: [Cppunit-devel] What's NEW?


----- Original Message -----
From: "Steve M. Robbins" <ste...@vi...>
To: "CppUnit Development" <cpp...@li...>
Sent: Sunday, September 23, 2001 6:50 AM
Subject: [Cppunit-devel] What's NEW?


> I'm working on the final documentation changes for release 1.6.0.  I'm
> going to have a quick sweep through the doxygen docs, then make a new
> (and hopefully final) snapshot before making the release Sunday night.
>
> I'd like to put together a list of the *major* user-visible changes
> (bug fixes and portability enhancements don't count, for example) to
> CppUnit since release 1.5.5.  This list should also answer the
> question "do I have to update any bits of my source code to move from
> 1.5.5 to 1.6.0?"
>

For compatibility related change, I think you covered most of them.

There are also some new functionnality provided by cppunit:
- VC++ integration for MFC TestRunner
- CPPUNIT_ASSERT_MESSAGE( message, expr)
- TestCaller can expect exception
- better setUp()/tearDown() failure support
- better documentation
- INSTALL-WIN32.txt that detail stuff for VC++ platform (project,
compilation and use). Also includes a tiny FAQ with common questions
relating to cppunit/VC++
- More MFC TestRunner examples.

We might also want to include an "expected change" section somewhere:
- include directory structure revision
- namespace for TestRunners
- TestCaller exception support provided with decoration.
- TestFixture
(stuffs we haven't discussed yet but I'd like to change/evolve:
  - Change TestFailure to store a flag indicating if it is an error or a
failure (failed assertion). That would make writing TestRunners a lot
easier.
  - support for 2 differents types in CPPUNIT_ASSERT_EQUAL (I'm kind of fed
up having to cast compatible types when C++ could do that. Make the
assertions harder to read too)
)

> By looking at the ChangeLog, I have generated the following list.  Can
> you help me complete it?  I'm sure that I have left out some stuff
> from the MS side of things.  And did anything change w.r.t. the
> registry?

   What w.r.t. means ?

    The only stuff that relate to the registry is DSPlugIn which is a COM
component and register itself there (it's done at compilation time, and VC++
do it when you add the add-in too I think).

    - VC++ default is now to use type_info. CPPUNIT_DONT_USE_TYPEINFO must
be define if you don't want to use type_info to name suite.

    - A experimental test plug-in runner.

    Notes that the actual implementation of CPPUNIT_TEST_xxx macros have
changed. It use a factory to instiate fixture instead of template methods.


>
> This list will appear in the file NEWS.
>
> Thanks,
> -Steve

    Well, that all I could find/remember.

    May be we should maintain a separate log which would contain change that
impact the user from one version to another ?

Baptiste.


>
>
> New in CppUnit 1.6.0
> --------------------
>
>
> * All CppUnit macros now begin with "CPPUNIT_".
>
>   Macros CU_TEST_SUITE, CU_TEST, CU_TEST_SUITE_END, CU_TEST_SUB_SUITE,
>   and CU_TEST_SUITE_REGISTRATION are renamed but are otherwise unchanged;
>   they take the same arguments, and have the same effect.  A string
replace
>   of CU_ --> CPPUNIT_ will be necessary to update your code.

>
>   Macros assert, assertEqual, and assertDoublesEqual, have been replaced
>   by CPPUNIT_ASSERT, CPPUNIT_ASSERT_EQUAL, and
CPPUNIT_ASSERT_DOUBLES_EQUAL,
>   respectively.  Macro assertLongsEqual is replaced by
CPPUNIT_ASSERT_EQUAL.
>   The old assert macros can be used if your sources #define
>   CPPUNIT_ENABLE_NAKED_ASSERT before including any CppUnit headers.
>
>
> * Equality assertion CPPUNIT_ASSERT_EQUAL(expected,actual) can test
>   any type of expression.  The types of "expected" and "actual" must
>   be the same; use a cast if necessary.
>
>
> * Equality tested using CPPUNIT_ASSERT_EQUAL may be re-defined using
>   a traits class.  Ditto for the string representation used in the
>   diagnostic messages.
>
>
> * CppUnit has a unit test for itself!

---
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).


_______________________________________________
Cppunit-devel mailing list
Cpp...@li...
https://lists.sourceforge.net/lists/listinfo/cppunit-devel