specs2

I found the following question/answer: Test MultipartFormData in Play 2.0 FakeRequest But it seems things have changed in Play 2.1. I've tried adapting the example like so: "Application" should { "Upload Photo" in { running(FakeApplication()) { val data = new MultipartFormData(Map(), List( FilePart("qqfile", "message", Some("Content-Type: multipart/form-data"), TemporaryFile(getClass().getResource("/test/photos/DSC03024.JPG").getFile())) ), List()) val Some(result) = routeAndCall(FakeRequest(POST, "/admin/photo/upload", FakeHeaders(), data)) status(result) must equalTo(CREATED) headers(result)

I want to write some integration tests for a service that runs slick and then clean a postgresql database up afterward up by rolling back a transaction, but I don't see a way to do it. I understand that I can test DBIO objects which have been composed together and roll them back, but it doesn't look like it's possible if I want to test at a higher level of abstraction. In pseudocode, I want to do this: StartDbTransaction() // setup DoSomethingInDB() AssertSomething() RollBackDbTransaction() // teardown For example, if I have this (simplified from the play-silhouette-slick-seed ): class

I am trying to learn the unit tests in Play scala, but I am running into some issues. I am trying to run several tests on my models layer like this: "User Model" should { "be created and retrieved by username" in { running(FakeApplication()) { val newUser = User(username = "weezybizzle",password = "password") User.save(newUser) User.findOneByUsername("weezybizzle") must beSome } } "another test" in { running(FakeApplication()) { // more tests involving adding and removing users } } } However when doing things this way, I fail to connect to the database on the second unit test, saying that the

Play 2.4 app, using dependency injection for service classes. I found that Specs2 chokes when a service class being tested has more than one injected dependency. It fails with " Can't find a constructor for class ... " $ test-only services.ReportServiceSpec [error] Can't find a constructor for class services.ReportService [error] Error: Total 1, Failed 0, Errors 1, Passed 0 [error] Error during tests: [error] services.ReportServiceSpec [error] (test:testOnly) sbt.TestsFailedException: Tests unsuccessful [error] Total time: 2 s, completed Dec 8, 2015 5:24:34 PM Production code , stripped to

By default all Logger output, visible when an application is running, is mute when the application is tested. How to force the debugs, infos etc. to be shown in the specs2 reports? First off, you may like some background why logging is disabled in test mode. This was Guillame Bort's answer to a question in the play forum (see this thread ): The logger is disabled in test mode for now because it was causing an huge PermGen space leak when running tests. But we are working to run tests in a forked JVM so we will enable it again soon. As a workaround, I created my own logger like this (Scala code