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


Mime
View raw message