Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <17551573.21601286437531143.JavaMail.jira@thor>
Date: Thu, 7 Oct 2010 03:45:31 -0400 (EDT)
From: "Kristian Waagan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-4834) Add helper class for working with
 index statistics in JUnit tests
In-Reply-To: <2059599.8411286381071104.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kristian Waagan commented on DERBY-4834:
----------------------------------------

Thanks for looking at the patch, Lily.

Committed patch 1a to trunk with revision 1005347.

We may need other convenience methods to investigate various parts of the Derby system. One concern I have, is that there is already a lot of stuff "floating around", but it is not that easy to find it when you need it. Maybe it's time we write a package.html file for the junit package - describing which classes are entry points for various functionality?
Another option is to improve the class JavaDoc of the various classes (the first sentence) such that a developer can navigate using the automatically generated JavaDocs.

> Add helper class for working with index statistics in JUnit tests
> -----------------------------------------------------------------
>
>                 Key: DERBY-4834
>                 URL: https://issues.apache.org/jira/browse/DERBY-4834
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Test
>    Affects Versions: 10.7.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>         Attachments: derby-4834-1a-indexstats_utility_class.diff
>
>
> Dealing with index statistics in the JUnit tests require some tedious work, like looking up table and index ids,  doing selects on the SYS.SYSSTATISTICS table, and analyzing the results of these queries.
> To make life easer and the tests easier to read, a set of utility methods will be added to a new class living in the JUnit test framework package.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.