see texttest (www.texttest.org, described in chapter 10 of my book),
which is a full acceptance testing framework designed around analysing
log entries.

--
gojko adzic
http://gojko.net

Tomas Pollak wrote:
>
>
>
> Hello all,
>
> I'm working on an agile project and we have been writing acceptance
> tests for every story so far.
> We are using Log4J for logging, and so far the developers have been
> using it at their own will. But recently some problem that wasn't logged
> correctly has raised our customer's awareness on this, and he included a
> story for the next sprint saying that we should define some logging
> criteria to prevent these problems in the future, and apply it uniformly
> throughout the code.
>
> My question is: how do you write acceptance tests for such a
> requirement? Our goal is that whatever tests we write on this sprint
> will also be useful as the code continues to evolve and more features
> (and their logging) are added.
> Do you have some experience where you tested that the logging was
> correct that you can share? Any useful links?
>
> Thanks,
> Tomás
>
>