EMS-360

VERSION 1.0
EMS-360

Document Overview
Title Version 1.0
Project EMS-360 Status Draft
Client Type Internal
Doc # 1 Doc Date March 16, 2020
Author Aroosa khan Last Save March 16, 2020
Description

Revision History
Ver # Rev Date Author Dist. Date Brief Description

Distribution List

Approved By
Name Role Version

Page i of ii
EMS-360

TABLE OF CONTENTS

1. Introduction............................................................................................................................................ 1
1.1 Definitions & Abbreviations......................................................................................................... 1
1.2 Objective.................................................................................................................................... 1
1.3 Background................................................................................................................................ 1
1.4 Intended Audience...................................................................................................................... 1

2. Scope...................................................................................................................................................... 2
2.1 Functional areas of the application to be tested.........................................................................2
2.2 Usability Testing......................................................................................................................... 4
2.3 Interface/GUI Testing................................................................................................................. 4
2.4 Compatibility Testing.................................................................................................................. 4
2.5 Performance Testing.................................................................................................................. 4
2.6 Security Testing.......................................................................................................................... 4

3. Strategy.................................................................................................................................................. 5
3.1 Test Strategy.............................................................................................................................. 5
3.2 Test Types.................................................................................................................................. 6
0 Functional Testing...................................................................................................................... 6
3.3 Testing Flow............................................................................................................................... 7
3.4 Testing Cycles............................................................................................................................ 8
3.5 Assumptions............................................................................................................................... 8
3.6 Risk Factors................................................................................................................................ 8

4. Test Management and Procedures...................................................................................................... 9

4.1 Procedures................................................................................................................................. 9
1 Processes................................................................................................................................... 9
2 Suspension and Resumption Criteria......................................................................................... 9
3 Pass/Fail Criteria........................................................................................................................ 9
4 Exit Criteria............................................................................................................................... 10
4.2 Testing Management................................................................................................................ 10
5 4.2.1Test Environment............................................................................................................. 10
6 4.2.2Testing Deliverables......................................................................................................... 10

Page ii of ii
EMS-360

1. INTRODUCTION
This document describes the Test Plan for EMS-360. It is intended that the QA Team of Tower
technologies will use this document to execute the system-testing phase. This Test Plan document
includes a discussion on the objective and assumptions of the testing activity as well as the methodology
and approach.

1.1 DEFINITIONS & ABBREVIATIONS

Term Definition
TP Test Plan
Test Planning activities, dependencies and effort required to conduct the Test
GUI Graphical user interface

1.2 OBJECTIVE

The objective of this test plan is to plan, organize and manage the activities/tasks that are required for the
testing of EMS-360. This test plan is formed:
0 To define the test scope, strategy and methodology to be used for the test.
1 To identify the activities required to prepare for and conduct testing.
2 To identify responsibilities for the tasks included in the plan.
3 To define the test tools and the environment needed to conduct the test.
4 To identify test interactions with other organizations.
5 To identify test customers and deliverables.
6 To identify the major testing milestones.
7 To define the sources of information used to prepare the plan.

1.3 BACKGROUND

Following is the list of Deliverables that will be delivered on completion of each milestone as per
Project Plan:
 Test Plan
 Test Cases
 Defect Reports

1.4 INTENDED AUDIENCE

Tower technologies Development Team,

Tower technologies QA Team

Page 1 of 10
EMS-360

2. SCOPE
Scope of the testing is to test the areas outlined below as well as any other areas as deemed necessary:

2.1 FUNCTIONAL AREAS OF THE APPLICATION TO BE TESTED

A full review of the Webapp when logged out, logged in (as Individual user) for the following functions:
 System Setup
 Admission
o Session
o Campus Program Map
o Program Course Map
o Board / University
o Board Type
o Gender
o Medium
o Month
o Nationality
o Religion
o Admission Type
o Degree
o Group
o Attendance status
 General
o Business Group
o Business Unit
o Institution
o Campus
o Zone
o Country
o Province
o City
o Sub- City
o Class
o Campus status

Page 2 of 10
EMS-360

o Institution Type
o Messages API
o Shift
o Define Grading Policy
o Define Fail Criteria
o Messages Template
 Building
o Building Info
o Campus Building Map
o Room
o Room Building map
o Room Type
o Building Section Link
o Possession
o Possession Type
o Building Address
 Academic
o Program
o Program Details
o Section
o Course
o Shift Timings
o Lecture Slot Timings
 Fee
o Fee Head
o Fee Structure
o Continuation Policy
o Batch Concession
o Concession
o Concession Detail
o Fee Structure Approval
o Paid Date restriction
o Bank Definition
o Campus Challan Note Map
o Challan Note

Page 3 of 10
EMS-360

o Challan Type
o Fee Structure Detail
o Scholarship Criteria

 Migrate
o Hadaf Migration
o Cms Migration
o Admission Enrollment
o Attendance percentage

2.2 USABILITY TESTING

A full review of text in the webapp for

 Ease of use
 Clear English and lack of jargon
 Email messages
 Pop up messages

2.3 INTERFACE/GUI TESTING

A full review of the webapp when logged out, logged in.

 GUI Review

2.4 COMPATIBILITY TESTING

A full review of compatibility that is very important aspect of a webapp.

 Browser Compatibility
 Operating System Compatibility

2.5 PERFORMANCE TESTING

A full review of performance, the webapp should be able to sustain to heavy load.
 Load Testing
 Stress Testing

2.6 SECURITY TESTING

A full review of security through Authentication and Authorization.

Page 4 of 10
EMS-360

 Authentication: It’s all about System Security, this security ensure that only those users
granted access to the system are capable of accessing the application.
 Authorization: It’s all about Application Security, this security ensure that based upon the
desired security, users are restricted to specific functions or are limited in the data that is
available to them.

Page 5 of 10
EMS-360

3. STRATEGY
3.1 TEST STRATEGY

The application will be tested to assure that the system meets the full requirements, including (Non-
functional requirements) and fit metrics for each quality requirement and satisfies the actual need of the
system and maintain the quality of the product. Web app will be tested on exploratory basis in order to
start testing. The cycle of testing of EMS-360 will reflect in test plan document in order to show its results.

At the end of the project development cycle, the user should find that the project has met or exceeded all
of their expectations.

The objective of testing application systems will be to identify and expose all issues and associated risks,
communicate all known issues to the project team, and ensure that all issues are addressed in an
appropriate matter before release. As an objective, this requires careful and methodical testing of the
application to first ensure all areas of the system are scrutinized and, consequently, all issues (bugs)
found are deal with appropriately.

All the defects found during testing cycles will be stored in bug tracking system (if available) otherwise will
be provided in document format.

Page 6 of 10
EMS-360

3.2 TEST TYPES

FUNCTIONAL TESTING

Test Objective: Ensure proper target-of-test functionality, including navigation,

processing, and retrieval.
Technique: Execute each, testing flow, or function, using valid and invalid data,
to verify the following:
 The expected results occur when valid data is used.
 The appropriate error or warning messages are displayed when
invalid data is used.
 Each business rule is properly applied.
Completion Criteria:  All planned tests have been executed.
 All identified defects have been addressed.

Page 7 of 10
EMS-360

3.3 TESTING FLOW

Page 8 of 10
EMS-360

3.4 TESTING CYCLES

Six testing cycles will be executed on EMS-360. First cycle will be executed with respect to Link
verification and functional testing to verify the working of each and every feature/function.
Second and third cycle will be executed for Usability and GUI testing.

The fourth, fifth and sixth cycle will base on Compatibility, Performance and Security review and
also documentation review.

3.5 ASSUMPTIONS

0 All reference data will be available on the server at the start of testing cycle.

3.6 RISK FACTORS

Any addition of functionality during testing cycle will increase the risk of un-stability in application.
Stopper bugs fixation at the end of testing cycle will increase the risk of ripples in rest of the webapp.

Page 9 of 10
EMS-360

4. TEST MANAGEMENT AND PROCEDURES

This section describes the methodology and approach used to test the EMS-360

4.1 PROCEDURES

PROCESSES

Test Cases will be prepared for Automation testing and Manual testing. The result of executed
test cases will be marked as “Pass/Fail/Open/On Hold”.

SUSPENSION AND RESUMPTION CRITERIA

Any test failure that prevents testing of other functions will cause the suspension of testing.
However, if any functions can be tested effectively in spite of the failure, tests will continue on
those functions to the extent possible.
A patch or, if appropriates, a new release that corrects the failure must be provided before the
test process can be resumed. Before the test cycle is resumed, regression testing will be
performed to verify that the patch or new release does not adversely affect existing functionality.

PASS/FAIL CRITERIA

The Testing Team reports bugs using four levels of severity:

SEVERITY LEVEL 1
Total Loss
 Total loss of access to system
 Security breach
 Loss of Main functionality

SEVERITY LEVEL 2
Serious Defect
 Partial loss of access to system
 Field validation
 Inaccurate data
 Incorrect functionality
 Performance outside of targeted service levels
0
SEVERITY LEVEL 3
Moderate Defect
 Minor errors but system still operates
 Screen layout incorrect
 Proper scrolling

Page 10 of 10
EMS-360

SEVERITY LEVEL 4
Cosmetic Defect
 Not affecting the functional operation of system
 Spelling errors
 Help text incorrect

EXIT CRITERIA

The exit criteria for the test phase are:

8 All planned test cycles have been executed.
9 No identified bugs are open.

4.2 TESTING MANAGEMENT

TEST ENVIRONMENT

Hardware: 8 GB RAM, Intel processer with Dual core 2.5 GHz, 500 GB Hard Disk.
Software: Eclipse.
Framework for Automation: TestNG, Maven

TESTING DELIVERABLES

Deliverable Name External/Internal Baseline Phase

Test Plan Internal Testing

Defect Reports Internal Testing

Defect Status Report Internal Testing

Page 11 of 10