[
https://issues.apache.org/jira/browse/DERBY-5764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-5764:
-----------------------------------
Attachment: derby-5764-3b-add_test_case_schema_null.diff
No, one of the checks can go away.
When modifying the code in for patch 3a I considered printing missing or extra
rows, but ended up not doing it. I've removed the last check in patch 3b.
> Make DatabaseMetaDataTest more robust wrt changes made by other tests
> ---------------------------------------------------------------------
>
> Key: DERBY-5764
> URL: https://issues.apache.org/jira/browse/DERBY-5764
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.9.1.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.10.0.0
>
> Attachments: derby-5764-1a-upgraderun_cleanup.diff,
> derby-5764-2a-specify_schema.diff,
> derby-5764-3a-add_test_case_schema_null.diff,
> derby-5764-3b-add_test_case_schema_null.diff
>
>
> The subset of tests from DatabaseMetaDataTest being run as part of the
> upgrade tests is sensitive to changes in the database made by other tests.
> For instance, adding tables with foreign keys will make the test fail due to
> extra rows in system tables.
> Usually this could be solved by using a single-use db wrapper of some sort,
> but in the upgrade tests the database will be booted several times with
> different versions of Derby and the data needs to be preserved between some
> of these boots.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
