├── .gitattributes ├── Manual Testing (BD Shop) ├── TestCase_BD-SHOP.xlsx └── README.md ├── Manual Testing (Mimo mobile app) ├── TestCase_Mimo.xlsx └── README.md ├── Manual Testing (Bikroy.com) ├── TestCase_Bikroy.com.xlsx └── README.md ├── Manual Testing (BetterReturn) └── TestCase_BetterReturn.xlsx ├── Manual Testing (Rokomari.com) ├── TestCase_Rokomari.com.xlsx └── README.md ├── Manual Testing (Sololearn Mobile App) └── TestCase_SoloLearn.xlsx └── README.md /.gitattributes: -------------------------------------------------------------------------------- 1 | # Auto detect text files and perform LF normalization 2 | * text=auto 3 | -------------------------------------------------------------------------------- /Manual Testing (BD Shop)/TestCase_BD-SHOP.xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/An-Nihal/Manual-Testing--Test-Cases-with-Scenarios--Mindmaps--Reports---Test-Metrics-/HEAD/Manual Testing (BD Shop)/TestCase_BD-SHOP.xlsx -------------------------------------------------------------------------------- /Manual Testing (Mimo mobile app)/TestCase_Mimo.xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/An-Nihal/Manual-Testing--Test-Cases-with-Scenarios--Mindmaps--Reports---Test-Metrics-/HEAD/Manual Testing (Mimo mobile app)/TestCase_Mimo.xlsx -------------------------------------------------------------------------------- /Manual Testing (Bikroy.com)/TestCase_Bikroy.com.xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/An-Nihal/Manual-Testing--Test-Cases-with-Scenarios--Mindmaps--Reports---Test-Metrics-/HEAD/Manual Testing (Bikroy.com)/TestCase_Bikroy.com.xlsx -------------------------------------------------------------------------------- /Manual Testing (BetterReturn)/TestCase_BetterReturn.xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/An-Nihal/Manual-Testing--Test-Cases-with-Scenarios--Mindmaps--Reports---Test-Metrics-/HEAD/Manual Testing (BetterReturn)/TestCase_BetterReturn.xlsx -------------------------------------------------------------------------------- /Manual Testing (Rokomari.com)/TestCase_Rokomari.com.xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/An-Nihal/Manual-Testing--Test-Cases-with-Scenarios--Mindmaps--Reports---Test-Metrics-/HEAD/Manual Testing (Rokomari.com)/TestCase_Rokomari.com.xlsx -------------------------------------------------------------------------------- /Manual Testing (Sololearn Mobile App)/TestCase_SoloLearn.xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/An-Nihal/Manual-Testing--Test-Cases-with-Scenarios--Mindmaps--Reports---Test-Metrics-/HEAD/Manual Testing (Sololearn Mobile App)/TestCase_SoloLearn.xlsx -------------------------------------------------------------------------------- /Manual Testing (BD Shop)/README.md: -------------------------------------------------------------------------------- 1 | 2 | # Manual Testing (BD Shop) 3 | 4 | This repository contains test artifacts for the Manual Testing of the BD Shop project, an ecommerce web application. The focus of this testing effort has been on the sign up and sign in modules. The repository includes mindmaps, test execution reports, test cases, and test metrics to effectively plan, execute, and track the testing activities for the BD Shop application. 5 | 6 | 7 | ## Table of Contents 8 | 9 | - Introduction 10 | - Project Overview 11 | - Test Artifacts 12 | - Contributing 13 | - FAQ 14 | ## Introduction 15 | Manual testing plays a vital role in ensuring the quality of the BD Shop ecommerce web application. This repository serves as a centralized resource for storing and organizing test artifacts related to the sign up and sign in modules. The test artifacts include mindmaps, test execution reports, test cases, and test metrics. 16 | ## Project Overview 17 | The BD Shop project is an ecommerce web application aimed at providing a seamless shopping experience to users in Bangladesh. The application allows users to sign up for an account, sign in to their existing account, and perform various actions such as browsing products, adding items to the cart, and making purchases. 18 | ## Test Artifacts 19 | The following test artifacts are included in this project: 20 | - Mindmaps 21 | - Test Execution Report 22 | - Test Cases 23 | - Test Metrics 24 | ## Contributing 25 | Contributions are welcome to enhance the repository with additional test artifacts, such as test cases, mindmaps, test execution reports, or test metrics, related to other modules of the BD Shop application. If you have any improvements or suggestions, please feel free to open an issue or submit a pull request. Please follow the repository's code of conduct and licensing terms. 26 | ## FAQ 27 | 28 | #### Q1: How can I contribute to this project? 29 | 30 | Answer: Contributions are welcome! You can contribute by adding new test cases, scenarios, mindmaps, reports, or test metrics to the respective directories. Simply open an issue or submit a pull request with your proposed changes. 31 | 32 | #### Q2: Can I use the test cases and scenarios provided in this repository for my own projects? 33 | 34 | Answer: Absolutely! The test cases and scenarios in this repository are meant to be shared and used as a reference for manual testing projects. Feel free to adapt and utilize them for your own testing efforts. 35 | 36 | #### Q3: Is there a specific format or template to follow for test cases? 37 | 38 | Answer: While there isn't a strict template to follow, we recommend including the test case ID, description, pre-requisites, test steps, and expected results. You can also add any additional fields that are relevant to your project. Consistency in format across test cases will make it easier to navigate and understand the test suite. 39 | 40 | #### Q4: Are all Test processes integrated in one file? 41 | 42 | Answer: Yes. In the excel file you can see test cases, scenarios, mindmaps, test report and test metrics. All in one. 43 | 44 | -------------------------------------------------------------------------------- /Manual Testing (Bikroy.com)/README.md: -------------------------------------------------------------------------------- 1 | 2 | # Manual Testing (Bikroy.com) 3 | 4 | This repository contains test artifacts for the Manual Testing of the Bikroy.com project, an ecommerce web application. The focus of this testing effort has been on the sign up and login modules. The repository includes mindmaps, test scenarios, test execution reports, test cases, and test metrics to effectively plan, execute, and track the testing activities for the Bikroy.com application. 5 | 6 | 7 | ## Table of Contents 8 | 9 | - Introduction 10 | - Project Overview 11 | - Test Artifacts 12 | - Contributing 13 | - FAQ 14 | ## Introduction 15 | Manual testing plays a crucial role in ensuring the quality and reliability of the Bikroy.com ecommerce web application. This repository serves as a centralized resource for storing and organizing test artifacts related to the sign up and login modules. The test artifacts include mindmaps, test scenarios, test execution reports, test cases, and test metrics. 16 | ## Project Overview 17 | Bikroy.com is an ecommerce web application that enables users to buy and sell products conveniently. The application provides features such as user registration, login, product listing, searching, and purchasing. The sign up and login modules are essential components of the application's functionality and security. 18 | ## Test Artifacts 19 | The following test artifacts are included in this project: 20 | - Mindmaps 21 | - Test Scenarios 22 | - Test Execution Report 23 | - Test Cases 24 | - Test Metrics 25 | ## Contributing 26 | Contributions are welcome to enhance the repository with additional test artifacts, such as test cases, mindmaps, test execution reports, or test metrics, related to other modules of the Bikroy.com web application. If you have any improvements or suggestions, please feel free to open an issue or submit a pull request. Please follow the repository's code of conduct and licensing terms. 27 | ## FAQ 28 | 29 | #### Q1: How can I contribute to this project? 30 | 31 | Answer: Contributions are welcome! You can contribute by adding new test cases, scenarios, mindmaps, reports, or test metrics to the respective directories. Simply open an issue or submit a pull request with your proposed changes. 32 | 33 | #### Q2: Can I use the test cases and scenarios provided in this repository for my own projects? 34 | 35 | Answer: Absolutely! The test cases and scenarios in this repository are meant to be shared and used as a reference for manual testing projects. Feel free to adapt and utilize them for your own testing efforts. 36 | 37 | #### Q3: Is there a specific format or template to follow for test cases? 38 | 39 | Answer: While there isn't a strict template to follow, we recommend including the test case ID, description, pre-requisites, test steps, and expected results. You can also add any additional fields that are relevant to your project. Consistency in format across test cases will make it easier to navigate and understand the test suite. 40 | 41 | #### Q4: Are all Test processes integrated in one file? 42 | 43 | Answer: Yes. In the excel file you can see test cases, scenarios, mindmaps, test report and test metrics. All in one. 44 | 45 | -------------------------------------------------------------------------------- /Manual Testing (Rokomari.com)/README.md: -------------------------------------------------------------------------------- 1 | 2 | ## Manual Testing (Rokomari.com) 3 | 4 | Welcome to the Manual Testing (Rokomari.com) project repository! This repository contains test artifacts for the manual testing of Rokomari.com—an online bookstore and variety store web application. The focus of this testing effort has been on the Registration and Sign-in modules. The repository includes test cases and a test execution report to effectively plan, execute, and track the testing activities for Rokomari.com. 5 | 6 | 7 | ## Table of Contents 8 | 9 | - Introduction 10 | - Project Overview 11 | - Test Artifacts 12 | - Contributing 13 | - FAQ 14 | ## Introduction 15 | Manual testing plays a critical role in ensuring the quality and reliability of Rokomari.com—an online bookstore and variety store web application. This repository serves as a centralized resource for storing and organizing test artifacts related to the Registration and Sign-in modules. The test artifacts include test cases and a test execution report. 16 | ## Project Overview 17 | Rokomari.com is a web application that offers an extensive collection of books and a variety of products. It provides users with the ability to browse, search, and purchase books, as well as other items available in the online store. The Registration and Sign-in modules are key components of the application, enabling users to create accounts, log in, and access personalized features. 18 | ## Test Artifacts 19 | The following test artifacts are included in this project: 20 | - Test Cases 21 | - Test Execution Report 22 | ## Contributing 23 | Contributions are welcome to enhance the repository with additional test artifacts, such as test cases, test execution reports, or other related modules of the Rokomari.com application. If you have any improvements or suggestions, please feel free to open an issue or submit a pull request. Your contributions will help ensure the overall quality and reliability of Rokomari.com. 24 | ## FAQ 25 | 26 | #### Q1: How can I contribute to this project? 27 | 28 | Answer: Contributions are welcome! You can contribute by adding new test cases, scenarios, mindmaps, reports, or test metrics to the respective directories. Simply open an issue or submit a pull request with your proposed changes. 29 | 30 | #### Q2: Can I use the test cases and scenarios provided in this repository for my own projects? 31 | 32 | Answer: Absolutely! The test cases and scenarios in this repository are meant to be shared and used as a reference for manual testing projects. Feel free to adapt and utilize them for your own testing efforts. 33 | 34 | #### Q3: Is there a specific format or template to follow for test cases? 35 | 36 | Answer: While there isn't a strict template to follow, we recommend including the test case ID, description, pre-requisites, test steps, and expected results. You can also add any additional fields that are relevant to your project. Consistency in format across test cases will make it easier to navigate and understand the test suite. 37 | 38 | #### Q4: Are all Test processes integrated in one file? 39 | 40 | Answer: Yes. In the excel file you can see test cases, scenarios, mindmaps, test report and test metrics. All in one. 41 | 42 | -------------------------------------------------------------------------------- /Manual Testing (Mimo mobile app)/README.md: -------------------------------------------------------------------------------- 1 | 2 | # Manual Testing (Mimo mobile application) 3 | 4 | Welcome to the Manual Testing (Mimo Mobile App) project repository! This repository contains test artifacts for the manual testing of the Mimo mobile application—an education-based app that allows users to learn coding and programming in various languages such as Python, JavaScript, HTML, and more. The focus of this testing effort has been on the Python Basics module. The repository includes test cases, a test execution report, and test metrics to effectively plan, execute, and track the testing activities for the Mimo mobile app. 5 | 6 | 7 | ## Table of Contents 8 | 9 | - Introduction 10 | - Project Overview 11 | - Test Artifacts 12 | - Contributing 13 | - FAQ 14 | ## Introduction 15 | Manual testing plays a vital role in ensuring the quality and functionality of the Mimo mobile app—an interactive platform for learning coding and programming. This repository serves as a centralized resource for storing and organizing test artifacts related to the Python Basics module. The test artifacts include test cases, a test execution report, and test metrics. 16 | ## Project Overview 17 | The Mimo mobile app is designed to provide an engaging learning experience for users who want to acquire coding and programming skills. With various modules focusing on different programming languages, the app offers interactive lessons, coding exercises, and quizzes to facilitate the learning process. The Python Basics module specifically targets beginners who want to learn the fundamentals of Python programming. 18 | ## Test Artifacts 19 | The following test artifacts are included in this project: 20 | - Test Cases 21 | - Test Execution Report 22 | - Test Metrics 23 | ## Contributing 24 | Contributions are welcome to enhance the repository with additional test artifacts, such as test cases, test execution reports, or test metrics, related to other modules or languages in the Mimo mobile app. If you have any improvements or suggestions, please feel free to open an issue or submit a pull request. Your contributions will help ensure the overall quality and reliability of the Mimo mobile app. 25 | ## FAQ 26 | 27 | #### Q1: How can I contribute to this project? 28 | 29 | Answer: Contributions are welcome! You can contribute by adding new test cases, scenarios, mindmaps, reports, or test metrics to the respective directories. Simply open an issue or submit a pull request with your proposed changes. 30 | 31 | #### Q2: Can I use the test cases and scenarios provided in this repository for my own projects? 32 | 33 | Answer: Absolutely! The test cases and scenarios in this repository are meant to be shared and used as a reference for manual testing projects. Feel free to adapt and utilize them for your own testing efforts. 34 | 35 | #### Q3: Is there a specific format or template to follow for test cases? 36 | 37 | Answer: While there isn't a strict template to follow, we recommend including the test case ID, description, pre-requisites, test steps, and expected results. You can also add any additional fields that are relevant to your project. Consistency in format across test cases will make it easier to navigate and understand the test suite. 38 | 39 | #### Q4: Are all Test processes integrated in one file? 40 | 41 | Answer: Yes. In the excel file you can see test cases, scenarios, mindmaps, test report and test metrics. All in one. 42 | 43 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | 2 | # Manual Testing (Test Cases with Scenarios, Mindmaps, Reports & Test Metrics) 3 | 4 | This repository contains test cases, scenarios, mindmaps, reports, and test metrics for manual testing projects. It serves as a comprehensive resource for manual testers to effectively plan, execute, and track their testing efforts. 5 | 6 | 7 | ## Table of Contents 8 | 9 | - Introduction 10 | - Test Cases 11 | - Scenarios 12 | - Mindmaps 13 | - Reports 14 | - Test Metrics 15 | - FAQ 16 | ## Introduction 17 | In manual testing, it is crucial to have well-defined test cases, detailed scenarios, visual representations, insightful reports, and meaningful test metrics. This repository aims to provide a centralized location for organizing and documenting these artifacts to enhance the efficiency and effectiveness of manual testing projects. 18 | ## Test Cases 19 | The test-cases directory contains a collection of test cases written for different features or modules of the system under test. Each test case should include the following information: 20 | 21 | - Test case ID 22 | - Test case description 23 | - Pre-requisites 24 | - Test steps 25 | - Expected results 26 | - Actual results (to be filled during test execution) 27 | 28 | Test cases are essential for ensuring thorough test coverage and providing a clear roadmap for manual testing. 29 | ## Scenarios 30 | The scenarios consists of detailed scenarios that represent different user workflows or use cases within the system. Scenarios help testers understand the system's behavior from end-users' perspectives and ensure that all user interactions are thoroughly tested. 31 | ## Mindmaps 32 | The mindmaps contains visual representations in the form of mindmaps. These mindmaps serve as a visual aid to understand the test coverage, dependencies between different features, and potential areas of focus during testing. Testers can use mindmaps to brainstorm ideas, track testing progress, and identify any gaps in their testing efforts. 33 | ## Reports 34 | The reports are dedicated to storing various reports generated during manual testing. Reports may include defect reports, test execution reports, test summary reports, and any other relevant documentation. These reports provide valuable insights into the testing progress, identified issues, and overall test results. 35 | ## Test Metrics 36 | The test-metrics contains metrics and measurements related to manual testing. Testers can track metrics such as test coverage, defect density, test execution time, and other relevant metrics to assess the quality and progress of testing activities. The metrics help identify areas of improvement and provide quantitative data for making informed decisions. 37 | ## FAQ 38 | 39 | #### Q1: How can I contribute to this project? 40 | 41 | Answer: Contributions are welcome! You can contribute by adding new test cases, scenarios, mindmaps, reports, or test metrics to the respective directories. Simply open an issue or submit a pull request with your proposed changes. 42 | 43 | #### Q2: Can I use the test cases and scenarios provided in this repository for my own projects? 44 | 45 | Answer: Absolutely! The test cases and scenarios in this repository are meant to be shared and used as a reference for manual testing projects. Feel free to adapt and utilize them for your own testing efforts. 46 | 47 | #### Q3: Is there a specific format or template to follow for test cases? 48 | 49 | Answer: While there isn't a strict template to follow, we recommend including the test case ID, description, pre-requisites, test steps, and expected results. You can also add any additional fields that are relevant to your project. Consistency in format across test cases will make it easier to navigate and understand the test suite. 50 | 51 | #### Q4: Are all Test processes integrated in one file? 52 | 53 | Answer: Yes. In the excel file you can see test cases, scenarios, mindmaps, test report and test metrics. All in one. 54 | 55 | --------------------------------------------------------------------------------