RE: Surefires test order

[christophe blin <cb...@tennaxia.com>]

Hi,

searching into the nabble archives, I found a thread which talks about my
problem. I quote the relevant part at the end of my message.

First, I'd like to know if there is finally a possibility to run the JUnit
tests in a specific order when they are executed with surefire ?

Second, I perfectly agree with David : surefire should run the tests in the
order they are written in the file.
While this is not important for unit tests, this is really important for
integration tests.
The reality is that you do not want to write a integration test that is 200
lines so you split up the test in various functions.
Then, you'd like that each function is a separate test case to have a report
that indicates precisely at which moment the test fail (it is easier to know
that the 3rd test case failed whereas to read the stacktrace of the testcase
to find where it crashes).

So my question is : who do not care about the order of integration tests
(i.e how do you do integration testing with surefire not executing the test
cases in the 'right' order) ?

Best regards,
chris


David Jackman wrote:
> 
> Actually, JUnit tests do run in a simple and predictable order
> (especially when a test class provides its own suite).  I agree that
> it's a bad idea to write tests that depend on their ordering, but it
> should not be the build system that enforces this (especially when the
> XML report is the only way to determine what order surefire used) unless
> it's through a property that explicitly tells it to do so.
>  
> ..David..
> 

-- 
View this message in context: http://www.nabble.com/Surefires-test-order-tf734875.html#a6449117
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

RE: Surefires test order

[christophe blin <cb...@tennaxia.com>]

Is no one interested by that question ? Or maybe I should not reply to a so
old question ?

chris

christophe blin wrote:
> 
> Hi,
> 
> searching into the nabble archives, I found a thread which talks about my
> problem. I quote the relevant part at the end of my message.
> 
> First, I'd like to know if there is finally a possibility to run the JUnit
> tests in a specific order when they are executed with surefire ?
> 
> Second, I perfectly agree with David : surefire should run the tests in
> the order they are written in the file.
> While this is not important for unit tests, this is really important for
> integration tests.
> The reality is that you do not want to write a integration test that is
> 200 lines so you split up the test in various functions.
> Then, you'd like that each function is a separate test case to have a
> report that indicates precisely at which moment the test fail (it is
> easier to know that the 3rd test case failed whereas to read the
> stacktrace of the testcase to find where it crashes).
> 
> So my question is : who do not care about the order of integration tests
> (i.e how do you do integration testing with surefire not executing the
> test cases in the 'right' order) ?
> 
> Best regards,
> chris
> 
> 
> David Jackman wrote:
>> 
>> Actually, JUnit tests do run in a simple and predictable order
>> (especially when a test class provides its own suite).  I agree that
>> it's a bad idea to write tests that depend on their ordering, but it
>> should not be the build system that enforces this (especially when the
>> XML report is the only way to determine what order surefire used) unless
>> it's through a property that explicitly tells it to do so.
>>  
>> ..David..
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Surefires-test-order-tf734875.html#a6521850
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org