Merge pull request #8 from auto-qa-hub/saucedemo-test-plan

add-test-plan

Author: andrew-ksv

TEST_PLAN.md

@@ -0,0 +1,133 @@
+# Test Plan for Automation - SauceDemo
+
+# 1. Introduction
+Link for SauceDemo web application - https://www.saucedemo.com
+
+## 1.1 Objective
+
+The purpose of this test plan is to define the scope, approach, resources, and schedule for the automation of the SauceDemo web application using Playwright with TypeScript. The objective is to ensure functional correctness, performance efficiency, and reliability of critical workflows through automated tests.
+
+## 1.2 Scope
+
+**The test automation will cover:**
+
+🔗 UI Testing of critical user flows
+
+🔗 Functional Testing of authentication, product catalog, and cart operations
+
+🔗 Cross-browser Testing (Chrome, Firefox, WebKit)
+
+# 2. Test Strategy
+
+## 2.1 Test Approach 🎯 
+
+- Utilize Playwright with TypeScript for automation
+
+- Implement Page Object Model (POM) for maintainability
+
+- Execute tests in headless and headed mode for debugging
+
+- Use CI/CD integration for test execution on each deployment
+
+## 2.2 Test Types 🔍
+
+- **Smoke Testing:** Validate basic functionalities (Login, Product List, Add to Cart)
+
+- **Functional Testing:** Verify login, sorting, checkout, and logout flows
+
+- **Regression Testing:** Run all test cases to check for unintended changes
+
+- **Cross-Browser Testing:** Run tests on Chrome, Firefox, and WebKit
+
+# 3. Test Environment
+
+## 3.1 Test Setup
+
+📄 **Framework:** Playwright with TypeScript
+
+📄 **Test Runner:** Playwright Test
+
+📄 **Assertion Library:** Built-in Playwright assertions
+
+📄 **CI/CD Tool:** GitHub Actions
+
+📄 **Browsers:** Chrome, Firefox, WebKit
+
+📄 **Reporting:** Playwright HTML reports / Allure reports
+
+# 4. Test Cases
+
+## 4.1 Test Scenarios
+
+1️⃣ Login Tests 
+- Verify valid login with correct credentials (standard_user)
+- Verify locked user cannot log in (locked_out_user)
+- Verify problem user (problem_user)
+- Verify user with performance glitch (performance_glitch_user)
+- Verify error user (error_user)
+- Verify visual user (visual_user)
+
+2️⃣ Product Catalog Tests
+
+3️⃣ Verify product list displays correctly
+
+4️⃣ Verify sorting functionality (price, name, ascending/descending)
+
+5️⃣ Verify filtering options
+
+5️⃣ Cart & Checkout Tests
+
+7️⃣ Verify items can be added/removed from the cart
+
+8️⃣ Verify checkout flow with valid and invalid details
+
+9️⃣ Logout Test
+
+🔟 Verify successful logout redirects to the login page
+
+# 5. Test Execution Plan
+
+## 5.1 Test Execution Strategy
+
+- Execute tests locally before pushing to local branch
+- Create pull request
+- Run automated tests on every code commit via CI/CD
+- Push to the main branch changes (if all tests are passed)
+
+## 5.2 Test Execution Schedule
+
+- Every pull request creation
+- After merging chnage sto the main
+
+# 6. Risks & Mitigation
+
+## 6.1 Risks
+
+🛡️ **Flaky Tests:** Due to dynamic elements or network latency
+
+🔄 **Cross-Browser Issues:** Variations in rendering
+
+🔧 **Test Maintenance Overhead:** Frequent UI changes affecting selectors
+
+## 6.2 Mitigation Strategies
+
+- Implement retry strategies in Playwright
+
+- Regular test script reviews and updates
+
+# 7. Reporting & Metrics
+
+## 7.1 Metrics to Track
+
+- Test Execution Time (Avg. duration of test runs)
+
+- Pass/Fail Rate (Percentage of passed vs. failed tests)
+
+## 7.2 Reporting Tools
+
+- Playwright HTML Reports
+- Allure Reports for detailed analysis
+
+# 9. Conclusion
+
+This test plan serves as a roadmap for effectively automating the SauceDemo website using Playwright and TypeScript. By following structured testing strategies, defect management, and risk mitigation, we aim to ensure the quality and reliability of the application while streamlining the testing process.