cppunit-devel — CppUnit Developer Mailing List

RE: [Cppunit-devel] URGENT: more information to be logged

[Michel A. <Arm...@si...>]

Maybe the "parameterized tests" approach we just developed may help you
here.
But currently this new feature isn't available in the CVS yet.

Regards,

bored

> -----Original Message-----
> From: Luis Joaquim [mailto:ljo...@cr...]
> Sent: Montag, 29. Juli 2002 17:03
> To: cpp...@li...
> Subject: [Cppunit-devel] URGENT: more information to be logged
> Importance: High
> 
> 
> Hello,
> 
>   I need to report more information about the tests, like a brief
>   description, the inputs and outputs.
> 
>   The programmer will write this fields (strings).
> 
>   I have thought on the implementation and it seems I have to change a
>   lot of files, and would my very hard future upgrades.
> 
>   Does anyone know a better solution?
> 
>   Does anyone have the some problem?
> 
>   Don't you think it would be a nice feature?
> 
>   Thanks in advance,
> 
>   Luis Joaquim
> 
> -- 
> Luis Joaquim
> Critical Software, SA
> EN1/IC2, Km 185,6, Banhos Secos, Santa Clara
> 3040-032 Coimbra
> Tel: +351.239.801300, Fax: +351.239.801319
> http://www.criticalsoftware.com
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: Dice - The leading online job board
> for high-tech professionals. Search and apply for tech jobs today!
> http://seeker.dice.com/seeker.epl?rel_code=31
> _______________________________________________
> Cppunit-devel mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppunit-devel
> 

Re: [Cppunit-devel] Bug(?) in cppunit-1.8.0

[Carlo W. <ca...@al...>]

On Fri, Aug 02, 2002 at 08:39:45AM +0200, Baptiste Lepilleur wrote:
> The QtTestRunner don't get compiled automatically. The makefile.am is only
> there to insure that it is distrubed in the tar ball.
> 
> You need to manually run the 'build' script in the src/qttestrunner
> directory.

I think you need to have a look at what ACTUALLY
goes into the tar that you release.  There seems to be
a lot missing.

For example, in the ChangeLog I find a references to
examples/qt/, but this directory is not there.  Other
directories or files might be missing as well.

There is no src/qttestrunner/build  script.
There is a src/qttestrunner/build.bat, but I am running linux
not DOS.  Trying to running that batch file gives me:

/usr/src/cppunit-1.8.0/src/qttestrunner>./build.bat
./build.bat: line 1: tmake: command not found
./build.bat: line 2: nmake: command not found
./build.bat: line 3: nmake: command not found

-- 
Carlo Wood <ca...@al...>

Re: [Cppunit-devel] Bug(?) in cppunit-1.8.0

[Baptiste L. <gai...@fr...>]

The QtTestRunner don't get compiled automatically. The makefile.am is only
there to insure that it is distrubed in the tar ball.

You need to manually run the 'build' script in the src/qttestrunner
directory.

Baptiste.

----- Original Message -----
From: "Carlo Wood" <ca...@al...>
To: <cpp...@li...>
Sent: Wednesday, July 31, 2002 4:20 PM
Subject: [Cppunit-devel] Bug(?) in cppunit-1.8.0


> Hum, I get this when I try to use QtUi::TestRunner:
>
> ~/c++/libecc/testsuite>g++ -I ../include test.cc -lcppunit
> /tmp/ccVXRRWI.o: In function `main':
> /tmp/ccVXRRWI.o(.text+0xe): undefined reference to
`CppUnit::QtUi::TestRunner::TestRunner(void)'
> /tmp/ccVXRRWI.o(.text+0x2d): undefined reference to
`CppUnit::QtUi::TestRunner::addTest(CppUnit::Test *)'
> /tmp/ccVXRRWI.o(.text+0x42): undefined reference to
`CppUnit::QtUi::TestRunner::run(bool)'
> /tmp/ccVXRRWI.o(.text+0x53): undefined reference to
`CppUnit::QtUi::TestRunner::~TestRunner(void)'
> /tmp/ccVXRRWI.o(.text+0x6e): undefined reference to
`CppUnit::QtUi::TestRunner::~TestRunner(void)'
> collect2: ld returned 1 exit status
>
> And indeed
>
> /usr/src/cppunit-1.8.0/src/qttestrunner/
>
> was never compiled, the Makefile.am says:
>
> SUBDIRS = cppunit
>
> qttestrunner is missing?
> Are you testing it?  Does it work at all?
>
> --
> Carlo Wood <ca...@al...>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: Dice - The leading online job board
> for high-tech professionals. Search and apply for tech jobs today!
> http://seeker.dice.com/seeker.epl?rel_code=31
> _______________________________________________
> Cppunit-devel mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppunit-devel
>

