[jira] [Resolved] (GROOVY-11887) Scripting support for JUnit5 conditional execution

["Paul King (Jira)" <ji...@apache.org>]

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

Paul King resolved GROOVY-11887.
--------------------------------
    Resolution: Fixed

Proposed PR merged.

> Scripting support for JUnit5 conditional execution
> --------------------------------------------------
>
>                 Key: GROOVY-11887
>                 URL: https://issues.apache.org/jira/browse/GROOVY-11887
>             Project: Groovy
>          Issue Type: New Feature
>            Reporter: Paul King
>            Assignee: Paul King
>            Priority: Major
>             Fix For: 6.0.0-alpha-1
>
>
> JUnit used to support @EnabledIf scripting (and @DisabledIf) where a String would be evaluated using e.g. JavaScript. This was deprecated in 5.5 and removed in 5.6. Instead in 5.7, a different @EnabledIf was introduced that point to a method name. The original scripting support was removed when JavaScript support was dropped but also since it was seen as a potential security issue. Groovy users are more familiar with using scripting in secure ways and do have a scripting language available, so this issue will look at adding @GroovyEnabledIf and @GroovyDisabledIf annotations to bring back the scripting support.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)