[
https://issues.apache.org/jira/browse/DERBY-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-1496:
--------------------------------------
Attachment: DERBY-1496_20070306.diff
DERBY-1496_20070306.stat
After an apparent inactivity of many moons, I'm attaching a preliminary step
for a second attempt at converting testSecMed.java.
While I'm battling testSecMec itself, the attached patch is an attempt at
combining relevant parts of users.sql, users2.sql, secureUsers.sql and
secureUsers1.sql with dataSourcePermissions/_net.java, so that these 6 tests
can be removed.
In addition to creating a number of test classes extending from the basic
datasource testing class AuthenticationTest.java, the patch also contains
changes to checkDataSource.java. These changes are there because of datasource
functionality (almost) tested in dataSourcePermissions_net.java, but which have
no authentication aspect. If decided they'd fit better in checkDataSource.
The new testing in checkDataSource could be done more efficiently, but I'm not
getting into that now - maybe that can be addressed when someone converts it.
Finally the patch modifies DropDatabaseSetup.java to not use the
JDBCDataSource.shutdownDatabase(ds), which results in an attempt to use a
ds.setter method not supprted with DerbyNetClient (see also DERBY-2296)
This patch is intended for review only - I have not tested the tests in a suite.
> testSecMec needs many masters - should convert to junit
> -------------------------------------------------------
>
> Key: DERBY-1496
> URL: https://issues.apache.org/jira/browse/DERBY-1496
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.2.1.6
> Reporter: Sunitha Kambhampati
> Assigned To: Myrna van Lunteren
> Priority: Minor
> Attachments: DERBY-1496_20070306.diff, DERBY-1496_20070306.stat,
> DERBY-1496_tmp_072206.diff, DERBY-1496_tmp_072206.stat
>
>
> derbynet/testSecMec.java fails with jcc2.8 with 131 vms. I have checked the
> diff and it is a master update with difference in the exception, message
> string.
> diff snippet:
> 8 del
> < T5:
> jdbc:derby:net://xxxFILTERED_HOSTNAMExxx:xxxFILTEREDPORTxxx/wombat:user=neelima;password=lee;securityMechanism=9;
> - EXCEPTION java.security.InvalidAlgorithmParameterException is caught when
> initializing EncryptionManager 'Prime size must be multiple of 64, and can
> only range from 512 to 1024 (inclusive)'
> 8a8
> > T5:
> > jdbc:derby:net://xxxFILTERED_HOSTNAMExxx:xxxFILTEREDPORTxxx/wombat:user=neelima;password=lee;securityMechanism=9;
> > - EXCEPTION java.security.NoSuchAlgorithmException is caught when
> > initializing EncryptionManager 'DH KeyPairGenerator not available'
> 14 del
> ----------------
> There is difference in the exception message and will require lot of jvm
> specific master files which can become difficult to maintain. Myrna
> suggested that this might be a good test to convert to junit.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
