CppUnit - C++ port of JUnit

I'm trying to install cppunit and I am having a problem compiling and 
activating TestRunnerDspPlugin.dll

Sometimes when I build I get a link error.
Sometimes I don't.

But the TestRunnerDspPlugin.dll is nowhere to be found.

Can you provide any direction.

OH, sorry.

using the 1.12 version.

Carl Mueller
The information transmitted is intended only for the person(s)or entity to which it is addressed and may contain confidential and/or legally privileged material. Delivery of this message to any person other than the intended recipient(s) is not intended in any way to waive privilege or confidentiality. Any review, retransmission, dissemination or other use of , or taking of any action in reliance upon, this information by entities other than the intended recipient is prohibited. If you receive this in error, please contact the sender and delete the material from any computer.

For Translation:

http://www.baxter.com/email_disclaimer

Vincent,

An easier fix is to have floatingPointIsFinite() return an int, since
that is what isfinite(), finite() and _finite() all do.

-Steve

Hello.

There is a new compilation warning with MSVC6 :

TestAssert.cpp
f:\sourceforge\cppunit\cppunit\include\cppunit\portability\floatingpoint.h(42) 
: warning C4800: 'int' : forcing value to bool 'true' or 'false' 
(performance warning)

The cause is in cppunit/include/cppunit/portability/FloatingPoint.h
function floatingPointIsFinite()

#elif defined(CPPUNIT_HAVE__FINITE)
    return _finite(x);
#else

The _finite() return value is an int.
Furthermore, casting to bool is not enough to remove the warning.

The above line could be fixed with :
    return _finite(x) ? true : false;

Could someone check this in please ?

Vincent Rivière
vriviere@...

Hi Baptiste,

The configure test for isfinite() is performed by compiling with C++  
compiler and linking with -lm.  See config/ax_cxx_have_isfinite.m4 for  
the macro itself, and see config.log for the detailed output.

I'm very surprised that it is detected at configure time but the  
function is not defined at compile time.  Can you check carefully  
config.log and to see whether different compiler options might account  
for this?

The only other thing that comes to mind is that the real code is  
inside namespace CppUnit, whereas the configure test is not.  Do we  
need to qualify it to ::isfinite()?


Puzzled,
-Steve

Compilation of CppUnit currently fails on both Solaris 10 (CC 5.8) & Suse 
Linux 9.3 (g++ 3.3.5).

configure detects either isfinite() or finite(), but compilation fails when 
attempting to use that function in CppUnit. Below are the relevant part of 
configure/config-auto and compilation failure message. I don't know how 
configure detects the presence of those function, but my guess is that it is 
not done the same way as we compile CppUnit.

Linux man page state that isfinite() is only available in standard C99 mode 
(which does not seem to be combinable with C++).
Solaris man page state that finite() requires include of <ieeefp.h>. 
isfinite() is also present but I guess it is also only when compiling C (did 
not manage to use it by changing the code).

Are the configure tests compiled in C or C++?

Here is the relevant data:
* Suse Linux 9.3 with g++ 3.3.5:
- configure:
checking for isfinite... yes
checking for finite... yes

- config-auto.h matches configure output:
 /* Define to 1 if you have the `finite' function. */
#ifndef CPPUNIT_HAVE_FINITE
#define CPPUNIT_HAVE_FINITE  1
#endif

/* define if compiler has isfinite */
#ifndef CPPUNIT_HAVE_ISFINITE
#define CPPUNIT_HAVE_ISFINITE  1
#endif

- but compilation fails:

g++ -DHAVE_CONFIG_H -I. -I../../../src/cppunit -I../../config -I../../include 
 -                      I../../../include -g -O2 -MT 
