Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of nkeywal@gmail.com designates
 209.85.215.49 as permitted sender)
MIME-Version: 1.0
From: Nicolas Liochon <nkeywal@gmail.com>
Date: Mon, 14 Jan 2013 14:57:08 +0100
Message-ID: 
 <CAPcDmSvT6FyxOsZ+5z9cOhyb1oeAv550ZBa-sHHbtmAzpj-SKg@mail.gmail.com>
Subject: junit 4.11 / JDK 1.7 and test methods execution order.
To: dev@hbase.apache.org
Content-Type: multipart/alternative; boundary=f46d04016ac795eefd04d3400657

--f46d04016ac795eefd04d3400657
Content-Type: text/plain; charset=ISO-8859-1

Hi all,

In JDK 1.7, the order of the methods returned by reflection can vary. While
the ordering was not guaranteed previously, it happens that it was always
the same (declaration order). It's not the case anymore in JDK 1.7

Consequence for the tests: the order in which the tests are executed within
a test class may vary.

Because of this, JUnit 4.11 decided to execute the tests in a different
order than the declaration order.
That's explained here:
http://randomallsorts.blogspot.fr/2012/12/junit-411-whats-new-test-execution-order.html

So depending on the execution order used to be bad, but can now randomly
breaks the tests, especially with jdk 1.7 and JUnit < 4.11.
With JUnit 4.11, the order is determined, but different from what it used
to be. So it breaks some tests. I'm currently fixing this (low priority).
But it's worth knowing, especially if you port the tests from one HBase
version to another.

Cheers,

Nicolas

--f46d04016ac795eefd04d3400657--