[
https://jira.codehaus.org/browse/SUREFIRE-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=337981#comment-337981
]
Andreas Gudian commented on SUREFIRE-1044:
------------------------------------------
I've rebased your commits locally and ran the integration tests. Any test-NG
tests that use the jdk4-style javadoc annotations fail with ClassNotFound
errors.
I've fixed that, and also changed some of your code to retain as much of the
test class order as possible. Otherwise the order would get mixed up as soon as
suite names or test names were specified.
Everything is pushed to master, so pls check commit
741c094e6ac1f9dec67ab4025ee519aec7dda49d. If you find anyting wrong with it,
please reopen this issue.
Thanks again for your contributions! :)
> 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
> 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 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
