db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6264) Improve test coverage of org.apache.derby.iapi.db.PropertyInfo
Date Thu, 20 Jun 2013 21:24:20 GMT

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

Bryan Pendleton commented on DERBY-6264:

I am looking at: http://dbtg.foundry.sun.com/derby/test/coverage/_files/11e.html

The unused methods are: getConglomerateProperties, getIndexProperties, and
getTableProperties -- these are the unused methods that I think we should
remove. There are only three such methods; I was confused and thought there
were 4 methods because the Emma tool noticed that the system-generated
default constructor PropertyInfo() is also unused, but since that method is
system-generated, I don't think we need to do anything about that.

The setDatabaseProperty() method, however, is used, and so we should keep it.

> 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