db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (DERBY-1001) Rewrite 'store/encryptionKey.sql' to a JUnit test
Date Tue, 08 May 2007 18:48:15 GMT

     [ https://issues.apache.org/jira/browse/DERBY-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Myrna van Lunteren reopened DERBY-1001:

test fails in tinderbox:
see: http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/Limited/testSummary-536200.html

org.apache.derbyTesting.functionTests.suites.All fail *************************************************************
1) testBackupEncryptedDatabase(org.apache.derbyTesting.functionTests.tests.store.EncryptionKeyAESTest)java.sql.SQLException:
The exception 'java.security.AccessControlException: access denied (java.io.FilePermission
extout read)' was thrown while evaluating an expression.
1) testBackupEncryptedDatabase(org.apache.derbyTesting.functionTests.tests.store.EncryptionKeyBlowfishTest)junit.framework.AssertionFailedError:
Refusing to continue, database already exists <Database '/export/home/tmp/os136789/testingDerbyTinderBox/SunOS-5.10_i86pc-i386/org.apache.derbyTesting.functionTests.suites.All/extinout/encryptionKeyDBToBackup'
not created, connection made to existing database instead.>
2) testBackupEncryptedDatabase(org.apache.derbyTesting.functionTests.tests.store.EncryptionKeyDESTest)junit.framework.AssertionFailedError:
Refusing to continue, database already exists <Database '/export/home/tmp/os136789/testingDerbyTinderBox/SunOS-5.10_i86pc-i386/org.apache.derbyTesting.functionTests.suites.All/extinout/encryptionKeyDBToBackup'
not created, connection made to existing database instead.>

Maybe the test needs to use singleUseDatabaseConfiguration ?

> Rewrite 'store/encryptionKey.sql' to a JUnit test
> -------------------------------------------------
>                 Key: DERBY-1001
>                 URL: https://issues.apache.org/jira/browse/DERBY-1001
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>    Affects Versions:
>            Reporter: Kristian Waagan
>         Assigned To: Kristian Waagan
>            Priority: Minor
>             Fix For:
>         Attachments: derby-1001-1a-preliminary.diff, derby-1001-1a-preliminary.stat,
derby-1001-2a.diff, derby-1001-2a.stat
> This test has failed on Solaris10 for a long time, due to issues with the default security
provider on this OS. See DERBY-788 for details.
> I consider rewriting this test as interresting because it allows us to see how things
can be done in "the JUnit way". 
> 1) Run test with multiple encryption algorithms with minimal test code duplication.
> 2) Special handling of exceptions for specific providers (PCKS11-Solaris).
> The rewritten test might cause some discussion on how we want to handle the issues mentioned

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message