db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6642) Make the JUnit result set assertion methods dump the actual rs when assertion fails
Date Mon, 30 Jun 2014 19:27:24 GMT

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

Dag H. Wanvik updated DERBY-6642:
---------------------------------

    Attachment: derby-6642.diff

Attaching a patch that adds this functionality to org.apache.derbyTesting.junit.JDBC.

Running regression. I am also testing most of the assertion methods on result sets manually,
to see if they do the job under the different failure scenarios. One concern is that some
tests might assert on very large result sets and formatting those as part of the error message
would fill up a lot of log space... If this turns out to be an issue, we can make opt-out
versions.

> 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
>
>
> 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