You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Charlie Groves (JIRA)" <ji...@codehaus.org> on 2006/05/29 09:08:41 UTC
[jira] Created: (MSUREFIRE-122) Support tests written in Jython
Support tests written in Jython
-------------------------------
Key: MSUREFIRE-122
URL: http://jira.codehaus.org/browse/MSUREFIRE-122
Project: Maven 2.x Surefire Plugin
Type: New Feature
Reporter: Charlie Groves
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
[jira] Commented: (MSUREFIRE-122) Support tests written in Jython
Posted by "Charlie Groves (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSUREFIRE-122?page=comments#action_69602 ]
Charlie Groves commented on MSUREFIRE-122:
------------------------------------------
Have we hit enough votes to start integrating this?
> Support tests written in Jython
> -------------------------------
>
> Key: MSUREFIRE-122
> URL: http://jira.codehaus.org/browse/MSUREFIRE-122
> Project: Maven 2.x Surefire Plugin
> Type: New Feature
> Reporter: Charlie Groves
> 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
[jira] Commented: (MSUREFIRE-122) Support tests written in Jython
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSUREFIRE-122?page=comments#action_67228 ]
Carlos Sanchez commented on MSUREFIRE-122:
------------------------------------------
Not sure if anybody is interested but if it works can be added. Getting votes in this issue will help though.
> Support tests written in Jython
> -------------------------------
>
> Key: MSUREFIRE-122
> URL: http://jira.codehaus.org/browse/MSUREFIRE-122
> Project: Maven 2.x Surefire Plugin
> Type: New Feature
> Reporter: Charlie Groves
> 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
[jira] (SUREFIRE-130) Support tests written in Jython
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated SUREFIRE-130:
----------------------------------
Fix Version/s: (was: Backlog)
> Support tests written in Jython
> -------------------------------
>
> Key: SUREFIRE-130
> URL: https://jira.codehaus.org/browse/SUREFIRE-130
> Project: Maven Surefire
> Issue Type: New Feature
> Components: Maven Surefire Plugin
> Reporter: Charlie Groves
> Attachments: jythonProvider.tar.gz, jythonProviderTest.tar.gz, MSUREFIRE-122-maven-surefire-plugin.patch, MSUREFIRE-122-surefire-providers.patch
>
>
> 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, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-130) Support tests written in Jython
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold updated SUREFIRE-130:
----------------------------------------
Assignee: (was: fabrizio giustina)
> Support tests written in Jython
> -------------------------------
>
> Key: SUREFIRE-130
> URL: http://jira.codehaus.org/browse/SUREFIRE-130
> Project: Maven Surefire
> Issue Type: New Feature
> Reporter: Charlie Groves
> Fix For: Backlog
>
> Attachments: jythonProvider.tar.gz, jythonProviderTest.tar.gz, MSUREFIRE-122-maven-surefire-plugin.patch, MSUREFIRE-122-surefire-providers.patch
>
>
> 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
[jira] Closed: (SUREFIRE-130) Support tests written in Jython
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold closed SUREFIRE-130.
---------------------------------------
Resolution: Won't Fix
http://mail-archives.apache.org/mod_mbox/maven-dev/201101.mbox/%3C1295866251.13332.27.camel@chunky%3E
> Support tests written in Jython
> -------------------------------
>
> Key: SUREFIRE-130
> URL: http://jira.codehaus.org/browse/SUREFIRE-130
> Project: Maven Surefire
> Issue Type: New Feature
> Components: Maven Surefire Plugin
> Reporter: Charlie Groves
> Fix For: Backlog
>
> Attachments: jythonProvider.tar.gz, jythonProviderTest.tar.gz, MSUREFIRE-122-maven-surefire-plugin.patch, MSUREFIRE-122-surefire-providers.patch
>
>
> 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
[jira] Updated: (SUREFIRE-130) Support tests written in Jython
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold updated SUREFIRE-130:
----------------------------------------
Component/s: Maven Surefire Plugin
> Support tests written in Jython
> -------------------------------
>
> Key: SUREFIRE-130
> URL: http://jira.codehaus.org/browse/SUREFIRE-130
> Project: Maven Surefire
> Issue Type: New Feature
> Components: Maven Surefire Plugin
> Reporter: Charlie Groves
> Fix For: Backlog
>
> Attachments: jythonProvider.tar.gz, jythonProviderTest.tar.gz, MSUREFIRE-122-maven-surefire-plugin.patch, MSUREFIRE-122-surefire-providers.patch
>
>
> 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
[jira] Commented: (SUREFIRE-130) Support tests written in Jython
Posted by "Ryan Lea (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209895#action_209895 ]
Ryan Lea commented on SUREFIRE-130:
-----------------------------------
I realise this is 3 years old. From reading through the comments on a few issues: http://jira.codehaus.org/browse/SUREFIRE-292 and http://jira.codehaus.org/browse/SUREFIRE-141 I'm not sure whether this kind of functionality is going to be implemented.
I'm about to start writing a similar provider and modify the surefire-plugin to handle my provider but was wondering if there was actually any kind of direction this project is taking that I should be taking into consideration to ensure that I don't require lots of rework.
Any comments or feedback would be welcomed.
Thanks
> Support tests written in Jython
> -------------------------------
>
> Key: SUREFIRE-130
> URL: http://jira.codehaus.org/browse/SUREFIRE-130
> Project: Maven Surefire
> Issue Type: New Feature
> Reporter: Charlie Groves
> Assignee: fabrizio giustina
> Fix For: 2.x
>
> Attachments: jythonProvider.tar.gz, jythonProviderTest.tar.gz, MSUREFIRE-122-maven-surefire-plugin.patch, MSUREFIRE-122-surefire-providers.patch
>
>
> 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
[jira] Commented: (MSUREFIRE-122) Support tests written in Jython
Posted by "fabrizio giustina (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSUREFIRE-122?page=comments#action_73990 ]
fabrizio giustina commented on MSUREFIRE-122:
---------------------------------------------
Hi Charlie,
I tried to integrate your patches, but looks like that tests on the jythonProviderTest don't work properly. After adding the surefire-jython provider and applying your patch to the maven surefire plugin this is what I get when I try running tests:
[INFO] Surefire report directory: \jythonProvider.tar\jythonProvider\jythonProviderTest\target\surefire-reports
*sys-package-mgr*: processing new jar, 'C:\repository\m2\jython\jython\2.2-alpha1\jython-2.2-alpha1.jar'
org.apache.maven.surefire.booter.SurefireExecutionException: Problem reflecting on class org.python.core.PySystemState; nested exception is java.lang.reflect.InvocationTargetException: null; nested exception is
org.apache.maven.surefire.testset.TestSetFailedException: Problem reflecting on class org.python.core.PySystemState; nested exception is java.lang.reflect.InvocationTargetException: null
org.apache.maven.surefire.testset.TestSetFailedException: Problem reflecting on class org.python.core.PySystemState; nested exception is java.lang.reflect.InvocationTargetException: null
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.maven.surefire.jython.JythonDirectoryTestSuite.setupInterpreter(JythonDirectoryTestSuite.java:130)
at org.apache.maven.surefire.jython.JythonDirectoryTestSuite.locateTestSets(JythonDirectoryTestSuite.java:102)
at org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:147)
at org.apache.maven.surefire.Surefire.run(Surefire.java:108)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:265)
at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:792)
Caused by: Traceback (innermost last):
File "<string>", line 7, in ?
ImportError: cannot import name SurefireTestSet
at org.python.core.Py.ImportError(Py.java:193)
at org.python.core.imp.importFromAs(imp.java:694)
at org.python.core.imp.importFrom(imp.java:667)
at org.python.pycode._pyx0.f$0(<string>:7)
at org.python.pycode._pyx0.call_function(<string>)
at org.python.core.PyTableCode.call(PyTableCode.java:213)
at org.python.core.PyCode.call(PyCode.java:14)
at org.python.core.Py.runCode(Py.java:1182)
at org.python.core.Py.exec(Py.java:1204)
at org.python.util.PythonInterpreter.exec(PythonInterpreter.java:137)
... 14 more
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
The problem may be caused by recent changes on the surefire classloader... let me know if you can have a look at it.
> 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
[jira] Commented: (SUREFIRE-130) Support tests written in Jython
Posted by "Karl Palsson (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=241451#action_241451 ]
Karl Palsson commented on SUREFIRE-130:
---------------------------------------
To me this sounds perfect, either via this patch, or via http://jira.codehaus.org/browse/SUREFIRE-141 We've started writing tests in jython, but currently it's an entirely separate project, that we copy the built jar over into, I'd love to see it better integrated!
> Support tests written in Jython
> -------------------------------
>
> Key: SUREFIRE-130
> URL: http://jira.codehaus.org/browse/SUREFIRE-130
> Project: Maven Surefire
> Issue Type: New Feature
> Reporter: Charlie Groves
> Assignee: fabrizio giustina
> Fix For: Backlog
>
> Attachments: jythonProvider.tar.gz, jythonProviderTest.tar.gz, MSUREFIRE-122-maven-surefire-plugin.patch, MSUREFIRE-122-surefire-providers.patch
>
>
> 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
[jira] Updated: (SUREFIRE-130) Support tests written in Jython
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated SUREFIRE-130:
----------------------------------
Fix Version/s: (was: 2.3)
2.4
> Support tests written in Jython
> -------------------------------
>
> Key: SUREFIRE-130
> URL: http://jira.codehaus.org/browse/SUREFIRE-130
> Project: Maven Surefire
> Issue Type: New Feature
> Reporter: Charlie Groves
> Assigned To: fabrizio giustina
> Fix For: 2.4
>
> Attachments: jythonProvider.tar.gz, jythonProviderTest.tar.gz, MSUREFIRE-122-maven-surefire-plugin.patch, MSUREFIRE-122-surefire-providers.patch
>
>
> 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
[jira] Commented: (SUREFIRE-130) Support tests written in Jython
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=247074#action_247074 ]
Kristian Rosenvold commented on SUREFIRE-130:
---------------------------------------------
Note that surefire-141 has now been fixed.
> Support tests written in Jython
> -------------------------------
>
> Key: SUREFIRE-130
> URL: http://jira.codehaus.org/browse/SUREFIRE-130
> Project: Maven Surefire
> Issue Type: New Feature
> Reporter: Charlie Groves
> Assignee: fabrizio giustina
> Fix For: Backlog
>
> Attachments: jythonProvider.tar.gz, jythonProviderTest.tar.gz, MSUREFIRE-122-maven-surefire-plugin.patch, MSUREFIRE-122-surefire-providers.patch
>
>
> 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
[jira] Moved: (SUREFIRE-130) Support tests written in Jython
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter moved MSUREFIRE-122 to SUREFIRE-130:
-------------------------------------------------
Fix Version/s: (was: 2.3)
2.3
Key: SUREFIRE-130 (was: MSUREFIRE-122)
Project: Maven Surefire (was: Maven 2.x Surefire Plugin)
> Support tests written in Jython
> -------------------------------
>
> Key: SUREFIRE-130
> URL: http://jira.codehaus.org/browse/SUREFIRE-130
> Project: Maven Surefire
> Issue Type: New Feature
> Reporter: Charlie Groves
> Assigned To: fabrizio giustina
> Fix For: 2.3
>
> Attachments: jythonProvider.tar.gz, jythonProviderTest.tar.gz, MSUREFIRE-122-maven-surefire-plugin.patch, MSUREFIRE-122-surefire-providers.patch
>
>
> 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
[jira] Commented: (SUREFIRE-130) Support tests written in Jython
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252623#action_252623 ]
Kristian Rosenvold commented on SUREFIRE-130:
---------------------------------------------
I am proposing this issue as wontfix. Now that surefire-141 is fixed, it is trivial to write a jython provider that seamlessly integrates with surefire. This provider should be part of the jython community and I really see no reason why it should be included in surefire itself.
> Support tests written in Jython
> -------------------------------
>
> Key: SUREFIRE-130
> URL: http://jira.codehaus.org/browse/SUREFIRE-130
> Project: Maven Surefire
> Issue Type: New Feature
> Components: Maven Surefire Plugin
> Reporter: Charlie Groves
> Fix For: Backlog
>
> Attachments: jythonProvider.tar.gz, jythonProviderTest.tar.gz, MSUREFIRE-122-maven-surefire-plugin.patch, MSUREFIRE-122-surefire-providers.patch
>
>
> 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
[jira] Commented: (MSUREFIRE-122) Support tests written in Jython
Posted by "Charlie Groves (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSUREFIRE-122?page=comments#action_74717 ]
Charlie Groves commented on MSUREFIRE-122:
------------------------------------------
Yep, I was depending on SurefireTestSet being on the classpath which no longer seems to be the case. I'll take a look at moving the classloading around so this works.
> 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
[jira] Commented: (SUREFIRE-130) Support tests written in Jython
Posted by "Johannes Buchner (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=276150#comment-276150 ]
Johannes Buchner commented on SUREFIRE-130:
-------------------------------------------
Take a look at my jython test plugin at http://mavenjython.sourceforge.net/test/
> Support tests written in Jython
> -------------------------------
>
> Key: SUREFIRE-130
> URL: https://jira.codehaus.org/browse/SUREFIRE-130
> Project: Maven Surefire
> Issue Type: New Feature
> Components: Maven Surefire Plugin
> Reporter: Charlie Groves
> Fix For: Backlog
>
> Attachments: jythonProvider.tar.gz, jythonProviderTest.tar.gz, MSUREFIRE-122-maven-surefire-plugin.patch, MSUREFIRE-122-surefire-providers.patch
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSUREFIRE-122) Support tests written in Jython
Posted by "fabrizio giustina (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (SUREFIRE-130) Support tests written in Jython
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated SUREFIRE-130:
----------------------------------
Patch Submitted: [Yes]
> Support tests written in Jython
> -------------------------------
>
> Key: SUREFIRE-130
> URL: http://jira.codehaus.org/browse/SUREFIRE-130
> Project: Maven Surefire
> Issue Type: New Feature
> Reporter: Charlie Groves
> Assignee: fabrizio giustina
> Fix For: 2.4
>
> Attachments: jythonProvider.tar.gz, jythonProviderTest.tar.gz, MSUREFIRE-122-maven-surefire-plugin.patch, MSUREFIRE-122-surefire-providers.patch
>
>
> 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
[jira] Updated: (MSUREFIRE-122) Support tests written in Jython
Posted by "Charlie Groves (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSUREFIRE-122?page=all ]
Charlie Groves updated MSUREFIRE-122:
-------------------------------------
Attachment: jythonProviderTest.tar.gz
MSUREFIRE-122-maven-surefire-plugin.patch
MSUREFIRE-122-surefire-providers.patch
I've updated the jython provider to work with the classloading changes. You should be able to apply the two patches to their respective projects, build, unpack the tar and run it to see the jython provider in action. If one test passes and one fails in the example project everything is working correctly.
I've been using this plugin at work for the past couple months and it seems pretty solid. I've added a traceback writer that cleans out most of the Jython invocation crud since I initially posted this. It's in the new patch.
> 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, jythonProviderTest.tar.gz, MSUREFIRE-122-maven-surefire-plugin.patch, MSUREFIRE-122-surefire-providers.patch
>
>
> 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