Selenium WebDriver is a tool that allows you to automate web browsers using code, making it easier to test web applications and perform repetitive tasks. It supports multiple programming languages like Java, Python, and JavaScript, and works across various browsers such as Chrome, Firefox, and Edge. You can learn more and get started at selenium.dev.

Selenium WebDriver is a programming interface developed by Simon Stewart in 2006.

• Cross-Platform Support: Works on Windows, Mac, and Linux.

• Cross-Browser Support: Compatible with major browsers like Chrome, Microsoft Edge, Firefox, and Safari.

• Multi-Language Support: Works with top programming languages including Java, JavaScript, Python, C#, and Ruby.

• Use Eclipse IDE to develop and manage test cases.

• Integrates with Jenkins for CI/CD pipeline automation.

• Supports Maven for build and dependency management.

• Use Git (version control) and GitHub (cloud-based repository hosting) for collaboration.

• Supports TestNG as a testing framework.

• Huge ecosystem of plugins – offering flexibility and enhanced capabilities.

• Generates HTML test reports using Maven, TestNG, Extent Reports, and Allure Reports.

• https://www.eclipse.org/downloads/packages/

• Help >> Eclipse Market place >> search >> testng >> Install.

1. Download the x64 Installer (.exe) from Oracle JDK Downloads.
2. Run the installer and complete the setup.
3. Set environment variables:
   • Open This PC > Properties > Advanced system settings > Environment Variables.
   • Under System variables, create a new variable: JAVA_HOME = C:\Program Files\Java\jdk-21
   • Edit the Path variable and add: C:\Program Files\Java\jdk-21\bin
4. Verify installation by running in Command Prompt: java --version

1. Download the Binary zip archive (apache-maven-3.9.9-bin.zip) from Apache Maven Downloads.
2. Extract the zip file to a desired location, e.g., C:\Program Files\apache-maven-3.9.9.
3. Set environment variables:
   • Right-click This PC → Properties → Advanced system settings → Environment Variables.
   • Under User variables, create a new variable:
     MAVEN_HOME = C:\Program Files\apache-maven-3.9.9
   • Edit the Path variable under System variables and add:
     C:\Program Files\apache-maven-3.9.9\bin
4. Verify installation by running in Command Prompt:

• https://mvnrepository.com/

src/main/java
├── com.qa.utils
    └── Base.java
    └── CommonUtils.java
    └── ExcelUtils.java
    └── ExtendReportManager.java
    └── SeleniumUtils.java
    └── PdfReader.java
    └── log4j2.xml


src/test/java
├── tests
    └── LoginTest.java
├── pages
    └── LoginPage.java

Configurations
├── Config.properties

Data
├── TestData.json

Include
├── UploadFile.pdf, UploadFile.png, UploadFile.csv...
├── SelectorHub.crx (browser extension)

Logs
├── execution.logs

reports
├── extendReport.html

Screenshots
├── assertDemo0313_Failed_183355.png

target (Maven Report)
├── surefire-reports
    └──index.html

test-output(Testng Report)
├── index.html

Test Suites
├──ts-smoke.xml
├──ts-sanity.xml
├──ts-regression.xml

README.md

This project is a structured Maven-based Selenium Java framework following a layered architecture for better modularity, scalability, and maintainability.

1. Test Execution

   • TestNG reads the test suite file (TS_app_smoke.xml or TS_app_Regression.xml).
   • Initializes WebDriver using Base.java.

2. Page Object Handling

   • LoginTest.java calls LoginPage.java methods.
   • LoginPage.java uses locators and actions to interact with web elements.

3. Utilities and Configuration

   • Config.properties provides browser type, URL, and other environment settings.
   • CommonUtils, SeleniumUtils, and ExcelUtils provide helper methods.

4. Data Handling

   • Test data is fetched from TestData.json or ExcelUtils.java.

5. Assertions and Reporting

   • Assert statements validate expected vs actual results.
   • ExtendReportManager.java generates Extent Reports.
   • Screenshots are captured for failed cases.

6. Logging

   • Logs are generated using log4j2.xml.

7. Teardown

   • Browser session is closed using Base.java cleanup methods.

• Proxy issues: Uses lazy proxies that can cause StaleElementReferenceException and are hard to debug.
• No built-in waits: Leads to flaky tests due to timing problems.
• Maintenance: Adds complexity and hides element lookup details.
• Better alternatives: Explicit By locators with WebDriverWait are clearer and more reliable.
• Limited modern support: Doesn’t support Selenium 4 features well.
• Performance: Proxy creation can slow down large test suites.

✅ Follows layered architecture for better maintainability
✅ Implements Page Object Model for clean separation of concerns
✅ Supports data-driven testing using JSON and Excel
✅ Provides logging and reporting with Log4j and Extent Reports
✅ Enables parallel and cross-browser testing using TestNG and Maven

This project demonstrates Selenium WebDriver features from version 3 up to 4.29, including:

1. Basic Selenium WebDriver actions
2. PDF file reading using Apache PDFBox
3. Comprehensive TestNG framework test cases
4. Core Java fundamentals
5. ChromeOptions and Chrome DevTools usage
6. Mobile emulator testing on Chrome browser
7. Data-driven testing with JSON, Excel, Properties files, and MySQL database
8. File upload automation with Robot class and AutoIT
9. Headless browser testing using HtmlUnit, ChromeDriver, FirefoxDriver, and PhantomJS
10. Logging with Log4j framework
11. Page Object Model design pattern demos: traditional POM and Page Factory with @FindBy annotation
12. Singleton design pattern example
13. Shadow DOM handling
14. Broken links detection
15. Use of relative/friendly locators

• Apache PDFBox for PDF handling
• Log4j for logging
• Automation library for friendly locators

1. Clone the repository.
2. Configure Config.properties with browser, URL, and timeout.
3. Run tests using:

mvn clean test

4. View reports at:

• target/surefire-reports/index.html
• reports/extendReport.html
• Allure report via:

allure serve allure-results

Run a suite with:

mvn clean test -DtestngFile=YourTestSuite.xml

Examples:

mvn clean test -DtestngFile=smoke-test-suite.xml
mvn clean test -DtestngFile=sanity-test-suite.xml
mvn clean test -DtestngFile=regression-test-suite.xml

• Adjust <suiteXmlFile> path if suite files are not in Test Suites.
• Change dependency scope from <scope>test</scope> to <scope>compile</scope> to run from command line.

• Parallel suite located in Test Suites/Parallel...

1. Maven surefire report target/surefire-reports/index.html

2. TestNG Report test-output/index.html

3. Allure Report install scoop window powershell : iwr -useb get.scoop.sh | iex install allure command: scoop install allure cmd command : allure serve allure-results

Bijaya Chhetri | Automation Engineer | 🔗 github.com/bija510

This project is licensed under the MIT License.