[ 
https://issues.apache.org/jira/browse/GEODE-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16805470#comment-16805470
 ] 

Anthony Baker commented on GEODE-167:
-------------------------------------

[~upthewaterspout] [~klund] Does this look useful?  I think I'd rather get rid 
of the 334 {{@Ignore}} statements rather than add new Ignore semantics.

> Leverage the @ConditionalIgnore annotation and corresponding JUnit Rule to 
> setup conditional test exclusions in the test suite based on timestamp or 
> complex condition implemented with IgnoreCondition.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-167
>                 URL: https://issues.apache.org/jira/browse/GEODE-167
>             Project: Geode
>          Issue Type: Improvement
>          Components: general
>         Environment: Apache Geode test infrastructure
>            Reporter: John Blum
>            Assignee: John Blum
>            Priority: Minor
>              Labels: ApacheGeode, ConditionalIgnore, Test, UnitTest
>         Attachments: ConditionalIgnoreRule.java, ConditionalIgnoreRule.java, 
> DefaultIgnoreCondition.java, IgnoreCondition.java, 
> IgnoreConditionEvaluationException.java
>
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> Make use of the {{@ConditionalIgnore}} annotation and corresponding JUnit 
> {{ConditionalIgnoreRule}} to ignore tests on a case-by-case basis using a 
> specific set of criteria (a.k.a. {{IgnoreCondition}}).
> This could be used for instance to ignore offending tests causing failure or 
> hangs in the test suite downstream or to conditional ignore a test based on 
> specific environmental/context requirements.
> See attached source code for reference.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to