I have some code-under-test that calls on a Java logger to report its status. In the JUnit test code, I would like to verify that the correct log entry was made in this logger. Something along the following lines: methodUnderTest(bool x){ if(x) logger.info("x happened") } @Test tester(){ // perhaps setup a logger first. methodUnderTest(true); assertXXXXXX(loggedLevel(),Level.INFO); } I suppose tha
Log4Unit is a JUnit extension combining JUnit with Log4J. The intention is to create test protocols for JUnit. JUnit is asymmetrical in the sense that it focusses on the documentation of test failures and errors. Successful execution of a test case is not further documented. In order to obtain a test protocol that documents the initial settings, the test case execution and its results, a logging c
Bob -- Have you considered using an appender that doesn't write to any files but simply collects all messages for later analysis?Here's how: 1) Create an appender that simply stores all logging messages in a static array. This appender should also provide static methods to (a) retrieve all messages that were logged and (b) clear out the static message array. Something like this: package com.fwl; i
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
