maven-issues mailing list archives

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

     [ https://jira.codehaus.org/browse/SUREFIRE-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andreas Gudian reassigned SUREFIRE-1044:
----------------------------------------

    Assignee: Andreas Gudian
    
> Changed behaviour of TestNG test execution after implementing runOrder support
> ------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-1044
>                 URL: https://jira.codehaus.org/browse/SUREFIRE-1044
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: TestNG support
>    Affects Versions: 2.16
>            Reporter: Sergey Kabashnyuk
>            Assignee: Andreas Gudian
>
> 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  org.testng.TestNG.run 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 
> https://github.com/skabashnyuk/mvntestng

--
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: http://www.atlassian.com/software/jira

Mime
View raw message