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-5853) Test for methods in BrokeredPreparedStatement
Date Sat, 14 Jul 2012 15:29:35 GMT

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

Bryan Pendleton commented on DERBY-5853:

The Emma documentation discusses exceptions in sections 2.5, 2.6, and 2.7 of the FAQ:

    "Thus, EMMA does not attempt to track the success or failure of every single 
    bytecode instruction: instead, it marks a basic block covered when the control 
    reaches its last instruction. A covered basic block is thus guaranteed to have 
    executed without failures at least once in a given coverage run session."

    "the motivation behind this has been that most legitimate code is written 
    so that methods return normally (without throwing an exception)."

> Test for methods in BrokeredPreparedStatement
> ---------------------------------------------
>                 Key: DERBY-5853
>                 URL: https://issues.apache.org/jira/browse/DERBY-5853
>             Project: Derby
>          Issue Type: Sub-task
>            Reporter: Siddharth Srivastava
>            Assignee: Siddharth Srivastava
>            Priority: Minor
>         Attachments: brokeredps.patch, pstest.patch
> According to emma code coverage report, several methods of BrokeredPreparedStatement
are uncovered. 
> This issue deals with adding tests for those methods.

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


View raw message