Well, this Leiningen plugin started out as a little experiment, mostly just extracted from one of my closed-source projects, without a clear vision. At least, that's how I have up until now justified the fact that it does not have an automated test suite. It's clear at this point, though, that it will be worthwhile to create one. The feature set has grown a little, and people are using it in varying circumstances, and it's gotten to the point where it's fairly easy to break stuff when working on the plugin.
It strikes me that this is a fairly important prerequisite to a "1.0" release of the plugin. The test suite will a) ensure that the supported feature set works as expected and b) hopefully ferret out any bad design decisions while it's still easy to change them.
Add some subproject tests (Issue #70).
Add some basic config tests. Issue #70.
Add a single jar test (Issue #70).
Add some basic util tests (Issue #70).
Convert all tests to use Midje (Issue #70).
Add more jar tests (Issue #70).
Start adding command-line handling tests.
Add tests for REPL and test commands (Issue #70).
Add REPL (support) tests (Issue #70).
Write some final unit tests (Issue #70).
Woohoo, I finally finished writing a fairly comprehensive unit test suite. Later on I think I'll write some integration tests, but this is a big step forward as-is.