[
http://jira.codehaus.org/browse/SUREFIRE-560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=184850#action_184850
]
Jörg Hohwiller edited comment on SUREFIRE-560 at 7/25/09 4:52 AM:
------------------------------------------------------------------
Please also note that extracting the @Ignored tests into a sub-class is not
always suitable when there are already sub-classes for other aspects.
was (Author: hohwille):
Please also note that extracting the @Ignored tests in also not always
suitable when there are already sub-classes for other aspects.
> tests with @Ignore are treated as "unsuccessful"
> ------------------------------------------------
>
> Key: SUREFIRE-560
> URL: http://jira.codehaus.org/browse/SUREFIRE-560
> Project: Maven Surefire
> Issue Type: Bug
> Components: report plugin
> Affects Versions: 2.4.3
> Reporter: Jörg Hohwiller
>
> According to SUREFIRE-303 you care about @Ignore tests which is generally a
> good idea.
> However you treat them as "unsuccessful" and then dashboard-maven-plugin
> marks this in red.
> I am using @Ignore for JUnit test-methods that can NOT run headless or in a
> os-independent batch, or whatever.
> Generally I think that this is what @Ignore is all about. If I have tests
> that do not work but definitely should, I would
> NOT add an @Ignore and get an according failure until the bug is fixed.
> So either provide a way to mark test-methods as skipped by maven but not
> treated unsuccessful, e.g.
> via some prefix like "OK:" in @Ignore("OK: manual test") or by generally
> treating @Ignore
> as harmless. I personally suggest the latter.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
