Sayed Asif Back to Portfolio
QA Proof of Work

Automation Exercise

End-to-End QA Automation & Continuous Testing

A self-initiated QA engineering project combining manual testing, REST API validation, Playwright UI automation, Page Object Model architecture, debugging and GitHub Actions CI.

View Source Code View CI Runs
Latest Regression Result Passed
26/26 passed

Automated tests executed successfully

0 Failed
0 Flaky
0 Skipped
API + UI Coverage layers
26 Automated Tests
API + UI Testing Layers
Playwright Automation Framework
POM Framework Architecture
CI GitHub Actions
The Challenge

How do you validate an e-commerce application beyond basic UI checks?

Rather than treating automation as a collection of isolated browser scripts, I approached the application through multiple QA layers.

The project combines test planning, manual and exploratory validation, API testing, UI automation, regression execution and release assessment.

The goal was to build a maintainable automation suite that could provide repeatable evidence rather than simply demonstrate that a few browser actions could be automated.

01

Plan

Define scope, risks and test scenarios.

02

Validate

Perform manual and exploratory testing.

03

API

Validate REST endpoints and negative cases.

04

Automate

Build Playwright UI regression coverage.

05

Integrate

Execute automated tests through GitHub Actions.

06

Assess

Review execution results and quality findings.

Test Coverage

What I tested

The automated suite covers the application's core customer journeys and selected API behaviours.

Authentication

  • Registration
  • Duplicate registration
  • Valid login
  • Invalid credentials
  • Account deletion

Products

  • Product listing
  • Product search
  • Brands
  • API validation

Shopping Cart

  • Single product
  • Multiple products
  • Product removal
  • Quantity validation
  • Guest checkout

Checkout

  • Order review
  • Product verification
  • Order comments
  • Payment flow
  • Order confirmation

API

  • Account lifecycle
  • Authentication
  • Product search
  • Brands
  • Negative scenarios
Framework Architecture

Built for maintainability, not just execution.

The automation framework separates test intent from page interaction logic and supports both UI and API testing.

Playwright Test Framework
Playwright Test Runner
↓
UI Tests
API Tests
↓
Login
Cart
Checkout
Account
Authentication
Products
↓
Page Objects + Reusable Utilities
↓
GitHub Actions CI

Page Object Model

Page interaction logic is separated from individual test scenarios to improve maintainability.

Reusable Utilities

Common operations are centralized instead of being repeatedly implemented inside individual tests.

Authentication State

Tests can begin from an authenticated state where the scenario requires it.

API + UI Layers

The suite validates behaviour beyond the browser layer by including direct API testing.

Continuous Testing

Automated regression through GitHub Actions

The project uses GitHub Actions to execute API and UI test suites in CI and preserve Playwright reports as workflow artifacts.

Push / Pull Request
↓
GitHub Actions
↓
API Tests
UI Tests
↓
Playwright Reports
↓
CI Artifacts

What the pipeline proves

The project is not dependent on a local machine to demonstrate that the automation works. The test suite is executable through the CI workflow.

  • Playwright dependencies installed in CI
  • Chromium installed for UI execution
  • API and UI suites executed independently
  • Test reports uploaded as artifacts
  • Workflow triggered by repository changes
Inspect GitHub Actions
Engineering & Debugging

Automation isn't useful if it isn't stable.

Checkout automation required investigation and stabilization.

During automation development, checkout scenarios exposed synchronization and cart-state problems. Instead of simply increasing timeouts, I used the available Playwright evidence to investigate the failure path and refine the automation.

01 · FAILURE Test exposes unexpected behaviour.
02 · EVIDENCE Screenshot, video and trace reviewed.
03 · ANALYSIS Locator and synchronization behaviour investigated.
04 · REFINEMENT Page-object interaction and waiting strategy refined.
05 · VERIFY Suite re-run until the current regression result was stable.
QA Outcome

Evidence over claims.

100% Latest automated execution pass rate
26 Automated tests executed
0 Critical defects
0 High-severity defects
2 Minor UI issues documented

QA finding

The documented QA assessment also records minor UI issues and a third-party ad injection behaviour. These findings are presented as observations from the tested environment rather than being described as application-critical production defects.

Proof & Documentation

Inspect the work.

The project is backed by source code, QA documentation and CI execution evidence.

Source Code

Explore the Playwright framework, page objects, API tests and utilities.

Open Repository

Test Plan

Review the project scope, testing approach, risks and planned validation.

View Test Plan

Manual Test Cases

Review the manually designed test scenarios supporting the project.

View Test Cases

Execution Report

Review the documented execution results and QA assessment.

View Report

CI Pipeline

Verify the GitHub Actions execution history and workflow results.

View CI Runs

Test Evidence

Explore repository evidence and generated testing artifacts where available.

Explore Evidence
Technology

Tools used in the project

Playwright JavaScript Node.js REST API Testing Page Object Model GitHub Actions Chromium Manual Testing Regression Testing
What This Demonstrates

More than a Playwright script.

01

QA Thinking

Test planning and validation were considered before building the automated regression layer.

02

Automation Engineering

The framework uses page objects and reusable components instead of placing every interaction directly inside test files.

03

API Testing

Application behaviour is validated at both the API and browser layers.

04

Debugging

Playwright screenshots, videos and traces are used as evidence when investigating failures.

05

CI Engineering

Automated tests can execute through GitHub Actions instead of relying only on local runs.

06

Quality Communication

Test planning, execution evidence and QA findings are documented alongside the code.

Don't just take my word for it. Inspect the implementation.

The source code, CI workflow and QA documentation are available for review.

View GitHub Verify CI Back to Portfolio