Marcin Zajaczkowski created GROOVY-9492:
-------------------------------------------
Summary: 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
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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
