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] Commented: (DERBY-3711) convert store/aes.sql to junit test & add unrestricted test cases.
Date Thu, 05 Jun 2008 17:37:45 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602718#action_12602718

Myrna van Lunteren commented on DERBY-3711:

Thx for your comment Kathey - I went ahead with that idea, will upload a patch...And I'll
commit soon.
There'll be a follow up patch to add the test to the store _Suite, and to do remove the old
test. I can take the println out then if that's preferred by the community.

> convert store/aes.sql to junit test & add unrestricted test cases.
> ------------------------------------------------------------------
>                 Key: DERBY-3711
>                 URL: https://issues.apache.org/jira/browse/DERBY-3711
>             Project: Derby
>          Issue Type: Task
>          Components: Test
>            Reporter: Myrna van Lunteren
>            Assignee: Myrna van Lunteren
>            Priority: Minor
> The store/aes.sql test can, because it's a master-based test, only test what's guaranteed
available, i.e. only the encryptionKeyLength=128.
> If it were a junit test, we could make it ignore the expected failures if the larger
key sizes weren't supported, but test otherwise.
> Having a junit test doesn't guarantee the test would get executed, of course, but at
least the test would exist. 
> Would it be useful/ok to have a message print to the console as a warning?

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

View raw message