[
https://jira.codehaus.org/browse/SUREFIRE-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329599#comment-329599
]
Andreas Gudian commented on SUREFIRE-1019:
------------------------------------------
Ok, then: do not specify the providers at all, but configure the parameter
{{testNGArtifactName}} to {{dev:null}} (or foo:bar) in the JUnit-execution to
not let Surefire auto-select the surefire-testng provider (because it does not
find testNG on the classpath).
The (third) default execution of Surefire that would now fail your build can be
configured with {{skip}} set to {{true}}, causing surefire not doing anything
during "default-tests".
> TestNG provider fails to execute JUnit4 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
> Assignee: Andreas Gudian
> Fix For: 2.16
>
> Attachments: maven-log.txt
>
>
> 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
