Test automation / Testing portfolio

Across the browsers.

Same journey. Different engines.

WHAT IT DOES

A testing portfolio that connects exploratory findings, browser coverage, and Playwright evidence to release decisions.

MY CONTRIBUTION

Solo QA project: automation, cross-browser checks, evidence capture, and CI workflows for a third-party application.

THE INTERESTING DECISION

Test IDs connect automation to the compatibility matrix. Defects include reproducible evidence; a release-readiness report communicates coverage and unresolved risk.

START WITH THE EVIDENCETrace + video

Failure artifacts preserve steps and browser context.

Inspect the source ↗

BUILT WITH

PlaywrightJavaScriptAccessibilityGitHub Actions

PROJECT TYPE

Testing portfolio

START HEREREADME & setup

01 / THE IDEA

Same journey. Different engines.

The problem

A checkout flow working in one browser is not enough. Layouts, validation, accessibility, and slow-resource behavior can fail differently across browsers and devices.

The approach

The project tests Sauce Labs' Swag Labs application using a compatibility matrix, exploratory artifacts, and Playwright automation across Chromium, Firefox, installed Edge, and mobile/tablet layouts.

02 / THE SYSTEM AT A GLANCE

Follow the flow.

01User journeys
02Browser matrix
03Automated checks
04Failure evidence
05Release decision

A simplified architecture overview. The repository documents the implementation details.

03 / THE ENGINEERING DECISIONS

Why it's built this way.

Trace tests to risk

Test IDs connect automation to the compatibility matrix. Defects include reproducible evidence; a release-readiness report communicates coverage and unresolved risk.

Preserve failures

Screenshots, videos, and traces attach to failed runs. CI publishes evidence even when the suite fails so findings remain inspectable.

Track known defects explicitly

Seeded defects use expected-failure handling. An unexpected pass prompts removal of a stale record. Rendering-engine tests do not stand in for branded Safari coverage.

04 / WHAT TO LOOK AT

Evidence over adjectives.

EvidenceTrace + video

Failure artifacts preserve steps and browser context.

ScopeCross-browser

Chromium, Firefox, and explicit installed Edge execution.

DecisionRisk based

A release-readiness report connects results to remaining risk.

Capabilities and result snapshots follow the project's current README, reviewed October 10, 2026. Read the source

Compatibility matrix Release assessment Defect reports

05 / THE HONEST PART

What I'd improve next.

Current boundaries

Swag Labs is third-party software; the contribution showcased is the testing work.
Real Safari needs a macOS runner and remains a coverage opportunity.
The remote CI result must be inspected before claiming that a published run passed.

The next iteration

Extend branded Safari coverage and use repeated critical-path runs to investigate flakiness.

Open my SQA & Testing CV

KEEP EXPLORING

EDiME

Look beyond a convincing image.