cppunit-devel — CppUnit Developer Mailing List

Re: [Cppunit-devel] Bug or misunderstanding?

[Duane M. <dua...@ma...>]

--- At Fri, 20 Dec 2002 11:45:45 +1300,
Seb...@en... wrote:

>Hi,
>
>I'm just starting on a new project and we are going to use CppUnit as a
>framework for our tests. Right now I'm working on the UI part of the
>application and so I started out with creating a Fixture that contains a
>UserInterface object as a member and has a static suite() function just as
>described in the CookBook. The suite creates two (for now) TestCallers and
>pass in test methods of the fixture. I expected one Fixture (and therefor
>one UserInterface) to be created and that all the testmethods are called on
>this one object (framed by calles to setUp() and tearDown() which reset the
>UI object to a
>known state.)
>
>However, it turned out that for each TestCaller instantiated one Fixture
>was instantiated and the testmethods were each called on a different
>Fixture object. This resulted in multiple UI objects to be created and
>since they create threads each calling a display driver which only expects
>calls from one UI at a time ..... I think you can imagine ...
>
>My understanding came from the following text from the CookBook:
>
>"Ordinarily, you'll have many little test cases that you'll want to run on
>the same set of objects. To do this use a fixture.      [...]  A fixture is
>a known set of objects that serves as a base for a set of test cases."
>
>
>Now my question is: Am I doing something wrong or is this a bug in CppUnit
>or is this intended behaviour (in which case I think the docu should be
>updated.)?
>
>Also if this is intended, can you give me just a pointer on how to do this
>kind of thing? Should I subclass TestSuite and keep the persistent objects
>there?

Others that work on CppUnit can speak up for why it is this way. I have
long considered this a bug. CppUnit likes calling new() :-). They
instiate a new Fixture() for each test case. You will have to work around
it somehow.

I worked around it by making a few additions to the CppUnit code to allow
me to register test cases that all share a single Fixture; which is how I
always thought the system should work. 

I could dig into my code to find the changes that I made if you would like.

 ...Duane

[Cppunit-devel] Bug or misunderstanding?

[<Seb...@en...>]

Hi,

I'm just starting on a new project and we are going to use CppUnit as a
framework for our tests. Right now I'm working on the UI part of the
application and so I started out with creating a Fixture that contains a
UserInterface object as a member and has a static suite() function just as
described in the CookBook. The suite creates two (for now) TestCallers and
pass in test methods of the fixture. I expected one Fixture (and therefor
one UserInterface) to be created and that all the testmethods are called on
this one object (framed by calles to setUp() and tearDown() which reset the
UI object to a
known state.)

However, it turned out that for each TestCaller instantiated one Fixture
was instantiated and the testmethods were each called on a different
Fixture object. This resulted in multiple UI objects to be created and
since they create threads each calling a display driver which only expects
calls from one UI at a time ..... I think you can imagine ...

My understanding came from the following text from the CookBook:

"Ordinarily, you'll have many little test cases that you'll want to run on
the same set of objects. To do this use a fixture.      [...]  A fixture is
a known set of objects that serves as a base for a set of test cases."


Now my question is: Am I doing something wrong or is this a bug in CppUnit
or is this intended behaviour (in which case I think the docu should be
updated.)?

Also if this is intended, can you give me just a pointer on how to do this
kind of thing? Should I subclass TestSuite and keep the persistent objects
there?



Another, completely unrelated, issue is that I get a warning from the
following code:

#ifndef _test_sm70Test_h_
#define _test_sm70Test_h_

#include "cppunit/ui/text/TestRunner.h"
#include "pfl/thread.h"

namespace sm70
{
  class RunCppUint : public pfl::Thread
  {
    CppUnit::TextUi::TestRunner runner;

    void* run();

  public:

    RunCppUint();
  };
}

#endif

The warning:
"/usr/local/include/cppunit/ui/text/TextTestRunner.h", line 88: Warning:
CppUnit::TextTestRunner::run hides the virtual function
CppUnit::TestRunner::run(CppUnit::TestResult&, const
std::basic_string<char, std::char_traits<char>, std::allocator<char>>&)

It does not keep me from compiling or running the tests (they seem to run
fine apart from above's problem) but it is rather anoying.

Thanks for your help,
Seb

Re: [Cppunit-devel] Silly question in CppUnit

[Phlip <pl...@sy...>]

[Administrator, please set "Reply-to" to the list]



> Are there any examples you can point me to that allows me to do something
interesting with
>
> CppUnit::TextUi::TestRunner.run("testname", true); ?

Have you seen this?

http://c2.com/cgi/wiki?DirtSimpleCppUnitExample

I wrote it after deciphering similar issues, and learning that there was no
samples except the complex ones. It doesn't cover your question, but I
suspect it's feature-complete so that your code would work on it.

This line probably does it:

  CPPUNIT_TEST_SUITE_NAMED_REGISTRATION( ExampleTestCase,
"ExampleTestCase" );

--

  Phlip
           http://www.greencheese.org/DontPlanDesigns
  --  To catch a bug, you'v got to learn to think like a bug  --

[Cppunit-devel] Silly question in CppUnit

[Erick E. <eer...@op...>]

Hi!

I'm trying to get my arms around CppUnit to figure out whether we can use it easily and I'm having a little problem....

Are there any examples you can point me to that allows me to do something interesting with 

CppUnit::TextUi::TestRunner.run("testname", true); ?

The fact that I can give a name to <run> implies that I can run some (suite?) of tests. My problem is that I completely miss how to register tests by name so they can be run later.

When I step through the debugger into <run>, it goes into code that searches a list (things like RunTestByName). Again, when stepping through here the only test returned is "All Tests" which is the default.

I have a feeling that either I'm totally missing the boat here or what I want to do is not possible. What I'm after is the ability to run a test suite by name from the command-line version.

I couldn't find a discussion of this problem on the net, perhaps I'm just not part of the right newsgroup.

Thanks
Erick Erickson

[Cppunit-devel] CppUnit, Borland C++ and STLPort

[Steve S. <ste...@ad...>]

Hi,

I'm currently looking into getting cppunit building under Borland C++ 6.0.
It's currently failing in TestResult.cpp with the following errors:

TestResult.cpp(136): E2034 Cannot convert
'_STL::_Deque_iterator<TestListener *,_STL::_Nonconst_traits<TestListener *>
>' to 'const char *'
TestResult.cpp(136): E2342 Type mismatch in parameter '__path' (wanted
'const char *', got '_STL::_Deque_iterator<TestListener
*,_STL::_Nonconst_traits<TestListener *> >')
TestResult.cpp(136): E2227 Extra parameter in call to std::remove(const char
*)
TestResult.cpp(137): E2285 Could not find a match for
'_STL::deque<TestListener *,_STL::allocator<TestListener *>
>::erase(int,_STL::_Deque_iterator<TestListener
*,_STL::_Nonconst_traits<TestListener *> >)'

The relevant code section is:

void
TestResult::removeListener ( TestListener *listener )
{
  ExclusiveZone zone( m_syncObject );
  m_listeners.erase( std::remove( m_listeners.begin(),
                                  m_listeners.end(),
                                  listener ),
                     m_listeners.end());
}

Interestingly this compiles fine under the version 5 compiler, and under
version 6.0 if you enable the RogueWave STL libraries (BCB6.0 builds with
STLPort by default).

This is under version 1.9.10.  Does anybody have any suggestions?

Cheers,
Steve

[Cppunit-devel] Information wanted

[Louis <lou...@sy...>]

Hi,

My name is Louis I would like to use cppunit to test function only is 
this possible.
Our teacher want we une struct and pointer we need to use a lot of 
pointers we simulate
a computer system stack queue program loader memory management etc. I 
need to test
all case when I use queue for example is this possible to do it...

by the way I send you my project program you can check to understand the 
situation.

Louis

[Cppunit-devel] Is this a bug?

[Sungmin C. <sm...@so...>]

Hi, thank you for the effots for making such a good program as CppUnit!
I tried to use the bug reporting system, but I'm not sure that it is a
bug or not so I email you directly.
 
I tried to use 1.8.0.
 
1. I tested with the STL complex
   Strangely enough, it seems that the test works only if I insert a
magic code in the main function.
 
   int main( int argc, char **argv)
  {
    // Strangely, there should a code like this
 
////////////////////////////////////////////////////////////////////////
////////////////////
      Complex x;
 
////////////////////////////////////////////////////////////////////////
////////////////////
2. When I replace the Complex class by the following code, it works.
class Complex { 
  friend bool operator ==(const Complex& a, const Complex& b);
  friend Complex operator +(const Complex& a, const Complex& b);
  double real, imaginary;
public:
  Complex( double r, double i = 0 ) : real(r) , imaginary(i) {}
};
 
bool operator ==( const Complex &a, const Complex &b )
{ 
  return (a.real == b.real)  &&  (a.imaginary == b.imaginary); 
}
Complex operator +( const Complex &a, const Complex &b )
{
    return Complex(a.real + b.real, a.imaginary + b.imaginary);
}
 
3.   Is it a bug or is there anything I made a mistake?
  Followings are the full source code and I compiled 
  g++ main.cpp -o main -lcppunit
 
Thank you in advance and looking forward to your answer.
With best regards.
 
Sungmin Cho.
softDSP Co., Ltd.
 
////////////////////////////////////////////////////////////////////////
//////
// source code (mainly from CookBook and CppWiki)
////////////////////////////////////////////////////////////////////////
//////
#include <memory>
#include <cppunit/extensions/TestFactoryRegistry.h>
#include <cppunit/ui/text/TestRunner.h>
#include <cppunit/CompilerOutputter.h>
#include <cppunit/TestCase.h>
#include <cppunit/extensions/HelperMacros.h>
 
#include <complex.h>
typedef complex<int> Complex;

class ComplexNumberTest : public CppUnit::TestFixture  {
 
CPPUNIT_TEST_SUITE( ComplexNumberTest );
CPPUNIT_TEST( testEquality );
CPPUNIT_TEST( testAddition );
CPPUNIT_TEST_SUITE_END();
 
  Complex *m_10_1, *m_1_1, *m_11_2;
public:
  void setUp()
  {
    m_10_1 = new Complex( 10, 1 );
    m_1_1 = new Complex( 1, 1 );
    m_11_2 = new Complex( 11, 2 );  
  }
 
  void tearDown() 
  {
    delete m_10_1;
    delete m_1_1;
    delete m_11_2;
  }
 
  void testEquality()
  {
    CPPUNIT_ASSERT(*m_10_1 != *m_10_1);
    CPPUNIT_ASSERT( !(*m_10_1 == *m_11_2) );
  }
 
  void testAddition()
  {
    CPPUNIT_ASSERT( *m_10_1 + *m_1_1 != *m_11_2 );
  }
};
 
CPPUNIT_TEST_SUITE_NAMED_REGISTRATION( ComplexNumberTest,
"ComplexNumberTest" );
 
CppUnit::Test *suite() {
    CppUnit::TestFactoryRegistry &registry =
       CppUnit::TestFactoryRegistry::getRegistry();
 
    registry.registerFactory(
        &CppUnit::TestFactoryRegistry::getRegistry( "ComplexNumberTest"
) );
    return registry.makeTest();
}
 
int main( int argc, char **argv)
{
    // Strangely, there should a code like this??
////////////////////////////////////////////////////////////////////////
////////////////////
    Complex x;
////////////////////////////////////////////////////////////////////////
////////////////////
 
    // if command line contains "-selftest" then this is the post build
check
    // => the output must be in the compiler error format.
    bool selfTest = (argc > 1)  &&
                    (std::string("-selftest") == argv[1]);
 
    CppUnit::TextUi::TestRunner runner;
    runner.addTest( suite() );   // Add the top suite to the test runner
 
    if ( selfTest )
    { // Change the default outputter to a compiler error format
outputter
      // The test runner owns the new outputter.
      runner.setOutputter( CppUnit::CompilerOutputter::defaultOutputter(
 
&runner.result(),
                                                          std::cerr ) );
    }
    // Run the test.
    bool wasSucessful = runner.run("",false);
    // Return error code 1 if the one off test failed.
    return wasSucessful ? 0 : 1;
}

[Cppunit-devel] cppunit-1.8.0 configure error on FreeBSD

[Thomas K. (gottlob) <kor...@db...>]

Dear Maintainers,

when doing a configure on my FreeBSD workplace PC, the following things
happen:

checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for mawk... no
checking for gawk... no
checking for nawk... nawk
checking whether make sets ${MAKE}... yes
checking whether make sets ${MAKE}... (cached) yes
checking for a BSD compatible install... /usr/bin/install -c
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for executable suffix...
checking for object suffix... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of gcc... gcc
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc
checking build system type... i386-unknown-freebsd4.7
checking host system type... i386-unknown-freebsd4.7
checking for ld used by GCC... /usr/libexec/elf/ld
checking if the linker (/usr/libexec/elf/ld) is GNU ld... yes
checking for /usr/libexec/elf/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependant libraries... pass_all
checking command to parse /usr/bin/nm -B output... ok
checking how to run the C++ preprocessor... g++ -E
checking for dlfcn.h... yes
checking for ranlib... ranlib
checking for strip... strip
checking for objdir... .libs
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... no
checking if we can lock with hard links... yes
checking if gcc supports -fno-rtti -fno-exceptions... yes
checking whether the linker (/usr/libexec/elf/ld) supports shared libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... freebsd4.7 ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking whether -lc should be explicitly linked in... yes
creating libtool
checking for doxygen... no
checking for cmath... yes
checking whether the compiler supports Run-Time Type Identification... yes
checking whether the compiler implements namespaces... yes
checking whether std::string::compare takes a string in argument 1... yes
checking whether the compiler has stringstream... yes
checking whether the library defines class strstream... checking for strstream... yes
yes
configure: creating ./config.status
config.status: creating Makefile
mv: Makefile: set owner/group (was: 528/0): Operation not permitted
config.status: creating cppunit.spec
mv: cppunit.spec: set owner/group (was: 528/0): Operation not permitted
config.status: creating cppunit-config
mv: cppunit-config: set owner/group (was: 528/0): Operation not permitted
config.status: creating src/Makefile
mv: src/Makefile: set owner/group (was: 528/0): Operation not permitted
config.status: creating src/cppunit/Makefile
mv: src/cppunit/Makefile: set owner/group (was: 528/0): Operation not permitted
config.status: creating include/Makefile
mv: include/Makefile: set owner/group (was: 528/0): Operation not permitted
config.status: creating include/cppunit/Makefile
mv: include/cppunit/Makefile: set owner/group (was: 528/0): Operation not permitted
config.status: creating include/cppunit/extensions/Makefile
mv: include/cppunit/extensions/Makefile: set owner/group (was: 528/0): Operation not permitted
config.status: creating include/cppunit/ui/Makefile
mv: include/cppunit/ui/Makefile: set owner/group (was: 528/0): Operation not permitted
config.status: creating include/cppunit/ui/mfc/Makefile
mv: include/cppunit/ui/mfc/Makefile: set owner/group (was: 528/0): Operation not permitted
config.status: creating include/cppunit/ui/qt/Makefile
mv: include/cppunit/ui/qt/Makefile: set owner/group (was: 528/0): Operation not permitted
config.status: creating include/cppunit/ui/text/Makefile
mv: include/cppunit/ui/text/Makefile: set owner/group (was: 528/0): Operation not permitted
config.status: creating doc/Makefile
mv: doc/Makefile: set owner/group (was: 528/0): Operation not permitted
config.status: creating doc/Doxyfile
mv: doc/Doxyfile: set owner/group (was: 528/0): Operation not permitted
config.status: creating examples/Makefile
mv: examples/Makefile: set owner/group (was: 528/0): Operation not permitted
config.status: creating examples/hierarchy/Makefile
mv: examples/hierarchy/Makefile: set owner/group (was: 528/0): Operation not permitted
config.status: creating examples/cppunittest/Makefile
mv: examples/cppunittest/Makefile: set owner/group (was: 528/0): Operation not permitted
config.status: creating config/config.h
config.status: config/config.h is unchanged
creating include/cppunit/config-auto.h - prefix CPPUNIT for config/config.h defines
/* automatically generated config/ contrib/ doc/ examples/ include

I think that this is related to the groups i have access to:

my groups:
uid=528(korimort) gid=50(diss) groups=50(diss), 17(laser)

it works however for the following person:
uid=405(pisjak) gid=10(staff) groups=10(staff), 0(wheel), 5(operator), 15(sysop), 17(laser), 18(colorlaser)

Compilation seems to work anyway. There is no hint in the INSTALL-unix
file on this issue.

Greetings, Thomas Korimort.

[Cppunit-devel] make distclean fails for cppunit 1.8.0 on FreeBSD 4.7-RELEASE

[Gerald P. <pf...@db...>]

...with the following error message:

  % make distclean
  Making distclean in doc
  rm -rf .libs _libs
  -r latex
  -r:No such file or directory
  *** Error code 1

  Stop in .../cppunit-1.8.0/doc.
  *** Error code 1

(With GNU make it seems to work.)

Gerald
-- 
Gerald "Jerry"   pf...@db...   http://www.pfeifer.com/gerald/

Re: [Cppunit-devel] Java's printStackTrace?

[Mark B. <br...@si...>]

On Tue, Nov 19, 2002 at 01:32:44PM +0100, Stefan Rank wrote:

> is there an equivalent to Java's printStackTrace? It would be helpful to 
> see the calling stack of a failed assertion.

Not portably, though the GNU libc offers the function backtrace() and
friends which offer this functionality.

-- 
"You grabbed my hand and we fell into it, like a daydream - or a fever."

[Cppunit-devel] Java's printStackTrace?

[Stefan R. <Ste...@sc...>]

Hello,

is there an equivalent to Java's printStackTrace? It would be helpful to 
see the calling stack of a failed assertion.

Cheers,

Stefan

[Cppunit-devel] Please move if() out of functions into macros

[<rm...@ma...>]

I was experiencing a 10x slow down running my test suite using cppunit. I
realized that the CPPUNIT_ASSERT and CPPUNIT_ASSERT_EQUAL cause the
construction of multiple std::strings even if the condition is true.  
This seems silly to me.  I wanted to suggest that the CPPUNIT_ASSERT macro
directly contain the conditional.  That way in the (hopefully) likely case
where the assertion is true, no unnecessary std::strings are constructed.

I've already modified my test suite to use if (...) CPPUNIT_FAIL(...),
but I think this should be a useful and harmless speed increase.

I understand that enough logic goes into CPPUNIT_ASSERT_DOUBLES_EQUAL that
the conditional should stay in the function, and I can live with that.

Thanks,

Ryan Mack

Re: [Cppunit-devel] CppUnit successfully built on IRIX 6.5 with M IPSpro 7.3.1.3 compi ler

[Steve M. R. <ste...@vi...>]

On Sun, Nov 10, 2002 at 10:47:17AM +0200, Doron Ofek wrote:
> Thanks to your help I managed to compile CppUnit on IRIX 6.5.
> One note: On my station I had to run the configure script with a third
> parameter thus:
> "./configure CC='CC -LANG:std' LDFLAGS=-LANG:std CXX='CC -LANG:std'"

It's been a while since I built CppUnit under IRIX, but I'm pretty sure
that only CXX needs to be set:

    ./configure CXX='CC -LANG:std'

Though I now see that README-unix incorrectly says to set "CC" ...
:-(

 
> -----Original Message-----
> From: DO, Soi [mailto:so...@ba...]
> Sent: Friday, August 02, 2002 6:03 AM
> To: 'cpp...@li...'
> Cc: FEODOROFF, Ray; David Coates (E-mail)
> Subject: [Cppunit-devel] CppUnit successfully built on IRIX 6.5 with
> MIPSpro 7.3.1.3 compi ler
> 
> 
> 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"

It is safer to edit only "Makefile.in".  [Editing Makefile.am might
cause you grief if your automake version is different from the one
used to package cppunit.]


-S

[Cppunit-devel] omitting semicolon on cppunit-1.9.10

[IIZUKA D. <ii...@mt...>]

Hi.
I found a tiny bug : omitting semicolon on cppunit-1.9.10 source code.
Here is a patch.

--- cppunit-1.9.10.orig/src/cppunit/DefaultProtector.cpp
+++ cppunit-1.9.10/src/cppunit/DefaultProtector.cpp
@@ -24,7 +24,7 @@
 #if CPPUNIT_USE_TYPEINFO_NAME
     shortDescription += TypeInfoHelper::getClassName( typeid(e) );
 #else
-    shortDescription += "std::exception (or derived)."
+    shortDescription += "std::exception (or derived).";
 #endif
     Message message( shortDescription, e.what() );
     reportError( context, message );

[Cppunit-devel] type_info::name()

[FUKUDA F. <ff...@nt...>]

Hi all,

current CppUnit uses type_info::name() to make test-name.
however, accoding to FDIS/IS, type_info::nmae() returns
implementation-defined NTBS(null terminated byte string).
so, I think type_info::name() is NOT gualanteed human-readable...
It had better not to use type_info::name()

how do you think about this?

-----:-----:-----:-----:-----:-----:-----:-----:-----:-----
FUKUDA (episteme) Fumiki -- magical, but never a magic...

RE: [Cppunit-devel] CppUnit successfully built on IRIX 6.5 with M IPSpro 7.3.1.3 compi ler

[Doron O. <Do...@bv...>]

Thanks to your help I managed to compile CppUnit on IRIX 6.5.
One note: On my station I had to run the configure script with a third
parameter thus:
"./configure CC='CC -LANG:std' LDFLAGS=-LANG:std CXX='CC -LANG:std'"

-----Original Message-----
From: DO, Soi [mailto:so...@ba...]
Sent: Friday, August 02, 2002 6:03 AM
To: 'cpp...@li...'
Cc: FEODOROFF, Ray; David Coates (E-mail)
Subject: [Cppunit-devel] CppUnit successfully built on IRIX 6.5 with
MIPSpro 7.3.1.3 compi ler


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


-------------------------------------------------------
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] CppUnit and gcc 3.2

[Dave G. <dg...@hy...>]

Gary Granger wrote:
> It looks like std::runtime_error destructor declares that it throws no 
> exceptions, while the default destructor for the 
> DynamicLibraryManagerException() does not. Adding such a definition 
> fixed it for me.  Patch attached.

Thanks, with that patch, I was able to build cppunit!

Re: [Cppunit-devel] CppUnit and gcc 3.2

[Gary G. <gr...@at...>]

It looks like std::runtime_error destructor declares that it throws no 
exceptions, while the default destructor for the 
DynamicLibraryManagerException() does not. Adding such a definition 
fixed it for me.  Patch attached.

gary

Dave Glowacki wrote:
> Trying to build the latest CVS version of CppUnit using gcc 3.2
> results in this error message:
> 
>   In file included from DynamicLibraryManager.cpp:4:
>   ../../include/cppunit/plugin/DynamicLibraryManagerException.h:20: looser 
> throw specifier for `virtual CppUnit::DynamicLibraryManagerException::~DynamicL
> ibraryManagerException()' /usr/local/include/c++/3.2/stdexcept:118:   
> overriding `virtual std::runtime_error::~runtime_error() throw ()'

[Cppunit-devel] CppUnit and gcc 3.2

[Dave G. <dg...@hy...>]

Trying to build the latest CVS version of CppUnit using gcc 3.2
results in this error message:

  In file included from DynamicLibraryManager.cpp:4:
  ../../include/cppunit/plugin/DynamicLibraryManagerException.h:20: looser 
throw specifier for `virtual CppUnit::DynamicLibraryManagerException::~DynamicL
ibraryManagerException()' /usr/local/include/c++/3.2/stdexcept:118:   
overriding `virtual std::runtime_error::~runtime_error() throw ()'

I'm fairly new to C++, so I have no idea what this is trying
to tell me.

Has anyone gotten CppUnit built using gcc 3.2?

[Cppunit-devel] 1.9.10 PlugInManager minor modification

[Eugene Z. <eug...@th...>]

Hi,
I've just downloaded the latest cppunit (1.9.10). What a great =
improvement from 1.8.0 in the plug-in approach!

One minor complaint. I am about to create the whole project test manager =
that will load all test dlls and organize the whole  (huge) project test =
suites but I won't modify/create and than support my own testrunner. I'm =
trying to create my own plug-in that will load and listen to whole =
project tests (actually, based on the ClockerPlugin example).
So I need to load some plug-ins and attach to my own registry and then =
run this under DLL-PlugIn-Runner.=20
It can be done both way:
1) Create my own PlugInManager but then I need access to the Dynamic =
Library Manager...
or
2) Modify the PlugInManager class to attach the loaded plug-in to my own =
registry.
Also, it'll be great to have a some messenger system between the =
Plug-ins smth like "who're you?".

Any idea on this case would be appreciated.
I can create an example and contribute it.

Thanks,
Eugene Zozulya
www.thinknet.com

Re: [Cppunit-devel] C++ test cases generator

[Phlip <pl...@sy...>]

FUKUDA Fumiki sez:

> # project 'cuppa' : http://sourceforge.jp/projects/cuppa/
> # SORRY, all of it's materials are in Japanese :-(

<plug>
    http://babelfish.altavista.com/tr does Japanese
</plug>

And I'l confess I too was interested in the existence of a Doxygen-style 
solution... ;-)

-- 
  Phlip
       http://www.greencheese.org/LucidScheming
  --  Who needs a degree when we have Web e-search engines?  --

Re: [Cppunit-devel] C++ test cases generator

[FUKUDA F. <ff...@nt...>]

Hi,

--- "[Cppunit-devel] C++ test cases generator" / Guillaume Puthod ---

>We are looking for tools on Unix and/or Windows that can generate test 
>cases for C++ code.
>
>Would you be kind enough to send me any references/ideas you have on 
>this subject ?

'doxygen' can genarate XML that contains function-signatures from the 
input C++ source.

and, our project 'cuppa' made test-skeleton-genarator 'curie' that
genarates test-skeleton from the XML.

for example, a source:

class Foo {
public:
  void one();
  void two();
};

doxygen + curie can genarate:

class FooTest : public CppUnit::TestFixture {
 ...
 void test_one();
 void test_two();
};

# project 'cuppa' : http://sourceforge.jp/projects/cuppa/
# SORRY, all of it's materials are in Japanese :-(

-----:-----:-----:-----:-----:-----:-----:-----:-----:-----
FUKUDA (episteme) Fumiki -- magical, but never a magic...

Re: [Cppunit-devel] C++ test cases generator

[Phlip <pl...@sy...>]

Guillaume Puthod sez:
>   Hello,
>
> We are a software service company specialized in testing.
>
> We are looking for tools on Unix and/or Windows that can generate test
> cases for C++ code.

With all respect, the *Unit test rigs generally dedicate >only< to tests 
written by programmers >as< they write the features.

We don't do this:

  write code -> spend 6 hours debugging it -> add tests to it

We do this:

  write a line of test -> get it to fail -> write enough code to pass ->
     test everything -> refactor the design -> test everything

This is a serious workflow which many have found to produce rock-solid code 
with a very clean design:

	http://c2.com/cgi/wiki?TestDrivenDevelopment

But it's actually much more incremental than one e-mail can express. When 
adding an ability to code you generally add just enough test lines to fail. 
When they pass, after you try to refactor, you add only one or two more lines 
of test, see if these fail, and repeat until done. When you refactor (if you 
find a reason to, typically duplication), you break it up into the smallest 
steps which can themselves be tested.

So there's simply no room in this loop for a tool that would read static 
code, as if it never changes, and writes a batch of tests for them. If you 
find a customer that actually thinks they need this ability, they must be 
re-educated.

-- 
  Phlip
http://c2.com/cgi/wiki?SheChangeDesignInTheDatabase
  --  Now collecting votes for a new group:
      news:alt.flame.moderated  --

[Cppunit-devel] C++ test cases generator

[Guillaume P. <pu...@pr...>]

  Hello,

We are a software service company specialized in testing.

We are looking for tools on Unix and/or Windows that can generate test 
cases for C++ code.

Would you be kind enough to send me any references/ideas you have on 
this subject ?

With my best regards

-- 
Guillaume Puthod
Precilog - Software Testing Automation
---------------------------------------------------------

 Address: 16 rue Champ Lagarde
          78000 Versailles / FRANCE
   Phone: +33 (0)1 39 20 13 55
     Fax: +33 (0)1 39 20 03 55
  E-mail: g.p...@pr...
 Website: www.precilog.com

Re: [Cppunit-devel] VC++ warning

[Phlip <pl...@sy...>]

Can we switch this list so "Reply" goes to the list? to review & archive
technical discussions?

From: "Baptiste Lepilleur"

> If you look at config-msvc6.h, you'll see that's already done. This get
> ride of most of those warnings, but not all. Hence the question...

I ain't looking at the code right now, but I suspect that such a #pragma
would have to be up as high as the sacred "stdafx.h" file.

> > #pragma warning(disable:4786)

--
 Phlip