QA Project

E-commerce Website Testing

Web testing case study that also demonstrates full QA documentation flow in TestRail / Confluence style: planning, detailed test cases, checklist coverage, bug reporting, and summary reporting.

Overview

I tested an e-commerce user flow from catalog to order confirmation with focus on business-critical purchase behavior.

The work included smoke and regression coverage, adaptive layout checks, browser compatibility review, and investigation of UI issues with Chrome DevTools, HTML, CSS, and database validation.

I also used this case to show how I maintain test documentation across the full QA lifecycle. The documentation flow included planning notes, structured test cases, responsive checklist items, defect reports, and a final summary report prepared in a TestRail / Confluence-style workflow.

  • Prepared scope and coverage notes before execution so the critical checkout flow was testable and traceable
  • Maintained detailed test cases and checklist coverage suitable for TestRail execution runs
  • Documented defects in a format that developers and product managers could act on quickly
  • Summarized executed coverage, open risks, and release readiness in a concise report after testing

This makes the project useful not only as a web-testing example, but also as evidence that I can keep documentation consistent from planning through reporting.

Project details

Goal: Ensure the catalog, cart, and checkout flow works correctly for desktop and mobile users and that high-risk issues are found and documented clearly before release.

Scope: Catalog, product page, cart, checkout, validation messages, order confirmation, UI-data consistency, and the full documentation lifecycle from planning to summary reporting.

Key findings: Detected layout breaks on tablet width, stale cart totals on mobile, inconsistent coupon validation, and an order-summary mismatch between UI and backend data. Coverage and defects were recorded in a structured TestRail / Confluence-style documentation flow.

Result / impact: Critical checkout and mobile issues were fixed before release, while the documentation package made coverage, open risks, and release status clear for the team.

Testing types

  • Functional testing

Artifacts

  • QA Documentation Flow in TestRail and Confluence

Tools

  • Chrome DevTools