Statistics show, that logging code take normally nearly 4% of the
application's code. To increase coverage and exclude side-effects from the
logging code it is useful to have unit tests running the compete logging code,
too. The MemoryLog class is especially designed for this purpose, since every
log entry can be retrieved later on as big list with each entry represented by
a bean. This makes it e.g. easy to test for thrown and logged exceptions.
Code for MemoryLog and MemoryLogTest attached, code borrows from SimpleLog.