TestAssert.lo -MD -MP -MF .deps/TestAssert.Tpo -c . 
./../../src/cppunit/TestAssert.cpp  -fPIC -DPIC -o .libs/TestAssert.o
In file included from ../../../src/cppunit/TestAssert.cpp:2:
../../../include/cppunit/portability/FloatingPoint.h: In function `bool
   CppUnit::floatingPointIsFinite(double)':
../../../include/cppunit/portability/FloatingPoint.h:38: error: `isfinite'
   undeclared (first use this function)
../../../include/cppunit/portability/FloatingPoint.h:38: error: (Each
   undeclared identifier is reported only once for each function it appears
   in.)

* Solaris 10 (CC 5.8):
- configure:
checking for isfinite... no
checking for finite... yes


- config-auto.h matches configure output:
/* Define to 1 if you have the `finite' function. */
#ifndef CPPUNIT_HAVE_FINITE
#define CPPUNIT_HAVE_FINITE  1
#endif

/* define if compiler has isfinite */
/* #undef CPPUNIT_HAVE_ISFINITE */

- but compilation fails:
CC -DHAVE_CONFIG_H -I. -I. -I../../config -I../../include -I../../include -pta 
 -mt -xtarget=generic -g -features=no%transitions -xildoff -c 
TestAssert.cpp -o TestAssert.o
"../../include/cppunit/portability/FloatingPoint.h", line 40: Error: The 
function "finite" must have a prototype.
1 Error(s) detected.

Baptiste.
---
Baptiste Lepilleur <blep@...>
CppUnit maintainer
OpenTest and CppUnit 2 developer.

Did it crash ? If so it means that there is something seriously wrong on =
your platform.=20

