Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Fri, 4 Jul 2014 12:23:34 +0000 (UTC)
From: "Dag H. Wanvik (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12717065.1401290692896.4500.1404476614716@arcas>
In-Reply-To: <JIRA.12717065.1401290692896@arcas>
References: <JIRA.12717065.1401290692896@arcas>
Subject: [jira] [Commented] (DERBY-6590) Make JUnit tests run the fixtures
 in a deterministic order.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Dag H. Wanvik commented on DERBY-6590:
--------------------------------------

Oops, was sure I had changed that. Thanks! Now I just need to clean up the import sections.... 

> Make JUnit tests run the fixtures in a deterministic order.
> -----------------------------------------------------------
>
>                 Key: DERBY-6590
>                 URL: https://issues.apache.org/jira/browse/DERBY-6590
>             Project: Derby
>          Issue Type: Improvement
>            Reporter: Dag H. Wanvik
>            Assignee: Dag H. Wanvik
>         Attachments: derby-6590-1.diff, derby-6590-2.diff
>
>
> Since JDK 7, when we use the standard decorator for JUnit tests, e.g.
> return TestConfiguration.defaultSuite(AggBuiltinTest.class);
> the order in which the test fixtures get run is indeterministic. This is undesirable because it doesn't add much coverage to the product and makes the tests more brittle than they need to be.


--
This message was sent by Atlassian JIRA
(v6.2#6252)