cppunit-devel — CppUnit Developer Mailing List

[Cppunit-devel] Autoreply from tamilmatrimony.com

[<web...@ta...>]

Dear Member,
 	
	   Thank you for contacting us. For further assistance, please visit the following URL:

Online Support - http://www.tamilmatrimony.com/support.shtml

Note : This is a system generated message. Please do not reply.

Thank You,

regards
Team BharatMatrimony

[Cppunit-devel] =?iso-8859-1?Q?C1=C1LlSS_VA1=EDUM_Vi=C0GGRA?=

[Franziska M. <Mea...@fw...>]

Hello, 

Eyes glazed with lassitude and fear looked up piteously out of ha
inference drawn from it might similarly have been drawn from Bloo
was bubbling to his lips, he swept on:  You have deliberated, yo
They took in sail and hove to as they came up with the drifting
be hanging from the yardarm of the Encarnacion at this moment.
already.
Do you think it's to benefit his health we're taking him?  There'
have opened for me the gates of hope.
It is what I myself should wish to do in like case.
realize it.  That is why there are so many madmen in the world.
what you did, and I realize that partly, at least, you may have
her stern chasers.  The small shot went whistling through La


Have a nice day.

[Cppunit-devel] keep it up

[Gaurav S. <gau...@v2...>]

We just want you people to provide as much detail as you can without
worrying about the length of the code. By the way I really appreciate the
materials you have currently provided. Once again thanks.
Gaurav Seth
Software Engg.
V2Solutions
A New Vision to Solutions
India: +91-22-56733201 Ext: 201
US : 1-408-705-2141 Ext: 201
http://www.v2solutions.com

[Cppunit-devel] CppUnit, one instance of a fixture per test run

[Eddie P. <ed...@re...>]

Hello!

 

We ran into a little difficulty with CppUnit here, and so I've built a
solution for it, and I'm wondering if it would be of use to the CppUnit
world at large. 

 

What we found, was that CppUnit ends up creating a new instance of a fixture
for each test method it's about to run. We were relying on the fact that
CppUnit would have one instance of a fixture, and iterate through each of
the methods enclosed, so that we could do some expensive construction only
once, and not have it happen for every test.

 

Anyhow, after rooting through the HelperMacros.h file (thanks for
documenting it! :-)), I found the root of our problem was the CPPUNIT_TEST
macro:

 

/*! \brief Add a method to the suite.

* \param testMethod Name of the method of the test case to add to the

*                   suite. The signature of the method must be of

*                   type: void testMethod();

* \see  CPPUNIT_TEST_SUITE.

*/

#define CPPUNIT_TEST( testMethod )                        \

    CPPUNIT_TEST_SUITE_ADD_TEST(                          \

        ( new CPPUNIT_NS::TestCaller<TestFixtureType>(    \

                  context.getTestNameFor( #testMethod),   \

                  &TestFixtureType::testMethod,           \

                  context.makeFixture() ) ) )

 

Apparently the problem is the context.makeFixture() call will create a new
fixture per method, which destroys our ability to construct things only
once.

 

As such, what I've done is the following:

 

1)       Move the bulk of the 'logic' from CPPUNIT_TEST to a macro I call
CPPUNIT_COMMON_TEST, and wired CPPUNIT_TEST to use it:

 

/*! \brief The common meat of adding a test

 *

 * This is used internatlly by CPPUNIT_TEST_AS_PART_OF_ONE_FIXTURE

 * and CPPUNIT_TEST

 *

 * \param testMethod Name of the method of the test case to add to the

 *                   suite. The signature of the method must be of

 *                   type: void testMethod(); 

 *

 * \param fixture    The fixture instance to execute against. 

 * \see  CPPUNIT_TEST CPPUNIT_TEST_AS_PART_OF_ONE_FIXTURE

 */

#define CPPUNIT_COMMON_TEST( testMethod, fixture )
\

    CPPUNIT_TEST_SUITE_ADD_TEST(
\

    ( new CPPUNIT_NS::TestCaller<TestFixtureType>(  context.getTestNameFor(
#testMethod)    \

                                                ,
&TestFixtureType::testMethod            \

                                                ,   fixture
\

                                                ) ) ) 

 

/*! \brief Add a method to the suite.

 * \param testMethod Name of the method of the test case to add to the

 *                   suite. The signature of the method must be of

 *                   type: void testMethod();

 * \see  CPPUNIT_TEST_SUITE.

 */

#define CPPUNIT_TEST( testMethod )                              \

    CPPUNIT_COMMON_TEST( testMethod, context.makeFixture() )

 

 

2)       Created a variant of CPPUNIT_TEST that uses a variable fixture from
another macro I'll define in step 3:

 

