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] [Commented] (DERBY-6264) Improve test coverage of org.apache.derby.iapi.db.PropertyInfo
Date Tue, 18 Jun 2013 16:20:20 GMT

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

Myrna van Lunteren commented on DERBY-6264:

Looks like the class TestPropertyInfo was just created to get info about *all* the properties,
as opposed to what one gets from org.apache.derby.iapi.db.PropertyInfo. I think initially
it was only used in syscat.sql (later converted (DERBY-2484) to lang.SystemCatalogTest). It
is now, as Dag said, also used in 2 further tests.

I tracked the original create comment in the cloudscape source (by Rick, back in 1998) and
it says:
"make PropertyInfo only reveal user-visible conglomerate properties; create new class TestPropertyInfo
to reveal ALL conglomerate properties."

Often, especially in older (.sql) tests, methods are used in procedures or functions, so just
doing a class or method search in an IDE is not sufficient to find whether a class (especially
one from the functionTests.util directory) is being used.

> Improve test coverage of org.apache.derby.iapi.db.PropertyInfo
> --------------------------------------------------------------
>                 Key: DERBY-6264
>                 URL: https://issues.apache.org/jira/browse/DERBY-6264
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Test
>            Reporter: Bryan Pendleton
>            Assignee: ahsan shamsudeen
>            Priority: Minor
> According to the coverage reports, only 1 of the 5 methods in
> org.apache.derby.iapi.db.PropertyInfo is exercised by the Derby
> regression tests.
> This sub-task is to improve that test coverage.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message