Hi Bernt,I have not tried this out but it looks like the port number is configurable by setting a system property. I think that the tricky bits are in org.apache.derbyTesting.junit.TestConfiguration.
Hope this helps, -Rick Bernt M. Johnsen wrote:
In the old test harness with the old tests this was impossible due to hardcoded use of port numbers (1527 etc). Is this taken into consideration when tests are moved to JUnit so that the port number(s) may be parameterized in a convenient way?
