[
http://jira.codehaus.org/browse/SUREFIRE-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Diesler reopened SUREFIRE-486:
-------------------------------------
Binding the execution of a test to the test source code is not a good idea.
Also your suggested solution would introduce a dependency to a particular
testing framework/version
Suppose you have a test suite that runs against various environments. In
environment A the test is expected to pass in environment B the test should be
excluded. Switching the exclude file depending on environment is common
practice in various TCKs (Test Compatibility Kit)
Please have a look at http://jbws.dyndns.org/mediawiki/index.php?title=WSF for
more background on this.
> 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
