db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepa Remesh (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-398) Exclude tests for J2ME/CDC/Foundation platform
Date Thu, 22 Dec 2005 22:53:31 GMT
     [ http://issues.apache.org/jira/browse/DERBY-398?page=all ]

Deepa Remesh updated DERBY-398:
-------------------------------

    Attachment: jdk14_tests.diff
                jdk14_tests.status

Attaching a patch 'jdk14_tests.diff' which adds jdk14 suite and some more tests to run with
J2ME/CDC/FP. Changes are:

M      java\tools\org\apache\derby\impl\tools\ij\mtTestCase.java

If ij.dataSource property is specified, remove ij.database and ij.protocol property. Similar
to what is done by test harness.  This is needed for stress.multi.

M      java\testing\org\apache\derbyTesting\functionTests\tests\i18n\iepnegativetests_ES_app.properties
M      java\testing\org\apache\derbyTesting\functionTests\multi\stress\init.properties
M      java\testing\org\apache\derbyTesting\functionTests\multi\stress\run.properties

Change 'database' property to 'ij.database' and add ij.dataSource properties.

M      java\testing\org\apache\derbyTesting\functionTests\tests\lang\holdCursorJava.java
M      java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\autoGeneratedJdbc30.java

Execute procedure tests only if DriverManager class is present.

A      java\testing\org\apache\derbyTesting\functionTests\tests\lang\procedureJdbc30_app.properties
A      java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\checkDataSource30_app.properties
M      java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\copyfiles.ant
M      java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\parameterMetaDataJdbc30_app.properties

These tests are part of jdk14 suite but cannot be run with JSR169.

M      java\testing\org\apache\derbyTesting\functionTests\tests\lang\maxMemPerTab_app.properties
M      java\testing\org\apache\derbyTesting\functionTests\tests\lang\triggerStream_app.properties
M      java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\LOBTest_app.properties
M      java\testing\org\apache\derbyTesting\functionTests\tests\store\bootLock_app.properties

Removed 'runwithfoundation=false' exclude from these tests

M      java\testing\org\apache\derbyTesting\functionTests\tests\lang\copyfiles.ant
D      java\testing\org\apache\derbyTesting\functionTests\tests\lang\maxMemPerTab.sql
A      java\testing\org\apache\derbyTesting\functionTests\tests\lang\triggerStream.java
A      java\testing\org\apache\derbyTesting\functionTests\tests\lang\maxMemPerTab.java
D      java\testing\org\apache\derbyTesting\functionTests\tests\lang\triggerStream.sql
M      java\testing\org\apache\derbyTesting\functionTests\suites\derbylang.runall
M      java\testing\org\apache\derbyTesting\functionTests\master\maxMemPerTab.out
M      java\testing\org\apache\derbyTesting\functionTests\master\triggerStream.out
M      java\testing\org\apache\derbyTesting\functionTests\util\StreamUtil.java
M      java\testing\org\apache\derbyTesting\functionTests\util\ProcedureTest.java

maxMemPerTab and triggerStream tests are converted from sql to java to avoid using procedures
with nested connections. 

M      java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\dbMetaDataJdbc30.java
M      java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\resultsetJdbc30.java

NoSuchMethodError for methods not present in JSR169.

M      java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\users_app.properties

User and password are specified in databaseName itself so that they don't get re-used for
other connections in the test

M      java\testing\org\apache\derbyTesting\functionTests\tests\store\bootLock1.java
M      java\testing\org\apache\derbyTesting\functionTests\tests\store\bootLock.java

Use Datasource instead of DriverManager

M      java\testing\org\apache\derbyTesting\functionTests\harness\RunList.java
M      java\testing\org\apache\derbyTesting\functionTests\suites\jdk14.properties

Change 'jdk14test' property to 'jdbc30test' property. Add check for jdb30test so that it can
run with foundation vm. 

M      java\testing\org\apache\derbyTesting\functionTests\master\resultsetJdbc30.out

Small correction in the test and master. 

A      java\testing\org\apache\derbyTesting\functionTests\master\j9_foundation\iepnegativetests_ES.out

Added new master because of difference in output of show connections.

A      java\testing\org\apache\derbyTesting\functionTests\master\j9_foundation\dbMetaDataJdbc30.out
A      java\testing\org\apache\derbyTesting\functionTests\master\j9_foundation\LOBTest.out
A      java\testing\org\apache\derbyTesting\functionTests\master\j9_foundation\autoGeneratedJdbc30.out
A      java\testing\org\apache\derbyTesting\functionTests\master\j9_foundation\resultsetJdbc30.out
A      java\testing\org\apache\derbyTesting\functionTests\master\j9_foundation\holdCursorJava.out
A      java\testing\org\apache\derbyTesting\functionTests\master\j9_foundation\users.out

New masters for difference in behaviour in J2ME

M      java\testing\org\apache\derbyTesting\functionTests\suites\jdk14.runall

Remove store/bootlock.java which is also part of store suite. 

With this patch, I ran derbyall with Sun J2SE 1.4.2. No failures. Also ran derbyall with foundation
VM in IBM WCTME 5.7. Some known failures:

derbyall/derbyall.fail:jdbcapi/metadata.java
derbyall/derbyall.fail:jdbcapi/odbc_metadata.java
derbyall/derbyall.fail:junitTests/lang/LangSuite.java
derbyall/derbyall.fail:i18n/JapanCodeConversion.sql
derbyall/storeall/storeall.fail:unit/T_RawStoreFactory.unit

I have couple of questions. I'd appreciate if anyone can answer these:

1. It is documented that triggers are not supported on this platform. But all trigger tests
we have pass. The only test excluded now is lang/triggerGeneral.sql. This also passes with
some changes to avoid using BigDecimal and nested connections. I have not included changes
for this test in this patch. Is there any known case where triggers fail with CDC and jsr169?
If not, I think this limitation can be removed.

2. I think it will be clearer to rename 'jdk14' suite to 'jdbc30' since these tests are for
jdbc 3.0. If this is okay, I can make this  change in my next patch.

Please review/commit this patch. Thanks.

> Exclude tests for J2ME/CDC/Foundation platform
> ----------------------------------------------
>
>          Key: DERBY-398
>          URL: http://issues.apache.org/jira/browse/DERBY-398
>      Project: Derby
>         Type: Sub-task
>   Components: Test
>     Reporter: Deepa Remesh
>     Assignee: Deepa Remesh
>  Attachments: derby-398_2.diff, derby-398_2.status, derbyall_report_2.txt, jdbcapi_lang_patch.diff,
jdbcapi_lang_patch.status, jdk14_tests.diff, jdk14_tests.status, nullSQLText_patch.diff, nullSQLText_patch.status,
readme_patch.diff, store_patch.diff, store_patch.status
>
> Exclude tests which use DriverManager, Driver or BigDecimal classes which are not in
J2ME or JSR169. Ensure that derbyall can be run successfully in J2ME/CDC/Foundation platform
using the JDBC Optional Package for CDC/Foundation Profile (JSR169).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message