[
https://issues.apache.org/jira/browse/DERBY-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-1318:
-----------------------------------
Attachment: derby-1318-1a-for_comments.stat
derby-1318-1a-for_comments.diff
'derby-1318-1a-for_comments.diff' is a first attempt at writing a test for
verifying compatibility for the current data source implementations towards to
old ones. It will do basic testing only by de-serializing an old data source
and recreating it by using javax.naming.Reference.
It is based on checked in versions of old data sources. This might not be
required if the upgrade test is run by default, but I think it might be a
valuable addition anyway to catch incompatibilities quickly and it doesn't
require you to have access to old releases.
I have also included a utility that can be run to write data sources to file.
All you have to do is run it with a given version of Derby on the classpath,
and it will write all data sources it knows about (predefined list) to file if
it can find them. The utility currently lives in
'functionTests/testData/serialized-data-sources', I'm not convinced if that's
the best place and I'm open for other suggestions :)
I would appreciate comments on the approach and the test in general.
I also feel the test I've written is a bit on the side of the Jira issue, so I
can create a separate issue if required.
> Add an upgrade test to verify that DataSources can be serialized by the
> previous release and then correctly deserialized by the current release
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1318
> URL: https://issues.apache.org/jira/browse/DERBY-1318
> Project: Derby
> Issue Type: Test
> Components: JDBC, Test
> Affects Versions: 10.2.1.6
> Reporter: Rick Hillegas
> Attachments: derby-1318-1a-for_comments.diff,
> derby-1318-1a-for_comments.stat
>
>
> Currently, our DataSources are serializable in order to play well with JNDI.
> However, we have no upgrade test verifying that DataSource serialization
> works across release boundaries. We should add this case to our upgrade tests.
> Further recommendations by Dan:
> "I do think though that upgrade testing recently brought into the mainline by
> Deepa should be enhanced to test:
> - serializing Derby''s data source implementations in 10.1 and seeing it
> unserializes with 10.2
> (maybe into a BLOB column)
> - making a Reference object out of Derby''s data source implementations in
> 10.1 and making it into
> an object with 10.2. (if this type of tetsing makes sense for
> References')"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
