[
https://issues.apache.org/jira/browse/DERBY-3369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-3369:
-----------------------------------
Attachment: derby-3369-1a.diff
'derby-3369-1a.diff' is the first rev of extending the test.
The diff is substantial, might be easier to just review the patched file...
In this config all three data sources are assumed to be equal, and the test
should cover all the things the previous version did and a little more. Adding
an extra property to one of the data source (i.e. maxStatements to
ClientConnectionPoolDataSource) is only a matter of creating a new descriptor
and start using it.
If derby.tests.debug is set to true, the test will print which data sources it
is testing.
Patch ready for review.
> Extend jdbcapi.DataSourceReferenceTest to handle data sources with differing
> property sets
> ------------------------------------------------------------------------------------------
>
> Key: DERBY-3369
> URL: https://issues.apache.org/jira/browse/DERBY-3369
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.4.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.4.0.0
>
> Attachments: derby-3369-1a.diff
>
>
> jdbcaip.DataSourceReferenceTest tests the JavaBean properties of the various
> data sources Derby has, and also recreation using Reference(able) and
> serialization/deserialization.
> As part of implementing JDBC statement pooling (see DERBY-3313), a new
> property must be introduced in some of the data source classes.
> The test must be extended to handle data sources with differing property sets.
> There are a few comments regarding this in DERBY-3325.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
