db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "DerbyJUnitTesting" by MyrnavanLunteren
Date Mon, 14 Sep 2009 20:41:55 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by MyrnavanLunteren:
http://wiki.apache.org/db-derby/DerbyJUnitTesting

------------------------------------------------------------------------------
  
  The first example will work perfectly, but to be absolutely safe, the ranges would be farther
apart.
  
+ == Running the LDAPAuthenticationTest JUnit test ==
+ 
+ The junit test LDAPAuthenticationTest requires an LDAP server configured in a very specific
way, details of which are described in the test' source code. As it is by nature not possible
to set up a secure server to be used by just anyone, the details for the LDAP server in the
test are provided by properties. As not everyone can have access to an LDAP server, if the
properties are not provided, the test will not be run.
+ For further information please refer to the test itself; but here are the properties the
test looks for:
+  * derbyTesting.ldapServer=[ldapserver_ipaddress]
+  * derbyTesting.ldapPort=[port for the ldap server]
+  * derbyTesting.dnString=[dn string for the ldap server]
+  * derbyTesting.ldapUser=[main ldap user] 
+  * derbyTesting.ldapPassword=[mail ldap user's password]
+  Note that the test requires an additional user to be set up on the LDAP server - for
+  details, see the test.
+ 
+ == Optional delay for Network Server start time ==
+ 
+ Sometimes when running JUnit tests with jvm options that are known to slow things down significantly
network server start timeouts can occur, for instance in derbynet.SecureServerTest. This is
governed by the default wait time set in org.apache.derbyTesting.junit.NetworkServerTestSetup.

+ To allow for one-off adjusting of the settings, without modifying the wait time in the test
framework source, one can use the following property (10.5 and up) to overwrite the default:

+  * derby.tests.networkServerStartTimeout=[int indicating wait time in seconds]
+  This property will overwrite the default specified in 
+ 
  == Switching the Derby harness over to JUnit ==
  
  An ultimate goal would be for all Derby tests to be JUnit tests and all existing logic in
the Derby test harness is replaced

Mime
View raw message