You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Marcin Zajaczkowski (Jira)" <ji...@apache.org> on 2020/09/28 20:34:00 UTC
[jira] [Updated] (GROOVY-9492) Relax groovy.test.NotYetImplemented
dependency on JUnit 4's AssertionFailedError
[ https://issues.apache.org/jira/browse/GROOVY-9492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcin Zajaczkowski updated GROOVY-9492:
----------------------------------------
Description:
Working on removing the remainder of JUnit 4 from spock-core, I have encountered {{@groovy.transform.NotYetImplemented}} which transformation is wired to {{junit.framework.AssertionFailedError}}. It's deprecated in favor of {{@groovy.test.NotYetImplemented}}, but the corresponding transformation is also wired to {{AssertionFailedError}}. That makes its usage without JUnit 4 (and also testing in Spock 2) harder
It would be good to check at runtime which exception is available at classpath to work also in the situation without JUnit 4 on classpath.
Btw, I don't know which component should I choose. There is no groovy-test component.
was:
Working on removing the remainder of JUnit 4 from spock-core, I have encountered {{@groovy.transform.NotYetImplemented}} which transformation is wired to {{junit.framework.AssertionFailedError}}. It's deprecated in favor of {{@groovy.test.NotYetImplemented}}, but the corresponding transformation is also wired to {{AssertionFailedError}}. That makes its usage without JUnit 4 (and also testing in Spock 2) harder
It would be good to check at runtime which exception is available at classpath to works also in the situation without JUnit 4 on classpath.
Btw, I don't know which component should I choose. There is no groovy-test component.
> Relax groovy.test.NotYetImplemented dependency on JUnit 4's AssertionFailedError
> --------------------------------------------------------------------------------
>
> Key: GROOVY-9492
> URL: https://issues.apache.org/jira/browse/GROOVY-9492
> Project: Groovy
> Issue Type: Improvement
> Components: groovy-test-junit5
> Affects Versions: 3.0.2
> Reporter: Marcin Zajaczkowski
> Assignee: Paul King
> Priority: Minor
> Labels: breaking
> Fix For: 4.0.0-alpha-1, 3.0.3
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Working on removing the remainder of JUnit 4 from spock-core, I have encountered {{@groovy.transform.NotYetImplemented}} which transformation is wired to {{junit.framework.AssertionFailedError}}. It's deprecated in favor of {{@groovy.test.NotYetImplemented}}, but the corresponding transformation is also wired to {{AssertionFailedError}}. That makes its usage without JUnit 4 (and also testing in Spock 2) harder
> It would be good to check at runtime which exception is available at classpath to work also in the situation without JUnit 4 on classpath.
>
> Btw, I don't know which component should I choose. There is no groovy-test component.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)