Maven project creation in Selenium Java - Framework Patterns

Framework Mode - Maven project creation

Folder Structure of a Maven Selenium Project

my-selenium-project/
├── pom.xml
└── src/
    └── test/
        └── java/
            └── com/
                └── example/
                    ├── pages/
                    │   └── LoginPage.java
                    └── tests/
                        └── LoginTest.java

Test Framework Layers

• Driver Layer: Manages WebDriver setup and teardown (e.g., ChromeDriver).
• Page Objects: Classes representing web pages with locators and actions (e.g., LoginPage.java).
• Tests: Test classes using TestNG or JUnit to run test cases (e.g., LoginTest.java).
• Utilities: Helper classes for common functions like waits, reading config, screenshots.
• Configuration: pom.xml for dependencies and test settings, plus property files for environment data.

Configuration Patterns

• pom.xml: Defines Selenium, TestNG/JUnit dependencies, plugins, and build settings.
• Property Files: Store environment URLs, browser types, and credentials separately (e.g., config.properties).
• Profiles: Use Maven profiles to switch between environments (dev, test, prod) easily.
• Driver Setup: Centralize WebDriver initialization to read browser type from config.

Test Reporting and CI/CD Integration

• TestNG Reports: Default HTML reports generated after test runs.
• Maven Surefire Plugin: Runs tests and generates reports during build.
• CI/CD Integration: Configure Jenkins/GitHub Actions to run mvn test on code push.
• Advanced Reporting: Integrate Allure or ExtentReports for detailed, user-friendly reports.

Best Practices for Maven Selenium Framework

1. Use Page Object Model: Keep locators and page actions in separate classes for maintainability.
2. Keep Tests Independent: Each test should run alone without depending on others.
3. Centralize Configuration: Use property files and Maven profiles to manage environment and browser settings.
4. Use Explicit Waits: Avoid flaky tests by waiting for elements properly.
5. Organize Code by Layer: Separate driver setup, page objects, tests, and utilities clearly.

Self Check

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

Key Result

A Maven Selenium framework organizes code into src/test/java for page objects and tests, uses pom.xml for dependencies, and applies the Page Object Model for maintainability.

Practice

1. What is the main purpose of using Maven when creating a Selenium Java project?

easy

A. To run Selenium tests only on Firefox browser

B. To automatically create a standard project structure and manage dependencies

C. To write Selenium test scripts manually without any setup

D. To replace Java programming language with XML

Solution

1. Step 1: Understand Maven's role in project setup

   Maven helps by creating a standard folder structure and managing libraries needed for Selenium tests.

2. Step 2: Compare other options

   Options A, B, and D describe incorrect or unrelated functions of Maven.

3. Final Answer:

   To automatically create a standard project structure and manage dependencies -> Option B

4. Quick Check:

   Maven manages structure and dependencies = C [OK]

Hint: Remember: Maven sets up structure and handles libraries [OK]

Common Mistakes:

• Thinking Maven only runs tests
• Confusing Maven with a browser
• Believing Maven replaces Java code

2. Which command correctly creates a new Maven project with the default directory structure?

easy

A. mvn selenium:start

B. mvn clean install

C. mvn archetype:generate

D. mvn compile test

Solution

1. Step 1: Identify the command for creating a new project

   The command mvn archetype:generate is used to create a new Maven project with standard folders.

2. Step 2: Understand other commands

   mvn clean install builds the project, mvn selenium:start is invalid, and mvn compile test compiles and tests but does not create a project.

3. Final Answer:

   mvn archetype:generate -> Option C

4. Quick Check:

   Project creation command = mvn archetype:generate [OK]

Hint: Use 'archetype:generate' to start new Maven projects [OK]

Common Mistakes:

• Using build commands instead of project creation
• Typing invalid Maven commands
• Confusing compile/test with project setup

3. Given the following Maven command run in a terminal:

mvn archetype:generate -DgroupId=com.example -DartifactId=seleniumtest -DarchetypeArtifactId=maven-archetype-quickstart -DinteractiveMode=false

What will be the result?

medium

A. The command runs tests but does not create any project

B. The command will fail because 'interactiveMode' is misspelled

C. Maven will only compile existing code without creating a project

D. A new Maven project named 'seleniumtest' with group 'com.example' is created automatically

Solution

1. Step 1: Analyze the command parameters

   The command uses archetype:generate with groupId, artifactId, archetypeArtifactId, and disables interactive mode, which creates a new project automatically.

2. Step 2: Check for errors

   The parameter -DinteractiveMode=false is correctly spelled and disables prompts, so the command succeeds.

3. Final Answer:

   A new Maven project named 'seleniumtest' with group 'com.example' is created automatically -> Option D

4. Quick Check:

   Correct parameters create project automatically = D [OK]

Hint: Use -DinteractiveMode=false for automatic project creation [OK]

Common Mistakes:

• Misspelling parameter names
• Confusing compile with project creation
• Expecting tests to run on project creation

4. You ran mvn archetype:generate but got an error: Could not find artifact org.apache.maven.archetypes:maven-archetype-quickstart. What is the likely cause and fix?

medium

A. No internet connection; connect to internet and rerun the command

B. Wrong Java version; downgrade Java to version 7

C. Maven is not installed; install Maven first

D. Project folder already exists; delete it before running

Solution

1. Step 1: Understand the error message

   The error means Maven cannot download the archetype artifact from its repository, usually due to no internet connection.

2. Step 2: Identify the fix

   Connecting to the internet allows Maven to download required files and run the command successfully.

3. Final Answer:

   No internet connection; connect to internet and rerun the command -> Option A

4. Quick Check:

   Artifact download error = no internet [OK]

Hint: Check internet if Maven can't download archetypes [OK]

Common Mistakes:

• Assuming Java version causes this error
• Thinking Maven is not installed when it is
• Deleting folders unnecessarily

5. You want to create a Maven Selenium Java project that includes the Selenium WebDriver dependency automatically. Which step should you do after creating the project with mvn archetype:generate?

hard

A. Add the Selenium WebDriver dependency XML snippet inside the <dependencies> section of pom.xml

B. Write Selenium test code before adding any dependencies

C. Run mvn clean install without modifying pom.xml

D. Delete the src folder and create it manually

Solution

1. Step 1: Understand Maven dependency management

   After project creation, you must add Selenium WebDriver dependency inside pom.xml to download required libraries.

2. Step 2: Why other options are incorrect

   Writing code before adding dependencies causes errors; running build without dependencies fails; deleting src folder breaks structure.

3. Final Answer:

   Add the Selenium WebDriver dependency XML snippet inside the <dependencies> section of pom.xml -> Option A

4. Quick Check:

   Add dependencies in pom.xml before coding = A [OK]

Hint: Always add dependencies in pom.xml before coding [OK]

Common Mistakes:

• Skipping dependency addition
• Running build without dependencies
• Altering project folders manually