如何为我的Scala Play2 CRUD应用程序设置内存测试数据库？

Question

I'm continuing my exploration of the Play framework and its related components. I used the template for CRUD application with a connection to a PostgreSQL database to begin with. It splits the application in models, repositories, controllers and views. This works well. Now, I'm trying to create some tests for this application with Specs2. More precisely, I'm trying to test the repository. It is defined as follow:

package dal
import javax.inject.{ Inject, Singleton }
import play.api.db.slick.DatabaseConfigProvider
import slick.driver.JdbcProfile

import models.Cat
import scala.concurrent.{ Future, ExecutionContext }

@Singleton
class CatRepository @Inject() (dbConfigProvider: DatabaseConfigProvider)(implicit ec: ExecutionContext) {
...
}

I would like to set an in memory database which would be created (schema, evolutions) before all tests, destroyed after all tests, populated (data, probably with direct SQL) and flushed around each test. I would like to pass it on to my repository instance which I would then use to perform my test. Like:

val repo = new CatRepository(inMem_DB)

So how do I go about: 1) creating this db and applying the evolutions? maybe:

trait TestDB extends BeforeAfterAll {
    var database: Option[Database] = None

    def before = {
        database = Some(Databases.inMemory(name = "test_db"))
        database match {
            case Some(con) => Evolutions.applyEvolutions(con)
            case _ => None
        }
        println("DB READY")
    }

    def after = {
        database match {
            case Some(con) => con.shutdown()
            case _ => None
        }
    }
}

Using a var and always making a "match/case" when I need to use the db isn't convenient. I guess there is a much better to do this...

2) Populate and flush around each test? Shall I create a trait extending Around, just as with BeforeAfterAll?

3) Create on of these play.api.db.slick.DatabaseConfigProvider from the database? Any link showing how to do this?

I found few examples which where covering this with running a FakeApplication, but I assume there is a way to pass somehow the db to such repository object outside of a running application..?

Thank you for helping. Cheers!

Answer 1

You can use a lazy val and AfterAll for the database setup/teardown, then BeforeAfterEach for each example:

trait TestDB extends AfterAll with BeforeAfterEach {
  lazy val database: Database = 
    Databases.inMemory(name = "test_db")

  def afterAll = 
    database.shutdown


  def before = 
    database.populate

  def after =
    datbase.clean
}