[jira] [Commented] (DERBY-6698) Make it easier to run suites.All on soft-upgraded database

["Knut Anders Hatlen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DERBY-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14090663#comment-14090663 ] 

Knut Anders Hatlen commented on DERBY-6698:
-------------------------------------------

When running suites.All with the 10.11.1.0 release candidate on a 10.10.2.0 database, the following tests failed:

TriggerTest.testQualifiedNamesInSystemTables: failed because it used WHEN clause, which requires db format 10.11
TriggerTest.testDerby5578InvalidateAllStatementsProc: failed because test expected stored meta-data query to be recompiled, but stored meta-data queries are not used in soft-upgrade

RenameTableTest.test_6672_1: failed because it used deferred constraints, which requires db format 10.11

ConstraintCharacteristicsTest: many failures because deferred constraints are not supported in old databases

ForeignKeysDeferrableTest: many failures because deferred constraints are not supported in old databases

RolesTest.testSemantics: failed because SYSROUTINEPERMS didn't have entry for SYSCS_PEEK_AT_IDENTITY (new function in 10.11)

AutoIncrementTest: various failures because some identity column bugs are only fixed if database is upgraded to 10.11 so that identity columns are backed by sequences

IdentitySequenceTest: various failures because the test expects identity columns to be backed by sequences

ToolScripts.ij7: fails because canon expects SHOW FUNCTIONS to list SYSCS_PEEK_AT_IDENTITY

TestDbMetaData: the testGetFunctions* test cases failed because DatabaseMetaData.getFunctions() didn't list SYSCS_PEEK_AT_IDENTITY

All of the above are expected failures, as far as I can tell.

In addition, some tests failed with self-deadlocks. They were fixed by DERBY-6692.

If an older database had been used, I would expect more test cases to fail.

> Make it easier to run suites.All on soft-upgraded database
> ----------------------------------------------------------
>
>                 Key: DERBY-6698
>                 URL: https://issues.apache.org/jira/browse/DERBY-6698
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>            Reporter: Knut Anders Hatlen
>
> See discussion here: http://mail-archives.apache.org/mod_mbox/db-derby-dev/201408.mbox/%3C53E3B191.2010608%40gmail.com%3E
> It would be useful if tests that know they will fail unless the database format is at least at a certain version, disable themselves when running on an older database. This would reduce the noise when running suites.All on a soft-upgraded database, which is an ad hoc test that's sometimes performed during release testing.



--
This message was sent by Atlassian JIRA
(v6.2#6252)