[Cppunit-devel] CppUnit successfully built on IRIX 6.5 with MIPSpro 7.3.1.3 compi ler

[DO, S. <so...@ba...>]

If you aren't an IRIX developer, please just ignore.

I have downloaded cppunit versions 1.8.0 and  1.9.9 and I managed to build
with the following changes

1.	Declare and export the following variables:
	In bash shell: "declare -x CFFLAGS='-LANG:std" and "declare -x
LDFLAGS=-LANG:std"
2.    Open the Makefile.am and Makefile.in and replace "cp -dpR" with "cp
-pR"
3.    Excecute the configure script: "./configure CC='CC -LANG:std'
LDFLAGS=-LANG:std
4.	Open the 'libtool' file and replace: 
	           "with_gcc=" with "with_gcc=no" and 
	           "LD=/usr/bin/ld -n32" with "LD=/usr/bin/CC" 

4.	Make a library: "make"
5.	Before install them: cd to "doc" directory and repeat step2
6.	Install the libs: "make install" 

I know that some of the steps are unnecessary but I just played it safe.
I managed to compile and run examples from the "CppUnit Cookbook".

Remember this is a workaround NOT a solution.

Have fun,
  Soi

[Cppunit-devel] Bug(?) in cppunit-1.8.0

[Carlo W. <ca...@al...>]

Hum, I get this when I try to use QtUi::TestRunner:

~/c++/libecc/testsuite>g++ -I ../include test.cc -lcppunit
/tmp/ccVXRRWI.o: In function `main':
/tmp/ccVXRRWI.o(.text+0xe): undefined reference to `CppUnit::QtUi::TestRunner::TestRunner(void)'
/tmp/ccVXRRWI.o(.text+0x2d): undefined reference to `CppUnit::QtUi::TestRunner::addTest(CppUnit::Test *)'
/tmp/ccVXRRWI.o(.text+0x42): undefined reference to `CppUnit::QtUi::TestRunner::run(bool)'
/tmp/ccVXRRWI.o(.text+0x53): undefined reference to `CppUnit::QtUi::TestRunner::~TestRunner(void)'
/tmp/ccVXRRWI.o(.text+0x6e): undefined reference to `CppUnit::QtUi::TestRunner::~TestRunner(void)'
collect2: ld returned 1 exit status

And indeed

/usr/src/cppunit-1.8.0/src/qttestrunner/

was never compiled, the Makefile.am says:

SUBDIRS = cppunit

qttestrunner is missing?
Are you testing it?  Does it work at all?

-- 
Carlo Wood <ca...@al...>

[Cppunit-devel] Feature request

[Carlo W. <ca...@al...>]

Hi, thanks for CppUnit.

Currently, a failure is printed like:

1) test: testEquality (F) line: 11 test.cc
 "libecc::bitset<30>("ABC") == libecc::bitset<30>("ABD")"

I'd to have more control about how this is printed
and would like to be able to override a virtual
method of test classes in order to change it.

My proposal is that the above is the default (although
I'd much prefer the default to say "test.cc:11" rather
than "11 test.cc" so that I can use copy&paste to
immedeately get where I want to be; "test.cc:11" is
the same format that is being used by gdb and libcwd).

Most logical is probably to write my own class, or to
derive my own class from a cppunit provided one, and
then being able to specify that this class/object
needs to be used to print the failures.

I leave the implementation details to you :).
Please let me know if this is already possible some how...

-- 
Carlo Wood <ca...@al...>

RE: [Cppunit-devel] writing abstract test class

