Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage News "Literate Testing" for Readable JUnit Tests

"Literate Testing" for Readable JUnit Tests

Brian Marick, a frequent writer on Agile software testing, has reported that Robert Chatley and Tom White are working on sentence style for testing in Java, to make tests easier to understand. They call it "Literate Testing".

One thing their teams like is the idea of constraints: now they always use the org.jmock.MockObjectTestCase base class rather than junit.framework.TestCase, even when they aren't mocking anything out!  Here's an example from Tom White:
We can use constraints to construct more flexible assertions:
assertThat(a, eq("3"));

is more readable and understandable than:
assertEquals("3", a);

You can read it as "assert that a eq(uals) 3".
In a subsequent entry, White introduces the concept of anaphor, a word used to avoid repetition. When judiciously used, in a situation where there is no ambiguity to obscure the reference, it can increase test readability.

Small tricks like changing IDE settings are also used increase readability.

Robert Chatley has recently taken the idea of literate testing further and applied it to functional (acceptance) tests.

And now, we've come full circle:  Chatley tells us that Marick is in the sentence structure game, now, too :-)

Rate this Article