对 SLF4J 日志消息进行单元测试的最佳方法是什么?
我正在使用 slf4j,我想对我的代码进行单元测试,以确保在某些条件下生成警告/错误日志消息。我宁愿这些是严格的单元测试,所以我不希望必须从文件中提取日志配置来测试是否生成日志消息。我使用的模拟框架是 Mockito。
I'm using slf4j and I want to unit test my code to make sure that warn/error log messages are generated under certain conditions. I'd rather these be strict unit tests, so I'd prefer not to have to pull up logging configuration from a file in order to test that the log messages are generated. The mocking framework I'm using is Mockito.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(19)
与@Zsolt类似,您可以模拟log4j
Appender
并将其设置在Logger
上,然后验证对Appender.doAppend()
的调用。这使您无需修改实际代码即可进行测试。Similar to @Zsolt, you can mock log4j
Appender
and set it on theLogger
, then verify calls toAppender.doAppend()
. This allows you to test without having to modify the real code.您可以尝试另一个库来支持简单的模拟 slf4j 记录器 - slf4j-mock,您的代码 cen看起来像:
如您所见,在测试代码中不需要任何特殊步骤。您只需要在项目中添加对库的依赖关系。
更多示例和说明请访问:
https://www.simplify4u.org/slf4j-mock/
You can try another library to support easy mocking slf4j loggers - slf4j-mock, your code cen be look as:
As you see you don't need any special steps, in test code. You need only add dependency to library in your project.
More examples and instructions at:
https://www.simplify4u.org/slf4j-mock/
这是我的实现(Java 11+,Junit 5,在 ClassWithALogger 中使用 Lombok 的 @Slf4j),我的要求是在测试之间重置记录器。
This is my implementation (Java 11+, Junit 5, using Lombok's @Slf4j in the ClassWithALogger), my requirements being for the logger to be reset between tests.
只需使用普通的 Mockito 和一些反射逻辑来模拟它:
使用 setFinalStatic 方法 beeing
然后只需执行要测试的代码并验证 - 例如,以下验证 Logger.warn 方法被调用了两次:
请注意,通过反射设置最终字段并非在所有情况下都有效。例如,如果多个测试用例试图修改它,我就无法让它工作。
Just use plain Mockito and some reflection logic to mock it:
with setFinalStatic method beeing
Then just execute the to be tested code and verify - e.g. the following verifies that the Logger.warn method was called twice:
Please note that setting the final fields via reflection does not work in all cases. I was for example not able to get it working if multiple testcases were trying to modify it.
我需要在不使用 ch.qos.logback 的情况下让它工作,因为这与我的主类中 log4j2 的使用相冲突。
向 https://codingcraftsman 致敬。 wordpress.com/2015/04/28/log4j2-mocking-with-mockito-and-junit/ 展示如何做到这一点。
对我来说改变的事情是将模拟中的记录器从 org.apache.logging.log4j.core.Logger 转换为记录器,我能够向它添加一个附加程序,但它没有不要破坏我的其余代码。
将他的代码粘贴到此处以保证答案的完整性。
I needed to get this to work without using
ch.qos.logback
because that was conflicting with the usage of log4j2 in my main classes.Hat tip to https://codingcraftsman.wordpress.com/2015/04/28/log4j2-mocking-with-mockito-and-junit/ for showing how to do it.
The thing that made a difference for me was casting the logger in the mocks to the logger from
org.apache.logging.log4j.core.Logger
, I was able to add an appender to it and it didn't break the rest of my code.Pasting his code here for answer completeness.
我创建了一个库来帮助单元测试断言某些消息是否记录在各种日志级别。
https://github.com/nalbion/test-appender
I've created a library to help unit tests to assert that certain messages are/not logged at various log levels.
https://github.com/nalbion/test-appender
我有一个新答案,我将在这篇文章的顶部发布(我的“旧”答案仍然在这篇文章的底部)(在撰写本文时,我的“旧”答案是“0”,所以没有坏处,没有犯规!)
新答案:
这是 Gradle 包:
Maven 链接:
https://mvnrepository .com/artifact/com.portingle/slf4jtesting
Germane 代码:(
下面的导入和私有方法将进入 MyTestClass(.java))
================== ===========下面的旧答案..请勿使用===============
下面是我之前的答案。我更改了下面的代码...在我发现它之后使用上面的包(上面的包)。
然后在我的单元测试中,我可以做以下两件事之一:
或与上面类似,但对自定义 Logger 进行强制转换
对代码持保留态度,想法就在那里。我没有编译代码。
I have a new answer that I will post at the top in this post (My "old" answer is still at the bottom of this post) (At the time of writing my "old" answer was a "0", so no harm, no foul! )
Newer answer:
Here is the Gradle Package:
Maven Link:
https://mvnrepository.com/artifact/com.portingle/slf4jtesting
Germane Code:
(below imports and private method would go in MyTestClass(.java))
============================= OLD ANSWER BELOW .. DO NOT USE================
Below is my previous answer. I changed my below code ... to use the above package after I discovered it (the above package).
Then in my unit tests, I can do one of two things:
or similar to the above, but do a cast on the custom Logger
Take the code with a grain of salt, the ideas are there. I didn't compile the code.
我专门为此用例创建了 LogCaptor ,它应该能够轻松捕获日志,而无需例如,需要嘲笑。它可以捕获由 SLF4J、Log4J2、Java Util Logging、JBoss Logging、Google Flogger 生成的日志以及带有 Lombok 注释的日志。请参阅下面的单元测试示例代码片段:
示例情况:
使用 LogCaptor 的示例单元测试:
我不太确定是否应该在此处发布此内容,因为它也可以被视为推广“我的库”的一种方式“但我认为这对于面临同样挑战的开发人员可能会有所帮助。
I have created LogCaptor specifically for this use case, which should do the trick of easily capturing logs without the need for mocking for example. It can capture logs generated by SLF4J, Log4J2, Java Util Logging, JBoss Logging, Google Flogger and with Lombok annotations. See below for an example code snippet with the unit test:
Example situation:
Example unit test with usage of LogCaptor:
I wasn't quite sure if I should post this here, because it could also be seen as a way to promote "my library" but I thought it could be helpful for developers who have the same challenges.
我知道这个问题发布已经有一段时间了,但我刚刚遇到了类似的问题,我的解决方案可能会有所帮助。按照 @Zsolt 提出的解决方案,我们使用附加程序,更具体地说是 Logback 的
ListAppender
。此处显示代码和配置(Groovy 代码,但可以轻松移植到 Java):用于日志访问的 Groovy 类:
示例 logback.xml 配置:
测试:
我在带有 Groovy+Spock 的 SpringBoot 项目中使用它,尽管我看不到为什么这在任何使用 Logback 的 Java 项目中都不起作用。
I know it's been a while since this question was posted but I just came across a similar issue and my solution may help. Along the lines of the solution proposed by @Zsolt, we use an appender, more specifically Logback's
ListAppender
. Showing the code and configurations here (Groovy code but can be easily ported to Java):Groovy class for log access:
Sample logback.xml config:
Test:
I use this in a SpringBoot project with Groovy+Spock, though I can't see why this wouldn't work in any Java project with Logback.
我尝试使用 slf4j-test,但发现在 eclipse 中运行测试时,我在类路径上有几个 slf4j 的实现,阻止了 slf4j-test。他们的文档(https://www.slf4j.org/codes.html#multiple_bindings )建议一些 Maven 配置,可以在通过 Maven 运行测试时整理测试类路径,但这在通过 Eclipse 运行测试时对我没有帮助。
最后,我实现了自己的 LogAppender(由 StringBuffer 支持),将其附加到我的 slf4j 记录器(由 logback 提供),并能够编写我的测试。
I tried using slf4j-test, but found, when running the test in eclipse, that I had several implementations of slf4j on the classpath, blocking slf4j-test. Their documentation (https://www.slf4j.org/codes.html#multiple_bindings) suggests some maven config that would sort out the test classpath when running tests via maven, but this didn't help me when running tests via eclipse.
In the end I implemented my own LogAppender (backed by a StringBuffer), attached that to my slf4j logger (provided by logback), and was able to write my test.
slf4j 使用三个流,System.out、System.err 和文件,
在此代码中我仅测试 System.err printStream 使用:
System.out 也是可能的..
slf4j use three stream, System.out, System.err, and file
in this code i test only System.err printStream use:
it possible for System.out too..
创建测试规则:
然后使用它:
----- JUnit 5 with Extension Oct 2021 -----
LogCapture:
LogCaptureExtension:
然后使用它:
Create a test rule:
Then use it:
----- JUnit 5 with Extension Oct 2021 -----
LogCapture:
LogCaptureExtension:
then use it:
要在不依赖特定实现(例如 log4j)的情况下测试 slf4j,您可以提供自己的 slf4j 日志记录实现,如 此 SLF4J 常见问题解答。您的实现可以记录已记录的消息,然后由单元测试询问以进行验证。
slf4j-test 包正是这样做的。它是一个内存中 slf4j 日志记录实现,提供检索记录消息的方法。
For testing slf4j without relying on a specific implementation (such as log4j), you can provide your own slf4j logging implementation as described in this SLF4J FAQ. Your implementation can record the messages that were logged and then be interrogated by your unit tests for validation.
The slf4j-test package does exactly this. It's an in-memory slf4j logging implementation that provides methods for retrieving logged messages.
对于 JUnit 5,创建一个扩展来实现上面 andrew-feng 提供的解决方案://stackoverflow.com/a/50868216/5468311">创建测试规则:
然后使用它:
For JUnit 5, create an extension that implements the solution provided by andrew-feng above in Create a test rule:
Then use it:
我认为您可以使用自定义附加程序来解决您的问题。创建一个实现
org.apache.log4j.Appender
的测试附加程序,并在log4j.properties
中设置附加程序,并在执行测试用例时加载它。如果您从该
appender
回调测试工具,您可以检查记录的消息I think you could solve your problem with a custom appender. Create a test appender which implements the
org.apache.log4j.Appender
, and set your appender in thelog4j.properties
and load it when you execute test cases.If you call back to the test harness from that
appender
you can check the logged messagesSLF4J 的一个更好的测试实现是 https://github.com/portingle,它在并发测试执行的环境中运行得非常好/slf4jtesting
我插话了一些关于 slf4j 日志测试和现有测试方法在并发测试执行方面的局限性的讨论。
我决定将我的话写进代码中,结果就是 git repo。
A better test implementation of SLF4J that works really well in an environment with concurrent test execution is https://github.com/portingle/slf4jtesting
I've chimed in on a few discussion on slf4j log testing and the limitations of existing test approaches when it comes to concurrent test execution.
I decided to put my words into code and that git repo is the result.
您可以将您需要测试的重要日志记录调用放在它们自己的方法中,而不是模拟 SLF4J,您可以更轻松地模拟这些方法。
如果您确实想模拟 SLF4J,我敢打赌您可以为其创建自己的提供程序,该提供程序将允许您从 SLF4J 端提供模拟记录器,而不是在服务对象中注入一个记录器。
Instead of mocking SLF4J you could place the important logging calls you need to test inside their own methods which you can mock more easily.
If you really want to mock SLF4J, I would bet you could create your own provider for it that would allow you to supply a mock logger from the SLF4J side instead of injecting one in your service objects.
使用 slf4j-test 可以删除上面讨论的许多解决方法
pom.xml
示例类
TestClass
请参阅 http:// /projects.lidalia.org.uk/slf4j-test/ 了解更多详情
Using slf4j-test can remove lot of workarounds discussed above
pom.xml
Sample class
TestClass
Refer http://projects.lidalia.org.uk/slf4j-test/ for more details
这个解决方案已经在这个绝妙答案以及这个评论,但因为我不认为它本身是答案,将其添加到此处作为社区 wiki 答案。
所以使用 logback listappender 的 JUnit5 解决方案:
This solution has been mentioned already before in this groovy answer as well as in this comment, but as I don't see it as an answer itself, adding it here as a community wiki answer.
So JUnit5 solution using logback listappender: