Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <29500324.1173713169530.JavaMail.jira@brutus>
Date: Mon, 12 Mar 2007 08:26:09 -0700 (PDT)
From: "Kristian Waagan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-2446) Remove notion of the old test
 harness from TestConfiguration
In-Reply-To: <21123662.1173704169291.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-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480118 ] 

Kristian Waagan commented on DERBY-2446:
----------------------------------------

Thanks for the information.

Is the current test in the old harness broken, or does it actually work because the test is run in a separate process?
Either way, I plan to make the suggested changes since we are aiming to "kill the old harness".
If anyone feel this is something we should investigate further, please create a separate Jira for it.

thanks,

> Remove notion of the old test harness from TestConfiguration
> ------------------------------------------------------------
>
>                 Key: DERBY-2446
>                 URL: https://issues.apache.org/jira/browse/DERBY-2446
>             Project: Derby
>          Issue Type: Task
>          Components: Test
>    Affects Versions: 10.3.0.0
>            Reporter: Kristian Waagan
>         Assigned To: Kristian Waagan
>            Priority: Minor
>
> TestConfiguration has a notion of the old test harness. It is used when the old harness is running JUnit tests, and differs mostly by reading the system properties set by the harness and propagating these to the test configuration.
> I found only one JUnit test being run from the harness; LobStreamsTest.junit. However, this is also run by the JUnit suite jdbcapi.
> My suggestion is to remove the code related to the old harness in TestConfiguration and disable LobStreamsTest in derbynetclientmats.
> A quick test showed that only LobStreamsTest failed when removing all the relevant code in TestConfiguration (ran both derbyall and suites.All).

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