[Moran Ben-D. <mbe...@ii...>]

Since there isn't reflection in C++.. i can't see a way around the
AUTOMATICALLY point..
 
However, with respect to the having a hierarchy of test classes.. you should
declare the cppunit stuff in your concrete class.. you could have your base
class inherit from TestFixture but use the CPPUNIT_* declaration macros in
your concrete class.
 
moran

-----Original Message-----
From: Bogaerts Marc [mailto:MB...@fa...]
Sent: Wednesday, July 31, 2002 4:25 AM
To: cpp...@li...
Subject: [Cppunit-devel] writing abstract test class



I've been looking for a Unit Test Framework for C++, since I've had good
experiences with JUnit in Java. 
That's how I got to CppUnit and tried it. 
Because I'm not used to C++ I had some difficulties using it. 
Being used to JUnit there are some things I miss in CppUnit, but maybe they
do exist, just that I cannot find them in the doc.

*	being able to build a suite that AUTOMATICALLY includes all test
functions i.e. functions whose name start with 'test'. 

*	being able to create a hierarchy of test classes, some of which may
be abstract, and execute all tests in concrete classes. This gives me errors
at compile time, because the helper macro CPPUNIT_TEST_SUITE tries to
instantiate an object of the test class, but this class is abstract and thus
cannot be instantiated. 

I was wondering if you might have a solution for these problems, or if you
would think of providing such features in the future?

Thanks. 
Marc. 

----------------------------------------------------------------------------

Marc Bogaerts - Software Engineer 
Phone : +32 (0)2 370.36.37 - e-mail : mb...@fa... 
----------------------------------------------------------------------------

S.A. FABRICOM N.V. 
Rue Gatti de Gamond, 254 - B-1180 Bruxelles - Belgium 
General Phone : +32 (0)2 370.33.35 - Fax : +32 (0)2 370.32.22 
----------------------------------------------------------------------------


The information contained in this e-mail is intended only for the person or
entity to which it is addressed and may contain confidential and / or
privileged material. If you are not the intended recipient of this e-mail,
the use of this information or any disclosure, copying or distribution is
prohibited and may be unlawful. 

If you received this in error, please contact the sender and delete the
material from any computer. 

This electronic transmission is intended exclusively for the person to 
whom it is addressed and may contain privileged and confidential material.
Any disclosure, copying, distribution or other action based upon 
the information by persons other than the intended recipient
is prohibited. If you receive this message in error, please contact the 
sender and delete the material. 
Our company does not warrant a proper and complete transmission of this
information, nor does it accept liability for any delays.

[Cppunit-devel] writing abstract test class

[Bogaerts M. <MB...@fa...>]

I've been looking for a Unit Test Framework for C++, since I've had good
experiences with JUnit in Java.
That's how I got to CppUnit and tried it.
Because I'm not used to C++ I had some difficulties using it.
Being used to JUnit there are some things I miss in CppUnit, but maybe they
do exist, just that I cannot find them in the doc.
*	being able to build a suite that AUTOMATICALLY includes all test
functions i.e. functions whose name start with 'test'.
*	being able to create a hierarchy of test classes, some of which may
be abstract, and execute all tests in concrete classes. This gives me errors
at compile time, because the helper macro CPPUNIT_TEST_SUITE tries to
instantiate an object of the test class, but this class is abstract and thus
cannot be instantiated.
I was wondering if you might have a solution for these problems, or if you
would think of providing such features in the future?
Thanks.
Marc.

----------------------------------------------------------------------------

Marc Bogaerts - Software Engineer
Phone : +32 (0)2 370.36.37 - e-mail : mb...@fa... 
----------------------------------------------------------------------------

S.A. FABRICOM N.V. 
Rue Gatti de Gamond, 254 - B-1180 Bruxelles - Belgium 
General Phone : +32 (0)2 370.33.35 - Fax : +32 (0)2 370.32.22 
----------------------------------------------------------------------------


The information contained in this e-mail is intended only for the person or
entity to which it is addressed and may contain confidential and / or
privileged material. If you are not the intended recipient of this e-mail,
the use of this information or any disclosure, copying or distribution is
prohibited and may be unlawful. 

