maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Rosenvold (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (SUREFIRE-776) Annotation based logic to identify Unit tests from Integration Tests
Date Sun, 13 Nov 2011 17:49:51 GMT

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

Kristian Rosenvold closed SUREFIRE-776.
---------------------------------------

    Resolution: Fixed
      Assignee: Kristian Rosenvold

Issue was fixed with SUREFIRE-329

> Annotation based logic to identify Unit tests from Integration Tests
> --------------------------------------------------------------------
>
>                 Key: SUREFIRE-776
>                 URL: https://jira.codehaus.org/browse/SUREFIRE-776
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: Maven Failsafe Plugin
>    Affects Versions: 2.10
>         Environment: All
>            Reporter: Josh Smith
>            Assignee: Kristian Rosenvold
>
> Currently, based on the documentation, the failsafe plugin only identifies classes to
use as integration tests based on the IT naming scheme in the class name. 
> It would be nice to be able to leverage some of the other options in JUNit4 and use a
annotation for that. If we had a @IntegrationTest annotation at the class/method level then
the Failsafe plugin and/or the surefire plugin could use that to identify what tests went
with which tool and when to execute. 
> Seems like a much cleaner and easier way to filter tests between the phases. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message