You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jan Goyvaerts (JIRA)" <ji...@codehaus.org> on 2012/02/09 12:58:02 UTC
[jira] (SUREFIRE-832) JUnit categories only work when junit47
provider is explicitly set
Jan Goyvaerts created SUREFIRE-832:
--------------------------------------
Summary: JUnit categories only work when junit47 provider is explicitly set
Key: SUREFIRE-832
URL: https://jira.codehaus.org/browse/SUREFIRE-832
Project: Maven Surefire
Issue Type: Bug
Components: Junit 4.x support
Reporter: Jan Goyvaerts
If no explicit JUnit 4.7 provider is stipulated, all tests will be run. Regardless of their @Category annotations. This is contrary to what's stipulated in the documentation; that the provider will automatically be chosen.
(why not just use the JUnit dependency of the project btw ? If it's not supporting categories, you can't use the @Category annotation either).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-832) JUnit categories only work when junit47
provider is explicitly set
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold closed SUREFIRE-832.
---------------------------------------
Resolution: Fixed
Fix Version/s: 2.13
Assignee: Kristian Rosenvold
Fixed with IT in r1242381. The buffering effect is SUREFIRE-817, which is one of the remaining reasons why this provider is not default for modern JUnit versions.
As for other slowdowns, some kind of evidence like a small sample project would be necessary. Please file separate issues for distinct problems, do not piggyback further onto this issue.
> JUnit categories only work when junit47 provider is explicitly set
> ------------------------------------------------------------------
>
> Key: SUREFIRE-832
> URL: https://jira.codehaus.org/browse/SUREFIRE-832
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.x support
> Reporter: Jan Goyvaerts
> Assignee: Kristian Rosenvold
> Fix For: 2.13
>
>
> If no explicit JUnit 4.7 provider is stipulated, all tests will be run. Regardless of their @Category annotations. This is contrary to what's stipulated in the documentation; that the provider will automatically be chosen.
> (why not just use the JUnit dependency of the project btw ? If it's not supporting categories, you can't use the @Category annotation either).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-832) JUnit categories only work when junit47
provider is explicitly set
Posted by "Jan Goyvaerts (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291283#comment-291283 ]
Jan Goyvaerts commented on SUREFIRE-832:
----------------------------------------
There seems to be some kind of performance/stability/threading problem for the JUnit 47 provider also. The tests fly if no provider is mentioned. But then the category selection does not work any more.
The most visible effect is that logging seems to stop. But that's because it's being buffered and released when all the tests have run. For long running tests there seems to be an important slowdown. If I would have to guess I'd say there's a synchronization/locking problem somewhere.
> JUnit categories only work when junit47 provider is explicitly set
> ------------------------------------------------------------------
>
> Key: SUREFIRE-832
> URL: https://jira.codehaus.org/browse/SUREFIRE-832
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.x support
> Reporter: Jan Goyvaerts
>
> If no explicit JUnit 4.7 provider is stipulated, all tests will be run. Regardless of their @Category annotations. This is contrary to what's stipulated in the documentation; that the provider will automatically be chosen.
> (why not just use the JUnit dependency of the project btw ? If it's not supporting categories, you can't use the @Category annotation either).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira