[DERBY-1048] Include run of junitTests/CompatibilitySuite, or converted compatibility test suite with 10.1/trunk combination into suites.All

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.2.1.6
• Fix Version/s: 10.10.1.1
• Component/s: Test
• Labels: derby_triage10_8
• Urgency: Normal
• Assignee: Unassigned
• Reporter: Katherine Marsden
• Created: 25/Feb/06 01:36
• Updated: 01/Oct/12 14:46
• Resolved: 01/Oct/12 14:46

Description

Incorporate a run of jdbcapi/Compatibility test into derbyall with the following combinations:

client server
10.1.1.0 trunk
trunk 10.1.1.0

This can provide some minimal compatibility testing in derbyall against the original client release.
It requires that the 10.1.1.0 jars be checked in. I will file a separate issue for this.
Rick is assigned to the top level issue to integrate testing procedures. He wrote the test but there was concern that we actually not adding any coverage for compatibility because it only runs with trunk server/ trunk client.

Adding this combination was discussed in this thread.

http://www.nabble.com/Question-about-client-compatibility-testing-and-DERBY-516-%28paging-Rick-%3A%29%29-t506203.html#a1372016

Issue Links

• is related to: DERBY-2076 Rewrite junitTests/derbyNet/CompatibilityTest to conform to current JUnit usage
• relates to: DERBY-516 Need to incorporate client backward/forward compatibility testing into testing procedures.