InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

"Literate Testing" for Readable JUnit Tests

Posted by Deborah Hartmann Preuss on Jun 15, 2006

Sections
Process & Practices,
Development
Topics
Java ,
Agile Techniques ,
Agile
Tags
Innovations ,
Testing
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 :-)
TestNG asserts are readable too by Alex Popescu Posted
  1. Back to top

    TestNG asserts are readable too

    by Alex Popescu

    TestNG has done a similar shift a long time ago. JUnit users were used with assertions in the form: assertEquals(expectedValue, computedValue [, reason]). We have considered that it is more readable (even if some of TestNG users considered it dangerous) as in assertEquals(computedValue, expectedValue [, reason]) with its English form: "assert that computedValue equals the expectedValue because reason". However, we still offer the JUnit assertion mode (see Assert and AssertJUnit).

    ./alex
    --
    .w( the_mindstorm )p.

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.