Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Mon, 4 Apr 2011 16:44:05 +0000 (UTC)
From: "Kathey Marsden (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <2052984713.32780.1301935445719.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <290931845.15263.1299916559640.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (DERBY-5127) Convert madhare.sql to JUnit
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kathey Marsden commented on DERBY-5127:
---------------------------------------

You are absolutely right. I guess I got wrapped up in the minutia in the review and missed this major point.  Siddharth can you submit a new patch using org.apache.derbyTesting.junit.JDBC.assertFullResultSet()   to verify the results?  You can see sample usage in lang.SimpleTest and other tests.

If the ResultSet is big I sometimes use org.apache.derbyTesting.junit.showResultSet() temporarily to print out the array to feed to assertFullResultSet().


> Convert madhare.sql to JUnit
> ----------------------------
>
>                 Key: DERBY-5127
>                 URL: https://issues.apache.org/jira/browse/DERBY-5127
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>            Reporter: Siddharth Srivastava
>            Assignee: Siddharth Srivastava
>            Priority: Minor
>         Attachments: d5127.diff, derby5127(2).diff, derby5127.diff, derby5127.diff, derby5127.diff, derby5127.diff
>
>
> Convert madhare.sql to JUnit

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira