Test Plan
Project: SauceDemo Manual Testing Project
Version: 1.0
Prepared by: Filip Jelinek
Date: June 2026
In-page Navigation
1. Introduction
This Test Plan defines the strategy, objectives, scope, resources,
and approach for manually testing the SauceDemo web application.
The purpose of this document is to ensure that testing activities are
planned, executed, and documented in a structured and repeatable manner
while validating the application’s core functionality and identifying
potential defects.
2. Objectives
The objectives of this testing project are to:
- Verify that core application features work as intended.
- Validate critical user workflows.
- Identify functional defects and usability issues.
- Confirm that the application behaves consistently under normal user
interactions.
- Produce professional QA documentation demonstrating
industry-standard testing practices.
3. Application Under Test
Application: SauceDemo
URL: https://www.saucedemo.com/
Application Type: Web Application
Domain: E-commerce
4. Scope
In Scope
The following functionality will be tested:
- User Login
- Product Inventory
- Product Details
- Shopping Cart
- Product Sorting
- Checkout Process
- Navigation
- Logout
- Form Validation
- Error Messages
Out of Scope
The following areas are not included in this project:
- Performance Testing
- Load Testing
- Stress Testing
- Security Testing
- Accessibility Testing
- Source Code Review
- Automation Testing
5. Test Strategy
Testing will primarily consist of manual functional testing supported
by exploratory testing techniques.
The testing approach includes:
- Functional Testing
- Positive Testing
- Negative Testing
- Boundary Value Testing (where applicable)
- Exploratory Testing
- Regression Testing
- User Interface (UI) Testing
Testing will be performed using predefined test cases while also
exploring unexpected user behavior to identify additional defects.
6. Test Environment
| Item |
Details |
| Operating System |
Windows 11 |
| Browser |
Google Chrome version: 149.0.7827.197 |
| Internet Connection |
Stable broadband connection |
| Test Device |
HP Omen Laptop |
| Application URL |
https://www.saucedemo.com |
7. Test Data
The following test data will be used:
Valid Users
- standard_user
- problem_user
- performance_glitch_user
- error_user
- visual_user
Invalid Data
- Invalid usernames
- Invalid passwords
- Empty username
- Empty password
- Empty login form
8. Entry Criteria
Testing may begin when:
- The application is accessible.
- Test environment is available.
- Test data is prepared.
- Test documentation has been completed.
9. Exit Criteria
Testing will be considered complete when:
- All planned test cases have been executed.
- Critical and High severity defects have been documented.
- Test execution results have been recorded.
- Test Summary Report has been completed.
10. Deliverables
The following documents will be produced:
- Test Plan
- Requirements Analysis
- Test Scenarios
- Test Cases
- Bug Reports
- Test Execution Report
- Test Summary Report
- Test Data
- Screenshots
- Requirements Traceability Matrix
11. Risks
Potential risks include:
- Limited application functionality.
- Test environment instability.
- Browser updates during testing.
- Existing application defects affecting additional test
execution.
12. Assumptions
This project assumes that:
- SauceDemo remains publicly available.
- Test user accounts remain functional.
- No major application changes occur during testing.
13. Test Schedule
| Activity |
Status |
| Test Planning |
Completed |
| Requirements Analysis |
Completed |
| Test Scenario Design |
Completed |
| Test Case Creation |
Completed |
| Test Execution |
Completed |
| Bug Reporting |
Completed |
| Test Summary |
Completed |
14. Approval
This document was prepared as part of a personal QA portfolio project
to demonstrate manual software testing skills and professional
documentation practices.
⬅️ Back to Saucedemo
qa-saucedemo-README.md