TEST PLAN

Project Name: RedSyn

Prepared by: EnoFlux

Date: March 03, 2020
Table of Contents
Overview...............................................................................................................................................2
Scope.....................................................................................................................................................3
Inclusions...........................................................................................................................................3
Test Environments.............................................................................................................................3
Exclusions..........................................................................................................................................3
Test Strategy..........................................................................................................................................4
Problem Tracking and Test Tracking Procedures...................................................................................5
Roles/Responsibilities............................................................................................................................6
Test Schedule........................................................................................................................................7
Test Deliverables...................................................................................................................................8
Pricing....................................................................................................................................................9
Overview
As part of the project, ‘RedSyn’ has asked EnoFlux to test few functionalities of ‘https://xyz.in” web
application.

This document serves as high level test planning document with details on the scope of the project,
test strategy, test schedule and resource requirements, test deliverables and schedule.
Scope
The scope of the project includes testing the following features of ‘https://xyz.in’ web application.

Inclusions
 Customers
o Create Customer
o Account Summary details
 New Orders
o Create/Edit Order
o Verify the details displayed in Account Summary page > Summary tab
o Verify the order details in Account Summary page > Orders tab
o Verify the order details in View Details page
 Create and Run a Billing Cycle to generate invoice
o Create a Billing Cycle
o Start Manual Billing Run
o Verify the invoice details before payment
o Download and email the invoice
 Make Payment
o Add a payment method
o Make payment as Client using
 Credit Card
 Check
 Cash
o Make payment as Customer using
 Credit Card
o Verify details in the invoice details, Account Summary Page > Summary and
Payments tabs

From our understanding, we believe above functional areas will cover our Functional Testing
Scenario.

Functional Testing Scenario will be run against the following test data,

Product: XYZ-SUBSCRIPTION

Plan: Subscription Plan

Charge:

1. One Time Charge

2. Recurring Charge

Price Type:

1. Fixed with Pre-paid

Test Environments
 Windows 10 + IE 11
Exclusions
 All the features except that are mentioned under ‘Inclusions’

Test Strategy
Functional Testing

EnoFlux will create and execute the Test Cases for the above feature(s) mentioned in the ‘Inclusions’
for RedSyn’s ‘https://xyz.in’ Web Application.

We’ll apply below listed techniques to test the application:

Functional Testing – Testing each feature (within the scope of pilot) of RedSyn’s ‘https://xyz.in’ web
application to identify things the product can do as per expectations.

Flow & Scenario Testing – Apart from testing individual features, flows and scenarios will be created
to replicate end user actions with the application.

Usability Testing – Testing the ease with which the user and test whether the application built in
user-friendly or not.
Problem Tracking and Test Tracking Procedures
Defect Reporting Procedure:

During the test execution –

 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 word document.

 Test cases will be documented in an excel document.
Roles/Responsibilities
Name Role Responsibilities
Dhanraj Errum Test Manager  Escalations
Varun Chinnuru Test Lead  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.
 Attend any meeting with client.
Mahesh Mehtha Senior Test Engineer  Interact with the application
 Create and Execute the Test cases.
 Report defects
Test Schedule
Following is the test schedule planned for the project –

Task Time Duration

 Creating Test Plan March 18th, 2020
 Test Case Creation (‘Customers and
‘Order Functionality’)
 Test Case Creation (‘Orders’ and March 19th, 2020
‘Invoices’ functionality)
 Test Case Creation (‘Invoices’ and March 20th, 2020
‘Payments’ functionality)
 Test Case Execution March 23rd, 2020
 Test Case Execution March 24th, 2020
 Summary Reports Submission
Test Deliverables
The following are to be delivered to the client:

Deliverables Description Responsible Target Completion

Owner Date
Test Plan Details on the scope of the Project, test EnoFlux March 18th, 2020
strategy, test schedule, resource
requirements, test deliverables and
schedule
Functional Test Cases Test Cases created for the scope EnoFlux March 20th, 2020
defined
Defect Reports Detailed description of the defects EnoFlux March 20th, 2020
identified along with screenshots and
steps to reproduce on a daily basis.
Summary Reports Summary Reports – EnoFlux March 24th, 2020
Bugs by Bug#,
Bugs by Functional Area and
Bugs by Priority
Pricing
Will be shared by Project Manager separately.