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

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

Kristian Waagan commented on DERBY-3711:
----------------------------------------

I notice EncryptionAESTest has some code in common with EncryptionKeyAESTest/EncryptionKeyTest,
but I assume they test different things?
Would it be beneficial/possible to run the new tests for the other encryption algorithms as
well?

> 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
>             Fix For: 10.5.0.0
>
>         Attachments: DERBY-3711-2.diff, DERBY-3711-2.stat, DERBY-3711_1.diff
>
>
> 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.


Mime
View raw message