Myrna van Lunteren wrote:
Maybe a first step would be to have the SURTest depend on this new class.
I understand Andreas had tested this?
Yes.
I also have some a test using the new base classes (will submit soon).
I created the issue with tasks like the following in mind:
* add support for getting default connection in JSR 169 environment
* add support for getting connections through DataSource
* add support for getting connections with when supplying a Properties
object
* add debug statements to BaseJDBCTestCase
* add JCC DataSource class name to JDBCClient.DERBYNET client definition
Such improvements can be added as sub-tasks. I do not want to add them
before someone actually require the new functionality.
If discussion determines a given functionality should not be added, it
would be nice to document this by resolving the sub-task as "Won't fix"
(or "Invalid").
--
Kristian
Myrna
On 3/17/06, *Kristian Waagan (JIRA)* <derby-dev@db.apache.org
<mailto:derby-dev@db.apache.org>> wrote:
Improve base JUnit testing classes
----------------------------------
Key: DERBY-1122
URL: http://issues.apache.org/jira/browse/DERBY-1122
Project: Derby
Type: Task
Components: Test
Versions: 10.3.0.0 <http://10.3.0.0>, 10.2.0.0 <http://10.2.0.0>
Reporter: Kristian Waagan
Priority: Minor
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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
<http://issues.apache.org/jira/secure/Administrators.jspa>
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
