Submitting forms in Selenium Java - Framework Patterns

Framework Mode - Submitting forms

Folder Structure

src/
└── test/
    └── java/
        └── com/
            └── example/
                ├── pages/
                │   └── LoginPage.java
                ├── tests/
                │   └── LoginTest.java
                ├── utils/
                │   └── WebDriverFactory.java
                └── config/
                    └── ConfigReader.java

Test Framework Layers

• Driver Layer: Manages browser setup and teardown (e.g., WebDriverFactory.java).
• Page Objects: Classes representing web pages with methods to interact with form elements and submit forms (e.g., LoginPage.java).
• Tests: Test classes that use page objects to perform form submission tests (e.g., LoginTest.java).
• Utilities: Helper classes for common tasks like reading configs or waiting for elements.
• Configuration: Handles environment variables, browser types, and credentials (e.g., ConfigReader.java).

Configuration Patterns

• Use config.properties file to store environment URLs, browser types, and user credentials.
• Load configuration in ConfigReader.java to provide easy access to test settings.
• Allow switching browsers via command line or environment variables for flexibility.
• Keep sensitive data like passwords outside source code, use environment variables or encrypted files.

Test Reporting and CI/CD Integration

• Use TestNG built-in reports for pass/fail status and test details.
• Integrate with tools like Allure or ExtentReports for detailed HTML reports showing form submission results.
• Configure CI/CD pipelines (e.g., Jenkins, GitHub Actions) to run tests automatically on code changes.
• Fail builds if form submission tests fail to catch issues early.

Best Practices

• Use Page Object Model: Encapsulate form fields and submit actions in page classes for easy maintenance.
• Explicit Waits: Wait for form elements to be visible and enabled before interacting to avoid flaky tests.
• Data-Driven Testing: Use external data sources (CSV, Excel) to test form submissions with multiple input sets.
• Clear Naming: Name methods clearly like fillUsername(), submitForm() for readability.
• Keep Tests Independent: Each test should set up its own form state and not rely on others.

Self Check

Where in this folder structure would you add a new page object class for a "Registration" form?

Key Result

Organize Selenium Java tests with Page Objects for forms, config for environments, and clear test layers.