db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6642) Make the JUnit result set assertion methods dump the actual rs when assertion fails
Date Tue, 01 Jul 2014 13:22:25 GMT

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

ASF subversion and git services commented on DERBY-6642:
--------------------------------------------------------

Commit 1607069 from [~dagw] in branch 'code/trunk'
[ https://svn.apache.org/r1607069 ]

DERBY-6642 Make the JUnit result set assertion methods dump the actual rs when assertion fails

Patch derby-6642b. The patch works by always collecting columns and
rows as they are read. The method JDBC#addRsToReport takes these
collections and what's left of the result set and formats a dump of
the result set and adds it to the text of already existing assertion
failure. This is then (re)thrown.

> Make the JUnit result set assertion methods dump the actual rs when assertion fails
> -----------------------------------------------------------------------------------
>
>                 Key: DERBY-6642
>                 URL: https://issues.apache.org/jira/browse/DERBY-6642
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>            Reporter: Dag H. Wanvik
>         Attachments: derby-6642.diff, derby-6642b.diff
>
>
> Often, when researching intermittent regression test errors, an assertion on a result
set fails, but the error report only shows which column in which row first fails to meet expectations.
It would be good if the assertion methods could dump the actual result set in such cases so
we'd have more information to go on when trying to understand the cause of the problem.



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

Mime
View raw message