如何在Play2上使用OpenId对应用程序进行功能测试？

Question

Let's say the app is protected with OpenId login (and only OpenId). Once the user has successfully authenticated via OpenId, I set an attribute in the session like this :

 Redirect(routes.Application.index).withSession('email -> userinfo.email)

Now, since a lot of the apps functionality relies on Javascript, the tests must be run on Selenium/Fluentlenium. How can I fake a connected user in my tests?

EDIT : As answered below, creating a user in the OpenId provider is not really an answer for two reasons:

1. The OpenID provider is Google and Google only.
2. I do not want to test if Google's OpenId is working as they probably test it way better than I ever could, I want to test the functionality of my app.

I would rather like to fake a connected user by manually setting the email attribute in session in fluentlenium but I have found no API to do this.

Answer 1

We have done this by extracting the OpenId integration into a trait which has got a real implementation (google) and a dummy one, in our case with a hardcoded user that gets logged in, this has also been useful to be able to use the app in devel mode without actually having to log in for real.

The actual trait is as simple as this:

sealed trait AuthLogic {
  def login: Action[AnyContent]
  def callback: Action[AnyContent]
}

Which is then implemented by the google one and the dummy, the actual instance used is decided upon first access (lazy val) by a configuration flag. All the dummy one does is redirect directly from login to callback, and then faking a login inside the callback implementation.

Hope this helped!

Answer 2

Why don't you create test account in OpenId supplier and use its username/password in your selenium scripts?

Testing in selenium/Fluentlenium concludes that your application is quite integrated (OpenID is setup as you mentioned, I suspect that DB is connected as well).

Answer 3

I've never used fluentlenium, but I assume you have access to the underlying selenium webdriver? If so, can't you just set a cookie? You'll just need to save a valid, signed session cookie.

http://docs.seleniumhq.org/docs/03_webdriver.jsp#cookies