db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-1001) Rewrite 'store/encryptionKey.sql' to a JUnit test
Date Wed, 09 May 2007 19:04:15 GMT

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

Kristian Waagan updated DERBY-1001:
-----------------------------------

    Attachment: derby-1001-3a-fixtestfailure.diff

Attached fix for the failing test. It is not quite clear to me if Derby actively needs read
permissions for the directory to backup to, or if it is required as part of some other file
system operation (e.g. create dir). Putting the backup in EXTINOUT instead of EXTOUT fixes
the problem.

I will investigate the issue a little more later, and I will also update the comments in the
file accordingly (class JavaDoc) when the fix is verified. It also not clear to me why the
test fails when running suites.All, but not individually or as part of store/_Suite.

Committed 'derby-1001-3a-fixtestfailure.diff' to trunk with revision 536621.

> 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: 10.3.0.0
>            Reporter: Kristian Waagan
>         Assigned To: Kristian Waagan
>            Priority: Minor
>             Fix For: 10.3.0.0
>
>         Attachments: derby-1001-1a-preliminary.diff, derby-1001-1a-preliminary.stat,
derby-1001-2a.diff, derby-1001-2a.stat, derby-1001-3a-fixtestfailure.diff
>
>
> 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
above.

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


Mime
View raw message