[fdo-dev] [UnitTest] More detailed log

[Dan Stoica]

In addition:

Use a UnitTestUtil::FailOnException(FdoString *ex) or CPPUNIT_FAIL( char
*ex) in the catch block. 

The fact we don't follow consistently this rule is because some of the
unit tests are quite old. 

Dan.



-----Original Message-----
From: Romica Dascalescu 
Sent: Monday, August 28, 2006 9:44 AM
To: dev at fdo.osgeo.org
Subject: RE: [fdo-dev] [UnitTest] More detailed log


Hi Mateusz,

You must fill up your MySqlInit.txt file with the right values.
The unit test stops when an exception is thrown in a test function and
there is missing a "try{}catch(...){}" block.

Regards,
Romy.

-----Original Message-----
From: Mateusz Loskot [mailto:mateusz at loskot.net] 
Sent: Sunday, August 27, 2006 10:28 PM
To: dev at fdo.osgeo.org
Subject: [fdo-dev] [UnitTest] More detailed log

Hi,

I tried to run MySQL Unit Test for the first time and it failed
with exception thrown.
I expected it, but I wonder how could I get detailed log message
with file/line/function info?
Simply, how to know what to fix here?


mloskot:~/dev/fdo/_svn/Providers/GenericRdbms/Src/UnitTest$
./UnitTestMySql
Test ID: 2031106080
.F.F.F.F.F.F.F.F.F.F.F..F.F.F.Test is in group 'rollback', skipping test
.Initializing Connection ...
terminate called after throwing an instance of 'FdoException*'
Aborted

Cheers
-- 
Mateusz Loskot
http://mateusz.loskot.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe at fdo.osgeo.org
For additional commands, e-mail: dev-help at fdo.osgeo.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe at fdo.osgeo.org
For additional commands, e-mail: dev-help at fdo.osgeo.org