{"id":2434,"date":"2016-09-19T13:25:11","date_gmt":"2016-09-19T12:25:11","guid":{"rendered":"https:\/\/davidkeen.com\/blog\/?p=2434"},"modified":"2025-10-23T10:12:28","modified_gmt":"2025-10-22T23:42:28","slug":"loading-test-data-with-scalatest-play","status":"publish","type":"post","link":"https:\/\/davidkeen.com\/blog\/2016\/09\/loading-test-data-with-scalatest-play\/","title":{"rendered":"Loading test data with ScalaTest + Play"},"content":{"rendered":"\n

The ScalaTest + Play<\/a> library provides a couple of useful traits for when your ScalaTest Play Framework functional tests need a running application for context. The OneAppPerSuite<\/span> trait will share the same Application<\/span> instance across all tests in a class whereas the OneAppPerTest<\/span> trait gives each test its own Application<\/span> instance.<\/p>\n\n\n\n

These traits will ensure you have a running application for your tests but if you want to test code that operates on a database it can be helpful to load some known test data before each test and clean it up afterwards. For this, we can mix in a ScalaTest before-and-after<\/a> trait.<\/p>\n\n\n\n

The BeforeAndAfter<\/span> trait lets you define a piece of code to run before each test with before<\/span> and\/or after each test with after<\/span>. There is also a BeforeAndAfterAll<\/span> trait which invokes methods before and after executing the suite but resetting the database for each test makes for better test isolation.<\/p>\n\n\n\n

Here is a base test class that sets up a running application and uses the Evolutions<\/span> companion object to load and clean up the database. Note this class uses Guice dependency injection to retrieve the database object but you can also easily connect to a database using the Database<\/span> companion object.<\/p>\n\n\n\n

We also override the db.default.url<\/span> config value to point to a test database.<\/p>\n\n\n\n

<\/circle><\/circle><\/circle><\/g><\/svg><\/span>