Carlos Chávez | 3 Feb 2008 21:24
Favicon

Junit Issues


Hello Armin,
Hello All.

 I ran the junit test cases of OJB, i found some issues; my environment
is: postgresql 8.2.6, java 1.5.0_14, ant 1.7.0, branch OJB_1_0_RELEASE
revision 616989.

1. In the profile for postgresql (profile/postgresql.profile) the
variables torque.database.createUrl and torque.database.buildUrl have the
wrong values.

 the value of torque.database.createUrl is
${urlProtocol}:${urlSubprotocol}://${torque.database.host}/template1, but
it shoul be
${urlProtocol}:${urlSubprotocol}://${torque.database.host}/${urlDbalias}.

 the value of torque.database.buildUrl is
${urlProtocol}:${urlSubprotocol}://${torque.database.host}/${urlDbalias},
but it should be
${urlProtocol}:${urlSubprotocol}://${torque.database.host}/template1

 Basically the torque.database.createUrl is used to indicate the database
test to create and torque.database.buildUrl looks like we need to
indicate some other database via ODBC in order to create a database as
far i understand, so the test try to create the database template1, but
this is wrong because that database already exists and is created by
postgresql.

2. The other issue is related to the table/field name quoted, in the file
(Continue reading)

Armin Waibel | 5 Feb 2008 01:33
Picon
Favicon

Re: Junit Issues

Hi Carlos,

thanks for testing the RC using postgresql (I don't use this DB for 
testing) and the detailed feedback.
The main test database is hsql and some tests use specific 
syntax/keywords not supported by all databases.
My local test-suit results against different databases are:

database    PB   ODMG
----------------------
hsql        0    0
mysql       0    0
oracleXE    0/1  0
maxDB       5/3  0

oracle fail on a locking test because of a date/timestamp issue (oracle 
specific date/timestamp precision).
maxDB fail/errors are caused by the jdbc-driver which show bad paging 
support (seems that maxDB returns wrong results when using 'offset')
I don't want to fix these issues, because the tests will became too 
complex if we always check for the current database.

Carlos Chávez wrote:
> Hello Armin,
> Hello All.
> 
>  I ran the junit test cases of OJB, i found some issues; my environment
> is: postgresql 8.2.6, java 1.5.0_14, ant 1.7.0, branch OJB_1_0_RELEASE
> revision 616989.
> 
(Continue reading)

Carlos Chávez | 5 Feb 2008 07:36
Favicon

Re: Junit Issues

Hi Armin.

Armin Waibel Escribio :-)
> Hi Carlos,
>
> thanks for testing the RC using postgresql (I don't use this DB for
> testing) and the detailed feedback.
> The main test database is hsql and some tests use specific
> syntax/keywords not supported by all databases.
> My local test-suit results against different databases are:
>
> database    PB   ODMG
> ----------------------
> hsql        0    0
> mysql       0    0
> oracleXE    0/1  0
> maxDB       5/3  0
>
> oracle fail on a locking test because of a date/timestamp issue (oracle
> specific date/timestamp precision).
> maxDB fail/errors are caused by the jdbc-driver which show bad paging
> support (seems that maxDB returns wrong results when using 'offset')
> I don't want to fix these issues, because the tests will became too
> complex if we always check for the current database.
>
> Carlos Chávez wrote:
>> Hello Armin,
>> Hello All.
>>
>>  I ran the junit test cases of OJB, i found some issues; my environment
(Continue reading)


Gmane