db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6590) Make JUnit tests run the fixtures in a deterministic order.
Date Tue, 08 Jul 2014 13:53:04 GMT

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

ASF subversion and git services commented on DERBY-6590:

Commit 1608782 from [~dagw] in branch 'code/trunk'
[ https://svn.apache.org/r1608782 ]

DERBY-6590 Make JUnit tests run the fixtures in a deterministic order.

A new test suite class is introduced to replace the standard JUnit
TestSuite: BaseTestSuite. From its Javadoc:

 * Derby replacement for TestSuite. This version, when provided with a
 * {@code Class} argument in a constructor or method, wraps a {@code TestSuite}
 * around a lexicographically sorted set of fixtures (i.e. test cases) to avoid
 * random fixture ordering (after Java 6). Its usage is similar to the original
 * JUnit TestSuite class.

The old TestConfiguration#orderedSuite has been removed. Import
sections have been updated.

> 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, derby-6590-3.zip
> 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

View raw message