[
https://jira.codehaus.org/browse/SUREFIRE-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dolk updated SUREFIRE-1019:
-----------------------------------
Attachment: maven-log.txt
I've installed the 2.16-SNAPSHOT and tried the test again. Unfortunately I have
only jUnit tests with that obscure runner. I can't tell if other jUnit test
would have shown the same behaviour. The provider still doesn't run the tests.
I've added a slightly sanitized maven log, showing what happens on my machine.
TestNG even tries to run tests on anonymous classes (the ones with the $x
suffix), while jUnit wouldn't touch them (visible when I explicitly define the
jUnit provider dependency)
> 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
> 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