If you received this in error, please contact the sender and delete the
material from any computer.



This electronic transmission is intended exclusively for the person to 
whom it is addressed and may contain privileged and confidential material.
Any disclosure, copying, distribution or other action based upon 
the information by persons other than the intended recipient
is prohibited. If you receive this message in error, please contact the 
sender and delete the material. 
Our company does not warrant a proper and complete transmission of this
information, nor does it accept liability for any delays.

[Cppunit-devel] IRIX MIPSpro build

[DO, S. <so...@ba...>]

Hi,
Just wonder, has anyone solved the "IRIX MIPSprob build" problem listed at
http://sourceforge.net/tracker/index.php?func=detail&aid=557330&group_id=117
95&atid=211795

Cheers,
  Soi

Re: [Cppunit-devel] cppunit and namespaces

[Baptiste L. <gai...@fr...>]

Portability is one of the area being worked on. Luckily for you, support for
'no namespace' is already in place. The current CVS version should be able
to compile without workspace (I tested on VC++ and it worked without the
classes being in the CppUnit namespace).

This setting is supposed to be automatically detected by autoconf.

Here are the important symbols that are of concerns:
CPPUNIT_HAVE_NAMESPACES
should be 0 if you don't have namespace.
This should automatically define (Portability.h):
#  define CPPUNIT_NO_NAMESPACE 1
#  define CPPUNIT_NO_STD_NAMESPACE 1

If you can't access CVS, let me know, I'll try to make a snapshot (I heard
somewhere there was a tool based on cvsview cgi script that could obtain
read-only version of a project through http, but I can't remember the name).

Baptiste.


----- Original Message -----
From: "Balooch Amir, Köln" <Ba...@fj...>
To: <cpp...@li...>
Sent: Friday, July 26, 2002 1:20 PM
Subject: [Cppunit-devel] cppunit and namespaces


> Hello All,
>
> i must compile cppunit-sources at the OS/390-System, but the C++
> copmiler(OSV2R10) at this system supports
> any "namespaces".
> Do you have any experiences with similar problems, or do you know one not
> too complex way to work around
> the "namespaces" in sourcecodes?
>
> Thanks for any help
> Amir Balooch

Re: [Cppunit-devel] CppUnit on IRX 6.5

[Baptiste L. <gai...@fr...>]

Somebody reported a bug during the installation step. So my guess would be
that yes, it compiled. See
http://sourceforge.net/tracker/index.php?func=detail&aid=579925&group_id=117
95&atid=111795

Please, let me know of any particular step that should be in the
documentation.
Baptiste.

----- Original Message -----
From: "DO, Soi" <so...@ba...>
To: <cpp...@li...>
Sent: Monday, July 29, 2002 7:24 AM
Subject: [Cppunit-devel] CppUnit on IRX 6.5


> Has anyone out there successfully compiled CppUnit 1.8 + example,
testsuite,
> on Irix 6.5?
>
> Many thanks,
> Soi

Re: [Cppunit-devel] SourceLine not correctly piped through

[Baptiste L. <gai...@fr...>]

Yes it is a bug. Your work around is correct.

Thanks for pointing this out. I'm currently reworking this area as you may
have noticed. I haven't managed to free the time to write the test yet (hope
this will be soon).

And I do like the compiler outputter a lot. Haven't use the GUI based
TestRunner in a loong time.

Baptiste.

----- Original Message -----
From: "Michael Lacher" <mic...@ge...>
To: <cpp...@li...>
Sent: Thursday, July 25, 2002 3:23 PM
Subject: [Cppunit-devel] SourceLine not correctly piped through


> Hi!
>
> I just downloaded and installed CppUnit from CVS and it seems that the
> SourceLine feature doesn't work correctly (the source line informatino
> gets lost somewhere and the Outputter doesn't print it).
>
> I think I tracked the problem down to a bug:
> In DefaultProtector::protect() the caught Exception message is passed on
> to reportTestFailure() but not the source line.
> I added an overload of reportTestFailure with an extra param for the
> source line and added the parameter to the call in DefaultProtector. Now
> everything works fine.
>
> Is this a bug ? or did I somehow missuse the library and the sourceline
> should get passed along in a different manner ?
>
> regards
> Michael
>
> P.S: the idea with the CompilerOutputter and to add the program as its
> own post-build step is great !!

