Databases
StackOverflow2013
Postsdbo
POPlay 2.1 Unit Test With Slick and Postgres
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPlay 2.1 Unit Test With Slick and Postgres
    primarykey
    data
    text
    <p>I want to run unit tests for a Play 2 Scala app using the same database setup as used in production: Slick with Postgres. The following fails with "java.sql.SQLException: Attempting to obtain a connection from a pool that has already been shutdown." on the 2nd test.</p> <pre><code>package controllers import org.specs2.mutable._ import play.api.db.DB import play.api.Play.current import play.api.test._ import play.api.test.Helpers._ import scala.slick.driver.PostgresDriver.simple._ class BogusTest extends Specification { def postgresDatabase(name: String = "default", options: Map[String, String] = Map.empty): Map[String, String] = Map( "db.test.driver" -&gt; "org.postgresql.Driver", "db.test.user" -&gt; "postgres", "db.test.password" -&gt; "blah", "db.test.url" -&gt; "jdbc:postgresql://localhost/blah" ) def fakeApp[T](block: =&gt; T): T = running(FakeApplication(additionalConfiguration = postgresDatabase("test") ++ Map("evolutionplugin" -&gt; "disabled"))) { def database = Database.forDataSource(DB.getDataSource("test")) database.withSession { implicit s: Session =&gt; block } } "Fire 1" should { "do something" in fakeApp { success } } "Fire 2" should { "do something else" in fakeApp { success } } } </code></pre> <p>I run the test like this:</p> <pre><code>$ play -Dconfig.file=`pwd`/conf/dev.conf "test-only controllers.BogusTest" </code></pre> <p>Two other mysteries: </p> <p>1) All tests run, even though I ask for just BogusTest to run</p> <p>2) application.conf is always used, not def.conf, and the driver information comes from application.conf, not the info configured in the code.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMeredith
    1. USMike Slinn
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POPlay 2.1 Unit Test With Slick and Postgres
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POPlay 2.1 Unit Test With Slick and Postgres
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POPlay 2.1 Unit Test With Slick and Postgres
      1. USMeredith
      1. VTFavorite
    1. COSee http://stackoverflow.com/questions/15399161/how-do-i-specify-a-config-file-with-sbt-0-12-2-for-sbt-test for info on how to specify a different config file with `test`.
      singulars
      1. POPlay 2.1 Unit Test With Slick and Postgres
      1. USJames Ward
    2. COThanks, looks like this should take care of mystery #2. Can you shed light on the main issue as well?
      singulars
      1. POPlay 2.1 Unit Test With Slick and Postgres
      1. USMike Slinn
    3. COI'm running into the same issue too. Even without using the Around trait from specs2, and simply wrapping within `in{ running(fakeApp) {Database.forDataSource(DB.getDataSource()) withSession {}} }` gives this exception too.
      singulars
      1. POPlay 2.1 Unit Test With Slick and Postgres
      1. USMeredith
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload