[darcs-users] Improving tests

Mark Stosberg mark at summersault.com
Mon Mar 30 16:31:19 UTC 2009

> Lately there was a discussion on #darcs about improving the automated
> tests for darcs. I intend to do some work on this at the darcs hacking
> sprint next month, and I seek some input on what sort of improvement
> you'd like to see the 

My suggestion for improving the tests is to use the standard TAP output
format. The Perl tests used to do this. There are a number of tools
and additional automations that become possible or easy when this is

There is a library to help easily do this with shell scripts:

Darcs used to ship the flexible 'prove' utility, which is flexible test 
script execution tool. It allows you express things like:

- highlight the test failures with color
- Provide minimal output, except for failures. Give verbose output for
- Rerun just the tests which failed the last time we ran 'prove'.

TAP has also been ported to Haskell, so it could be used for the unit
tests as well:


The result could be that 'prove' is used as single test harness to drive
both the unit and functional tests with a consistent interface.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.osuosl.org/pipermail/darcs-users/attachments/20090330/7c28c064/attachment.pgp>

More information about the darcs-users mailing list