[Cppunit-devel] Project Status on sourceforge

[Prashant R. <pra...@ya...>]

Hi,

The project status appears as pre-alpha on
sourceforge, even though you have release 1.8 out.
If you have usable application, the status should be
stable (4 or 5). Many people won't be able to see it
or will get turned-off by the project status when it
says pre-alpha, you should change it to stable.

Thanks,
Prashant Rane

__________________________________________________
Do You Yahoo!?
Yahoo! Health - Feel better, live better
http://health.yahoo.com

Re[2]: [Cppunit-devel] URGENT: more information to be logged

[Luis J. <ljo...@cr...>]

Hello,

But that way you separate the information with the result.

This is, I want my XML file to show the name of the test, some
information, and the result.

How do you manage this?

Thanks again,

Luis Joaquim


Monday, July 29, 2002, 4:10:13 PM, you wrote:

MBD> I guess it all depends if you need this information at run-time.. I like to
MBD> use Doxygen (www.doxygen.org) to comment all of my test classes.  of course,
MBD> this doesn't provide the comments at run-time.  

MBD> perhaps providing a method of launching a browser with a link to the doxygen
MBD> comments would be a solution.

MBD> moran

MBD> -----Original Message-----
MBD> From: Luis Joaquim [mailto:ljo...@cr...]
MBD> Sent: Monday, July 29, 2002 11:03 AM
MBD> To: cpp...@li...
MBD> Subject: [Cppunit-devel] URGENT: more information to be logged
MBD> Importance: High


MBD> Hello,

MBD>   I need to report more information about the tests, like a brief
MBD>   description, the inputs and outputs.

MBD>   The programmer will write this fields (strings).

MBD>   I have thought on the implementation and it seems I have to change a
MBD>   lot of files, and would my very hard future upgrades.

MBD>   Does anyone know a better solution?

MBD>   Does anyone have the some problem?

MBD>   Don't you think it would be a nice feature?

MBD>   Thanks in advance,

MBD>   Luis Joaquim



----------------------------------------------------------------------------
------------
Critical Software has changed address and phones -
please check new contacts below
----------------------------------------------------------------------------
------------
---
Luis Joaquim
Critical Software, SA
EN1/IC2, Km 185,6, Banhos Secos, Santa Clara
3040-032 Coimbra
Tel: +351.239.801300, Fax: +351.239.801319
http://www.criticalsoftware.com
ljo...@cr...

RE: [Cppunit-devel] URGENT: more information to be logged

[Moran Ben-D. <mbe...@ii...>]

I guess it all depends if you need this information at run-time.. I like to
use Doxygen (www.doxygen.org) to comment all of my test classes.  of course,
this doesn't provide the comments at run-time.  

perhaps providing a method of launching a browser with a link to the doxygen
comments would be a solution.

moran

-----Original Message-----
From: Luis Joaquim [mailto:ljo...@cr...]
Sent: Monday, July 29, 2002 11:03 AM
To: cpp...@li...
Subject: [Cppunit-devel] URGENT: more information to be logged
Importance: High


Hello,

  I need to report more information about the tests, like a brief
  description, the inputs and outputs.

  The programmer will write this fields (strings).

  I have thought on the implementation and it seems I have to change a
  lot of files, and would my very hard future upgrades.

  Does anyone know a better solution?

  Does anyone have the some problem?

  Don't you think it would be a nice feature?

  Thanks in advance,

  Luis Joaquim

-- 
Luis Joaquim
Critical Software, SA
EN1/IC2, Km 185,6, Banhos Secos, Santa Clara
3040-032 Coimbra
Tel: +351.239.801300, Fax: +351.239.801319
http://www.criticalsoftware.com



-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
_______________________________________________
Cppunit-devel mailing list
Cpp...@li...
https://lists.sourceforge.net/lists/listinfo/cppunit-devel

[Cppunit-devel] URGENT: more information to be logged

[Luis J. <ljo...@cr...>]

