You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flume.apache.org by "Ashish Paliwal (JIRA)" <ji...@apache.org> on 2014/11/05 08:08:34 UTC

[jira] [Resolved] (FLUME-40) Use @Categories in JUnit tests

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

Ashish Paliwal resolved FLUME-40.
---------------------------------
       Resolution: Won't Fix
    Fix Version/s: v0.9.5

Won't fix. 0.X branch not maintained anymore

> Use @Categories in JUnit tests
> ------------------------------
>
>                 Key: FLUME-40
>                 URL: https://issues.apache.org/jira/browse/FLUME-40
>             Project: Flume
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: v0.9.4
>            Reporter: Jonathan Hsieh
>            Priority: Minor
>             Fix For: v0.9.5
>
>
> This is a new JUnit 4.8 feature that can be used to group slow tests, and tests for different subsystems, or other categories like the torture or perf tests.
> Look at these examples:
> http://saffgreenbar.blogspot.com/2009/11/heres-test-code-snippet-public.html
> http://weblogs.java.net/blog/johnsmart/archive/2010/04/25/grouping-tests-using-junit-categories-0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)