db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4157) Create a test to verify that virgin metadata is identical to hard-upgraded metadata
Date Tue, 14 Apr 2009 18:23:15 GMT

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

Rick Hillegas updated DERBY-4157:

    Attachment: derby-4157-01-aa-refactor.diff

Attaching derby-4157-01-aa-refactor.diff. This patch is a first step toward writing the new
test. This patch factors out some of the existing upgrade test machinery so that the new test
can re-use that machinery:

1) logic to discover old versions
2) logic to create class loaders out of those old versions
3) logic to use those class loaders

Touches the following files:

A      java/testing/org/apache/derbyTesting/functionTests/tests/upgradeTests/OldVersions.java
A      java/testing/org/apache/derbyTesting/functionTests/tests/upgradeTests/UpgradeClassLoader.java

New classes to hold the logic which has been factored out. OldVersions used to be an inner
class of _Suite. UpgradeClassLoader consists of code extracted from UpgradeRun and PhaseChanger.

M      java/testing/org/apache/derbyTesting/functionTests/tests/upgradeTests/PhaseChanger.java
M      java/testing/org/apache/derbyTesting/functionTests/tests/upgradeTests/_Suite.java
M      java/testing/org/apache/derbyTesting/functionTests/tests/upgradeTests/UpgradeRun.java

Pre-existing code re-wired to use the new shareable code.

> Create a test to verify that virgin metadata is identical to hard-upgraded metadata
> -----------------------------------------------------------------------------------
>                 Key: DERBY-4157
>                 URL: https://issues.apache.org/jira/browse/DERBY-4157
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>    Affects Versions:
>            Reporter: Rick Hillegas
>         Attachments: derby-4157-01-aa-refactor.diff
> We should write a test to verify that the metadata is correct for each release for all
hard-upgrade trajectories which terminate in that release. The test should examine all system
tables. Note that if there are N releases, then there will (2<sup>N</sup> - N)
- 1 trajectories to examine.

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

View raw message