software Testing Assignment – Week 2
Test Planning & Advanced Testing
Application name (SauceDemo)
Student Name:Khadija Shaikh
Course: Software Testing
Table of Contents
1. Test Plan
2. Bug Report
3. Compatibility & Retesting Report
1. Test Plan
1.1 Objective
The objective of this test plan is to verify the functional behavior, usability, and browser
compatibility of the SauceDemo web application using structured testing techniques. The
goal is to identify defects and ensure the application meets expected requirements.
1.2 Scope
In Scope
• Login functionality
• Product listing page
• Add to cart feature
• Cart management
• Checkout process
• UI validation
• Cross-browser compatibility
Out of Scope
• Performance testing
• Security testing
• API testing
1.3 Testing Approach
The following testing methods were applied:
• Manual Testing
• Black-Box Testing Techniques:
o Boundary Value Analysis (BVA)
o Equivalence Partitioning (EP)
• Exploratory Testing
• Retesting & Verification
1.4 Resources Required
Resource Details
Tester 1 (Self)
Browser, MS Word,
Tools
Excel
Browsers Chrome, Firefox, Edge
1.5 Test Environment
Component Details
Application SauceDemo
URL [Link]
OS Windows 10/11
Browsers Chrome, Firefox, Edge
Network Stable Internet
1.6 Entry Criteria
• Application is accessible
• Test scenarios are prepared
• Test environment is configured
1.7 Exit Criteria
• All test cases executed
• Critical defects identified and retested
• Reports completed
• No unresolved critical issues
1.8 Testing Schedule
Phase Duration
Test Planning 1 Day
Test Design 1 Day
Test Execution 2 Days
Cross-Browser
1 Day
Testing
Retesting & Reporting 1 Day
2. Bug Report
BUG-001 – Login fails with valid credentials on first
attempt
Severity: Critical
Priority: High
Environment: Chrome (latest), Windows 11
Preconditions:
User is on login page
Steps to Reproduce:
1. Open the application
2. Enter username: standard_user
3. Enter password: secret_sauce
4. Click Login
Expected Result:
User should be redirected to the products page
Actual Result:
Login fails on the first attempt; requires second attempt
Status: Open
BUG-002 – Add to Cart button not working in Edge
Severity: High
Priority: High
Environment: Microsoft Edge
Preconditions:
User is logged in
Steps to Reproduce:
1. Login to the application
2. Navigate to Products page
3. Click Add to Cart
Expected Result:
Item should be added and button should change to “Remove”
Actual Result:
Button does not respond
Status: Open
BUG-003 – Cart badge not updating
Severity: Medium
Priority: Medium
Preconditions:
User is logged in
Steps to Reproduce:
1. Add product to cart
2. Observe cart icon
Expected Result:
Cart count should increase
Actual Result:
Cart count does not update
Status: Open
BUG-004 – Checkout allows empty form submission
Severity: High
Priority: High
Preconditions:
Product added to cart
Steps to Reproduce:
1. Go to checkout page
2. Leave fields empty
3. Click Continue
Expected Result:
Validation messages should be displayed
Actual Result:
User proceeds without entering data
Status: Open
BUG-005 – UI misalignment in Firefox
Severity: Low
Priority: Low
Preconditions:
User is logged in
Steps to Reproduce:
1. Open product page in Firefox
2. Observe layout
Expected Result:
UI should be properly aligned
Actual Result:
Images overlap with text
Status: Open
3. Compatibility & Retesting Report
3.1 Cross-Browser Testing Results
Feature Chrome Firefox Edge Remarks
Login Pass Pass Pass Working
Add to Cart Pass Pass Fail Edge issue
Cart
Fail Fail Fail Functional bug
Update
Validation
Checkout Fail Fail Fail
issue
UI Layout Pass Fail Pass Firefox issue
3.2 Retesting Summary
Previous
Bug ID Current Status
Status
BUG-001 Failed Open
BUG-002 Failed Open
BUG-003 Failed Open
BUG-004 Failed Open
BUG-005 Failed Open
3.3 Observations
• Major issues found in cart and checkout functionality
• Cross-browser inconsistency observed in Edge
• UI defect detected in Firefox
• Login functionality shows inconsistent behavior
3.4 Conclusion
The application is partially functional but contains critical defects affecting core features
such as login reliability, cart updates, and checkout validation. These issues must be
resolved before the application can be considered stable for production use.