[
https://issues.apache.org/jira/browse/GROOVY-7474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14615589#comment-14615589
]
Dmitry Andreychuk commented on GROOVY-7474:
-------------------------------------------
I've made a pull request: https://github.com/apache/incubator-groovy/pull/55
> Difference between junit3 and junit 4 shouldFail {...} not described in docs
> ----------------------------------------------------------------------------
>
> Key: GROOVY-7474
> URL: https://issues.apache.org/jira/browse/GROOVY-7474
> Project: Groovy
> Issue Type: Bug
> Components: Documentation
> Reporter: Dmitry Andreychuk
> Priority: Trivial
> Labels: contributers-welcome
>
> Groovy language documentation chapter on junit4
> ([http://docs.groovy-lang.org/latest/html/documentation/#_junit_4]) states
> that "shouldFail can be used the same way it can be used in a
> GroovyTestCase". In fact junit4 version returns exception while junit3
> returns message.
> I've spent quite a lot of time trying to figure out why shouldFail in my code
> returns an exception while documentation and tests say that it returns
> message. It turned out that I was reading documentation for a wrong
> shouldFail. But I've never thought that methods in GroovyTestCase and
> GroovyAssert may have different signature or semantic. A small notice in
> documentation might help others avoid this confusion. An example for junit 4
> version would be nice too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
