Appium and Page Object Model

There are several advantages to using the Page Object Model design pattern.

• Improves code maintenance: All locators for a specific flow are grouped together in a specific POM. If a page or application changes its UI, you no longer need to modify all your tests scattered with locators. Simply change it in the page object model.
• Encourages code reuse: There is no need to write the same logic across different tests. For example, no need to keep doing the same log in flow if your test requires a logged-in state. Keep all logic for a specific page or action in its own POM file.
• Improves code readability: You can find where specific test code is located more easily. If a specific change is required, you can do it in the appropriate file. You no longer need to modify several files for a change in one specific test logic.

A good example of a Page Object Model would be the Login Page Object.
This will be responsible for typing in the username and password, and proceeding with the actual login.
Other test cases can use this POM when a logged-in state is required.

This is an example of a Login Page Object Model. The login method will be responsible for several things. It will hide the soft keyboard, type in a username, a password and submit.

This is logic that may be used by several other test cases that require a logged in state.

Of course, you can implement Page Object Model in any programming language; Java, Kotlin, Swift, ...

You can use Selenium's PageFactory class with Appium and POM.
The PageFactory class can be used with initElements to initialize all elements located by the @FindBy (or AndroidFindBy) annotation.
PageFactory will automatically assign the elements to your Page Object Model.

package com.testingbot.example;
import io.appium.java_client.MobileBy;
import io.appium.java_client.android.AndroidDriver;
import io.appium.java_client.android.AndroidElement;
import io.appium.java_client.android.AndroidKeyCode;
import io.appium.java_client.pagefactory.AndroidFindBy;
import io.appium.java_client.pagefactory.AppiumFieldDecorator;
import org.openqa.selenium.support.PageFactory;
import java.util.concurrent.TimeUnit;

public class ExamplePage {
    private AndroidDriver driver;
    public ProfilePage() {
    }
    public ProfilePage(AndroidDriver driver) {
        this.driver = driver;
        PageFactory.initElements(new AppiumFieldDecorator(driver), this);
    }
    @AndroidFindBy(className = "UIAKeyboard")
    private AndroidElement keyboard;
    @AndroidFindBy(id = "userName")
    private AndroidElement userNameElement;
    @AndroidFindBy(id = "password")
    private AndroidElement passwordElement;
    @AndroidFindBy(id = "login")
    private AndroidElement loginElement;
    public boolean isDisplayed() {
        return loginElement.isDisplayed();
    }
    public void typeUserName(String name) {
        userNameElement.sendKeys(name);
    }
    public void typePassword(String password) {
        passwordElement.sendKeys(password);
    }
    public void clickLogin() {
        loginElement.click();
    }
    public void hideKeyboardIfVisible() {
        if (keyboard != null) {
            driver.pressKeyCode(AndroidKeyCode.KEYCODE_ESCAPE);
        }
    }
    public void login (String name, String password) {
        hideKeyboardIfVisible();
        typeUserName(name);
        typePassword(password);
        clickLogin();
    }
}

FindBy uses the same locator strategies as the findElement() method used in POM.

• id
• name
• className
• xpath
• css
• tagName
• linkText
• partialLinkText