013 ‐ Independent Software Testing Live Project (Part 6) ‐ Test Scenarios - rkb-sdet/SoftwareTesting GitHub Wiki

📘 Session 13 – Independent Software Testing (Live Project Part 6)

Topic: Test Scenarios -

1. Context of the Project

  • We are working on a Live E-commerce Web Application (TutorialsNinja).
  • Project phases so far:
  1. Step 1: Project Initiation (how projects begin)
  2. Step 2: Application Exploration (understanding & listing functionalities manually)
  3. Step 3: Test Plan creation (scope, approach, features in/out scope, etc.) - Mistake corrected: Client name should be mentioned, not your company name.
  4. Step 4 (Current): Creation of Test Scenarios

2. What are Test Scenarios?

  • Definition: A test scenario represents “What to test”.
  • Use: Helps identify the areas/features of the application to be tested.
  • Relation to Test Cases:
    • Scenarios → High-level description of what to test
    • Test Cases → Detailed steps on how to test each scenario

📌 Example:

  • Scenario: Verify the Register Account functionality
  • Test Cases: Multiple cases like "Register with valid details", "Register without entering password", etc.

3. Placement of Test Scenarios

  • Can be included inside a Test Plan document or maintained as a separate Test Scenarios document.
  • Depends on company practice.

For this project → A separate Test Scenarios Document is prepared.

4. Metadata for Test Scenarios Document

  • Project Name: TutorialsNinja Web Application
  • Client: TutorialsNinja
  • Reference Document: Application URL (No formal business requirement doc provided)
  • Created By: Solaytic (Arun Motoori)
  • Creation Date: Dec 14, 2020
  • Approval Date: Dec 16, 2020 (after client review)

5. Priority System Used

  • P0 – Highest (must-have features, core functionality)
  • P1 – High but not critical
  • P2 – Medium importance
  • P3 – Low but nice-to-have
  • P4 – Lowest, optional

💡 Priorities suggested by the tester are tentative. Final decision rests with the client/business stakeholders.

6. Test Scenarios for TutorialsNinja

(Derived from Transcript + Excel file)

Scenario ID Test Scenario Description Priority
TS_001 Verify Register Account functionality P0
TS_002 Verify Login functionality P0
TS_003 Verify Logout functionality P0
TS_004 Verify Forgot Password functionality P2
TS_005 Verify Search functionality P1
TS_006 Verify Product Compare functionality P3
TS_007 Verify Product Display pages for different product types P1
TS_008 Verify Add to Cart functionality P0
TS_009 Verify Wish List functionality P3
TS_010 Verify Shopping Cart functionality P1
TS_011 Verify application functionalities with different currencies P2
TS_012 Verify Home Page P1
TS_013 Verify Checkout functionality P1
TS_014 Verify My Account → Account Information P3
TS_015 Verify My Account → Password Change P3
TS_016 Verify My Account → Address Book P3
TS_017 Verify My Account → Order History P2
TS_018 Verify My Account → Downloads P4
TS_019 Verify My Account → Reward Points P4
TS_020 Verify My Account → Return Requests P3
TS_021 Verify My Account → Transaction History P4
TS_022 Verify My Account → Recurring Payments P3
TS_023 Verify My Account → Affiliate P4
TS_024 Verify My Account → Newsletter P4
TS_025 Verify Contact Us page P4
TS_026 Verify Menu Options P3
TS_027 Verify Footer Options P3
TS_028 Verify Category Pages P2

7. Key Learnings from Session

  • Scenarios vs Test Cases:
    • Scenarios = What to test
    • Test Cases = How to test
  • Scenarios ensure complete coverage of application functionalities.
  • Always review Test Scenarios with the client before proceeding to Test Case design.
  • Document should have version control & approval date.
  • Priorities should be suggested by testers, but finalized by business/client.

8. Next Steps

  • From these 28 scenarios, multiple Test Cases will be derived in upcoming sessions.
  • Each scenario may produce several test cases (covering positive, negative, and edge cases).
  • Once prepared → The Test Scenarios document is sent for client review → Final approval → Proceed to Test Case design.

✅ Summary

In this session, we:

  1. Recapped progress till now (Exploration → Test Plan → Scenarios).
  2. Learned that test scenarios define high-level functionalities to be tested.
  3. Created a separate Test Scenarios document for TutorialsNinja application.
  4. Mapped 28 scenarios with priorities (P0–P4).
  5. Understood the importance of client review and approval.
flowchart TD
    TN["TutorialsNinja Web Application"]
    TN --> TS["Test Scenarios"]

    TS --> AC["Account Features"]
    TS --> CA["Cart Features"]
    TS --> CH["Checkout"]
    TS --> PR["Product Features"]
    TS --> SE["Search"]
    TS --> CU["Currencies"]
    TS --> PA["Pages"]
    TS --> OT["Other Functionalities"]
    
    %% Account Features
    AC --> S01["Register Account"]
    AC --> S02["Login"]
    AC --> S03["Logout"]
    AC --> S04["Forgot Password"]
    AC --> S14["Account Info"]
    AC --> S15["Password Change"]
    AC --> S16["Address Book"]
    AC --> S17["Order History"]
    AC --> S18["Downloads"]
    AC --> S19["Reward Points"]
    AC --> S20["Return Requests"]
    AC --> S21["Transaction History"]
    AC --> S22["Recurring Payments"]
    AC --> S23["Affiliate"]
    AC --> S24["Newsletter"]

    %% Cart Features
    CA --> S08["Add to Cart"]
    CA --> S09["Wish List"]
    CA --> S10["Shopping Cart"]

    %% Checkout
    CH --> S13["Checkout"]

    %% Product Features
    PR --> S06["Product Compare"]
    PR --> S07["Product Display Pages"]

    %% Search
    SE --> S05["Search"]

    %% Currencies
    CU --> S11["Functions with Different Currencies"]

    %% Pages
    PA --> S12["Home Page"]
    PA --> S25["Contact Us"]
    PA --> S28["Category Pages"]

    %% Other Functionalities
    OT --> S26["Menu Options"]
    OT --> S27["Footer Options"]