Are you using on the gcc version with broken exception handling ? (see =
http://llvm.org/docs/GettingStarted.html#brokengcc).

Baptiste.
  ----- Original Message -----=20
  From: CppUnit development mailing list=20
  To: cppunit-devel@...
  Sent: Thursday, January 18, 2007 12:29 PM
  Subject: [Cppunit-devel] Problem coming with CPPUNIT when using Linux


  Hi,=20
    I am building the CPPUNIT on linux
  i have followed the following steps to build it ..

  STEPS
     1.                            ./configure
     2.                             make
     3.                             make check
     4.                              make install

  Now when i am at step 3 i.e when giving the command "make check"
   i  am recieveing the following on my computer screen ...
   =20
  TestResultCollectorTest::testWasSuccessfulWithErrorsAndFailures : OK
  TestResultCollectorTest::testWasSuccessfulWithSuccessfulTest : OK
  TestResultCollectorTest::testSynchronizationAddFailure : OK
  TestResultCollectorTest::testSynchronizationStartTest : OK=20
  TestResultCollectorTest::testSynchronizationRunTests : OK
  TestResultCollectorTest::testSynchronizationTestErrors : OK
  TestResultCollectorTest::testSynchronizationTestFailures : OK
  TestResultCollectorTest::testSynchronizationFailures : OK=20
  TestResultCollectorTest::testSynchronizationWasSuccessful : OK
  TestResultTest::testConstructor : OK
  TestResultTest::testStop : OK
  TestResultTest::testAddError
  =20

  after printing the last statement here i.e " =
TestResultTest::testAddError" , it does not move ahead ... and i am not =
able to go to step 4 i.e "check install"


  I would be highly obliged if you can provide me the solution to tackle =
this problem ...


  Regards,
  Gaurav Bhateja ..=20
  ---
Baptiste Lepilleur <blep@...>
CppUnit maintainer
OpenTest and CppUnit 2 developer.

Hi,
   
  I had heard about CPPUnit long time back and wanted to use it in my project. i used the mfc samples and found it to be exciting.
   
  However, I have a few queries regarding one feature of CppUnit "Compiler-like text output to integrate with an IDE".
  the mfc sample which i used, will pop up the testcase UI only when we Run the application.
   
  can the feature be used during developing dlls and services ? i.e is it possible to display the results of the Test cases when we compile/build a dll rather than executing it ?
   
  if yes, please let me know "how"
   
  Thanks,
  Nidhish

 				
---------------------------------
 Here’s a new way to find what you're looking for - Yahoo! Answers

Hello,

   I currently have my test driver code declared in in a .h file, the 
following code is said to have a global, but clearly does not:

void UMDIOTraceTest::testHasMoreRecords()
{
     // Test with a valid trace
     UMDIOTrace test(1, "tests/support/umd_io_trace.tra");
     for (int i = 0; i < 10; i++)
     {
         CPPUNIT_ASSERT(true == test.hasMoreRecords());
         test.nextRecordAsMessage();
     }

     CPPUNIT_ASSERT(false == test.hasMoreRecords());
}

I think simply because the variable is in the header file (i.e. inline), 
your detector must be getting confused.

Cheers,
Brad

What is a  7-zip file?
I assume it's a compressed archive.
How do uncompress?

regards
Gilbert Semmer
---
Senior Software Architect
Advanced Technologies, Stryker Instruments

c/o Stryker Leibinger GmbH & Co. KG
Boetzinger Strasse 41
DE-79111 Freiburg, Germany
Tel. +49 761 4512 457
Fax  +49 761 4512 449 457
--- simple is not easy ---

NOTE: This electronic message is confidential and intended solely for
the use of the individuals or entities to whom it is addressed.

Hi cppunit developers and users!

I have a question about test execution. I have a test suit as shown
below with two test methods. The code is then compiled into a dll
and I run it with this command:

DllPlugInTesterd_dll.exe -c plugin_d.dll

I now have the following problem. During startup cppunit creates two
instances of the ExampleTest class. Then it calls setup(), sampleTest()
and finally teardown(). Then it does the same on the second instance 
with the method sampleTest2().

This looks quite strange. I thought I could initialize some class in the
setup method which is then shared between all the different test method
calls?

The reason why I would like to share an instance between them is that I
have to start an external program during test execution (which takes
very long and therefore should not be started and killed for each test
method invocation). I therefore used a shared pointer which I thought
would be accessible for all test invocations. But since each invocation
uses a different instance this does not work.

Any suggestions how this should be done would be really great!

Please also tell me if what I wrote / want is unclear

Thanks a lot, Fabian



class ExampleTest : public CPPUNIT_NS::TestFixture
{
  CPPUNIT_TEST_SUITE( ExampleTest );
  CPPUNIT_TEST( sampleTest );
  CPPUNIT_TEST( sampleTest2 );
  CPPUNIT_TEST_SUITE_END();

public:
  void setUp();
  void tearDown();

  // The different test methods
  void sampleTest();  
  void sampleTest2();  
};

This mecanism is not supported, but you can implement your own test =
factory in a TestSuite subclass.

Baptiste.
  ----- Original Message -----=20
  From: CppUnit development mailing list=20
  To: cppunit-devel@...
  Sent: Wednesday, January 31, 2007 9:18 PM
  Subject: [Cppunit-devel] Question about cppUnit


  Folks -

  =20

  I am a novice user of cppUnit but a pretty experienced one of JUnit & =
MbUnit. I was wondering if one of you could provide an answer to the =
following query:

  =20

  JUnit & MbUnit have the capability to loop over test cases defined in =
XML files, parse them, dynamically create test cases and run these test =
cases using their respective runners - I was wondering if cppUnit =
offered the same capability so that I could refrain from statically =
defining all my test cases. This would permit me to execute the same =
sequence of test steps though with disparate data defined in these XML =
files

  =20

  Any hints, suggestions will be greatly appreciated.

  =20

  Thanks

---
Baptiste Lepilleur <blep@...>
CppUnit maintainer
OpenTest and CppUnit 2 developer.

Hello,
I think I have found a small bug in the CppUnit Cookbook:

http://cppunit.sourceforge.net/doc/lastest/cppunit_cookbook.html

Section: TestRunner
in the code example is:

static CppUnit::Test *suite()

and should be

static CppUnit:: TestSuite *suite()

Please let me know, if I was right :-)

