Scribd
Upload
13 views7 pages

Test Plan - WebShop

The document outlines a test plan for the Demo Web Shop project, detailing the scope, schedule, roles, responsibilities, and deliverables for testing the web application. It includes a list of features to be tested, assumptions, risk management strategies, and exit criteria for successful testing. The plan specifies the tools and environments to be used, as well as the process for defect management and reporting.

Uploaded by

shahbhumikak
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
13 views7 pages

Test Plan - WebShop

The document outlines a test plan for the Demo Web Shop project, detailing the scope, schedule, roles, responsibilities, and deliverables for testing the web application. It includes a list of features to be tested, assumptions, risk management strategies, and exit criteria for successful testing. The plan specifies the tools and environments to be used, as well as the process for defect management and reporting.

Uploaded by

shahbhumikak
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

Test Plan:

Product Name: Demo Web Shop

Prepared by : Bhumika Shah


Date : 11/10/2022
Table of contents:
Overview

Scope/Out of Scope

Assumptions

Schedules:

Roles and Responsibilities:

Deliverables

Environments

Tools

Risk and Risk Management

Exit Criteria
Overview:
As part of the project, ‘Webshop’ is the web application with the URL
https://demowebshop.tricentis.com/

Webshop is the online shopping web site.

This document serves as high level test planning document with details on the scope of the
project, test schedule and resource requirements, test deliverables, risk and management.

Scope:
The scope of the project includes testing the following features of
‘https://demowebshop.tricentis.com/

’ web application.

Inclusions:

• Register

• Login & Logout

• Forgot Password

• Search

• Category Pages

• Menu Options

• Product Compare

• Product Display Page

• Add to Cart

• Wish List

• Shopping Cart

• Home Page

• Checkout Page

• My Account Page

• Contact Us Page
• Footer Options

Above functional areas need to be Tested.

Exclusions(Out of Scope):

• All the features except that are mentioned under ‘Inclusions’

• Any third-party features or Payment gateways

• Test Automation

Assumptions:
•Production like data required and be available in the system prior to start of Functional Testing

•During Functional testing, testing team will use preloaded data which is available on the system
at the time of execution.

Schedules:
Following is the test schedule planned for the project –

1. Creating Test Plan : 7/11/22 – 8/11/22


2. Test Scenario Preparation : 8/11/22 –9/11/22
3. Test Case Creation : 9/11/22 –10/11/22
4. Test Case Execution : 10/11/22 –11/11/22
5. Test Cycle – 2 Cycle
6. Summary Reports Submission Date : 12/11/22
Roles and Responsibilities:
Name Role Responsibilities
Manager_A Manager Escalations

Create the Test Plan and get the


client signoffs
✓ Interact with the application, create
and execute the test cases
✓ Report defects
✓ Coordinate the test execution. Verify
validity of the defects being reported.
✓ Submit daily issue updates and
summary defect reports to the client.
TL_A Test Lead ✓ Attend any meeting with client
✓ Interact with the application
Sr. Test ✓ Create and Execute the Test cases.
QAE_A Engineer ✓ Report defects

Deliverables :
Target
Deliverables Description Completion Date

Details on the scope of the Project,


test schedule, resource
requirements, test deliverables and
Test Plan schedule 8/11/2022
Functional
Test Test Cases created for the scope
Cases defined 10/11/2022
Detailed description of the defects
Defect identified along with screenshots and
Reports steps to reproduce on a daily basis. N/A

Summary Summary Reports –


Reports Bugs by Bug#, 12/11/2022
Environment:
Windows 10 – Chrome, Firefox and Edge

• Mac OS – Safari Browser

• Android Mobile OS – Chrome

• iPhone Mobile OS - Safari

Tools:
The following are the list of Tools we will be using in this Project

•JIRA Tracking tool, For Bug tracking.

•Snippet Screenshot tool

•Word and excel document

Defect Management:
•Any deviation from expected behaviour by the application will be noted. If it can’t be reported
as a defect, it’d be reported as an observation/issue or posed as a question.

• Any usability issues will also be reported.

• After discovery of a defect, it will be retested to verify reproducibility of the defect.


Screenshots with steps to reproduce are documented.

• Every day, at the end of the test execution, defects encountered will be sent along with the
observations.

Note:

• Defects will be documented in a excel and will be updated on JIRA tool.

• Test scenarios and Test cases will be documented in an excel document and will be updated
on JIRA tool.
Risk and Risk Management:
The following are the list of risks possible and the ways to mitigate them:

Risk: Non-Availability of a Resource

Mitigation: Backup Resource Planning

Risk: Build URL is not working

Mitigation: Resources will work on other tasks

Risk: Less time for Testing

Mitigation: Ramp up the resources based on the Client needs dynamically

Exit Criteria:
100% Test Scripts executed (OR as decided with customer)

95% pass rate of Test Cases

No open Critical and High severity defects

95% of Medium severity defects have been closed

All remaining defects are either cancelled or low severity or documented as Change Requests
for a future release

You might also like