[
https://issues.apache.org/jira/browse/DERBY-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491111
]
Sunitha Kambhampati commented on DERBY-1001:
--------------------------------------------
Each of the tests- EncryptionKeyDESTest and the EncryptionKeyAESTest require a
clean testrun directory..
I ran the EncryptionKeyDESTest and then cleaned up my testrun directory and
then ran the AES test and it worked OK in Eclipse as well as on command
prompt. I was using 1.4.2 Sun JVM.
kristian> 2) How many encryption algorithms/variations should we test?
How about the algorithms that we test in EncryptionSuite. It would be
interesting to see how much time the tests would take in this case..
I just took a quick look at the suite() methods in the DES and AES test and was
wondering why they were different.. In one, there is the SupportFilesSetup
decorator but in AES test that is not used..
Thanks.
> 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
> Attachments: derby-1001-1a-preliminary.diff,
> derby-1001-1a-preliminary.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 above.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