Hello,

  I need to report more information about the tests, like a brief
  description, the inputs and outputs.

  The programmer will write this fields (strings).

  I have thought on the implementation and it seems I have to change a
  lot of files, and would my very hard future upgrades.

  Does anyone know a better solution?

  Does anyone have the some problem?

  Don't you think it would be a nice feature?

  Thanks in advance,

  Luis Joaquim

-- 
Luis Joaquim
Critical Software, SA
EN1/IC2, Km 185,6, Banhos Secos, Santa Clara
3040-032 Coimbra
Tel: +351.239.801300, Fax: +351.239.801319
http://www.criticalsoftware.com

[Cppunit-devel] CppUnit on IRX 6.5

[DO, S. <so...@ba...>]

Has anyone out there successfully compiled CppUnit 1.8 + example, testsuite,
on Irix 6.5?

Many thanks,
Soi  

[Cppunit-devel] cppunit and namespaces

[<Ba...@fj...>]

Hello All,

i must compile cppunit-sources at the OS/390-System, but the C++
copmiler(OSV2R10) at this system supports
any "namespaces".
Do you have any experiences with similar problems, or do you know one not
too complex way to work around 
the "namespaces" in sourcecodes?

Thanks for any help
Amir Balooch  

[Cppunit-devel] SourceLine not correctly piped through

[Michael L. <mic...@ge...>]

Hi!

I just downloaded and installed CppUnit from CVS and it seems that the 
SourceLine feature doesn't work correctly (the source line informatino 
gets lost somewhere and the Outputter doesn't print it).

I think I tracked the problem down to a bug:
In DefaultProtector::protect() the caught Exception message is passed on 
to reportTestFailure() but not the source line.
I added an overload of reportTestFailure with an extra param for the 
source line and added the parameter to the call in DefaultProtector. Now 
everything works fine.

Is this a bug ? or did I somehow missuse the library and the sourceline 
should get passed along in a different manner ?

regards
Michael

P.S: the idea with the CompilerOutputter and to add the program as its 
own post-build step is great !!

[Cppunit-devel] please~ I need your help about cppUnit

[<bar...@ha...>]

<br> I am Korean. I can't speak English well. You understand me. sorry.
<br>
<br> I want to use MFC UI cppUnit. but I will write a code in console mod=
e.
<br>
<br> Can MFC UI cppUnit work only  MFC  environment?=20
<br>
<br> How can I use a MFC UI in console mode ?=20
<br>
<br> To Begin with, Thanks to you.=20
<br>
<br>   =20
<img src=3D"http://www26.hanmail.net/Mail-bin/chkcmail?from=3Dbarrios-kmc=
&rcpt=3Dcppunit%2Ddevel%40lists%2Esourceforge%2Enet&msgid=3D2002072200380=
5%2EHM%2EP0000000005irQR%40www26%2Ehanmail%2Enet">

<br><br><table border=3D0 cellpadding=3D5 cellspacing=3D0 width=3D100%%>
<tr><td background=3D'http://image.hanmail.net/hanmail/general/dotline_si=
m.gif' height=3D1></td></tr>
<tr>
<td><font color=3D"#312400" style=3D"font-size:9pt;">
"=BF=EC=B8=AE =C0=CE=C5=CD=B3=DD, Daum" <a href=3Dhttp://www.daum.net tar=
get=3D_top><font color=3D"#312400">http://www.daum.net</font></a><br>
</font></td></tr></table><table bgcolor=3D#F8F8F8 border=3D0 cellpadding=3D=
3 cellspacing=3D0 width=3D100%%  style=3D"border: #ECECEC solid 1px;">
<tr>
<td width=3D50 align=3Dright nowrap><a href=3D'http://hmm.daum.net/msg_we=
lcome' target=3D_blank><img src=3D'http://image.hanmail.net/hanmail/top/a=
dver/messenger.gif' width=3D40 height=3D40 border=3D0></a></td>
<td width=3D50%% class=3Dbase style=3D"line-height:140%%; font-size:9pt;"=
>
<a href=3D'http://hmm.daum.net/msg_welcome' target=3D_blank><font color=3D=
#BD8000 style=3D"font-size:9pt;">
=BA=FC=B8=A3=B4=D9! =C6=ED=C7=CF=B4=D9! Daum=B8=DE=BD=C5=C0=FA</font></a>=
<br>=B8=C5=C0=CF=B8=C5=C0=CF =BE=B2=B0=ED =B0=E8=BD=C3=C1=D2?
</td>
<td width=3D3 nowrap><img src=3D'http://image.hanmail.net/hm/line_h.gif' =
width=3D3 height=3D40></td>
<td width=3D40><a href=3D'http://hmm.daum.net/card_0401' target=3D_blank>=
<img src=3D'http://image.hanmail.net/hanmail/top/adver/ecard.gif' width=3D=
40 height=3D40 border=3D0></a></td>
<td width=3D50%% class=3Dbase style=3D"line-height:140%%; font-size:9pt;"=
>
<a href=3D'http://hmm.daum.net/card_0401' target=3D_blank><font color=3D#=
BD8000 style=3D"font-size:9pt;">Daum=BF=A3=C5=CD=C4=AB=B5=E5</font></a><b=
r>Daum=C8=B8=BF=F8=C0=C7 =C7=CA=BC=F6=C7=B0! =BF=C2=BF=C0=C7=C1 =C3=D6=B0=
=ED=C0=C7 =C7=FD=C5=C3=C0=BB =B4=A9=B8=AE=C0=DA!</td>
</table>

