JUnit 4.4 Released

Posted by Ben Hughes on Jul 20, 2007

Sections

Process & Practices,

Development

Topics

Agile ,

Unit Testing ,

Java

Tags

JUnit

The new version of the unit testing suite JUnit has been released and is downloadable from Sourceforge. JUnit 4.4 has some noteable new features:

• assertThat – provides more readable (and flexible) tests using the value/matcher pattern (as introduced by the xMock frameworks), allowing for more readable error messages.

For example:

assertTrue(responseString.contains("color") || responseString.contains("colour"));
// ==> failure message:
// java.lang.AssertionError:

Becomes:

assertThat(responseString, anyOf(containsString("color"), containsString("colour")));
// ==> failure message:
// java.lang.AssertionError:
// Expected: (a string containing "color" or a string containing "colour")
// got: "Please choose a font"


You can read more about assertThat in Joe Walnes’s blog.


• Assumptions & Theories (via the assertThat method) enabling the test writer make assumptions in their tests about the environment they’re testing in, useful when testing against an entity outside of the domain of the test.

The latest release is available for download, as is the updated cookbook.

1. Back to top

   Nice

   by Sandeep Khurana

   Its nice. One question about assumptions, if assumptions are not met(e.g. file separator is not the one mentioned in assumption) then by default test will pass. Is there a to make the test fail..if assumptions are not met?

   Reply

2. Back to top

   Re: Nice

   by Alex Popescu

   Its nice. One question about assumptions, if assumptions are not met(e.g. file separator is not the one mentioned in assumption) then by default test will pass.

   
   If I am recalling correctly, this is the current behavior but may change in the next versions to ignored.
   If you want your test to fail, then you should use normal asserts and not assumptions.
   
   bests,
   ./alex
   --
   .w( the_mindstorm )p.
   ________________________
   Alexandru Popescu
   Senior Software Eng.
   InfoQ TechLead&CoFounder

   Reply

3. Back to top

   I don't know...

   by Joe Wolf

   I personally find the assertTrue code more readable than assertThat for the example provided, although the assertThat assertion failure message is much better.

   Reply

4. Back to top

   ass hat?

   by Jason Carreira

   I've probably been reading Hani's blog too long, 'cause assertThat looked like "ass hat" to me when I first looked...

   Reply

• Older >