jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Maven Surefire
  • SUREFIRE-141

Surefire should provide a pluggable means to specify a custom provider

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 2.7
  • Component/s: None
  • Labels:
    None

Description

The current way that surefire determines which provider to use is hard coded and based on a project's dependencies. I would like to write a custom surefire-provider and be able to specify to use that provider without having to patch the surefire plugin. In my case I want to write a surefire-provider that will run Eclipse PDE Junits which wouldn't neccessarily have a specific dependency listed

Issue Links

is depended upon by

Task - A task that needs to be done. SUREFIRE-292 Documentation for surefire API and providers

  • Blocker - Blocks development and/or testing work, production could not run
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
is related to

Improvement - An improvement or enhancement to an existing feature or task. SUREFIRE-352 Get rid of hardcoded TestNG dependency name.

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Arnaud Bailly added a comment - 06/Feb/07 6:09 AM

In my case, I would like to add a custom provider for generating coverage information during testing. This would allow coverage reports to be generated without the need to rerun tests.

Show
Arnaud Bailly added a comment - 06/Feb/07 6:09 AM In my case, I would like to add a custom provider for generating coverage information during testing. This would allow coverage reports to be generated without the need to rerun tests.
Hide
Permalink
Ralf Ebert added a comment - 28/Jul/10 6:20 AM

Also there is a nitpicking corner case where the provider cannot be guessed by looking at the project dependencies: Building JUnit with Maven. JUnit has a pom.xml ( http://github.com/KentBeck/junit/blob/master/pom.xml ) but will not specify JUnit as dependency but still wants its tests to be executed using 'surefire-junit4'. A way to explicitly specify the provider would help here.

Show
Ralf Ebert added a comment - 28/Jul/10 6:20 AM Also there is a nitpicking corner case where the provider cannot be guessed by looking at the project dependencies: Building JUnit with Maven. JUnit has a pom.xml ( http://github.com/KentBeck/junit/blob/master/pom.xml ) but will not specify JUnit as dependency but still wants its tests to be executed using 'surefire-junit4'. A way to explicitly specify the provider would help here.
Hide
Permalink
Stephen Connolly added a comment - 10/Aug/10 5:57 AM

Putting in the bucket for 2.7

Show
Stephen Connolly added a comment - 10/Aug/10 5:57 AM Putting in the bucket for 2.7
Hide
Permalink
Stephen Connolly added a comment - 10/Aug/10 5:58 AM

this should be a must fix for 2.7

Show
Stephen Connolly added a comment - 10/Aug/10 5:58 AM this should be a must fix for 2.7
Hide
Permalink
Jacek Furmankiewicz added a comment - 24/Sep/10 3:36 PM

is there any timeline for this? We would like to start using non-Java BDD tools such as Cucumber (Ruby) or Lettuce (Python) instead of using typical JUnit for integration tests. This would mean writing either our own separate Mojo that would plug into the integration-test phase (or better) just adding a Surefire provider.

Thank you

Show
Jacek Furmankiewicz added a comment - 24/Sep/10 3:36 PM is there any timeline for this? We would like to start using non-Java BDD tools such as Cucumber (Ruby) or Lettuce (Python) instead of using typical JUnit for integration tests. This would mean writing either our own separate Mojo that would plug into the integration-test phase (or better) just adding a Surefire provider. Thank you
Hide
Permalink
Kristian Rosenvold added a comment - 09/Dec/10 4:08 PM

Fixed in a large number of commits. API is not frozen until further notice.

Show
Kristian Rosenvold added a comment - 09/Dec/10 4:08 PM Fixed in a large number of commits. API is not frozen until further notice.

People

  • Assignee:
    Kristian Rosenvold
    Reporter:
    Micah Whitacre
Vote (23)
Watch (12)

Dates

  • Created:
    25/Aug/06 3:41 PM
    Updated:
    09/Dec/10 4:08 PM
    Resolved:
    09/Dec/10 4:08 PM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.