DemoWebShop Selenium Java BDD Automation Framework

This project demonstrates a test automation framework built using Selenium WebDriver, Java, and Cucumber (BDD) to automate functional test scenarios for the Demo Web Shop application.

The goal of this project is to showcase modern QA automation practices including Page Object Model (POM), Behavior Driven Development (BDD), and CI/CD integration using GitHub Actions.

Test Target:
https://demowebshop.tricentis.com/

---

Tech Stack

• Language: Java 17+

• Automation Tool: Selenium WebDriver 4

• BDD Framework: Cucumber (Gherkin)

• Build Tool: Maven

• Test Runner: JUnit 4

• Design Pattern: Page Object Model (POM)

• CI/CD: GitHub Actions

---

Framework Architecture

The framework follows the Page Object Model (POM) design pattern to improve test maintainability and scalability.

Project structure:

├── .github/workflows 
├── src/test/java
│   ├── base            
│   ├── hooks           
│   ├── pages           
│   ├── stepdefinitions 
│   └── testrunner      
├── src/test/resources
│   ├── features        
│   └── config.properties 

---

Test Coverage

The framework covers the following functional scenarios, mapped to specific Cucumber tags for targeted execution:

Feature Area	Automated Scenario	Tag
Authentication	Valid Login	@Login
Authentication	Login with Invalid Credentials	@Invalid_Login
Search	Product Catalog Discovery	@Search
Shopping Cart	Add Product to Cart	@AddToCart
Checkout	Check out product	@Checkout
Log out	Log out to demo site	@Logout
End to End	Complete Purchase Journey (Login to Checkout)	@EndtoEnd

---

How to Run Tests

Local Execution

1. Clone the repository:

git clone https://github.com/gian-aguilar/DemoWebShop-Selenium-Java-BDD.git

2. Run all tests via Terminal:

mvn clean test

3. Run specific suites using Tags:

mvn test -Dcucumber.filter.tags="@EndtoEnd"

4. Execution via IDE: Right-click src/test/java/testrunner/TestRunner.java and select Run as JUnit Test. (The runner is configured to be tag-agnostic, allowing for full suite execution).

---

Continuous Integration (CI)

This project uses GitHub Actions to automatically run automation tests whenever code is pushed to the repository.

• Trigger: Every push or pull_request to the main branch.

• Environment: Runs on ubuntu-latest using Chrome Headless mode.

• Artifacts: Cucumber HTML reports are generated and stored in the "Actions" summary after every run.

Workflow configuration can be found here:

.github/workflows

This ensures that automated tests run consistently in a CI pipeline similar to real-world QA environments.

---

Reporting

The framework generates a detailed HTML report for every execution.

• Local: target/cucumber-reports.html

• GitHub Actions: Download the cucumber-report artifact from the Summary page of any successful run.

• Features: Includes step-by-step pass/fail status, execution time, and Gherkin formatting.

---

Test Execution Screenshot

Console Output using Maven execution

Cucumber Report

Purpose of This Project

This project serves as a portfolio automation framework demonstrating:

• Selenium automation framework development
• Behavior Driven Development (BDD) implementation
• Page Object Model architecture
• CI/CD pipeline integration

---

Author

Gian Aguilar
Senior QA Engineer | Automation Enthusiast