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/02 23:40:55 UTC
[jira] Created: (DERBY-3659) revive tests with ldap references to
be runnable as junit tests
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
Priority: Minor
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.
[jira] Updated: (DERBY-3659) revive tests with ldap references to
be runnable as junit tests
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ 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_2b.diff
attaching a second version of the patch.
I answered my two questions myself:
re InvalidLDAPAuthenticationServerTest - the failed connection attempts apparently caused the test to cling to the db.lck. I resolved the cleanup trouble by using a singleUseDatabaseDecoratorNoShutdown instead of singlueUseDatabaseDecorator - now the teardown doesn't attempt to connect & the cleanup runs smoothly.
re LDAPAuthenticationTest system shutdowns: the original out file was created using a derby.properties file that set requireAuthentication to true - that's why the shutdown with non-system users failed. This is already tested in AuthenticationTest, and isn't testing LDAP per se, so I felt it ok to remove it from the LDAP test.
I added the tests to jdbcapi/_Suite.java with an if block to ensure the ldapServer property is specified.
I am not sure how to force a more useful message to pop up. For now, if people don't set the derbyTesting.ldapServer, derbyTesting.ldapUser, derbyTesting.ldapPassword, derbyTesting.dnString, derbyTesting.ldapPort properties, the test will do nothing, which means no worse test coverage than we had before.
When the properties are set, and the extra user (kathy/kathyS) is specified, the test will run.
> 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, 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.
[jira] Commented: (DERBY-3659) revive tests with ldap references to
be runnable as junit tests
Posted by "Andrew McIntyre (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593904#action_12593904 ]
Andrew McIntyre commented on DERBY-3659:
----------------------------------------
Surely the Apache Directory project has a test server running somewhere. Maybe check on their dev and/or user list if they have a test server that they're ok having multiple automated Derby test clients hitting at all hours of the day.
> 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
> Priority: Minor
>
> 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.
[jira] Updated: (DERBY-3659) revive tests with ldap references to
be runnable as junit tests
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ 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-3.diff
> 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-3.diff, 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.
[jira] Commented: (DERBY-3659) revive tests with ldap references to
be runnable as junit tests
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594636#action_12594636 ]
Myrna van Lunteren commented on DERBY-3659:
-------------------------------------------
Thx for your suggestions Andrew. I want to postpone sorting through finding a server until we have something that is runnable...
> 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
>
> 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.
[jira] Closed: (DERBY-3659) revive tests with ldap references to be
runnable as junit tests
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren closed DERBY-3659.
-------------------------------------
Resolution: Fixed
closing after committing the minor changes of patch DERBY-3659-3 with revision 662920.
> 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-3.diff, 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.
[jira] Assigned: (DERBY-3659) revive tests with ldap references to
be runnable as junit tests
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren reassigned DERBY-3659:
-----------------------------------------
Assignee: Myrna van Lunteren
> 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
>
> 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.
[jira] Updated: (DERBY-3659) revive tests with ldap references to
be runnable as junit tests
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ 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_2.diff
attaching a patch with 2 'new' tests, LDAPAuthenticationTest and InvalidLDAPServerAuthenticationTest.
LDAPAuthenticationTest essentially tests what was contributed with master file 'secureUsersldap.out'. It was never made into a test because there was no ldap server. This test will need to be run with 5 properties passed in; derbyTesting.ldapServer, derbyTesting.dnString, derbyTesting.ldapUser, derbyTesting.ldapPassword, and derbyTesting.ldapPort.
There should be 2 users on the ldap server, with ou=People;
mamta / yeehaLdap and kathy/kathyS.
InvalidLDAPServerAuthenticationTest tests that an appropriate 08004 error is returned when the ldapServer used does not exist. It's a somewhat silly test, and only works without security manager (else, I got
security manager errors even though I had added the non-existing ldapServer to the policy files).
I ran into one strange thing with these test:
1. re LDAPAuthenticationTest: the sql executed in ij as reflected in the secureUsersldap.out file resulted in a 08004 error when an invalid user attempted to shutdown the system.
-----------
ij> -- Derby system shutdown - check user - should fail
connect ';user=jamie;password=LetMeIn;shutdown=true';
ERROR 08004: Connection refused : Invalid authentication.
-----------
However, when I attempted a similar construction in junit, connecting either with DataSources or DriverManager, I was able to successfully shutdown the system; at least, I got the XJ015 error (system shutdown). Anyone any suggestions on this?
2. InvalidLDAPAuthenticationServerTest will result in an unusable database, and I tried to make it so the test would cleanup fine. However, the test does not cleanly delete db.lck, yet I don't see what is causing the test (framework?) to hang on to it. If anyone sees what I'm missing?
> 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, DERBY-3659_2.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.
[jira] Reopened: (DERBY-3659) revive tests with ldap references to
be runnable as junit tests
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Closed: (DERBY-3659) revive tests with ldap references to be
runnable as junit tests
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren closed DERBY-3659.
-------------------------------------
Resolution: Fixed
Fix Version/s: 10.5.0.0
committed patch DERBY-3659-2b.diff with revision 661924.
> 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.
[jira] Updated: (DERBY-3659) revive tests with ldap references to
be runnable as junit tests
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DERBY-3659) revive tests with ldap references to
be runnable as junit tests
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren updated DERBY-3659:
--------------------------------------
Derby Info: [Patch Available]
> 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.
[jira] Commented: (DERBY-3659) revive tests with ldap references to
be runnable as junit tests
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600314#action_12600314 ]
Myrna van Lunteren commented on DERBY-3659:
-------------------------------------------
I sent of a mail to the apache directory project. We'll see if someone has a server we can run our tests against.
> 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, DERBY-3659_2.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.
[jira] Commented: (DERBY-3659) revive tests with ldap references to
be runnable as junit tests
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595429#action_12595429 ]
Myrna van Lunteren commented on DERBY-3659:
-------------------------------------------
Logged DERBY-3669 to document that the xadatasource is not equal after bind and lookup from jndi with network server.
> 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.
[jira] Updated: (DERBY-3659) revive tests with ldap references to
be runnable as junit tests
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren updated DERBY-3659:
--------------------------------------
Derby Info: (was: [Patch Available])
committed the patch with modifications, with revision 654656.
> 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.