/*! \brief Executes a test against the fixture specified earlier

 *

 *  This will add a test, however it will use the fixture specified 

 *  in CPPUNIT_ONE_TEST_FIXTURE_ONLY.

 *  Make sure to call CPPUNIT_ONE_TEST_FIXTURE_ONLY before this.

 * 

 * \param testMethod Name of the method of the test case to add to the

 *                   suite. The signature of the method must be of

 *                   type: void testMethod(); 

 * \see CPPUNIT_ONE_TEST_FIXTURE_ONLY

 */

#define CPPUNIT_TEST_AS_PART_OF_ONE_FIXTURE( testMethod )
\

    CPPUNIT_COMMON_TEST( testMethod, *pTestFixture )

 

 

3)       Created a new macro, to be used after CPPUNIT_TEST_SUITE, if you
want this functionality:

 

/*! \brief Creates only one fixture for the run

 *

 * This macro is to be used after CPP_UNIT_TEST_SUITE.

 * It will build one test fixture, to be used for each of the

 * test runs.

 */

#define CPPUNIT_ONE_TEST_FIXTURE_ONLY(  )
\

      TestFixtureType *pTestFixture = context.makeFixture()

 

So, the usage will be something like this:

 

class StringTests : public CPPUNIT_NS::TestFixture

{

public:

    StringTests();

    ~StringTests();

private:   

    CPPUNIT_TEST_SUITE  ( StringTests );

    CPPUNIT_ONE_TEST_FIXTURE_ONLY();

    CPPUNIT_TEST_AS_PART_OF_ONE_FIXTURE( TestFoo ); 

    CPPUNIT_TEST_SUITE_END();

    void TestFoo ();

};

 

 

Anyhow, I'm looking for some feedback: I'm not super happy with the macro
names, but they seem explicit enough. Would this be welcomed as a patch to
HelperMacros.h, or some variant thereof?

 

I look forward to your response!

 

Cheers,

 

-e-

[Cppunit-devel] Questions regarding CPPUnit

[Reagan, T. <tr...@am...>]

Hi,
    I was wondering if someone could answer a couple of questions for me.  I
can't seem to find anyway to access the PROPERTIES and can find no examples.
Does the 1.10.2 release support them? It appears they are only available
inside the static suite function, am I missing something here?  Also, I
noticed that if I try to use the CPPUNIT_TEST_SUB_SUITE macro I get another
suite of tests that include both the parent tests and the tests of the new
sub suite.  Is this the way it is supposed to work?  I was expecting to have
a new suite that fell underneath the parent and only contained the tests
defined for that class.  Finally, I couldn't seem to find anyway to provide
a separate fixture for the sub suite, is this the intended implementation?
I was hoping you could specify separate setUps and tearDowns for each
suite/sub suite since they may have different requirements.
    Thanks,
       Troy
 
 
Troy C Reagan
Software Engineer
American Student Assistance
Boston, MA 02114
tr...@am... <mailto:tr...@am...> 
 

[Cppunit-devel] Here is your documents. - ALCATEL POLICY: Your message has been refused

[<ald...@al...>]

jes...@it...
**************** e-mail Manager Notification ****************
As a security precaution this mail was blocked and discarded since it
contains attachments with file extensions not allowed
by our email policy (.exe .vbs etc..)
Our mail system policy does not accept certain attachment types.
See http://aww.alcatel.com/group/ist/policy/email_attachments.htm for
additional details.

In addition
a list of  ZIP files attachments are filtered at the moment
such as attach.zip
document.zip
info.zip ...
This is a temporary measure due to a number of worms currently rapidly
spreading on the Internet.

In case of doubt
please rename your attachment with a second extension (such as
filename.zip.RENAMED) and resend it.

If you have questions contact your local e-mail support representative.
************************ End of message ***********************


Scanned by ScanMail for Lotus Notes 2.6 SP1
with scanengine 7.510-1002
and pattern version 2.617.00