[Cppunit-devel] where is the example cppunit test code?

[l t. <luc...@ya...>]

Hi,

In your CPPUnit Cookbook
(http://cppunit.sourceforge.net/cppunit_cookbook.html),
at the end of this document you have mentioned 
there is a example project in examples/cppunittest. 
Where is it?

Thanks in advance.

CPPUnit User - Lucille

__________________________________________________
Do You Yahoo!?
Yahoo! Autos - Get free new car price quotes
http://autos.yahoo.com

RE: [Cppunit-devel] Parameterizing tests by using XML

[Moran Ben-D. <mbe...@ii...>]

I'd just like to add to the discussion with a point about usefullness of
parameterizing tests..

The protocol for passing parameters to tests cases that I'm actually looking
for is one which allows my command line tools to pass in variables to my
tests.. that is.. I always create a command line tool for running the tests
for the case where i need to check the validity of component on a remote
system for support, etc.. thus, my tests have several contexts in which they
run:

	1. development (my machine)
	2. qa (centralized server)
	3. other developers machines
	4. production (which can often mean two machines if there is a
staging server)

Just thought I throw this into the salad of parameterizing tests.. XML in my
case is too beaurocratic to run in the case of the QA or production
servers.. i need a quick way of running a parameterized test and XML as
simple as it is, still ends up costing too much effort on my part (e.g. with
issues like is the installed xml parser version correct, does it work
properly, etc.)

moran

-----Original Message-----
From: Robert Wenner [mailto:ro...@po...]
Sent: Friday, July 19, 2002 3:01 AM
To: Michel Armin; cpp...@li...
Subject: Re: [Cppunit-devel] Parameterizing tests by using XML


Hi,

On Friday 19 July 2002 08:36, Michel Armin wrote:
> Hi all.
>
> Actually I was thinking about a little bit different solution here.
> It differs mainly in two points:
>
> 1. the framework should be responsible for parsing the xml file and
> invoke the test with a particular set of parameters (as opposed to
> let each of the test cases perform the parsing)
>
> 2. the DTD of the xml file is a less sophisticated

These are _very_ important points -- you would not want to need test 
cases for your test cases, right?

I still see two big drawbacks on using a XML driven test.

First it drops the advantage of having the tests written in the same 
language as the code under test. Developers have to learn another new 
language / syntax / semantics and can not focus on their real work. 
Even though XML looks easy, it has some pitfalls you will most likely 
uncover and which will cost really lots of time, nerves, and sanity.

Second I don't think the XML overhead justifies the results. How many 
tests do you have that run the same way that you just need to exchange 
the input and output values? (And how many of those use primitive 
inputs and outputs?) If I ever have to write more than three tests for 
the same method, I think hard about abetter design, usually the method 
has just too much responsibilities.

Just my 2 cents,

Robert


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Cppunit-devel mailing list
Cpp...@li...
https://lists.sourceforge.net/lists/listinfo/cppunit-devel

Re: [Cppunit-devel] Parameterizing tests by using XML

[Robert W. <ro...@po...>]

On Friday 19 July 2002 09:19, Michel Armin wrote:
> Actually almost all of my tests would benifit from such a
> parameterized testing approach. (Most of our code is concerned with
> manipulating images. Of course, we support a number of different
> types of images. Our functions should be able to deal with all of
> these types of images in a transparent way. If I have a possibility
> to parameterize the type of the image used for a test, I could
> greatly improve the test coverage.)

Wouldn't a template be more helpful?
Or a (abstract) base class that excercises test for all images and is 
not directly called but its derived classes call it and offer 
specialised methods the base calls (template class pattern)?

Robert

[Cppunit-devel] TestContext

[Michel A. <Arm...@si...>]

Hi again.

Maybe it would be worthwhile to introduce a TestContext class that is
responsible for encapsulating test data that is read in at runtime (see XML
parameterized tests topic).
This TestContext class should be retrievable from CppUnit::Test, enabling
TestListeners to make use of it too (e.g. Outputter subclass could report
about the actual set of parameters used for the execution of a test).

The problem is that I don't know what the interface of TestContext should
look like. It should be flexible enough to allow for an open set stored
information. A simple solution could allow for the following:

class TestContext {
	std::istream& getStream(const std::string& name) = 0;
      void setStream(std::istream& stream, std::string& name) = 0;
};

Alternatively, TestContext could contain a (fixed) set of HashMaps that are
specialized for a (fixed) set of types (std::string, std::istream, ...).
Each of these HashMaps would contain named objects of the corresponding
types. This approach would also allow to (type-safely) iterate through the
complete content of a TestContext object, a fact which is certainly useful
when talking in terms of test reports.

For example, a TestMethod/TestListener etc. could call getStream("in"),
getStream("exp"), getStream("description") etc. to retrieve and use the
corresponding (named) streams.

I don't believe that this is a very elaborated/good solution yet. But I hope
that it can at least serve as a basis for discussion.

Armin.

RE: [Cppunit-devel] Parameterizing tests by using XML

[Michel A. <Arm...@si...>]

> -----Original Message-----
> From: Robert Wenner [mailto:ro...@po...]
> Sent: Freitag, 19. Juli 2002 09:01
> To: Michel Armin; cpp...@li...
> Subject: Re: [Cppunit-devel] Parameterizing tests by using XML
> 
> 
> Hi,
> 
> On Friday 19 July 2002 08:36, Michel Armin wrote:
> > Hi all.
> >
> > Actually I was thinking about a little bit different solution here.
> > It differs mainly in two points:
> >
> > 1. the framework should be responsible for parsing the xml file and
> > invoke the test with a particular set of parameters (as opposed to
> > let each of the test cases perform the parsing)
> >
> > 2. the DTD of the xml file is a less sophisticated
> 
> These are _very_ important points -- you would not want to need test 
> cases for your test cases, right?
> 
> I still see two big drawbacks on using a XML driven test.
> 
> First it drops the advantage of having the tests written in the same 
> language as the code under test. Developers have to learn another new 
> language / syntax / semantics and can not focus on their real work. 
> Even though XML looks easy, it has some pitfalls you will most likely 
> uncover and which will cost really lots of time, nerves, and sanity.

That's of course true, but I do not want to get rid of the current flavor of
programming tests; I just want to add a new possibility to write tests.

> Second I don't think the XML overhead justifies the results. How many 
> tests do you have that run the same way that you just need to 
> exchange 
> the input and output values? (And how many of those use primitive 
> inputs and outputs?) If I ever have to write more than three 
> tests for 
> the same method, I think hard about abetter design, usually 
> the method 
> has just too much responsibilities.

Actually almost all of my tests would benifit from such a parameterized
testing approach. (Most of our code is concerned with manipulating images.
Of course, we support a number of different types of images. Our functions
should be able to deal with all of these types of images in a transparent
way. If I have a possibility to parameterize the type of the image used for
a test, I could greatly improve the test coverage.)

Armin.