Google Groups

Re: 2.0.2 breakage of integration tests (using play.api.libs.ws.WS)?


peter hausel Jun 26, 2012 7:20 PM
Posted in group: play-framework
That error usually happens if the functional test runner could not create the NettyServer instance. 

Can you check if there is any other play app running in the background on the same localhost port?
Can you check if the app is working in the dev mode after upgrading to 2.0.2?

Thanks,
Peter

On Tuesday, June 26, 2012 8:46:42 PM UTC-4, scott clasen wrote:
Hey All-

   I have a play app that has an integration test that is usually run via 'play test-only *Integration*' 

This uses play WS to talk to a rest api of a running play app. Worked just fine till upgrading to 2.0.2 today

Now when running this spec, I get blood on the screen, no play app started.

[error]     RuntimeException: There is no started application (Play.scala:44)
[error] play.api.Play$$anonfun$current$1.apply(Play.scala:44)
[error] play.api.Play$$anonfun$current$1.apply(Play.scala:44)
[error] play.api.Play$.current(Play.scala:44)
[error] play.api.libs.ws.WS$.client(WS.scala:43)
[error] play.api.libs.ws.WS$WSRequest.execute(WS.scala:119)
[error] play.api.libs.ws.WS$WSRequestHolder.get(WS.scala:300)


[error]     RuntimeException: There is no started application (Play.scala:44)
[error] play.api.Play$$anonfun$current$1.apply(Play.scala:44)
[error] play.api.Play$$anonfun$current$1.apply(Play.scala:44)
[error] play.api.Play$.current(Play.scala:44)
[error] play.api.libs.ws.WS$.client(WS.scala:43)

Was there a change in 2.0.2 that would cause this breakage? How to work around?