[Cppunit-devel] =?iso-8859-1?Q?V=E0LLlUM_C=ECALlS_V=ECAGRA?=

[Agneta B. <Bec...@ga...>]

Hello, 

of their meeting was in itself curious.  He did not perceive the
King's commission if so be him'd quit piracy and be o' good
Bishop, marvelling a little, after the manner in which yesterday
I saw him often.  I knew him very well.
the gallant Captain himself did not survive to enquire into it.
in his power to offer her a great position, one to which she, a
Levasseur contained his rage, that he might reason with the Irish
and in that guise I spent a week in the city and studied carefull
Taunton.  Those who were too sorely wounded to march were conveye
had smashed through into the great cabin, reducing it to wreckage
I thought that you....
powder on his face to render him unrecognizable.


Have a nice day.

[Cppunit-devel] Re: OK OK

[India N. L. S. (14.3) <LIS...@LI...>]

> ok ok ok,,,,, here is it
Too many arguments specified - maximum is 2.

Summary of resource utilization
-------------------------------
 CPU time:        0.000 sec                Device I/O:        0
 Overhead CPU:    0.000 sec                Paging I/O:        0
 CPU model:         300MHz AMD-K6 3D processor (125M)
 Job origin:      cpp...@LI...

[Cppunit-devel] Message ("Your message dated Fri, 06 May 2005 18:00:02 UTC...")

[India N. L. S. (14.3) <LIS...@LI...>]

Your message dated Fri, 06 May 2005 18:00:02 UTC with no subject has been
submitted  to   the  moderator   of  the   INDNET  list:   India  Network
<in...@YA...>.

[Cppunit-devel] Message ("Your message dated Fri, 06 May 2005 18:00:02 UTC...")

[India N. L. S. (14.3) <LIS...@LI...>]

Your message dated Fri, 06 May 2005 18:00:02 UTC with no subject has been
submitted  to   the  moderator  of   the  insur-l  list:   India  Network
<in...@YA...>.

Re: [Cppunit-devel] MFC test runner broken?

[Roel V. <ro...@ri...>]

Hi,

Sorry for replying to myself, seems that I just made a fool out of 
myself <blush> The problem was that I need to select a testcase first by 
clicking 'browse' - and that the combobox is a 'history' of most 
recently used tests. Sorry for the noise.

cheers,

roel



Roel Vanhout wrote:
> Hi,
> 
> I've tried using the mfc test runner but whatever I do, I cannot get any 
> tests to show up in the combo box where they should be. So then I tried 
> the example of the testrunner that comes with cppunit but that one 
> doesn't work either. So before I start posting code and going into the 
> mfc testrunner code, can anyone confirm that the example in 0.10.2 does 
> actually work? Anyone any ideas what could be causing this problem? (and 
> yes, I am doing runner.AddTest :) Actually I've also tried using the 
> registry but that didn't help either). Thanks.
> 
> cheers,
> 
> roel
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.
> Get your fingers limbered up and give it your best shot. 4 great events, 4
> opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
> win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
> _______________________________________________
> Cppunit-devel mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppunit-devel

[Cppunit-devel] MFC test runner broken?

[Roel V. <ro...@ri...>]

Hi,

I've tried using the mfc test runner but whatever I do, I cannot get any 
tests to show up in the combo box where they should be. So then I tried 
the example of the testrunner that comes with cppunit but that one 
doesn't work either. So before I start posting code and going into the 
mfc testrunner code, can anyone confirm that the example in 0.10.2 does 
actually work? Anyone any ideas what could be causing this problem? (and 
yes, I am doing runner.AddTest :) Actually I've also tried using the 
registry but that didn't help either). Thanks.

cheers,

roel

RE: [Cppunit-devel] TestPlugInRunner Broken?

[Adriaan B. <adr...@re...>]

After some more investigation, I have a strong suspicion that the problem is caused by not building both modules, the runner and the
test DLL with the DLL runtime library.  There is a known issue with the std library and heap corruption when used across the DLL
boundary.  This is probably the reason the DLL call code was removed?
 
The only solutions I can think of are:
 
a) Re-build all of my production code into the test DLL so it can link to the DLL runtime.
 
