Page Factory模式Has-A关系下，不新建对象能否访问PaginationHelper变量？

Yes, you absolutely can access the PaginationHelper variables from your test class without creating a separate instance of it—you just need to adjust how your RCON_D_ContactsPage exposes either the helper instance itself or the state you need (like whether buttons are enabled). Let's break down two clean approaches:

Approach 1: Expose the PaginationHelper instance via a getter #

If you want direct access to all elements and methods in PaginationHelper, add a simple getter method to your RCON_D_ContactsPage class:

import com.rconweb.helper.PaginationHelper;
public class RCON_D_ContactsPage {
    WebDriver driver;
    PaginationHelper pagination;

    public RCON_D_ContactsPage(WebDriver driver) {
        PageFactory.initElements(new AjaxElementLocatorFactory(driver, 10), this);
        this.driver = driver;
        pagination = new PaginationHelper(driver);
    }

    // Existing wrapper methods
    public void clickNextPage() { pagination.clickNextPage(); }
    public void clickLastPage() { pagination.clickLastPage(); }
    public void clickFirstPage() { pagination.clickFirstPage(); }
    public void clickPreviousPage() { pagination.clickPreviousPage(); }
    public List<WebElement> getAllPages() { return pagination.getAllPages(); }

    // Add this getter to expose the helper instance
    public PaginationHelper getPaginationHelper() {
        return this.pagination;
    }
}

Then in your test class, you can access the helper's elements through this getter:

@Test
public void pagesNavigation() throws IOException, InterruptedException {
    while(contacts.getPaginationHelper().nextPageButton.isEnabled()) {
        contacts.clickNextPage();
        CommonMethods.waitUntilLoaderGetInvisible(driver);
        TakeScreenshot.passedScreenShot("Next Page");
        LogWriter.logger.info("Clicked Next Page");
    }
    // Repeat the pattern for other buttons using contacts.getPaginationHelper().previousPageButton etc.
}

Approach 2: Encapsulate state checks in RCON_D_ContactsPage (Recommended) #

A better practice for the Page Object Model (POM) is to avoid exposing raw elements to test classes. Instead, wrap state checks (like "is the next button enabled?") in methods on your page class. This keeps your test code cleaner and decouples it from the underlying element structure.

Update RCON_D_ContactsPage with these state-check methods:

import com.rconweb.helper.PaginationHelper;
public class RCON_D_ContactsPage {
    WebDriver driver;
    PaginationHelper pagination;

    public RCON_D_ContactsPage(WebDriver driver) {
        PageFactory.initElements(new AjaxElementLocatorFactory(driver, 10), this);
        this.driver = driver;
        pagination = new PaginationHelper(driver);
    }

    // Existing wrapper methods
    public void clickNextPage() { pagination.clickNextPage(); }
    public void clickLastPage() { pagination.clickLastPage(); }
    public void clickFirstPage() { pagination.clickFirstPage(); }
    public void clickPreviousPage() { pagination.clickPreviousPage(); }
    public List<WebElement> getAllPages() { return pagination.getAllPages(); }

    // Add state-check methods for each button
    public boolean isNextPageButtonEnabled() {
        return pagination.nextPageButton.isEnabled();
    }

    public boolean isPreviousPageButtonEnabled() {
        return pagination.previousPageButton.isEnabled();
    }

    public boolean isLastPageButtonEnabled() {
        return pagination.lastPageButton.isEnabled();
    }

    public boolean isFirstPageButtonEnabled() {
        return pagination.firstPageButton.isEnabled();
    }
}

Then your test class becomes much cleaner and more readable:

@Test
public void pagesNavigation() throws IOException, InterruptedException {
    while(contacts.isNextPageButtonEnabled()) {
        contacts.clickNextPage();
        CommonMethods.waitUntilLoaderGetInvisible(driver);
        TakeScreenshot.passedScreenShot("Next Page");
        LogWriter.logger.info("Clicked Next Page");
    }
    while(contacts.isPreviousPageButtonEnabled()) {
        contacts.clickPreviousPage();
        CommonMethods.waitUntilLoaderGetInvisible(driver);
        TakeScreenshot.passedScreenShot("Previous Page");
        LogWriter.logger.info("Clicked Previous Page");
    }
    // Repeat for last/first page checks
}

Why Approach 2 is better? #

• It follows the encapsulation principle of POM: test classes should only interact with high-level page actions and state checks, not raw WebElements.
• If a button's locator changes later, you only need to update PaginationHelper—your test code stays untouched.
• Makes test code more readable (anyone reading isNextPageButtonEnabled() immediately understands its purpose, without needing to know about the underlying element).

内容的提问来源于stack exchange，提问作者NarendraR