[ http://jira.codehaus.org/browse/MSUREFIRE-122?page=all ]
fabrizio giustina updated MSUREFIRE-122:
----------------------------------------
Assignee: fabrizio giustina
Fix Version/s: 2.3
> Support tests written in Jython
> -------------------------------
>
> Key: MSUREFIRE-122
> URL: http://jira.codehaus.org/browse/MSUREFIRE-122
> Project: Maven 2.x Surefire Plugin
> Issue Type: New Feature
> Reporter: Charlie Groves
> Assigned To: fabrizio giustina
> Fix For: 2.3
>
> Attachments: jythonProvider.tar.gz
>
>
> I've written a first pass at a surefire-provider for JUnit and Python
> unittest TestCases written in Jython. Before I continue any further I'd like
> to make sure that the provider is wanted and that I'm heading in the right
> direction.
> To do the minimum to get it up and running, I've hooked into the
> maven-surefire-plugin to hook my provider into the system somewhat like the
> TestNG provider did. maven-surefire-plugin passes a path(defaults to
> src/test/jython) to the provider. The provider searches the path for files
> matching include patterns and loads those as Python modules. For every class
> in the matching modules that extends junit or unittest TestCase, it makes a
> SurefireTestSuite and exposes them for running. Sound like a decent approach?
> To give it a spin, apply maven-surefire-plugin.patch, mvn install on the
> surefire-jython project and run mvn test in jythonProviderTest. It's just
> contains a single Junit testcase with a failing and passing test.
> I haven't even checked what happens when the jython tests throw exceptions,
> and I know there's alot to be done as far as making it a usable plugin, but I
> felt like getting some feedback before continuing.
--
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