b) Put all the test-running logic inside the DLL and use listeners to track the state (performing the appropriate copies to avoid
passing std::string instances across the DLL boundary.
 
I anyone has found any other solutions, or I am way off base, please chime in.
 
Thanks.

RE: [Cppunit-devel] TestPlugInRunner Broken?

[Adriaan B. <adr...@re...>]

The relevant code appears to have been there initially and been removed for the 1.9 release.  Does anyone know why?
 

[Cppunit-devel] TestPlugInRunner Broken?

[Adriaan B. <adr...@re...>]

As far as I can tell, the TestPlugInRunner is supposed to call the exported function  TestPlugInInterface *GetTestPlugInInterface()
on the loaded Dll.  From what I can see, reading the code, it does not do this, it simply gets ant registered tests from the local
module (of which there are none, of course).  Is this code funamentally broken, or am I missing something?
 
The relevant function (I think?):
 
CPPUNIT_NS::Test *
TestPlugIn::makeTest()
{
  reloadDll();
  return CPPUNIT_NS::TestFactoryRegistry::getRegistry().makeTest();
}

I would expect a call to GetTestPlugInInterface here?
 
Regards.
 

Adriaan Brae
WTS Development
(x281)


 

[Cppunit-devel] Doubts regarding QtTestRunner..

[siva s. <ssa...@gm...>]

Hello,
i am new to Linux and so to Qt designer.
i have used cppunit with my application in windows and able to come
out with the test suite successfully.
I am now supposed to do the same in linux for which i have to use Qt
designer,i guess.
i tried to run the examples.pro given in the examples\qt.but i am
getting the errors in Mian.cpp as "CppUnit::QtUi" undeclared
identifier, etc.what do i do to get rid of this error. Please guide me
to solve this problem.
Thanks in advance.
Shankari

[Cppunit-devel] about cppunit

[Huiting H. <heh...@zd...>]

Hi,

=20

Does cppunit support 64-bit multithreading programe?

Thanks ^_^

=20

Best regards,

Huiting

[Cppunit-devel] cpp unit

[Dermot M. <D.M...@an...>]

Hi,
=20
Where can I find documentation, to create information on the test run,
eg a log file, containing information on each test, whether it has
passed or not?
=20
Thanks
Dermot..

[Cppunit-devel] RE: How to use cppunit on AIX5L?

[Huiting H. <heh...@zd...>]

Hello Henning,

=20

I'm very happy to tell you that the problem has been solved.

The default compiler for c++ is g++, but my system uses xlC as the
compiler.

I added the initial value "CXX=3DxlC_r" while doing the first step
'configure' and the test codes can be successfully executed.

Thank you very much ^_^.

=20

Best regards,

Huiting

Re: [Cppunit-devel] RE: How to use cppunit on AIX5L?

[Henning W. <hen...@di...>]

Am Donnerstag 14. April 2005 11:06 schrieb Huiting He:
> Hello Henning,
>[Compile and link problem fixed]
> However, the core dump problem still exists.
> If the codes do not contain any test case (don't add any test case to
> TestSuite),  the execution file can be successfully run:
> Otherwise, "Illegal instruction (core dumped)" will occur.
>
> You wrote that it may be a library problem, then, how to solve it?
>
> Best regards,
>
> Huiting

Hello Huiting,

sorry for the late reply. If your code can be now sucessfully linked, it 
should be also executable.. I have unfortunally no aix system available, and 
no experience with this system.

Have you examined the core dump of your test case with a debugger program? On 
linux i use the following commands:

- gdb "executable" "corefile" starts the gnu debugger
- "where" shows you a backtrace of the problem
(please omit the quotes, perhaps the aix system ships another debugger)

This could give you further hints to solve your problem.
If the problem persists, you could send me the complete commands used to 
compile the test case. And the output from ldd "your_executable" could also 
be helpful. Have you installed the cppunit in your system library path? 

Henning

[Cppunit-devel] cppunit in solaris 9 with forte 6.2

[Michael K. <ki...@es...>]

    We are trying to get some of our c++ code under cruisecontrol, which means 
    getting it under unit test.  We are trying to get cppunit to compile under sun's 
    forte 6.2 compiler, but aren't having a whole lot of luck.

    Before I start really delving into it, does anyone out there have any pointers to 
    recent instructions of people who have done this?  It seems there are a number 
    of currently published ways, none of which seem to work on solaris 9 with forte 
    6.2

We have also been told that forte 6.2 doesn't support the standard template library.  I'm
a java programmer (and thus my rather simple questions), and I find it difficult to beleive
that forte 6.2 doesn't support the "STANDARD".  But it is sun, and perhaps this is the case.

More likely, I would guess that our environment isn't configured for the standard template library,
in which case I'll need to figure that out too.

Any help would be much appreciated.

Thanks,
Mike (just a poor java programmer attempting to do C++)

 ---
ki...@es...
To obtain my PGP public key, mail "SEND PUB KEY" in the 
subject to "ki...@es..."

Re: [Cppunit-devel] How to use cppunit on AIX5L?

[Henning W. <hen...@di...>]

Am Dienstag 12. April 2005 08:38 schrieb Huiting He:
> Hi,
>
> I'm writing to you for help because I've met some problems while using
> cppuint.
>
> My OS is AIX5L; I download cppunit-1.10.2 from
> http://sourceforge.net/projects/cppunit
> [...]
> I have used the test codes written on CppUnit Cookbook. What was worse,
> the codes even can't be successfully compiled.

> ld: 0711-317 ERROR: Undefined symbol:
> CppUnit::TestCase::run(CppUnit::TestResult*)
>[...]
> I have already included all necessary head files. How to deal with this
> error?

Hello Huiting He, 

the error message is from ld, that is the linker program. Have you added the 
appropriate linker flags to the compiler/linker invocation? On my linux 
system i use "-lcppunit -ldl". 
And did the linker find the cppunit lib? You could either install cppunit 
system-wide, or you must add the location of the lib to the compiler call 
too. You wrote that you could compile the cppunit test examples. Please refer 
to them for the right compiler flags.

The coredump problem after the execution of the tests could be perhaps a 
library problem too.

Best regards,

Henning

[Cppunit-devel] How to use cppunit on AIX5L?

[Huiting H. <heh...@zd...>]

Hi,

=20

I'm writing to you for help because I've met some problems while using
cppuint.

My OS is AIX5L; I download cppunit-1.10.2 from
http://sourceforge.net/projects/cppunit

I have tried to install cppunit followed the instruction:

  1. `cd' to the directory containing the package's source code and type

     `. /configure --disable-shared --disable-typeinfo-name`

  2. Type `gmake' to compile the package.

  3. Optionally, type `gmake check' to run any self-tests that come with
the package.

  4. Type `gmake install' to install the programs and any data files and
documentation.

Problem happened during the third step.=20

bash-2.05$ gmake check

Making check in src

gmake [1]: Entering directory `/home/hth/testcase/cppunit-1.10.2/src'

Making check in cppunit

gmake [2]: Entering directory
`/home/hth/testcase/cppunit-1.10.2/src/cppunit'

gmake [2]: Nothing to be done for `check'.

gmake [2]: Leaving directory
`/home/hth/testcase/cppunit-1.10.2/src/cppunit'

Making check in DllPlugInTester

gmake [2]: Entering directory
`/home/hth/testcase/cppunit-1.10.2/src/DllPlugInTester'

gmake DllPlugInTesterTest

gmake [3]: Entering directory
`/home/hth/testcase/cppunit-1.10.2/src/DllPlugInTester'

source=3D'DllPlugInTesterTest.cpp' object=3D'DllPlugInTesterTest.o'
libtool=3Dno \

depfile=3D'.deps/DllPlugInTesterTest.Po'
tmpdepfile=3D'.deps/DllPlugInTesterTest.TPo' \

depmode=3Dgcc /bin/sh../../config/depcomp \

g++ -DHAVE_CONFIG_H -I. -I. -I../../config -I../../include
-I../../include    -g -O2 -c -o DllPlugInTesterTest.o `test -f
'DllPlugInTesterTest.cpp' || echo './'`DllPlugInTesterTest.cpp

source=3D'CommandLineParserTest.cpp' object=3D'CommandLineParserTest.o'
libtool=3Dno \

depfile=3D'.deps/CommandLineParserTest.Po'
tmpdepfile=3D'.deps/CommandLineParserTest.TPo' \

depmode=3Dgcc /bin/sh ../../config/depcomp \

g++ -DHAVE_CONFIG_H -I. -I. -I../../config -I../../include
-I../../include    -g -O2 -c -o CommandLineParserTest.o `test -f
'CommandLineParserTest.cpp' || echo './'`CommandLineParserTest.cpp

/bin/sh ../../libtool --mode=3Dlink g++  -g -O2   -o DllPlugInTesterTest
-ldl DllPlugInTesterTest.o CommandLineParser.o CommandLineParserTest.o
../../src/cppunit/libcppunit.la

g++ -g -O2 -o DllPlugInTesterTest DllPlugInTesterTest.o
CommandLineParser.o CommandLineParserTest.o  -ldl
../../src/cppunit/.libs/libcppunit.a

gmake[3]: Leaving directory
`/home/hth/testcase/cppunit-1.10.2/src/DllPlugInTester'

gmake  check-TESTS

gmake[3]: Entering directory
`/home/hth/testcase/cppunit-1.10.2/src/DllPlugInTester'

/bin/sh: 77724 Illegal instructions(coredump)

FAIL: DllPlugInTesterTest

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

1 of 1 tests failed

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

gmake[3]: *** [check-TESTS] Error 1

gmake[3]: Leaving directory
`/home/hth/testcase/cppunit-1.10.2/src/DllPlugInTester'

gmake[2]: *** [check-am] Error 2

gmake[2]: Leaving directory
`/home/hth/testcase/cppunit-1.10.2/src/DllPlugInTester'

gmake[1]: *** [check-recursive] Error 1

gmake[1]: Leaving directory `/home/hth/testcase/cppunit-1.10.2/src'

gmake: *** [check-recursive] Error 1

=20

It's my first time to use cppunit, so I don't know how to deal with this
problem.

As it is an optional step, I just skip it and did the last step and
finished the installation.

All the test codes under the folder "example" can be successfully
compiled but can't be=20

executed -- "Illegal instruction (core dumped)". Why?

I have used the test codes written on CppUnit Cookbook. What was worse,
the codes=20

even can't be successfully compiled.=20

ld: 0711-317 ERROR: Undefined symbol:
CppUnit::TestCase::run(CppUnit::TestResult*)

ld: 0711-317 ERROR: Undefined symbol:
CppUnit::TestLeaf::countTestCases() const

ld: 0711-317 ERROR: Undefined symbol:
CppUnit::TestLeaf::getChildTestCount() const

ld: 0711-317 ERROR: Undefined symbol: CppUnit::Test::getChildTestAt(int)
const

ld: 0711-317 ERROR: Undefined symbol: CppUnit::TestCase::getName() const

ld: 0711-317 ERROR: Undefined symbol: CppUnit::Test::findTestPath(const
CppUnit::Test*,CppUnit::TestPath&) const

ld: 0711-317 ERROR: Undefined symbol: CppUnit::Test::findTestPath(const
std::basic_string<char,std::char_traits<char>,std::allocator<char>
>&,CppUnit::TestPath&) const

ld: 0711-317 ERROR: Undefined symbol: CppUnit::Test::findTest(const
std::basic_string<char,std::char_traits<char>,std::allocator<char> >&)
const

ld: 0711-317 ERROR: Undefined symbol:
CppUnit::Test::resolveTestPath(const
std::basic_string<char,std::char_traits<char>,std::allocator<char> >&)
const

ld: 0711-317 ERROR: Undefined symbol:
CppUnit::Test::checkIsValidIndex(int) const

ld: 0711-317 ERROR: Undefined symbol:
CppUnit::TestLeaf::doGetChildTestAt(int) const

ld: 0711-317 ERROR: Undefined symbol:
.CppUnit::TextTestRunner::TextTestRunner(CppUnit::Outputter*)

ld: 0711-317 ERROR: Undefined symbol:
.CppUnit::TestRunner::addTest(CppUnit::Test*)

ld: 0711-317 ERROR: Undefined symbol:
.CppUnit::TextTestRunner::run(std::basic_string<char,std::char_traits<ch
ar>,std::allocator<char> >,bool,bool,bool)

ld: 0711-317 ERROR: Undefined symbol:
.CppUnit::TextTestRunner::~TextTestRunner()

ld: 0711-317 ERROR: Undefined symbol: .operator new(unsigned long)

ld: 0711-317 ERROR: Undefined symbol:
.CppUnit::TestSuite::TestSuite(std::basic_string<char,std::char_traits<c
har>,std::allocator<char> >)

ld: 0711-317 ERROR: Undefined symbol:
.CppUnit::TestSuite::addTest(CppUnit::Test*)

ld: 0711-317 ERROR: Undefined symbol: .operator delete(void*)

ld: 0711-317 ERROR: Undefined symbol: .CppUnit::Message::Message(const
std::basic_string<char,std::char_traits<char>,std::allocator<char>
>&,const
std::basic_string<char,std::char_traits<char>,std::allocator<char> >&)

ld: 0711-317 ERROR: Undefined symbol:
.CppUnit::SourceLine::SourceLine(const
std::basic_string<char,std::char_traits<char>,std::allocator<char>
>&,int)

ld: 0711-317 ERROR: Undefined symbol:
.CppUnit::Asserter::failIf(bool,const CppUnit::Message&,const
CppUnit::SourceLine&)

ld: 0711-317 ERROR: Undefined symbol:
.CppUnit::SourceLine::~SourceLine()

ld: 0711-317 ERROR: Undefined symbol: .CppUnit::TestCase::TestCase(const
std::basic_string<char,std::char_traits<char>,std::allocator<char> >&)

ld: 0711-317 ERROR: Undefined symbol: .CppUnit::TestCase::~TestCase()

ld: 0711-317 ERROR: Undefined symbol: .std::_String_base::_Xran() const

ld: 0711-317 ERROR: Undefined symbol: .std::_String_base::_Xlen() const

ld: 0711-317 ERROR: Undefined symbol:
.std::__setUncaughtExceptionFlag(bool)

ld: 0711-317 ERROR: Undefined symbol: .__CleanupCatch

ld: 0711-317 ERROR: Undefined symbol: .operator new(unsigned long,void*)

=20

I have already included all necessary head files. How to deal with this
error?

=20

I'm really puzzled. Could you please tell me how to use cppunit on
AIX5L?

Thank you very much. Looking forward to your reply. ^_^

=20

Best regards,

Huiting

[Cppunit-devel] unresolved external symbol

[slatvick <sla...@gm...>]

Cannot solve the problem while compile next:
 // CODE=20
=20
int Testing()

{

// Get the top level suite from the registry

CppUnit::Test *suite =3D=20
CppUnit::TestFactoryRegistry::getRegistry().makeTest();

/*

// Adds the test to the list of test to run

CppUnit::TextUi::TestRunner runner;

runner.addTest( suite );

// Change the default outputter to a compiler error format outputter

runner.setOutputter( new CppUnit::CompilerOutputter( &runner.result(),

std::cerr ) );

// Run the tests.

bool wasSucessful =3D runner.run();

// Return error code 1 if the one of test failed.

return wasSucessful ? 0 : 1;

*/

return 0;

}
int main(....
 // ERROR
=20
------ Build started: Project: MPI_Robot, Configuration: Debug Win32 ------

Linking...

MPI_Robot.obj : error LNK2019: unresolved external symbol "public: static=
=20
class CppUnit::TestFactoryRegistry & __cdecl=20
CppUnit::TestFactoryRegistry::getRegistry(class=20
std::basic_string<char,struct std::char_traits<char>,class=20
std::allocator<char> > const &)" (?getRegistry@TestFactoryRegistry@CppUnit@=
@
SAAAV12@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z)=
=20
referenced in function "int __cdecl Testing(void)" (?Testing@@YAHXZ)

Debug/MPI_Robot.exe : fatal error LNK1120: 1 unresolved externals

Build log was saved at "file://c:\Documentes\Development and=20
idies\Programming\Visual Studio Projects\mpi\MPI_Robot\Debug\BuildLog.htm"

MPI_Robot - 2 error(s), 0 warning(s)

 ---------------------- Done ----------------------

Build: 0 succeeded, 1 failed, 0 skipped

[Cppunit-devel] Linking Error

[Izzy <mor...@gm...>]

Hello,

Im trying to link cppunit with my dll's. However i get a bunch of 
linking error on unresolved symbols on the Message, Sourceline etc. Can 
someone point me out what im missing? Im using msvc++ 2003 .net. I tried 
1.10.2 and 1.9.14 , both give me the same errors.
If someone has a link to a email regarding the same problem with a 
solution to it, please let me know.

Regards
Morrowyn