Page Object

Page Object

1. What is it?

   • Object oriented class that acts an as interface to a page of your AUT
   • Design pattern, popularly used in Test Automation

2. Why use it?

   • If UI changes, tests don't need to be changed; only the code within the page object
     • Example
       • If buttons on a page are relocated, automation tests will fail as test script won't be able to find element locators to perform tasks
         • So What?
           • Tester will need to examine the entire code to update all locators, which consumes time and leads to duplication
             • Solution
               • Page Object
                 • Saves time
                 • Increases code coverage
   • Enhances test maintenance and reduces code duplication
   • Advantages
     • Tests and element locators are kept separate "Separation of concerns"
       • Keeps code clean, organised and easy to maintain
     • Page Object Repository is independent of Automation tests
       • Can therefore be integrated with different frameworks such as Cucumber, JUnit, NUnit etc
     • Due to reusability of page object methods in POM classes, test cases become short and optimised
     • UI changes can be easily implemented, updated and maintained into Page objects and classes

Images and files in the map