[
https://issues.apache.org/jira/browse/DERBY-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490141
]
Kristian Waagan commented on DERBY-1001:
----------------------------------------
Nothing special should be required to run the test, but you do need to have the
necessary encryption software. With a recent JVM you should be good to go, but
I have only tested with Sun JVMs.
What JVM did you run with?
I was able to run the test(s) on Windows XP, both under Cygwin and at the
command prompt (cmd.exe). I used the Java SE 6 platform.
I know nothing about Eclipse, so I can't say whether running in it would make
any difference.
> 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.
