You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dan Fabulich (JIRA)" <ji...@codehaus.org> on 2008/04/28 23:59:46 UTC

[jira] Closed: (SUREFIRE-486) Exlude tests via an external exlude file

     [ http://jira.codehaus.org/browse/SUREFIRE-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Fabulich closed SUREFIRE-486.
---------------------------------

    Resolution: Won't Fix

I don't think that's the feature you want; there's a better way to do it.  JUnit 4 includes a @Ignore annotiation; TestNG allows you to have your tests throw a SkipException which does something similar.  That will keep the tests in the report, but mark them as "yellow" or "skipped".

If we excluded known bugs entirely, they would simply disappear from the report.

> Exlude tests via an external exlude file
> ----------------------------------------
>
>                 Key: SUREFIRE-486
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-486
>             Project: Maven Surefire
>          Issue Type: New Feature
>            Reporter: Thomas Diesler
>
> Similar to Ant, Surefire should support excludes defined in an external file like this
>               <testExcludes>
>                    <excludeFile>test-excludes-jboss501.txt</excludeFile>
>               </testExcludes>
> The exclude file would look like this
> # [JBWS-2135] WebServiceException: Undefined port type
> org/jboss/test/ws/jaxws/jbws1822/**
> # [JBWS-2136] ClassCastException: com.sun.xml.ws.server.EndpointMessageContextImpl
> org/jboss/test/ws/jaxws/namespace/**
> # [JBAS-5359] mapped-name is required for context of deployment
> org/jboss/test/ws/jaxws/jbws1611/**

-- 
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