Best Regards
Marcin Sochacki


***************************************************************************=
*************

Note:  If the reader of this message is not the intended recipient, or an=
 employee or agent responsible for delivering this message to the intended=
 recipient, you are hereby notified that any dissemination, distribution or=
 copying of this communication is strictly prohibited. If you have received=
 this communication in error, please notify us immediately by replying to=
 the message and deleting it from your computer. Thank you.=0D

***************************************************************************=
*************

Hi,

I have an input file with each line contains a specific string that I want
to check against a function that returns a boolean.  How do I create a
single test for each line under cppUnit?  So far, I've been doing all this
under a single test for all lines:

StrTest.h:

class StrTest : public CppUnit::TestFixture {
   CPPUNIT_TEST_SUITE(StrTest);
   CPPUNIT_TEST(testOpen);
   CPPUNIT_TEST_SUITE_END();
  public:
   void testOpen() {
      string line;
      yutString errStr;

      ifstream dbFile("forbiddenList.txt");
      if (dbFile.is_open())
      {
         while (!dbFile.eof())
         {
            getline(dbFile, line);
            cout << line << endl;
            if (!line.empty())
               CPPUNIT_ASSERT(isValidString(line, errStr) == true);
      ...

strTest.cc:

int main() {
   CppUnit::TextUi::TestRunner runner;
   runner.addTest(StrTest::suite());
   runner.run();
}



Thanks

The detection of NaN in assertDoubleEquals failed on Microsoft Visual Studio 
6.

The implementation assumes that NaN != NaN (IEEE-754 says it should). The 
failure was caused by the way MSVC6 compares floating point number equality:
fld         qword ptr [nan]
fcomp       qword ptr [nan]
fnstsw      ax                        // copie fp (floating-point) status to 
register to ax
test        ah,40h                    // test bit 14 of ax (0x4000) => C3 of 
fp status register
je          $L18438+0B9h (00410be2)

According to this doc:
http://webster.cs.ucr.edu/AoA/Windows/HTML/RealArithmetic.html#1000117
C2 should be tested for "undefined" value (which I guess NaN fall into).

NaN comparison works under visual studio 2005. The equality test is done as 
follow:
fld         qword ptr [ebp+10h]
fcomp       qword ptr [ebp+8]
fnstsw      ax
test        ah,44h         // Visual Studio 2005 does test both C2 & C3...
jp          CppUnit::assertDoubleEquals+1B5h (4777A5h)

This seems to confirm that MSVC6 code generator is bug (does not respect 
IEEE-754 standard in spite of what the doc claim).

To work-around this, I added an explicit test for NaN value when testing 
non-finite value for equalities. Here is the function:
// To work around this, a NaN is assumed to be detected if no strict 
ordering is found.
inline bool floatingPointIsUnordered( double x )
{
   // x != x will detect a NaN on conformant platform
   // (2.0 < x  &&  x < 1.0) will detect a NaN on non conformant platform:
   // => no ordering can be found for x.
   return  (x != x) ||  (2.0 < x  &&  x < 1.0);
}

I'm not an expert on floating-point manipulation & NaN. Does any one see 
anything wrong on the above implementation or the comments? I modified the 
defined implementation for isfinite() test to:

/// \brief Tests if a floating-point is finite.
/// @return \c true if x is neither a NaN, nor +inf, nor -inf, \c false 
otherwise.
inline bool floatingPointIsFinite( double x )
{
   double testInf = x * 0.0;  // Produce 0.0 if x is finite, a NaN 
otherwise.
   return testInf == 0.0  &&  !floatingPointIsUnordered(testInf);
}

Feedbacks are welcome,
Baptiste.
---
Baptiste Lepilleur <blep@...>
CppUnit maintainer
OpenTest and CppUnit 2 developer.