โ† Back to Freelance Page
ShopEase Inc.
QA Document ยท Test Plan
Test Plan
ShopEase Platform v2.3.0
Release Candidate ยท Sprint 14โ€“16
Document ID
SE-TP-2025-023
Version
1.2 (Final)
Date
15 April 2025
Prepared By
Zeeshan Mustafa
Role
QA Lead
Status
โœ“ Approved
Table of Contents
  1. 1. Introduction & Objectives
  2. 2. Scope
  3. 3. Test Strategy & Approach
  4. 4. Entry & Exit Criteria
  5. 5. Test Environment
  6. 6. Resource & Schedule
  7. 7. Risk Register
  8. 8. Defect Management
  9. 9. Sign-Off

1. Introduction & Objectives

This Test Plan defines the scope, approach, resources, and schedule for testing the ShopEase Platform v2.3.0. The release introduces a redesigned checkout flow, Apple Pay / Google Pay integration, and a new wishlist sharing feature across web and mobile (iOS 17+, Android 11+).

1.1 Objectives

1.2 References

2. Scope

2.1 In Scope

ModuleCoverageType
Checkout Flow (Redesigned)Full E2E including guest + auth userIn Scope
Apple Pay / Google PayIntegration + sandbox payment flowsIn Scope
Wishlist SharingShare via link, social, emailIn Scope
User AuthenticationRegression (login, OTP, SSO)In Scope
Product Search & FiltersRegressionIn Scope
Order ManagementView, cancel, return โ€” regressionIn Scope
Mobile App (iOS & Android)Smoke + new feature validationIn Scope
API Layer (Stripe, order APIs)Contract + integration testingIn Scope

2.2 Out of Scope

AreaReason
Admin / Back-Office PanelOut of Scope No changes in v2.3.0
Third-Party Logistics (FedEx/DHL) IntegrationOut of Scope Scheduled for v2.4.0
Load / Soak TestingOut of Scope Separate performance sprint
Penetration TestingOut of Scope Handled by security team

3. Test Strategy & Approach

3.1 Test Levels

LevelApproachToolingOwnership
UnitComponent-level, white-boxJest, React Testing LibraryDevelopers
IntegrationAPI contract & service integrationPostman / Newman, Playwright APIQA + Backend
System (E2E)Critical user journeys, black-boxPlaywright (Web), XCUITest (iOS), Appium (Android)QA
RegressionAutomated suite on every PRPlaywright CI (GitHub Actions)QA Automation
UATBusiness sign-off on stagingManual, TestRailProduct Owner

3.2 Test Types

4. Entry & Exit Criteria

4.1 Entry Criteria

All conditions must be met before testing begins

4.2 Exit Criteria

Release blocked if any critical condition unmet

5. Test Environment

EnvironmentURL / DetailsPurpose
QA / Stagingstaging.shopease.comPrimary functional + E2E testing
Devdev.shopease.comDeveloper integration smoke tests
Production (pre-launch read-only)shopease.comPost-deploy smoke only
API Sandboxapi-sandbox.shopease.comStripe + payment API tests

5.1 Browser Matrix

BrowserVersionOSPriority
Chrome124+Windows 11, macOS 14P1
Safari17.4+macOS 14, iOS 17P1
Firefox125+Windows 11P2
Edge124+Windows 11P2
Chrome (Android)124+Android 11+P1
Safari (iOS)17+iOS 15+P1

6. Resource & Schedule

PhaseActivitiesStartEndOwner
Test PlanningRequirement analysis, test plan, TC authoring01 Apr 202507 Apr 2025Zeeshan M.
Test Case ReviewPeer review, sign-off08 Apr 202509 Apr 2025QA Lead + PM
Smoke TestingBuild verification on RC-110 Apr 202511 Apr 2025Zeeshan M.
Functional Testing (Sprint 14โ€“15)New features + integration12 Apr 202522 Apr 2025Zeeshan M.
Regression Testing (Sprint 16)Full automated regression run23 Apr 202525 Apr 2025Zeeshan M.
Bug Fix VerificationRetest resolved defects26 Apr 202528 Apr 2025Zeeshan M.
UATBusiness sign-off29 Apr 202501 May 2025Product Owner
Release Sign-OffFinal approval & deploy02 May 202502 May 2025All stakeholders

7. Risk Register

#RiskLikelihoodImpactMitigation
R-01Stripe sandbox instability during payment testsMediumHighUse mock server (WireMock) as fallback; schedule tests off-peak hours.
R-02iOS XCUITest flakiness on async payment sheetMediumMediumAdd explicit waits for Apple Pay sheet, retry logic max 2x.
R-03Late delivery of RC build (>1 day delay)LowHighPrioritise P1 test cases; compress schedule by parallelising mobile + web runs.
R-04Test data inconsistency (product stock changes)MediumLowSeed dedicated test product catalogue; isolate from production data.
R-05Cross-browser CSS regression in checkout redesignMediumMediumRun visual regression snapshots (Playwright Snapshot) on P1 browsers.

8. Defect Management

8.1 Severity & Priority Definitions

SeverityDefinitionResponse SLA
P0 BlockerSystem crash, data loss, payment failure, cannot proceed testingFix & retest within 4 hours
P1 CriticalCore feature broken, no workaround, major UX failureFix & retest same day
P2 MajorFeature degraded, workaround exists, significant UX impactFix within 2 business days
P3 MinorCosmetic issue, minor UX glitch, edge case onlyFix in next sprint or defer

8.2 Bug Lifecycle

New โ†’ In Progress โ†’ Fixed โ†’ Ready for Retest โ†’ Closed / Reopened. All defects tracked in JIRA project SE. Bug reports follow template SE-BUG-TEMPLATE-001.

9. Sign-Off

By signing below, the parties confirm they have reviewed this Test Plan and agree to the scope, schedule, and exit criteria defined herein.

Role Name Signature Date
QA Lead Zeeshan Mustafa ____ / ____ / 2025
Product Owner Sarah Mitchell ____ / ____ / 2025
Engineering Lead Ahmed Al-Farsi ____ / ____ / 2025
Project Manager Lena Kovaฤ ____ / ____ / 2025