Manual Testing Documentation for Banglashoppers

This repository contains manual testing documentation for Banglashoppers. The testing process was done using an Excel sheet, which contains test scenarios, test cases, bug reports, test reports, and test metrics.

Table of Contents

1. Overview
2. Test Plan
3. Test Scenarios
4. Test Cases
5. Bug Reports
6. Test Report
7. Test Metrics
8. How to Use
9. Contributing

---

Overview

Manual testing is performed to ensure the quality and correctness of the application. The testing process covered various functional and non-functional aspects of the system. The Excel sheet includes a detailed breakdown of the following:

• Test Plan: Outlines the strategy, scope, resources, and schedule for verifying the functionality, usability, and reliability of a system through human-executed tests.
• Mind Map: Visually organizes the key functionalities, user flows, and test areas of an application, highlighting the connections between different features and the corresponding test cases to ensure comprehensive coverage.
• Test Scenarios: High-level actions or objectives to be verified during testing.
• Test Cases: Step-by-step instructions to validate the correct behavior of specific features.
• Bug Reports: Documented defects or issues encountered during testing.
• Test Report: Summary of the test execution status.
• Test Metrics: Quantitative measurements to evaluate the quality of testing.

---

Test Plan

The Test Plan for Banglashoppers outlines the strategy, scope, and approach for testing the website. The goal is to ensure that the website functions smoothly, providing a reliable and secure shopping experience. Key aspects include:

Objective

Validate the core functionalities such as account management, product browsing, checkout, and payment processing to ensure seamless performance and usability across devices and browsers.

Test Strategy

Manual testing with a focus on:

• Functional testing
• Non-functional testing
• Usability testing
• Performance testing
• Security testing
• Compatibility testing

Scope of Testing

Covers critical functionalities including:

• User registration
• Product browsing
• Shopping cart management
• Payment gateway integration
• Customer support

Test Environment

Testing is conducted on:

• Devices: Desktop, mobile, and tablet
• Browsers: Chrome, Firefox, Safari, and Edge
• Network Conditions: 3G, 4G, Wi-Fi

Defect Management

Issues found during testing will be logged and prioritized by severity to be fixed accordingly.

---

Test Scenarios

The test scenarios are high-level descriptions of what needs to be tested. Each scenario addresses specific features or functionalities of the application.

• Scenario ID: Unique identifier for each scenario.
• Scenario Description: A brief explanation of the feature or process to be tested.
• Pre-Conditions: Any setup that must be completed before running the test.
• Expected Outcome: What the system should do if it’s functioning correctly.

---

Test Cases

Test cases include detailed instructions for testing specific scenarios. Each test case consists of:

• Test Case ID: Unique identifier for the test case.
• Test Scenario ID: The scenario ID to which the test case belongs.
• Steps to Execute: The detailed steps to perform the test.
• Expected Result: The anticipated result after executing the test.
• Actual Result: The observed result after running the test.
• Status: Pass/Fail based on the actual result.

---

Bug Reports

During testing, bugs and issues were recorded with the following details:

• Bug ID: Unique identifier for the bug.
• Description: A brief description of the issue.
• Severity: The impact of the bug on the application (e.g., Critical, Major, Minor).
• Steps to Reproduce: Steps followed that led to the bug.
• Expected Behavior: What should have happened instead.
• Actual Behavior: What actually happened.
• Status: Current state of the bug (e.g., Open, Fixed, Closed).

---

Test Report

The test report provides a summary of the test execution, including the status of each test case:

• Total Test Cases Executed: Number of test cases run during the testing phase.
• Passed Test Cases: Number of test cases that passed successfully.
• Failed Test Cases: Number of test cases that failed.
• Pending Test Cases: Test cases that were not executed during the test cycle.
• Blocked Test Cases: Test cases that could not be executed due to issues or blockers.

---

Test Metrics

Test metrics are quantitative indicators of the effectiveness of the testing process. Key metrics include:

• Test Coverage: Percentage of requirements or functionalities covered by the test cases.
• Defect Density: Number of defects found per unit of functionality tested.
• Defect Severity Distribution: Breakdown of defects by severity (Critical, Major, Minor).
• Test Case Execution Rate: Percentage of test cases executed within the test cycle.

---

How to Use

1. Download the Excel file from this repository.
2. Open the file and navigate through the different sheets (Test Scenarios, Test Cases, Bug Reports, Test Report, Test Metrics) to get an understanding of the testing process.
3. Follow the documentation to see the detailed results and outcomes of the manual testing process.

---