db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-1684) Move client data source tests from jdbcapi/dataSourceReference.java to a separate test
Date Fri, 04 Feb 2011 02:53:23 GMT

     [ https://issues.apache.org/jira/browse/DERBY-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Myrna van Lunteren closed DERBY-1684.
-------------------------------------

    Resolution: Won't Fix

This test was converted to Junit as an aside for DERBY-2296. 
And with the junit tests we actually prefer to run the same test with client and server -
at least when there's a possibility of different implementation.

> Move client data source tests from jdbcapi/dataSourceReference.java to a separate test
> --------------------------------------------------------------------------------------
>
>                 Key: DERBY-1684
>                 URL: https://issues.apache.org/jira/browse/DERBY-1684
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>            Reporter: Deepa Remesh
>            Priority: Minor
>
> jdbcapi/dataSourceReference.java currently tests both embedded and client data sources.
The tests for client data source must be moved to a separate test. This will ensure following:

> * Can run embedded driver tests without requiring client jars.
> * Can separate out all client tests and make it part of derbynetclientmats suite. This
way, we can run just this suite to test any client changes.
> It would be good to check if there are other tests which fall into similar category.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message