Skip to content

SabbirMamun12/fabriclagbe-manual-testing

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

3 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Fabriclagbe manual testing(Test plan, Schedule, Mindmaps, Test cases, Jira & Test Metrix)

In this Fabriclagbe manual testing project, I covered the topics Test Plans, Test Schedules, Mindmaps, Test Cases, Reports, and JIRA

Table of Contents:

• Introduction

• Test Plan

• Test Schedule

• Test Mindmaps

• Test Cases

• Test Report

• Bug Report (JIRA)

Introduction:

In the manual testing project, it is difficult to have a well-defined test plan, manageable test schedule, visualization of the project using a mind map, meaningful test cases, understandable reports and hazel-free bug reports using jira. This project aims to provide all the things.

Test Plan:

This test plan is a rule book for testing the project. It describes the scope and approach also. The plan identifies the risk of the product and also helps to mitigate the risk. This Test plan contains:

• Analyse the product

• Develop a test strategy

• Define test objective

• Define test criteria

• Resource planning

• Test environment

• Estimation

• Release and test deliverables

Test Schedule:

This test schedule is a list of activities, tasks, or events of the test process, identifying their intended start and finish dates and/or times, and interdependencies.

Demo

Screenshot (34)

Screenshot (35)

Mindmaps:

These mindmaps serve as a visual aid to understand the test coverage, dependencies between different features, modules and potential areas of focus during testing.

Demo

Screenshot (33)

Test Cases:

These test cases are designed to verify that the application is operating as expected. Each test case should include the following information:

• Test case ID

• Test case description

• Expected result

• Actual result

• Test data

• Reproducing steps

• Bug Screenshots

• Status

Demo

Screenshot (40)

Test Report:

In this Reports may include defect reports, test execution reports, test summary reports, and any other relevant documentation.

Demo

Screenshot (41)

Bug Report (JIRA):

Jira is the most effective tool for tracking & reporting bugs. In this project Jira for reporting the bug to the developer and track the bug also.

Demo

Screenshot (39)