Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <27351647.1176925275320.JavaMail.jira@brutus>
Date: Wed, 18 Apr 2007 12:41:15 -0700 (PDT)
From: "Andrew McIntyre (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-2151) "Fixer-upper" utility to help convert
 ij canon-based tests to JUnit.
In-Reply-To: <12344641.1165340780981.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrew McIntyre updated DERBY-2151:
-----------------------------------

    Attachment: derby-2151-andrew-v2.diff

Attaching an updated version of the last patch which includes statement push back, and detects ij's show and describe statements and marks them as unconverted. I tried this on a handful of sql and it does at least a good of a job converting them as the original patch.

I do think this could be useful in the future as well as for the current test converrsion project, so if no one objects, I'll check this in shortly.

> "Fixer-upper" utility to help convert ij canon-based tests to JUnit.
> --------------------------------------------------------------------
>
>                 Key: DERBY-2151
>                 URL: https://issues.apache.org/jira/browse/DERBY-2151
>             Project: Derby
>          Issue Type: Test
>          Components: Test, Tools
>    Affects Versions: 10.3.0.0
>            Reporter: A B
>            Priority: Minor
>         Attachments: derby-2151-andrew-v1.diff, derby-2151-andrew-v2.diff, ijToJUnit.java
>
>
> As part of my work to get the XML tests running in JUnit (DERBY-1758) I had to convert the old ij test lang/xml_general.sql into a JUnit equivalent.  After hand-converting about twenty or so lines of ij "master" output to the corresponding JUnit commands, I became bored with the melancholy of such a task.  So I hastily threw together a small utility to help automate as much of the process as possible.
> To be perfectly frank, the utility is a shameful piece of code.  It's poorly-written, non-intuitive, overly complex and not at all well thought-out.  It's also completely UN-commented. I wish I could follow-up with a half-hearted claim that "at least it works", but I'm not even sure *that*'s always true...
> My first (and still lingering) inclination is to just bury the utility and never look at it again.  However, I have to admit that, while the code is a nightmare to understand, it did a) prompt me to add some general-purpose JUnit utility methods that can be useful (DERBY-1976), and b) save me a lot of time by providing a rough translation of the ij test to JUnit.  Then instead of piddling away at line-by-conversions of the test I was able to spend my time re-organizing the JUnit version to make it adhere to the JUnit suggestions on the second page of:
>   http://www.javaworld.com/jw-12-2000/jw-1221-junit.html
> So the utility *did* save me time.  And for that reason I've decided to choke down my embarassment and post it to a Jira issue for other developers who may find it useful (or perhaps entertaining as an example of bad programming)...

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