First Selenium Java test - Framework Patterns

Framework Mode - First Selenium Java test

Folder Structure

selenium-java-project/
├── src/
│   └── test/
│       └── java/
│           └── com/
│               └── example/
│                   ├── pages/
│                   │   └── HomePage.java
│                   ├── tests/
│                   │   └── FirstSeleniumTest.java
│                   └── utils/
│                       └── WebDriverManager.java
├── testng.xml
└── pom.xml

Test Framework Layers

• Driver Layer: Manages browser setup and teardown (e.g., WebDriverManager.java).
• Page Objects: Classes representing web pages with locators and actions (e.g., HomePage.java).
• Tests: Test classes with test methods using TestNG or JUnit (e.g., FirstSeleniumTest.java).
• Utilities: Helper classes for common tasks like waits or reading config.
• Configuration: Files like testng.xml and pom.xml to manage test execution and dependencies.

Configuration Patterns

• pom.xml: Defines Selenium, TestNG dependencies and build plugins.
• testng.xml: Specifies which tests to run and test groups.
• Environment Handling: Use Java system properties or profiles in Maven to switch browsers or URLs.
• Credentials: Store sensitive data in environment variables or external files, not in code.

Test Reporting and CI/CD Integration

• TestNG Reports: Built-in HTML reports showing passed/failed tests.
• Surefire Plugin: Maven plugin to run tests and generate reports.
• CI/CD: Integrate with Jenkins, GitHub Actions, or GitLab CI to run tests on code changes.
• Advanced Reporting: Use Allure or ExtentReports for detailed, user-friendly reports.

Best Practices

• Use Page Object Model: Keep locators and actions in page classes to separate test logic from UI details.
• Explicit Waits: Use waits to handle dynamic page elements instead of Thread.sleep().
• Keep Tests Independent: Each test should run alone without depending on others.
• Use Descriptive Names: Name tests and methods clearly to explain their purpose.
• Manage Browser Drivers: Use WebDriverManager library to handle driver binaries automatically.

Self Check

Where in this folder structure would you add a new page object class for the Login page?

Answer: Add it under src/test/java/com/example/pages/LoginPage.java.

Key Result

Organize Selenium Java tests using Page Object Model with clear layers and configuration for maintainability.