我这里有一个小问题,真的不知道如何实现记录器消息的单元测试。当然,这听起来有点奇怪,但对我来说这是一个非常有趣的话题。但让我说得更具体一些。
我有一些 scala 类和测试规范:
class Testable extends Logging {
def method() = {
// some method calls
logger.info("Message1")
}
}
class TestableSpec extends Specification with ShouldMatchers with Mockito {
"Testable instance" should {
// some important tests
"print proper log message during method call" in {
// And how to test that logger really prints proper message ("Message1")?
}
}
}
我的第一个想法是拦截底层记录器引擎消息,但由于在 Testable 类中使用 mixin,实现起来似乎有点困难,因此任何执行此类操作的想法都会非常有帮助。
UPDATE:我最终进行了测试并决定与社区分享我的解决方案。我们不能直接模拟 scalalogging.Logger 类,因为它是最终的,但我们仍然可以模拟底层 slf4j Logger。澄清一个想法:
class Testable extends Logging {
def foo() = {
// ...
logger.info("Foo has been called")
}
}
// Another imports are omitted.
import com.typesafe.scalalogging.slf4j.Logger
import org.slf4j.{Logger => Underlying}
class TestableSpec extends Specification with Mockito with ShouldMatchers {
def initTestable(mocked: Underlying): Testable = {
new Testable() {
override lazy val logger = Logger(mocked)
}
}
"Testable instance" should {
"invoke logger with a proper message" in {
val mocked = mock[Underlying]
mocked.isInfoEnabled returns true // Should be set to true for test
initTestable(mocked).foo()
there was one(mocked).info("Foo has been called")
}
}
}
感谢埃里克的帮助。他的回答是解决问题的关键。
一种可能性是使用 Mockito 来检查方法调用:
class Testable extends Logging {
def method() = {
// some method calls
logger.info("Message1")
}
}
class TestableSpec extends Specification with ShouldMatchers with Mockito {
"Testable instance" should {
"print proper log message during method call" in {
val mockLogger = mock[Logger]
val testable = new Testable {
// switch the logger with a mock instance
override val logger = mockLogger
}
testable.method()
there was one(mockLogger).info("Message1")
}
}
}
这是主要思想,但您可能必须根据您的具体特征和日志框架进行调整:
- 记录器必须是可覆盖的
- info 方法不能是最终方法(Mockito 的限制之一)
本文内容由网友自发贡献,版权归原作者所有,本站不承担相应法律责任。如您发现有涉嫌抄袭侵权的内容,请联系:hwhale#tublm.com(使用前将#替换为@)