selenium page objects101

Page Objects101

Adam Goucher@adamgoucher

[email protected]

Wednesday, July 27, 2011

mailto:[email protected]

mailto:[email protected]

A language neutral pattern for representing a complete page

or portion of a page in an Object Oriented manner.


3 [Big] Reasons

1.Maintenance

2.Readability of Scripts

3.Separation of Concerns


Scripts & Page Objects


Page Objects


Locators

•A specific locator appears only once in your entire set of PO

•Locators do not cross PO boundaries


Elements

•Anything directly interacted with [via Selenium] is an Element

•Elements override Get/Set


Tip - Create common base classes for

Elements


Actions

•Repeated series of commands

•[Usually] Named with verbs

•[Often] Require Sync


Synchronization

• In Synchronization

•Out Synchronization

• ‘Flag’ driven


Tip - Create custom wait_for_* method in a

common base PO


1.Locator

2.Element Implementation

3.Add Element to Page Object

4.Actions

Order of Operations


Tip - Do NOT create the whole PO at once. Do ONLY what you

need now.


Asserts do not belong in PO


Scripts


Do not have synchronization code


Do not have driver API calls


Do have interactions with PO


Do have asserts


Technology