You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Henri Yandell (JIRA)" <ji...@apache.org> on 2006/05/17 08:11:10 UTC
[jira] Updated: (LOGGING-87) [logging] Add MemoryLog
[ http://issues.apache.org/jira/browse/LOGGING-87?page=all ]
Henri Yandell updated LOGGING-87:
---------------------------------
Reporter: Joerg Schaible (was: Jörg Schaible)
> [logging] Add MemoryLog
> -----------------------
>
> Key: LOGGING-87
> URL: http://issues.apache.org/jira/browse/LOGGING-87
> Project: Commons Logging
> Type: Improvement
> Versions: 1.0.4
> Environment: Operating System: All
> Platform: All
> Reporter: Joerg Schaible
> Priority: Minor
> Attachments: MemoryLog.java, MemoryLogTest.java
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org