You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2008/05/06 19:24:56 UTC

[jira] Updated: (DERBY-3659) revive tests with ldap references to be runnable as junit tests

     [ https://issues.apache.org/jira/browse/DERBY-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Myrna van Lunteren updated DERBY-3659:
--------------------------------------

    Attachment: DERBY-3659.diff

Attaching a patch with converted XAJDNITest.java (from xaJNDI.java), incl. policy file.
This file now uses 3 system properties, one of which is also used in the policy file:
- derbyTesting.ldapServer
- derbyTesting.ldapPort
- derbyTesting.dnString

So, to run the test, currently you have to pass values in for an ldap server, like so (note, the host doesn't exist (I assume)):
java -DderbyTesting.ldapServer=ldapserverhost.apache.org -DderbyTesting.ldapPort=333 -DerbyTesting.dnString=approp.riate.string junit.textui.TestRunner org.apache.derbyTesting.functionTests.tests.jdbcapi.XAJNDITest

Question:
The test compares a datasource with one created using ic.rebind and ic.lookup, and expects them to be the same.
Is that a valid assumption?
(If so, then there's a bug with NetworkServer, 'cause with network server the two are not identical (from a quick glance looks like the id is different. The original test only ran with embedded).

Also, the original test went on to unset the property createDatabase, and then compare the two datasources (modified one & one created before using ic.rebind and ic.lookup). This is now different. However, I tried (by mistake) to blank out the databaseName property, and then the datasources are still the same. Does that make sense?


> 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
>         Attachments: DERBY-3659.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.