Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
10.5.1.1
-
None
-
None
Description
Because the network server tests use port 1527 for their testing, you cannot currently run concurrent test runs on a single machine. This is very inconvenient, especially on multiple cpu machines where running tests in parallel might be faster than serial runs. I think the things that need to be done for this task are:
- Convert the remaining network server tests. as of 3/11/2009 this appear to be
derbynet/dblook_test_net.java
derbynet/dblook_test_net_territory.java
derbynet/DerbyNetAutoStart.java
[x] - derbynet/runtimeinfo.java
derbynet/testProtocol.java
lang/holdCursorIJ.sql
lang/wisconsin.java
[x] - lang/ShutdownDatabase.java
[x] - store/holdCursorExternalSortJDBC30.sql
[x] - store/holdCursorJDBC30.sql
- Make the default port for the suites.All run configurable with a system property.
Attachments
Issue Links
- incorporates
-
DERBY-3801 Convert "org.apache.derbyTesting.functionTests.tests.lang.holdCursorIJ.sql" to junit.
- Closed
-
DERBY-3839 Convert "org.apache.derbyTesting.functionTests.tests.store.holdCursorJDBC30.sql" to junit.
- Closed
-
DERBY-3842 Convert "org.apache.derbyTesting.functionTests.tests.store.holdCursorExternalSortJDBC30.sql" to junit.
- Closed
-
DERBY-2031 Convert derbynet/testProtocol.java to JUnit
- Closed
-
DERBY-3834 Convert derbynet/runtimeinfo to JUnit
- Closed
-
DERBY-3838 Convert derbynet/DerbyNetAutoStart to JUnit
- Closed
-
DERBY-2464 convert lang/ShutdownDatabase.java to junit
- Closed
- is related to
-
DERBY-2419 Tighten encapsulation of state in TestConfiguration
- Closed
-
DERBY-4638 Expose names of top-level test suites for easier scripting
- Closed
- is required by
-
DERBY-5038 updatelocks test failing in tinderbox when background update statistics are enabled.
- Closed
-
DERBY-5039 store/updatelocksJDBC30.sql test failing in tinderbox when background update statistics are enabled.
- Closed