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] [Updated] (DERBY-6180) DatabaseMetaDataTest should not fail if there are extra columns but only check the expected ones
Date Thu, 25 Sep 2014 18:15:35 GMT

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

Myrna van Lunteren updated DERBY-6180:
--------------------------------------
    Attachment: DERBY-6180_2.diff

Attaching a second patch which moves the new method from the DatabaseMetaDataTest to the JDBC
class, and makes the jdbc4.TestDBMetaData also use this method.
Again I tested this by making modifications to the various expected arrays and running the
tests to confirm it would flag (test failure) if an (added) item in the expected array was
not found in the actual data, but did *not* fail if there was an item in the actual ResultSet
that was not in (removed from) the expected array.
I intend to commit this shortly.

> DatabaseMetaDataTest should not fail if there are extra columns but only check the expected
ones
> ------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-6180
>                 URL: https://issues.apache.org/jira/browse/DERBY-6180
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>            Reporter: Kathey Marsden
>            Assignee: Myrna van Lunteren
>         Attachments: DERBY-6180.diff, DERBY-6180_2.diff
>
>
> In new JDBC versions colums can be added  to DatabaseMetaData. Tests should just check
expectedColumns and ignore extra columns to prevent failures with compatibility testing.
> This check occurs in assertColumnNames and assertColumnTypes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message