[
https://issues.apache.org/jira/browse/DERBY-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren reopened DERBY-3659:
---------------------------------------
some minor things popped up with these tests
- fails with jars
- on re-checking, I found that only LDAPAuthenticationTest needs a special
policy file. I don't know anymore why I thought one was needed for XAJNDITest -
that test works fine with the default. Possibly initially at some point I had
code making a connection.
I want to:
- rename the XAJNDITest.policy to LDAPTests.policy
- add the permission grant to ldapServer to derby.jar section
- make some minor adjustments to XAJNDITest, among others to remove reference
to the policy file
- make LDAPAuthenticationTest use LDAPTests.policy
> revive tests with ldap references to be runnable as junit tests
> ---------------------------------------------------------------
>
> Key: DERBY-3659
> URL: https://issues.apache.org/jira/browse/DERBY-3659
> Project: Derby
> Issue Type: Test
> Components: Test
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.5.0.0
>
> Attachments: DERBY-3659.diff, DERBY-3659_2.diff, DERBY-3659_2b.diff
>
>
> During initial contribution some tests were created with references to ldap
> security mechanism.
> However, because we don't have ourselves setup for a public ldap server,
> these tests have fallen by the wayside.
> Specifically, there is still a secureUsers .out file in functionTests.master
> that uses some ldap references, and there's the -not running -
> jdbcapi.xaJNDI.java.
> These should be turned into junit tests out of these that take properties for
> the ldapserver, port, and dnString.
> If we ever get a Zone, with an ldap server, or somehow get access to another
> public ldap server, then we can modify the tests to have the correct
> references.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
