Over a million developers have joined DZone.

{{announcement.body}}

{{announcement.title}}

Good Unit Test CheckList

DZone's Guide to

Good Unit Test CheckList

by

Jean-baptiste Rieu

·

Aug. 20, 11 · Java Zone ·

Free Resource

Like (0)

Comment (47)

Save

{{ articles[0].views | formatCount}} Views

Automist automates your software deliver experience. It's how modern teams deliver modern software.

Here are a few items I try to respect every time I write unit tests.

My test class is testing one and only one class
My methods are testing one and only one method at a time
My variables and methods names are explicit
My test cases are easy to read by human
My tests are also testing expected exception with @Test(expected=MyException.class)
My tests don’t need access to database
My tests don’t need access to network resources
My tests respect the usual clean code standards (lenght of lines, cyclomatic complexity,…)
My tests control side effects, limit values (max, min) and null variables (even if it throws an exception)
My tests can be run any time on any place without needing configuration
My tests are concrete (ex. dates are hardwired, not computed every time, strings too…)
My tests use mock to simulate/stub complex class structure or methods

I’m pretty sure there are more. Any ideas?

From http://jbrieu.info/leblog/2011/good-unit-test-checklist/

Get the open source Atomist Software Delivery Machine and start automating your delivery right there on your own laptop, today!

DOWNLOAD

Topics:

Like (0)

Comment (47)

Save

{{ articles[0].views | formatCount}} Views

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.linkDescription }}

{{ parent.urlSource.name }}

by {{ parent.authors[0].realName || parent.author}}

· {{ parent.articleDate | date:'MMM. dd, yyyy' }} {{ parent.linkDate | date:'MMM. dd, yyyy' }}

· {{ parent.portal.name }} Zone