Batch test case failures

[sebb <se...@gmail.com>]

The batch tests compare the output of the CSV and XML files to check
if the test has been successful.

This means that the listeners must be carefully configured to avoid
random test failures if the environment changes, e.g. different host
OS, Java version, external URLs.

The fewer the fields that are saved, the less likely there will be an
unexpected change.

However of course there need to be enough fields saved to ensure
changes in behaviour are detected.

The following fields cannot be saved, as they are bound to vary:
timestamps and elapsed times
byte counts if the target is not a fixed file

The following may cause issues:
Response message if derived from an Exception