[Cppunit-devel] Re: RE: Integrating CppUnit Windows edition...

[<bl...@cl...>]

>I must admit, autoconf doesn't help you a single bit, if you use MSVC++, =
but
>I think .dsw and .dsp files can easily be added to the tree, if someone
>supplies them.
  Yes, having it compiling on VC++ was not difficult (some missing std::, =
and a iterator on a vector<Test *const> instead of a const=5Fiterator on a=
 vector<Test *>, and setting up the project. =

  There is also the need to change the =23include =22TestCase=22 to someth=
ing like =23include <TestCase> or =23include <cppunit/TestCase.h> (which i=
s better? I prefer the second because its avoid conflict but...).
  And that's true, the use of doxygen makes a very nice and useful documen=
tation (though the doc is not up to date (think TestCase autoregistration.=
..))

>platform. But I think in one of the SourceForge forums there must be some
>docs about it, you're not the only SourceForge member working on a window=
s
>system. =

  Yes, I found a few thing. I'll try it this evening. It's not your simple=
 point and click... And the docs are not as clear as I whish they were.

>diff utility. To make a diff between two directory trees (the original
>untouched one, and one you modified) use: =

>
>diff -Naur cppunit.orig cppunit > cppunit.patch
  I'll do this. As far as I know, the diff function of WinCVS can not prod=
uce patch file.

>That one will definitely go in. Note that for your and mine (in)convenien=
ce,
>I've started moving files around (only the header files I believe) after =
the
>1.5.4 release. I expect to do some more shuffling, to keep the framework
>sources from the extension sources.
  Let me know when you have a relatively stable version. Are those change =
in CVS HEAD ?

>
>        - AutoRegisterSuite, a set of macros to make your life easier. Ye=
t,
>
>Arrggh, did you say 'macro'? Sorry, I'm very allergic to macros=21 :-) =

  Yes, my usual feeling. I'll write about that in the dev mailing list. Bu=
t as usual, it's an optionnal features. You don't like it, you don't use i=
t...

>        - TestRunner GUI application for Windows.
>
>Yes, I'd like to see that back in the main tree too, even though I won't =
use
>it. I think it's one of the reasons win32 people still stick to Michaels
>version. Having it in the tree hopefully will encourage other people to d=
o
>KDE and GNOME ports too. =

   Humm... I actualy enhanced it to make it more usuable (I believe so, at=
 least).

>However, I do prefer a cross platform TestRunner. Therefore one of my
>ambitions is to couple the JUnit runner to CppUnit tests through standard
>in- and output and XML test reports. Besides the cross platform support t=
his
>has another benefit: by keeping the code needed to build unit test minima=
l,
>one also minimizes the chance of conflicts, e.g. MFC vs other widget set =
or
>Java green threads vs POSIX threads. =

  We'll have to discuss that point on the mailing list. There plenty of pr=
o/cons and how. I'd like to see what you aim exactly. I have further idea =
about integrating Unit testing with the IDE (having a Add-Ins that collect=
 failed test location and allows you to go just there would be nice).

>> For technical discussions about CppUnit development, please join the
>> devel mailinglist.
  Well, I sent the first mail: Test Registry... ;-)

  Baptiste.

---
Baptiste Lepilleur <gaiacrtn=40free.fr>
http://gaiacrtn.free.fr/index.html
Language: English, French