{"id":2712,"date":"2018-01-04T13:21:31","date_gmt":"2018-01-04T13:21:31","guid":{"rendered":"https:\/\/davidkeen.com\/blog\/?p=2712"},"modified":"2025-10-23T10:08:49","modified_gmt":"2025-10-22T23:38:49","slug":"loading-test-data-with-play-framework-evolutions","status":"publish","type":"post","link":"https:\/\/davidkeen.com\/blog\/2018\/01\/loading-test-data-with-play-framework-evolutions\/","title":{"rendered":"Loading test data with Play Framework Evolutions"},"content":{"rendered":"\n

In a previous article<\/a> I described how to load test data that your ScalaTest Play Framework functional tests might need using Play Framework’s Evolutions. This made use of the SimpleEvolutionsReader<\/span> class and defining evolutions in the test setup code.<\/p>\n\n\n\n

Recently I wanted to also load some test data from a file and so turned to the ClassLoaderEvolutionsReader<\/span> class which loads resources from the class path.<\/p>\n\n\n\n

The trouble was I wanted to apply the schema from my standard evolution files first and then load the test data. The ClassLoaderEvolutionsReader<\/span> requires evolutions revisions to start at 1 which would conflict with the standard application evolutions already applied.<\/p>\n\n\n\n

So I wrote a custom SingleRevisionClassLoaderEvolutionsReader<\/span> that reads a single revision from the class path.<\/p>\n\n\n\n

\n