Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Sun, 13 Oct 2013 18:39:43 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12364715.1173704062989.57876.1381689583938@arcas>
In-Reply-To: <JIRA.12364715.1173704062989@arcas>
References: <JIRA.12364715.1173704062989@arcas>
Subject: [jira] [Commented] (DERBY-2446) Remove notion of the old test
 harness from TestConfiguration
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&focusedCommentId=13793749#comment-13793749 ] 

ASF subversion and git services commented on DERBY-2446:
--------------------------------------------------------

Commit 1531729 from [~myrna] in branch 'code/trunk'
[ https://svn.apache.org/r1531729 ]

DERBY-2446; Remove notion of the old test harness from TestConfiguration
  Removing remaining references, and also removing remaining files from tests/junitTests

> 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.1.4
>            Reporter: Kristian Waagan
>            Priority: Minor
>              Labels: derby_triage10_11
>         Attachments: Derby-2446_1.diff, Derby-2446_1.stat
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)