Real-Time Projects That Get You Hired - Getcamped

Build a complete end-to-end Hybrid Selenium framework for a live e-commerce application — covering user registration, product search, cart operations, and checkout flows. This is the core capstone combining everything from Phases 1 through 3.

What You'll Build

• Test Plan in Jira — epics, stories, and test cases linked to requirements
• 20+ Manual Test Cases covering positive and negative scenarios
• Hybrid Framework — Java + Selenium + TestNG + Maven + Page Object Model
• 5 critical automated flows — Login, Search, Add to Cart, Checkout, and Order History
• API Tests via RestAssured for Login and User services
• GitHub push and Jenkins pipeline trigger on every commit
• Allure and Extent Reports with screenshot-on-failure

Tech Stack

• Java 17
• Selenium 4
• TestNG
• Maven
• Page Object Model
• Page Factory
• RestAssured
• Apache POI
• Allure Reports
• Jenkins
• GitHub
• Jira
• MySQL

Automated Flows Covered

• User Registration & Login
• Product Search & Filter
• Add to Cart & Quantity Update
• End-to-End Checkout Flow
• Order History Validation

Key Skill: Page Object Model separates test logic from UI locators — making the framework maintainable as the app evolves. You will implement this pattern the same way senior SDETs do in production.

Sample Output — TestNG Console Report

• Tests run: 11, Failures: 1, Skipped: 0 | Total time: 7.48 seconds
• TC_001 | validUserLogin — PASS (235ms)
• TC_002 | loginWithRememberMe — PASS (198ms)
• TC_003 | loginWithInvalidPassword — FAIL (312ms) — Expected: "Invalid credentials" | Found: "Something went wrong" — Bug logged: BUG-204
• TC_010 | searchByKeyword_returnsResults — PASS (541ms)
• TC_011 | filterByCategory_Electronics — PASS (623ms)
• TC_012 | sortByPriceLowToHigh — PASS (480ms)
• TC_020 | addSingleItemToCart — PASS (391ms)
• TC_021 | updateQuantity_recalculatesTotal — PASS (448ms)
• TC_022 | removeItemFromCart — PASS (312ms)
• TC_030 | e2eCheckout_CreditCard — PASS (1842ms)
• TC_031 | orderConfirmation_emailNotification — PASS (2104ms)
• Screenshot captured — /reports/screenshots/TC_003_FAIL.png
• Allure Report published — /allure-results/index.html

Sample Framework Structure — Maven Project

• ecommerce-qa-framework/
• src/main/java/base/ — BaseTest.java — Driver initialisation using Singleton pattern
• src/main/java/pages/ — LoginPage.java, HomePage.java, ProductPage.java, CheckoutPage.java — @FindBy locators and page actions
• src/main/java/utils/ — ExcelReader.java (Apache POI), ScreenshotUtil.java
• src/test/java/ — LoginTests.java, ProductSearchTests.java, CartTests.java, CheckoutTests.java
• resources/ — config.properties for ENV URLs and browser settings
• resources/ — testdata.xlsx for data-driven test inputs
• Root — testng.xml, Jenkinsfile, pom.xml

Automate the complete backend service layer of a Banking application using RestAssured in Java. Cover account creation, fund transfers, authentication, and schema validation — the skills most SDET roles specifically require.

What You'll Build

• RestAssured test suite with BDD Given/When/Then syntax
• POJO classes for JSON Serialization and Deserialization using Jackson
• Token extraction from Login chained to authenticated API calls
• Response Schema Validation using JSON Schema validator
• SQL validation — verify database state after each API transaction
• Postman Collection exported as regression reference

API Endpoints Tested

• POST /api/auth/login
• POST /api/users/register
• GET /api/accounts/{id}/balance
• GET /api/accounts/{id}/transactions
• POST /api/transfers/initiate
• PUT /api/users/{id}/profile
• DELETE /api/beneficiaries/{id}

Sample Output — RestAssured API Test Run

