[
https://issues.apache.org/jira/browse/LUCENE-5475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13913172#comment-13913172
]
Robert Muir commented on LUCENE-5475:
-------------------------------------
Separately, I really wish when an annotation disables a test (like \@BadApple,
or \@Slow, or any other reason), if the test-framework could somehow reflect
some attributes about that annotation to the console?
e.g. instead of:
{noformat}
[junit4] IGNOR/A 0.00s | FooTestClass.testBar
[junit4] > Assumption #1: 'badapple' test group is disabled (@BadApple)
{noformat}
maybe something like:
{noformat}
[junit4] IGNOR/A 0.00s | FooTestClass.testBar
[junit4] > Assumption #1: 'badapple' test group is disabled (@BadApple:
bugUrl=http://issues.apache.org/jira/browse/WHATEVER-1234)
{noformat}
I don't think this should block this change, but if something like this is
possible, it would give more visibility to these tests. Maybe [~dweiss] has an
idea.
> add required attribute bugUrl to @BadApple
> ------------------------------------------
>
> Key: LUCENE-5475
> URL: https://issues.apache.org/jira/browse/LUCENE-5475
> Project: Lucene - Core
> Issue Type: Bug
> Components: general/test
> Reporter: Robert Muir
> Attachments: LUCENE-5475.patch
>
>
> This makes it impossible to tag a test as a badapple without a pointer to a
> JIRA issue.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
