maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Gudian (JIRA)" <>
Subject [jira] (SUREFIRE-1044) Changed behaviour of TestNG test execution after implementing runOrder support
Date Mon, 16 Dec 2013 18:48:45 GMT


Andreas Gudian commented on SUREFIRE-1044:

Hi Sergey, 
I have not yet merged your pull request to master and switched off the checks for runOrder
in the IT for the older versions because I wonder if there is something with creating the
suite that we should do differently. 
For example, always having the suite named "suite" and the test named "test" feels strange.
The TestNG code for creating suites out of the 'command line tests' for example reads some
annotations and grabs the information about suite name and test name from there (if present).
I know, with 2.16, we broke that as well. But is that something we should keep breaking?
The thing is, I haven't that much experience with TestNG as a user and so I'm having a hard
time to imagine what TestNG users might expect. And how important the TestNG generated HTML
report is for them (where suite name and test name are the primary and the secondary criteria
for structuring the result pages).
What's your opinion on this?
> 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
>            Assignee: Andreas Gudian
>             Fix For: 2.17
> 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