What is the best way to organize locator storage when developing automated tests for the user interface?

The best way to store locators in automated tests is to use the Page Object pattern. In this approach, a separate class is created for each page or interface component, where locators are stored as private fields or constants, and interaction with elements is encapsulated in methods.

Advantages:

• Locators are centralized and easy to maintain.
• UI changes require modifications only in one place.
• Test code becomes cleaner and more readable.

Example in Java with Selenium:

public class LoginPage {
    private WebDriver driver;
    private By usernameField = By.id("username");
    private By passwordField = By.id("password");
    private By loginButton = By.id("loginBtn");

    public LoginPage(WebDriver driver) {
        this.driver = driver;
    }

    public void enterUsername(String username) {
        driver.findElement(usernameField).sendKeys(username);
    }

    public void enterPassword(String password) {
        driver.findElement(passwordField).sendKeys(password);
    }

    public void clickLogin() {
        driver.findElement(loginButton).click();
    }
}

Thus, locators are stored in one place, and tests use class methods to interact with the UI.