Clearing fields in Selenium Java - Framework Patterns

Framework Mode - Clearing fields

Folder Structure

selenium-java-project/
├── src/
│   ├── main/
│   │   └── java/
│   │       └── com/example/app/pages/
│   │           └── LoginPage.java
│   └── test/
│       └── java/
│           └── com/example/app/tests/
│               └── LoginTest.java
├── resources/
│   └── testdata.properties
├── drivers/
│   └── chromedriver.exe
├── pom.xml
└── testng.xml

Test Framework Layers

• Driver Layer: Manages WebDriver setup and teardown (e.g., ChromeDriver initialization).
• Page Objects: Java classes representing web pages, encapsulating elements and actions like clearing fields.
• Tests: Test classes using TestNG to run test cases that interact with page objects.
• Utilities: Helper classes for common functions like waits, logging, and reading test data.
• Configuration: Properties files and XML files to manage environment settings, browser types, and credentials.

Configuration Patterns

• Environment Properties: Use testdata.properties to store URLs, usernames, and passwords.
• Browser Setup: Configure browser type and driver path in pom.xml or system properties.
• Credentials: Store securely in properties files or environment variables, avoid hardcoding.
• TestNG XML: Define test suites and parameters like browser and environment for flexible test runs.

Test Reporting and CI/CD Integration

• Use TestNG built-in reports for test execution results (pass/fail).
• Integrate with tools like Allure or ExtentReports for detailed HTML reports with screenshots.
• Configure CI/CD pipelines (e.g., Jenkins, GitHub Actions) to run tests automatically on code commits.
• Publish reports as build artifacts and notify teams on failures.

Best Practices for Clearing Fields in Selenium Java Framework

1. Use Page Object Model: Encapsulate the clear action inside page object methods for reusability and readability.
2. Explicit Waits: Wait for the field to be visible and enabled before clearing to avoid flaky tests.
3. Clear Before SendKeys: Always clear input fields before typing new text to avoid input errors.
4. Handle Special Cases: For fields that do not clear with clear(), use JavaScript executor as fallback.
5. Keep Tests Independent: Ensure fields are cleared or reset in setup methods to avoid test interference.

Self Check

Where in this folder structure would you add a new method to clear the password field on the login page?

Key Result

Use Page Object Model to encapsulate field clearing actions with explicit waits for reliable Selenium Java tests.