• API Base URI: https://api.bankingapp-staging.com
• Auth Strategy: Bearer Token extracted from POST /login
• TC_A01 | POST /auth/login — 200 OK, token extracted — PASS (182ms)
• TC_A02 | POST /auth/login — 401 invalid password — PASS (140ms)
• TC_A03 | POST /auth/login — 400 empty body validation — PASS (122ms)
• TC_B01 | GET /accounts/{id}/balance — 200, balance greater than or equal to 0 — PASS (210ms)
• TC_B02 | GET /accounts/{id}/balance — schema validated — PASS (198ms)
• TC_B03 | GET /accounts/9999/balance — Expected 404 — FAIL (156ms) — Received: 500 Internal Server Error — Bug: BUG-317
• TC_C01 | POST /transfers/initiate — 201 Created — PASS (354ms)
• TC_C02 | DB Verified — debit account balance updated — SQL OK — PASS
• TC_C03 | POST /transfers — 422 insufficient funds — PASS (289ms)
• Tests: 9 passed, 1 failed | Response time average: 206ms
• BUG-317 logged in Jira — Severity: HIGH, Priority: P1

Sample Code — Chained Request — Login then Balance Check

• Step 1: Send POST to /auth/login with LoginPOJO body containing email and password. Assert status code 200. Extract the accessToken value from the data.accessToken path in the response.
• Step 2: Use the extracted token in the Authorization Bearer header. Send GET to /accounts/{id}/balance. Assert status code 200 and that balance is greater than or equal to 0. Deserialize the response body into AccountResponse POJO using Jackson.
• Step 3: Query the database — SELECT balance FROM accounts WHERE id equals accountId. Use assertEquals to confirm the API response balance matches the database balance value.

Configure a full Jenkins CI/CD pipeline that automatically triggers your test suite on every GitHub commit. Add parallel cross-browser execution, nightly scheduling, and email reporting — the DevOps layer that makes automation actually useful in teams.

What You'll Configure

• Jenkinsfile declarative pipeline committed to the GitHub repository
• Auto-trigger on every push to main branch via GitHub webhook
• Parallel stages — Chrome and Firefox running simultaneously
• Nightly scheduled runs using cron at midnight
• Email notifications on failure with log attachments
• Allure report published as a Jenkins build artifact

Bonus — Docker + Selenium Grid

• Docker Compose with Hub, Chrome node, and Firefox node
• RemoteWebDriver for containerized browser sessions
• Headless execution — no display required on server

Why this matters for interviews: Most junior QA candidates can write Selenium scripts. Very few can explain how their tests run automatically in a CI pipeline. This project gives you that edge.

Sample Output — Jenkins Pipeline Console Log

• Pipeline: ECommerce-QA-Pipeline | Build 47 | Started by GitHub push to main by John Doe
• Stage Checkout SCM — Cloned from GitHub, Branch: main, Commit: a3f8c2d — PASS
• Stage Build — mvn clean compile — BUILD SUCCESS in 12.3 seconds — PASS
• Stage Run Tests Parallel — Chrome Node: LoginTests 3 of 3 passed (14.2s), CartTests 3 of 3 passed (21.8s), CheckoutTests 2 of 3 passed (18.4s) — 1 FAILURE
• Stage Run Tests Parallel — Firefox Node: LoginTests 3 of 3 passed (16.1s), CartTests 3 of 3 passed (23.5s), CheckoutTests 3 of 3 passed (19.2s) — ALL PASS
• Stage Publish Report — Allure Report published to Build 47/allure, Screenshots archived to Build 47/artifacts — PASS
• Notification — Email sent to qa-team@company.com — Subject: FAILED Build 47 — CheckoutTests Chrome
• Pipeline Result: UNSTABLE | Duration: 1 minute 43 seconds
• Next run: Scheduled at 00:00 nightly cron

Sample Jenkinsfile — Declarative Pipeline

• pipeline block defines the full CI/CD flow
• agent any — runs on any available Jenkins agent
• triggers — cron set to run nightly at midnight: 0 0 * * *
• Stage Build — runs: mvn clean compile -q
• Stage Test Parallel — Chrome stage runs: mvn test -Dbrowser=chrome
• Stage Test Parallel — Firefox stage runs: mvn test -Dbrowser=firefox
• Stage Publish — Allure plugin publishes results from allure-results folder
• post failure block — emailext sends failure notification to qa-team@company.com with build logs