maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Kabashnyuk (JIRA)" <>
Subject [jira] (SUREFIRE-1044) Changed behaviour of TestNG test execution after implementing runOrder support
Date Wed, 04 Dec 2013 20:34:45 GMT


Sergey Kabashnyuk commented on SUREFIRE-1044:

I made some research about what we have now in surefire plugin 2.16
Basically we have one testng sute for each test class.

But after reading testng documentation
A suite is represented by one XML file. It can contain one or more tests and is defined by
the <suite> tag.

And reviewing author of TestNG plugin to eclipse there he use only one sute per run as it
was in surefire plugin 2.15

Make me feel that old (2.15) behaviour was "more" correct :)

I've made my fork of maven-surefire and add several changes
CheckTestNgVersionsIT.test685  - is working. Other test fail.

But to approve this strategy we should consider such facts:

Fact 1: Support of run order from 6.1.  TESTNG-476: <test> tags are now run in the order
found in testng.xml

Fact 2: Made preserve-order true by default.

So, doing this way we may preserv test order wit testNg versions >6.1-6.3

I thought if we REALY need support for older version TestNGExecutor may play with group or
method dependencies

> Changed behaviour of TestNG test execution after implementing runOrder support
> ------------------------------------------------------------------------------
>                 Key: SUREFIRE-1044
>                 URL:
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: TestNG support
>    Affects Versions: 2.16
>            Reporter: Sergey Kabashnyuk
> I have some code automation around TestNG listeners. And I notice different behaviour
of maven-surefire-plugin 2.15 and 2.16.
> In 2.15  In method during execution contains 1-XmlTestSuite with
1-XmlTest with 2 XmlClass inside. 
> I've also checked InteliJ org.testng.RemoteTestNG he has the same state during execution.
> But in 2.16 we have 2-XmlTestSuite with 1-XmlTest with 1 XmlClass inside. 
> As a result TestNG initialise two IInvokedMethodListener instead of one. 
> Is this expected behaviour?
> Example of test code I put here 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message