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] Resolved: (DERBY-3863) improve test importExportIJ.sql
Date Thu, 04 Sep 2008 21:31:44 GMT

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

Myrna van Lunteren resolved DERBY-3863.

       Resolution: Fixed
    Fix Version/s:     (was:

I committed the original patch, and, with appropriate variations, backported to 10.4, 10.3,
10.2 and 10.1. Not 10.0, because importExport tests weren't included on that branch.
Also removed the now unnecessary files that had belonged to the old test. (and backported
that too).
Finally, for trunk only, I wrapped the new test in a scripttestcase.
I thought about converting the test cases to full junit & putting them in ImportExportTest,
but I think it's relevant to do some of the testing in IJ.

> improve test importExportIJ.sql 
> --------------------------------
>                 Key: DERBY-3863
>                 URL: https://issues.apache.org/jira/browse/DERBY-3863
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>            Reporter: Myrna van Lunteren
>            Assignee: Myrna van Lunteren
>            Priority: Trivial
>             Fix For:,,,,
>         Attachments: DERBY-3863.diff
> The test importExportThruIJ.sql has test cases that try to test functionality not supported
by derby.
> Various test cases don't match the data, and comments don't reflect the state of the
> I'm going to create a new test that follows mostly the same lines, but has cleaned up
test cases with suitable datasets, and appropriate comments.
> I'll backport this to all branches.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message