Test Plan ‐ Swag Labs - rodroidrx/SwagLabs GitHub Wiki

Test Plan: Swag Labs E-commerce Website

Project Name: Swag Labs E-commerce Platform Version: 1.0 Date: July 5, 2025 Author: Roan Hidalgo (Robot Test Labs Inc)

1. Introduction

This document outlines the test plan for the SwagStore E-commerce Website, a platform designed for users to browse, select, and purchase various products. The goal of this testing is to ensure the website functions correctly, meets all specified requirements, provides a positive user experience, and is free of critical defects.

2. Test Objectives

Verify all core e-commerce functionalities (user authentication, product Browse, cart management, checkout process) are working as expected. Ensure the website is responsive and functions correctly across different browsers and devices. Validate data integrity and security measures. Confirm user interface (UI) and user experience (UX) elements are intuitive and visually appealing. Identify and report all defects to the development team for resolution.

3. Scope of Testing

3.1. In-Scope:

  • User Management:
  • User Registration (if applicable)
  • User Login/Logout (Standard, Locked Out, Problem User, Performance Glitch User)
  • Password Reset (if applicable)
  • User Profile Management (if applicable)
  • Product Catalog:
  • Product Browse and Filtering (Name, Price)
  • Product Details View
  • Product Search (if applicable)
  • Image Display
  • Shopping Cart:
  • Adding/Removing items from the cart
  • Updating item quantities
  • Viewing cart contents
  • Checkout Process:
  • Entering Shipping Information (First Name, Last Name, Postal Code)
  • Order Summary review
  • Payment simulation (as per Swag Labs' simplified model)
  • Order Confirmation
  • Navigation:
  • Header, Footer, and Sidebar navigation links
  • Back/Forward button functionality
  • Error Handling:
  • Validation messages for invalid inputs
  • Error pages for unavailable resources
  • Security:
  • Basic authentication checks (e.g., handling invalid credentials)

3.2. Out-of-Scope Integration with external payment gateways (Swag Labs uses a simulated payment) Detailed backend database testing (focused on frontend interaction and data display) Extensive penetration testing (basic security checks are in scope) User analytics and tracking validation (unless specifically a requirement) Third-party API integrations beyond what is directly visible on the front end

4. Test Strategy

4.1. Test Types

  • Functional Testing: Verifying all features and functionalities as per requirements.
  • UI/UX Testing: Ensuring the user interface is visually appealing, consistent, and provides a good user experience.
  • Compatibility Testing: Checking website compatibility across different browsers and devices.
  • Regression Testing: Re-running existing tests to ensure new changes haven't introduced defects in existing functionalities.
  • Exploratory Testing: Ad-hoc testing to discover issues not covered by formal test cases.

4.2. Test Levels

  • System Testing: Testing the complete integrated system.
  • User Acceptance Testing (UAT): Business users will perform final validation to ensure the system meets their needs.

4.3. Test Data Management Pre-defined test users (e.g., standard_user, locked_out_user, problem_user, performance_glitch_user as per Swag Labs). Sample product data with various attributes (price, description, images). Valid and invalid shipping information.

5. Test Environment

  • Operating Systems: Windows 10/11, macOS (latest two versions), Android (latest two versions), iOS (latest two versions).
  • Browsers:
  • Chrome (latest stable version)
  • Firefox (latest stable version)
  • Edge (latest stable version)
  • Safari (latest stable version)
  • Devices:
  • Desktop/Laptop (various screen resolutions)
  • Test URL: www.saucedemo.com (or the equivalent internal staging/QA environment)

6. Test Deliverables

  • Test Plan Document (this document)
  • Test Cases
  • Test Data
  • Test Summary / Defect Report
  • Traceability Matrix (linking requirements to test cases)

7. Roles and Responsibilities

  • QA Lead: Overall test strategy, plan approval, resource allocation, reporting.
  • QA Engineers: Test case design, execution, defect reporting, regression testing.
  • Developers: Defect fixing, unit testing.
  • Product Owner/Business Analyst: Requirement clarification, UAT.

8. Entry and Exit Criteria

8.1. Entry Criteria (for System Testing)

  • All major features are developed and deployed to the testing environment.
  • Smoke tests have been executed successfully.
  • Test environment is stable and accessible.
  • Test data is prepared and available.
  • Test cases are reviewed and approved.

8.2. Exit Criteria (for System Testing)

  • All critical and high-priority defects are resolved and retested.
  • All test cases (or a defined percentage, e.g., 95%) have been executed.
  • Test coverage goals are met.
  • No open blocking or major issues remain.
  • Test summary report is signed off.