[jira] [Closed] (SUREFIRE-833) Support for annotated JUnit @Category

["Tibor Digana (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SUREFIRE-833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tibor Digana closed SUREFIRE-833.
---------------------------------
    Resolution: Won't Fix

See tags in JUnit5 [1].
You can already use it and strings are better than empty classes.
We are working on migrating junit5 surefire-provider.

[1] http://junit.org/junit5/docs/current/user-guide/#writing-tests-tagging-and-filtering

> Support for annotated JUnit @Category
> -------------------------------------
>
>                 Key: SUREFIRE-833
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-833
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: Junit 4.x support
>    Affects Versions: 2.12
>            Reporter: Jan Goyvaerts
>            Assignee: Tibor Digana
>         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.3.4#6332)