RE: [cdt-dev] CppUnit integration

["Lescuyer, Martin " <mlescuyer@xxxxxxxxxxxx>]

Many thanks for suggestions.
If it is true to say the CppUnit is not (yet?) a de-facto standard as can be
JUnit for Java, Mike is also right in mentionning that no standard is
available today for C/C++. So why not CppUnit, which concepts are the
closest from JUnit (it is the official port to C++).
The JDT and JUnit plugins target the Java developper (both application
developpers and plugin developers). 
The CDT and CppUnit would only target the C/C++ application developer (I
mean that CppUnit would have exactly the same audience than the CDT itself).
C-only shops can use any C++ testing framework as soon as their compiler is
a C/C++ one (which is now classic).
The C/C++/embedded market is historically segmented, and many companies have
their own tools. Porting/Importing existing test cases to a new framework is
definitely an issue for such people, but this is true for any new testing
framework.
Standardizing data collection protocols and display between IDE and test
programs is addressed by the Hyades project, which scope is much larger than
the C/C++ developper. We should not impose Hyades adoption for a pretty
little test case... and Hyades (http://www.eclipse.org/hyades) target dates
seem to be a bit far in the future.

Martin



-----Message d'origine-----
De : Schaefer, Doug [mailto:dschaefer@xxxxxxxxxxxx]
Envoye : samedi 15 fevrier 2003 16:05
A : 'cdt-dev@xxxxxxxxxxx'
Objet : RE: [cdt-dev] CppUnit integration


Here's my $0.02.

There is an enhancement request logged into bugzilla (for what that's worth)
requesting CPPUnit integration:

	http://bugs.eclipse.org/bugs/show_bug.cgi?id=23546

One thing to understand is that the JDT and the JUnit integration form part
of the Eclipse Platform SDK.  Unless we can convince people to write plugins
in C++ (:-)) our target audience is different.  In that light, including
CPPUnit in the CDT isn't as clear cut as I first thought.

One possible consideration is the new Hyades project which may also be a
candidate for this integration.  It appears, however, that they do not yet
have the infrastructure set up for submitting code (which actually goes to
the same place, BTW).

I haven't made anything clearer, but food for thought...

Doug Schaefer
Senior Staff Software Engineer
Rational - the software development company
Ottawa (Kanata), Ontario, Canada
 

-----Original Message-----
From: Mike Capp [mailto:aphelion@xxxxxxxxxxx] 
Sent: Friday, February 14, 2003 4:19 PM
To: cdt-dev@xxxxxxxxxxx
Subject: Re: [cdt-dev] CppUnit integration

On Fri, 14 Feb 2003 15:01:42 +0100, Lescuyer, Martin 
<mlescuyer@xxxxxxxxxxxx> wrote:

> From this, the CDT works the same without this plugin. But making a 
> parallel
> with the JDT, my thought is that it can be part of the CDT.
> Then the question is "Does the CppUnit framework itself should be part of
> the CDT or not".

I think the Java parallel is potentially misleading here. CppUnit has 
nothing *like* the mindshare among C++ developers that JUnit has for Java 
or NUnit for C#. A lot of people use other test frameworks (Boost.Test, 
cxxunit, home-grown), and even those that do use CppUnit generally end up 
modifying it to suit their own preferences. Pure C shops might not take too 
well to a C++ test framework either. Where there's a major investment in 
test code for some other framework, people aren't going to want to rewrite 
all that code by hand, and trying to convert it automagically doesn't sound 
like much fun.

I can see a standardized unit-test plugin interface or a recommended 
easily-parsed stdout format being very useful; folk could just write 
adaptors or sed scripts or whatever for their own framework. But I'm 
worried that bundling vanilla CppUnit with the CDT would just bulk up the 
distro without getting much use.

Cheers,
Mike

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev