You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Dmitry Andreychuk (JIRA)" <ji...@apache.org> on 2015/06/22 16:58:00 UTC

[jira] [Created] (GROOVY-7474) Difference between junit3 and junit 4 shouldFail {...} not described in docs

Dmitry Andreychuk created GROOVY-7474:
-----------------------------------------

             Summary: 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


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)