[
https://jira.codehaus.org/browse/SUREFIRE-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329520#comment-329520
]
Andreas Gudian commented on SUREFIRE-1019:
------------------------------------------
I've committed a fix already that works with simple JUnit4 tests.
However, I already saw that using the Parameterized runner the tests would be
executed (when using the JUnit 4.10 style of the Parameterized-API - with the
4.11 style, no test was executed) - but Surefire get's no information about
them.
So please try the latest 2.16-SNAPSHOT after the next build on our CI server
finished (successfully, I hope):
https://builds.apache.org/job/maven-surefire/1234/
Let me know if it executes your tests and if the test results are reported
correctly in the TEST-*.xml files and on the console.
I'll extend our own ITs as soon as I found out where the problem with the more
obscure runners might be.
> TestNG provider fails to execute certain jUnit tests
> ----------------------------------------------------
>
> Key: SUREFIRE-1019
> URL: https://jira.codehaus.org/browse/SUREFIRE-1019
> Project: Maven Surefire
> Issue Type: Bug
> Components: TestNG support
> Affects Versions: 2.15
> Reporter: Andreas Dolk
>
> TestNG won't run certain jUnit tests. The test that showed this behaviour are
> compiled from specs bei jnario and use the special jnario test runner. During
> a maven build, TestNG "inspects" all test classes but doesn't execute any
> test method.
> This thread on the maven uses mailing list contain further informations about
> this issue:
> http://mail-archives.apache.org/mod_mbox/maven-users/201307.mbox/%3ccakbglvvdaw7tibdyxpjqnnwgknmkxecwdre_m5ncbh6u06v...@mail.gmail.com%3E
--
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
