WithBrowser class doesn't have a parameter with name 'browser' but it has a parameter with name 'webDriver' Ref Link: https://github.com/playframework/playframework/blob/2.1.x/framework/src/play-test/src/main/scala/play/api/test/Specs.scala
Added some text to show tailing of a heroku log; added commentary to clarify that Procfile is not actually required by Heroku. There is another point on Heroku involving setting the build pack (see http://stackoverflow.com/questions/11510256/deploy-a-play-2-0-2-application-on-heroku): heroku config:add BUILDPACK_URL=https://github.com/heroku/heroku-buildpack-scala.git --app <app name here> ...but I am not sure this is required in all scenarios.
Issue #1356 reports spurious NPEs when the maximum length is exceeded in a request body. This is fixed in Play 2.2, but the fix was a significant refactor, not suitable for 2.1.x. This commit changes the error handling for the NPE so that it logs at debug level.
* The deadlock was caused by Play closing Netty connections twice. Usually Netty silently handles this invalid usage, but HTTPS connections can deadlock when closed twice, due to a race in Netty's SslHandler.closeOutboundAndChannel method. * Added tests to verify Play's interactions with Netty. We can now do cool things like simulate failure to send a response and check that connections are still closed properly. Most importantly though, we can check that close is only called once. This is very difficult to test usually because Netty either ignores the second close or occasionally - and only when using an HTTPS connection - deadlocks on the second close.