You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@groovy.apache.org by "John Wagenleitner (JIRA)" <ji...@apache.org> on 2017/05/23 15:06:04 UTC

[jira] [Updated] (GROOVY-8197) Make JUnit3/4 GroovyRunners

     [ https://issues.apache.org/jira/browse/GROOVY-8197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Wagenleitner updated GROOVY-8197:
--------------------------------------
    Description: 
Current {{GroovyShell}} currently has reflective methods to detect and run JUnit3 and JUnit4 classes.  These methods might work god as {{GroovyRunner}} classes and they could be added to the RUNNER_REGISTRY in {{GroovySystem}}.

Runners should be able to be registered during class loading (like most other things) rather than during Grape processing.

  was:Current {{GroovyShell}} currently has reflective methods to detect and run JUnit3 and JUnit4 classes.  These methods might work god as {{GroovyRunner}} classes and they could be added to the RUNNER_REGISTRY in {{GroovySystem}}.


> Make JUnit3/4 GroovyRunners
> ---------------------------
>
>                 Key: GROOVY-8197
>                 URL: https://issues.apache.org/jira/browse/GROOVY-8197
>             Project: Groovy
>          Issue Type: Brainstorming
>          Components: groovy-runtime
>    Affects Versions: 2.5.0-alpha-1, 2.4.11
>            Reporter: John Wagenleitner
>            Priority: Minor
>
> Current {{GroovyShell}} currently has reflective methods to detect and run JUnit3 and JUnit4 classes.  These methods might work god as {{GroovyRunner}} classes and they could be added to the RUNNER_REGISTRY in {{GroovySystem}}.
> Runners should be able to be registered during class loading (like most other things) rather than during Grape processing.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)