Running tests via Maven in Selenium Java - Framework Patterns

Framework Mode - Running tests via Maven

Folder Structure for Selenium Java Maven Project

selenium-maven-project/
├── pom.xml
├── src/
│   ├── main/
│   │   └── java/
│   │       └── com/example/app/          # Application code (if any)
│   └── test/
│       └── java/
│           └── com/example/tests/        # Test classes
│               ├── pages/                 # Page Object classes
│               ├── tests/                 # TestNG or JUnit test classes
│               └── utils/                 # Utility/helper classes
└── target/                               # Maven build output

Test Framework Layers

• Driver Layer: Manages WebDriver setup and teardown, browser configuration.
• Page Objects: Classes representing web pages with locators and actions.
• Tests: Test classes using TestNG or JUnit to run test scenarios.
• Utilities: Helper classes for common functions like waits, logging, data handling.
• Configuration: Maven pom.xml and property files for environment and browser settings.

Configuration Patterns

• pom.xml: Defines dependencies (Selenium, TestNG/JUnit), plugins (Surefire for test execution).
• Profiles: Use Maven profiles in pom.xml to switch environments or browsers.
• Properties Files: Store URLs, credentials, and other environment-specific data.
• System Properties: Pass parameters via command line to customize test runs, e.g., -Dbrowser=chrome.
• TestNG XML: Define test suites and groups for selective test execution.

Test Reporting and CI/CD Integration

• Surefire Plugin Reports: Generates HTML and XML reports after test runs.
• TestNG Reports: Detailed test execution reports with pass/fail status.
• CI/CD Integration: Maven commands can be integrated into Jenkins, GitHub Actions, or other pipelines to run tests automatically on code changes.
• Fail Fast: Configure Maven to stop on first failure or continue to gather full results.

Best Practices for Running Tests via Maven

• Keep pom.xml clean and modular with dependencies and plugins clearly defined.
• Use Maven profiles to easily switch between browsers and environments without code changes.
• Organize tests and page objects clearly to maintain readability and scalability.
• Use TestNG XML files to group and manage test execution efficiently.
• Integrate test execution into CI/CD pipelines for continuous feedback.

Self Check

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

Key Result

Use Maven's pom.xml with profiles and Surefire plugin to organize and run Selenium Java tests efficiently.

Practice

1. What is the basic Maven command to run all Selenium tests in a project?

easy

A. mvn test

B. mvn clean

C. mvn compile

D. mvn install

Solution

1. Step 1: Understand Maven lifecycle phases

   Maven has phases like clean, compile, test, package, install. The test phase runs tests.

2. Step 2: Identify command for running tests

   The command mvn test runs all tests in the project, including Selenium tests.

3. Final Answer:

   mvn test -> Option A

4. Quick Check:

   Maven test phase = mvn test [OK]

Hint: Use mvn test to run all tests quickly [OK]

Common Mistakes:

• Using mvn clean which only cleans files
• Using mvn compile which only compiles code
• Confusing mvn install with running tests

2. Which Maven command runs a specific Selenium test class named LoginTest?

easy

A. mvn run -Dtest=LoginTest

B. mvn test -Dtest=LoginTest

C. mvn test -Dclass=LoginTest

D. mvn compile -Dtest=LoginTest

Solution

1. Step 1: Recall Maven syntax for running specific tests

   Maven uses -Dtest=ClassName to run a specific test class.

2. Step 2: Match correct command format

   mvn test -Dtest=LoginTest runs only the LoginTest class.

3. Final Answer:

   mvn test -Dtest=LoginTest -> Option B

4. Quick Check:

   Run single test = -Dtest=ClassName [OK]

Hint: Use -Dtest=ClassName to run one test class [OK]

Common Mistakes:

• Using -Dclass instead of -Dtest
• Using mvn run which is not a valid phase
• Trying to run tests during compile phase

3. Given the Maven command mvn test -Dtest=LoginTest, what will be the output if LoginTest has 3 passing Selenium tests?

medium

A. No tests run because -Dtest is ignored

B. All tests run, but only 3 tests from LoginTest pass

C. Only 3 tests from LoginTest run and all pass

D. Tests fail because mvn test can't run specific tests

Solution

1. Step 1: Understand -Dtest effect

   The -Dtest=LoginTest option runs only tests in the LoginTest class.

2. Step 2: Interpret test results

   If LoginTest has 3 tests and all pass, only those 3 tests run and pass.

3. Final Answer:

   Only 3 tests from LoginTest run and all pass -> Option C

4. Quick Check:

   -Dtest runs specified tests only [OK]

Hint: Specific test runs only those tests, others skipped [OK]

Common Mistakes:

• Thinking all tests run despite -Dtest
• Assuming -Dtest is ignored
• Believing mvn test can't run specific tests

4. You run mvn test -Dtest=LoginTest but get an error: Could not find or load main class LoginTest. What is the likely cause?

medium

A. Maven does not support running specific tests

B. The pom.xml file is missing

C. You forgot to compile the project before testing

D. The test class name is misspelled or not in the correct package

Solution

1. Step 1: Analyze error message

   The error says it cannot find the LoginTest class, meaning the name or location is wrong.

2. Step 2: Check common causes

   Misspelling the class name or incorrect package path causes this error. Maven supports running specific tests, so A is wrong. Compile errors or missing pom.xml cause different errors.

3. Final Answer:

   The test class name is misspelled or not in the correct package -> Option D

4. Quick Check:

   Class not found = wrong name or package [OK]

Hint: Check test class spelling and package path first [OK]

Common Mistakes:

• Assuming Maven can't run specific tests
• Ignoring compilation errors
• Thinking missing pom.xml causes this error

5. You want to run all Selenium tests but exclude the SlowTests class using Maven. Which command achieves this?

hard

A. mvn test -Dtest=!SlowTests

B. mvn test -DexcludedTests=SlowTests

C. mvn test -Dtest='*' -DexcludedTests=SlowTests

D. mvn test -Dtest='*' -DexcludeTests=SlowTests

Solution

1. Step 1: Recall Maven syntax for excluding tests

   Maven allows excluding tests by prefixing the class name with an exclamation mark in -Dtest, like -Dtest=!ClassName.

2. Step 2: Match correct command

   mvn test -Dtest=!SlowTests runs all tests except SlowTests. Other options use invalid or unsupported properties.

3. Final Answer:

   mvn test -Dtest=!SlowTests -> Option A

4. Quick Check:

   Exclude test with -Dtest=!ClassName [OK]

Hint: Use -Dtest=!ClassName to exclude tests [OK]

Common Mistakes:

• Using -DexcludedTests which is unsupported
• Using wrong property names like excludeTests
• Trying to exclude tests without exclamation mark