Maven build lifecycle in Selenium Java - Framework Patterns

Framework Mode - Maven build lifecycle

Folder Structure of a Maven Selenium Java Project

my-selenium-project/
├── pom.xml
├── src/
│   ├── main/
│   │   └── java/
│   │       └── com/example/app/
│   │           └── App.java
│   └── test/
│       └── java/
│           └── com/example/tests/
│               ├── pages/
│               │   └── LoginPage.java
│               ├── tests/
│               │   └── LoginTest.java
│               └── utils/
│                   └── WebDriverFactory.java
└── target/
    └── (compiled classes, reports, jars)
  

Test Framework Layers in Maven Selenium Java

• Driver Layer: Manages WebDriver setup and teardown (e.g., WebDriverFactory.java).
• Page Objects: Classes representing web pages with locators and actions (e.g., LoginPage.java).
• Test Layer: Test classes containing test methods using TestNG or JUnit (e.g., LoginTest.java).
• Utilities: Helper classes for common functions like waits, logging, or data handling.
• Configuration: pom.xml for build lifecycle, dependencies, plugins, and profiles.

Configuration Patterns in Maven Build Lifecycle

The pom.xml file controls the build lifecycle phases:

• clean: Removes previous build files (target folder).
• compile: Compiles source code.
• test-compile: Compiles test code.
• test: Runs tests using TestNG or JUnit.
• package: Packages compiled code into a JAR or WAR.
• verify: Runs checks on results (e.g., integration tests).
• install: Installs package into local repository.
• deploy: Copies package to remote repository.

Use profiles in pom.xml to manage different environments (dev, test, prod) and browsers.

Example snippet for profiles:

<profiles>
  <profile>
    <id>chrome</id>
    <properties>
      <browser>chrome</browser>
    </properties>
  </profile>
  <profile>
    <id>firefox</id>
    <properties>
      <browser>firefox</browser>
    </properties>
  </profile>
</profiles>

Test Reporting and CI/CD Integration

• Use Maven Surefire Plugin to run tests and generate reports in target/surefire-reports.
• Integrate with Jenkins or GitHub Actions to run Maven commands automatically on code push.
• Reports can be viewed in Jenkins UI or exported as HTML/XML for analysis.
• Use plugins like maven-failsafe-plugin for integration tests and advanced reporting.

Best Practices for Maven Build Lifecycle in Selenium Java

• Keep pom.xml clean and modular by using profiles and properties.
• Separate test code from production code under src/test/java and src/main/java.
• Use explicit Maven phases to control build steps and avoid running unnecessary tasks.
• Use dependency management to keep Selenium and TestNG/JUnit versions consistent.
• Automate test runs in CI/CD pipelines using Maven commands like mvn clean test.

Self Check Question

Where in this Maven project structure would you add a new page object class for the "Dashboard" page?

Key Result

Maven organizes Selenium Java tests with a clear lifecycle controlling build, test, and packaging phases using pom.xml.