Comments on: Groovy closures make unit testing with “soft asserts” simple

By: tednaleid

tednaleid — Tue, 01 Feb 2011 22:18:39 +0000

@Richard you’re using the language keyword “assert”, it’s not a method call and isn’t intercepted by groovy’s metaclass stuff. If you rewrite it with assertEquals instead of just assert it should work as expected.

Keywords (such as assert, if, for, while, etc) aren’t methods so groovy can’t intercept them. When they’re compiled into byte code, they look totally different from method calls (like assertEquals).

By: Richard

Richard — Tue, 01 Feb 2011 18:21:52 +0000

This doesn’t seem to work in Groovy 1.7 (with power asserts). Should it work? For me I only get the first assert failure.

Example:

softAsserts {
assert 1==2
assert 2==3
}

Yields:

Assertion failed:

assert 1 == 2
|
false

By: Matthias Bohlen

Matthias Bohlen — Tue, 04 Aug 2009 07:30:53 +0000

Ted, this is a very good post! Easy to understand and introduces a very helpful feature. Thank you for writing it.
Matthias

By: Matthias Bohlens Blog

Matthias Bohlens Blog — Tue, 04 Aug 2009 07:20:01 +0000

[...] Naleid hat einen guten Artikel über Unit-Testing mit Soft Assertions geschrieben. Von Matthias Bohlen, 4. August 2009, 08:19 [...]

By: Ted Naleid » Modularizing Groovy Config Files With a Dash of Meta-Programming

Fri, 31 Jul 2009 04:56:10 +0000

[...] is a continuation of a sporadic set of blog posts about some practical uses for groovy [...]

By: Kartik Shah

Kartik Shah — Wed, 01 Jul 2009 18:41:42 +0000

Extremely helpful. Thanks for writing this blog entry.

By: Hamlet D'Arcy

Hamlet D'Arcy — Fri, 26 Jun 2009 18:43:25 +0000

Very nice explanation of Closure owners!

By: Thomas

Thomas — Fri, 26 Jun 2009 06:33:35 +0000

Great hint!