[DERBY-1122] Improve base JUnit testing classes

• Type: Task
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.3.1.4
• Fix Version/s: 10.3.1.4
• Component/s: Test
• Assignee: Unassigned
• Reporter: Kristian Waagan
• Created: 17/Mar/06 16:07
• Updated: 24/May/07 10:29
• Resolved: 24/May/07 10:29

Description

This is a placeholder issue for keeping track of improvements and bugs for base JUnit testing classes.
The first submission is very minimalistic and will need to be extended.
There are currently 4 base classes, all located in '...derbyTesting.functionTests.util':
JDBCClient
TestConfiguration
BaseTestCase
BaseJDBCTestCase

Issue Links

• incorporates: DERBY-1157 Helper methods in BaseJDBCTestCase for creating data sources
• relates to: DERBY-1970 Add framework for performance tests in derby using Junit.
• relates to: DERBY-993 junitTests cannot be run with J2ME

Sub-Tasks

• Add mechanism to assert/compare SQLStates: Closed
• Add mechanism to run tests in a single leg xa transaction: Closed
• Add assertEquals overloads for Blob and Clob: Closed
• Add assertEquals overloads for InputStream and Reader: Closed
• Add BaseJDBCTestCase.assertSQLState() overload with no message parameter: Closed
• Add new utility methods to BaseJDBCTestCase to make conversion of ij tests to JUnit easier.: Closed