Skip to content
June 12, 2013 / selenium34

PageObjects

As I’ve sat through many presentations here at the selenium conference this week it is quite apparent where the community is heading, and that’s mobile. This should be of no surprise to you.

What that means is that we need new abstractions for our Page Objects. We likely need many concrete instances of these Page Objects now. One for Android, one for ios, and another for our desktop sites.

The market will have a lot to decide upon. ios-driver 0.7 looks to bring the ability to run on a native device. Appium looks to allow you to run against native and hybrid ios / android applications.

Have you noticed anything exciting in the space which allows for abstracting away the need for multiple page objects?

Advertisements

2 Comments

Leave a Comment
  1. autumnator / Jun 18 2013 11:10 pm

    > Have you noticed anything exciting in the space which allows for abstracting away the need for multiple page objects?

    Did you come upon anything in this area?

    Also, would be interesting to see if one can apply a “base” page object that applies across mobile & desktop. Maybe you then extend from base a generic mobile (platform generic) page object to (platform then UI flow) specific mobile page objects and same with desktop ones.

    • selenium34 / Jun 19 2013 6:08 pm

      We haven’t currently implemented any mobile testing, but it is high on my wish list to get some automation running on the both mobile platforms — sorry windows phone / blackberry…

      I assume that will pretty much be the standard procedure, moving page object methods out to interfaces, then perhaps some base classes implementing what they can of the functionality — my worry is that would mean our platform specific pages would likely need to implement getters on the WebElements themselves to handle some of the functionality, which I certainly do not like.

      Let’s think of a login form. On the web page it might be located with standard IDs, on the iPhone we might have a hybrid app. We can’t necessarily reuse those locators, and our login function would need to access the webelements to send the keys. I’m not really a big fan of that.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: