Run-MyTest

A collection of Java + Selenium WebDriver + TestNG + Maven UI automation frameworks grouped by domain (E-commerce, Banking, Travel/Tourism, and HRMS).

---

What you tested

This repository contains multiple automation suites targeting different sample/demo applications:

• E-commerce: user/auth flows, product browsing, cart and checkout journeys
  (suite folder: E-com_AutomationTesting/)
• Banking: login and account flows, transactions, validations
  (suite folder: parabank-automation-framework/)
• Travel/Tourism: search/booking flows, form validations, end-to-end journeys
  (suite folder: Travel-Tourism-Automation/)
• HRMS (OrangeHRM): authentication, employee management (PIM), admin/security checks, UI validations
  (suite folder: OrangeHRMTesting/)

---

Tools used

• Language: Java
• UI Automation: Selenium WebDriver
• Test Framework: TestNG
• Build Tool: Maven
• Reporting (varies by suite): Extent Reports
• CI (varies by suite): Jenkinsfile included in some suites

---

How to run

Each suite is an independent Maven project. Run from the suite folder you want:

1) Run via Maven

Example (E-commerce suite):

cd E-com_AutomationTesting
mvn clean test

2) Run via TestNG suite XML (IDE)

Most suites include testng.xml. You can run it from IntelliJ/Eclipse:

• Right-click testng.xml → Run as TestNG Suite

Prerequisites

• Java (typically Java 11+ as per suite docs)
• Maven
• Chrome/Firefox/Edge (depending on suite configuration)

---

Proper folder structure (pages, tests, utils)

All suites follow standard Maven/TestNG structure and generally use Page Object Model (POM).

Typical structure:

• src/main/java
  • pages/ → Page Objects (UI locators + page actions)
  • utils/ → reusable utilities (waits, config readers, screenshots, data readers, etc.)
  • driver/, base/, listeners/, constants/, reports/ → framework helpers
• src/test/java
  • tests/ (or domain-based packages) → test scenarios
  • dataprovider/ → data providers (when applicable)
• src/test/resources
  • config/ → configuration files (URLs, browser, timeouts)
  • testdata/ → Excel/JSON test data (if present)

---

2–3 solid test scenarios (examples)

Below are representative scenarios covered across the suites:

1. Authentication flows

   • Valid login
   • Invalid login
   • Logout / session handling

2. End-to-end business flows

   • E-commerce: Search/browse product → Add to cart → Checkout validations
   • Banking: Login → account navigation → transfer/transaction validations
   • Travel: Search → fill traveller details → booking/confirmation validations

3. UI + validation checks

   • Required field validations
   • Error messages assertions
   • Navigation/menu validation

---

Test suite folders in this repo

You asked to mention these folders in the README:

• /ecommerce-tests
• /banking-tests
• /travel-tests
• /hrms-tests

In this repository, those map to the existing suite folders as follows:

• /ecommerce-tests → E-com_AutomationTesting/
• /banking-tests → parabank-automation-framework/
• /travel-tests → Travel-Tourism-Automation/
• /hrms-tests → OrangeHRMTesting/

---

Quick links

• E-commerce suite: E-com_AutomationTesting/
• Banking suite: parabank-automation-framework/
• Travel/Tourism suite: Travel-Tourism-Automation/
• HRMS suite: OrangeHRMTesting/

For detailed coverage and architecture, see each suite’s README.md inside its folder.