[
https://jira.codehaus.org/browse/SUREFIRE-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=356103#comment-356103
]
Andreas Gudian commented on SUREFIRE-833:
-----------------------------------------
I would opt to not add a new parameter for this now. For version 3, I still
envision that we provide some extension points where users can hook in their
own implementations to allow stuff like:
* detection of tests to run (e.g. from file system, from classpath, from an
excel sheet, from some server, what ever...)
* filtering the tests to run (use case right here)
* imposing an order on the test cases (e.g. failed first, depending on
annotations, other crazy stuff)
* test listeners (provider independent)
* ??
We should really create a ticket for that some day... ;)
> Support for annotated JUnit @Category
> -------------------------------------
>
> Key: SUREFIRE-833
> URL: https://jira.codehaus.org/browse/SUREFIRE-833
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Junit 4.x support
> Affects Versions: 2.12
> Reporter: Jan Goyvaerts
> Attachments: SUREFIRE-833-spraguep-2.patch,
> SUREFIRE-833-spraguep.patch
>
>
> The current implementation of Surefire seems to look for explicit @Category
> annotations in the test classes. And will only consider those. Suppose I'd
> like to add a more concise annotation for this:
> @Category(IntegrationTests.class) <== JUnit @Category
> @Target({ElementType.TYPE})
> @Retention(RetentionPolicy.RUNTIME)
> @Documented
> public @interface IntegrationTest {}
> Annotating my test class with @IntegrationTest does not work. Although I
> think it looks much better than repeating everywhere in my code
> "@Category(com.foo.bar.IntegrationTests.class)". For which I add an
> additional dependency in the interface class btw.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
