mockito无法模拟hadoopMap器上下文

xurqigkl  于 2021-05-27  发布在  Hadoop
关注(0)|答案(1)|浏览(362)

所以我尝试使用mockito为hadoopMap函数创建一个单元测试。我已正确创建Map器类:

class XmlMapper extends Mapper[LongWritable, Text, Text, LongWritable] {

    override def map(key: LongWritable, value: Text, context: Mapper[LongWritable, Text, Text, LongWritable]#Context): Unit = {
        //does stuff
    }
}

然后我做了以下测试:

import org.apache.hadoop.io.{LongWritable, Text}
import org.scalatest.FlatSpec
import org.scalatest.mockito.MockitoSugar
import org.mockito.Mockito.verify
import org.mockito.Mockito.times

class XmlMapperTest extends FlatSpec with MockitoSugar {

    "XmlMapper" should "output" in {
        val mapper = new XmlMapper
        val context = mock[mapper.Context]
        //so far does nothing yet
    }
}

但我得到以下错误:

- should output***FAILED***
[info]   org.mockito.exceptions.base.MockitoException: Mockito cannot mock this class: class org.apache.hadoop.mapreduce.Mapper$Context.
[info]
[info] Mockito can only mock non-private & non-final classes.
[info] If you're not sure why you're getting this error, please report to the mailing list.

这没有意义,因为mapper.context是一个公共抽象类。
以下是总堆栈跟踪:

[info] Underlying exception : java.lang.UnsupportedOperationException: Cannot define class using reflection
[info]   at org.scalatest.mockito.MockitoSugar.mock(MockitoSugar.scala:73)
[info]   at org.scalatest.mockito.MockitoSugar.mock$(MockitoSugar.scala:72)
[info]   at XmlMapperTest.mock(XmlMapperTest.scala:7)
[info]   at XmlMapperTest.$anonfun$new$1(XmlMapperTest.scala:11)
[info]   at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.java:12)
[info]   at org.scalatest.OutcomeOf.outcomeOf(OutcomeOf.scala:85)
[info]   at org.scalatest.OutcomeOf.outcomeOf$(OutcomeOf.scala:83)
[info]   at org.scalatest.OutcomeOf$.outcomeOf(OutcomeOf.scala:104)
[info]   at org.scalatest.Transformer.apply(Transformer.scala:22)
[info]   at org.scalatest.Transformer.apply(Transformer.scala:20)
daolsyd0

daolsyd01#

看起来您使用的是旧版本的mockito内核,考虑到您使用的是scala,我强烈建议您使用最新版本的mockito scala
另外,只要可能,作为一个好的实践,你应该避免嘲笑你没有的类。更好的方法是将与第三方的交互封装在一个类(或一组类)中,并进行集成测试以证明它们按预期工作。
在系统的其余部分,您注入这些类,因此,为了进行测试,您模拟这些类,这允许您控制(并简化)公开的接口,并且在第三方lib的未来版本更改其api时将中断最小化。
有关更多详细信息,请查看这个stackoverflow答案和mockito博客上的这篇文章

相关问题