Page Object Model/Page Factory VS. User Interface Mapping

Page Object Model

Id	Detail
Define	A page object is an object-oriented class that serves as an interface to a page of your AUT. The tests then use the methods of this page object class whenever they need to interact with the UI of that page. Page Object Model is a design pattern to create Object Repository for web UI elements Each web page in the application should have corresponding page class 3.  Page class will find the WebElements of that page and also contain Page methods which perform operations on those WebElements
Advantages	The Page Object Design Pattern provides the following advantages 1. There is a clean separation between test code and page specific code such as locators (or their use if you’re using a UI Map) and layout. 2. There is a single repository for the services or operations offered by the page rather than having these services scattered throughout the tests.
Basic Rules	There are a few basic rules for getting the desired maintainability of your test code: Page objects themselves should never make verifications or assertions A page object does not necessarily need to represent an entire page. The Page Object design pattern could be used to represent components on a page. If a page in the AUT has multiple components, it may improve maintainability if there is a separate page object for each component.

 User Interface Mapping

Id	Detail
Define	A User Interface (UI) Map is a mechanism that stores all the locators for a test suite in one place for easy modification when identifiers or paths to UI elements change in the application under test (AUT).
Advantages	To summarize, a UI Map has two significant advantages Using a centralized location for UI objects instead of having them scattered throughout the script. This makes script maintenance more efficient. Cryptic HTML Identifiers and names can be given more human-readable names improving the readability of test scripts.

 Page Factory

Id

Detail

Define

Page Factory is an inbuilt Page Object Model concept for Selenium WebDriver which is very optimized Separation of Page Object Repository and Test Methods Page Factory Class provide @FindBy annotation to find WebElemnts @FindBy can accept tagName, partinalLinkText, name, LinkText, id, css, className & xpath as attributes     @FindBy(how = How.CSS, using = "input[id='submit.button']")     WebElement loginLocator;         public Login() {         PageFactory.initElements(this.driver, this);     }