我们的应用程序基于 Play 2.4与Scala 2.11和Akka 。 使用的数据库是 MySQL 。
在我们的应用程序中大量使用缓存。我们使用 Play默认的EhCache 进行缓存。
我们的示例代码段:
import play.api.Play.current
import play.api.cache.Cache
case class Sample(var id: Option[String],
//.. other fields
)
class SampleTable(tag: Tag)
extends Table[Sample](tag, "SAMPLE") {
def id = column[Option[String]]("id", O.PrimaryKey)
// .. other field defs
}
object SampleDAO extends TableQuery(new SampleTable(_)) with SQLWrapper {
def get(id: String) : Future[Sample] = {
val cacheKey = // our code to generate a unique cache key
Cache.getOrElse[Future[[Sample]](cacheKey) {
db.run(this.filter(_.id === id).result.headOption)
}
}
}
我们使用Play的内置 Specs2 进行测试。
var id = "6879a389-aa3c-4074-9929-cca324c7a01f"
"Sample Application " should {
"Get a Sample" in new WithApplication {
val req = FakeRequest(GET, s"/v1/samples/$id")
val result = route(req).get
assertEquals(OK, status(result))
id = (contentAsJson(result).\("id")).get.toString().replaceAllLiterally("\"", "")
}
但是我们进行单元测试时经常遇到以下错误。
[error] 1) Error in custom provider, java.lang.IllegalStateException: The CacheManager has been shut down. It can no longer b
e used.
[error] at play.api.cache.EhCacheModule.play$api$cache$EhCacheModule$$bindCache$1(Cache.scala:181):
[error] Binding(interface net.sf.ehcache.Ehcache qualified with QualifierInstance(@play.cache.NamedCache(value=play)) to Prov
iderTarget(play.api.cache.NamedEhCacheProvider@7c8b0968)) (via modules: com.google.inject.util.Modules$OverrideModule -> play.ap
i.inject.guice.GuiceableModuleConversions$$anon$1)
[error] while locating net.sf.ehcache.Ehcache annotated with @play.cache.NamedCache(value=play)
[error] at play.api.cache.EhCacheModule.play$api$cache$EhCacheModule$$bindCache$1(Cache.scala:182):
[error] Binding(interface play.api.cache.CacheApi qualified with QualifierInstance(@play.cache.NamedCache(value=play)) to Pro
viderTarget(play.api.cache.NamedCacheApiProvider@38514c74)) (via modules: com.google.inject.util.Modules$OverrideModule -> play.
api.inject.guice.GuiceableModuleConversions$$anon$1)
[error] while locating play.api.cache.CacheApi annotated with @play.cache.NamedCache(value=play)
[error] while locating play.api.cache.CacheApi
[error]
[error] 1 error (InjectorImpl.java:1025)
[error] com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1025)
[error] com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1051)
[error] play.api.inject.guice.GuiceInjector.instanceOf(GuiceInjectorBuilder.scala:321)
[error] play.api.inject.guice.GuiceInjector.instanceOf(GuiceInjectorBuilder.scala:316)
[error] play.api.Application$$anonfun$instanceCache$1.apply(Application.scala:234)
[error] play.api.Application$$anonfun$instanceCache$1.apply(Application.scala:234)
[error] play.utils.InlineCache.fresh(InlineCache.scala:69)
[error] play.utils.InlineCache.apply(InlineCache.scala:62)
[error] play.api.cache.Cache$.cacheApi(Cache.scala:63)
[error] play.api.cache.Cache$.getOrElse(Cache.scala:106
我们期待帮助解决上述问题或专门为测试实施模拟缓存的方法。
先谢谢。
答案 0 :(得分:5)
I had a similar issue, so I stubbed out a cache implementation and swapped it in for the tests.
class FakeCache extends CacheApi {
override def set(key: String, value: Any, expiration: Duration): Unit = {}
override def get[T](key: String)(implicit evidence$2: ClassManifest[T]): Option[T] = None
override def getOrElse[A](key: String, expiration: Duration)(orElse: => A)(implicit evidence$1: ClassManifest[A]): A = orElse
override def remove(key: String): Unit = {}
}
Override the injection:
class AbstractViewTest extends PlaySpecification {
def testApp(handler: DeadboltHandler): Application = new GuiceApplicationBuilder()
.overrides(bind[CacheApi].to[FakeCache])
.in(Mode.Test)
.build()
}
You can see how I use this on GitHub: https://github.com/schaloner/deadbolt-2-scala/blob/master/code/test/be/objectify/deadbolt/scala/views/AbstractViewTest.scala
答案 1 :(得分:3)
另一种解决方案是在每次测试开始时调用sequential
方法。
class MySpec extends Specification {
sequential
...
}
注意强>
parallelExecution in Test := false
也应在build.sbt
文件中设置。
答案 2 :(得分:1)
我认为通过伪造缓存绕过缓存测试是一种不好的做法。它使您的测试无效,所有这些都是因为您试图不以可扩展和分布式方式使用EhCache。更好的方法是实现@Singleton接口,详见此处:https://stackoverflow.com/a/31835029/5736587