APP Name

Application name Master Test Plan

Document
Code:
Creator:
Reviewer:
Approver:
File Name:
Status:
Function:

Qatutorial.com
Qatutorial.com
Qatutorial.com
186444201.doc
In-Progress/Sent For Review/ Reviewed/Approved

Change History
Issue
1

Approved by

QATUTORIAL

Date
Date

xxxxxxxxxxxxx

Author
Qatutorial.com

Comments
Initial Draft

APP Name

Table of Contents
1. Introduction................................................................................................................................. 3
2. Requirements Traceability Summary.......................................................................................... 4
3. Testing strategy and Process ..................................................................................................... 5
4. Risk and Change Management.................................................................................................. 11
5. Test Organization and Resources.............................................................................................. 12
6. Quality assurance..................................................................................................................... 12
7. Testing Environment and Infrastructure....................................................................................13
8. Metrics...................................................................................................................................... 14
9. Glossary.................................................................................................................................... 14

QATUTORIAL

APP Name

1.

INTRODUCTION

1.1

Document Purpose & Scope

1.1.1

Purpose

The purpose of the application name Master Test Plan (MTP) is to define how the testing effort for the
app version maintenance release is planned, executed, and controlled. The MTP is distributed to the app
version Program Management Team (PMT) for approval and signoff. This MTP will be updated when
there are changes in project plans. The app version QA lead is responsible for keeping this MTP updated.
All app version test team members are responsible for following this plan.
1.1.2

Scope

The main sections of this document are:

Introduction
Requirements traceability summary - identifies the software requirements and components that
are tested
Test strategy and process - defines how the testing effort aligns with the chosen development
process and lists the types of testing conducted for each test phase
Risks, changes, and dependencies - lists the quality services risks that affect delivery
Testing organization and resources - identifies the resources, estimates test efforts, and provides
an overview of the testing schedule, major milestones.
Test environments and infrastructure lists the tools, systems, hardware, and software
necessary for testing
Glossary defines terms specific to the product
1.2

References
Product Requirements Document
Functional Requirements Document
Server Requirements Document
Approved PMT Program Change Requests (PCRs)

1.3

1.4

Deliverables

Master Test Plan

PMT Status Reports

Final Test Report

Program Change Requests (PCR)

PCR #

QATUTORIAL

Date Approved

Summary

Affected
Section

APP Name

1.5

MTP Document Location

Microsoft Project Server, SharePoint server (https://www.qatutorial.com/ProjectServer) under the app

version Project. A copy is also available in Perforce under the following depot; xxxxxxxxxxxx
2.

REQUIREMENTS TRACEABILITY SUMMARY

2.1

Product Overview And Background

Application Name is a maintenance release addressing the following objectives:

Adding functionality 1 for certain devices

Expanding device support for HTC wildfire, Samsung Galaxy, etc

Implementation functionality 2

Enhanced functionality for..

Integration of xxxxxxx hot fix release

Resolution of defects afflicting customers as deemed necessary by Customer Support

2.2

Product Requirements / Traceability

2.2.1

Adding functionality 1 for certain devices

Small Description
2.2.2

Expanding device support for HTC wildfire, Samsung Galaxy, etc

Device validation consists of the following requirements;

Some points
Point2
The DeviceChecklist test case must be enhanced to include Settings Provisioning test cases for future
releases.
2.2.3

Implementation of functionality 2

Small Description
2.2.4

Enhanced functionality for..

Small Description
2.2.5

Integration of xxxxxxx hot fix release

Small Description

QATUTORIAL

APP Name

2.2.6

Customer Support defects

The following table identifies the defects targeted for this release.
Defect
ID
12345
12345
12344
12344
12344
12344
12344
12344
2.2.7

Summary
Defect
Defect
Defect
Defect
Defect
Defect
Defect
Defect

desc
desc
desc
desc
desc
desc
desc
desc

Test Case
1
2
3
4
5
6
7
8

Resource
Resource1
Resource2
ResourcM3
Resource1
ResourcM4
Resource5
ResourcM3
Resource2

The following items have been added through approved PCRs;

TBD
2.2.8

Unapproved release changes

Small description
TBD
2.3

Installation/Upgrade Testing

Requirements for Installation and upgrade testing are derived from

Small description
2.4

Features or Requirements Not to be tested

Small description

3.

TESTING STRATEGY AND PROCESS

3.1

Overview

App name testing consists of the following testing disciplines

Functional test
Installation/Upgrade testing
Defect verification testing
Regression test including System Regression and Device Regression
3.2

Development Process Model

A waterfall development process model is followed.

QATUTORIAL

APP Name

3.3

Product program M Milestones

3.4

Mileston
e
M1

Date

QA Exit Criteria

Date

Draft Master Test Plan, Test Schedule

M2
M3

Date
Date

M4

date

Master Test Plan approved, Test Cases approved

Functional testing complete; defect fix verifications complete,
System regression testing complete
Release approved by support, posted to support site

Reporting Responsibilities

PMT status reports are produced for weekly meetings, beginning after M1. Status reports include
testing activities progress, defect status, and QA confidence levels.
3.5

Testing Phases

3.5.1

Unit Testing

The software engineers are responsible for designing, executing, and reporting on unit testing.
3.5.2

Integration Testing

The software engineers are responsible for designing, executing, and reporting on integration testing.
3.5.3

Functional Testing

The QA team prepares test cases during phase 2 for;

Feature Enhancements
Defect verification
System/Device Regression testing
Device Validation Testing

Functional test execution formally commences upon completion of M2. Defects discovered during the
phase are evaluated for resolution in the current release or deferral to a future release. Phase
originated defects that are resolved in the current phase are also retested during phase. Defects that
are deferred are submitted to the technical support group for generation of a knowledge base
resolution.
3.5.3.1

Functionality1 Functional testing

Functional testing for the Functionality1 feature consists of validating the Admin GUI, User GUI, and
End to End functionality. Admin GUI testing concentrates on the server level Settings functionality.
Range checking of input fields is performed as are various interactions with system dependencies (ie.
License variations, Administration/Group privileges, Navigation persistence of parameters, and server
upgrades). User GUI testing consists Range validation for input fields, various parameter combinations,
License and group privilege variations. End to End testing is performed using the device table below.
This testing validates that user entries are properly configured on the device after the processing
thread. Testing is performed with the default browser, email client, and functionali1 client available on
the device. A test will also be performed for Browser1 and Browser2 on devices1 for Bookmark setting

QATUTORIAL

APP Name

only. The functionality2 client will be used on Samsung and HTC device. No third party client email
application is tested during this release.
Device

Device
Firmware

Device1

1.1

Device2

2.1

DevicM3

3.1

3.5.3.2

Device
Languag
e

Applicatio
n
Language
en_US
da_DK
de_DE
es_ES
fi_FI
fr_FR
it_IT
pt_BR
no_NO
sv_SE
en_US
da_DK
de_DE
es_ES
fi_FI
fr_FR
it_IT
pt_BR
no_NO
sv_SE
en_US
da_DK
de_DE
es_ES
fi_FI
fr_FR
it_IT
pt_BR
no_NO
sv_SE

Settings to Send
WAP Access Point
Internet Access Point
Email Access Point
Bookmark
Functionality1

WAP Access Point

Internet Access Point
Email Access Point
Bookmark
Functionality1

WAP Access Point

Internet Access Point
Email Access Point
Bookmark
Functionality1

Functionality2 Functional testing

Functional testing for Functionality2 consists of validating Sub-Functionality2 and SubFunctionality2. There are several aspects of Functionality2 testing to account for various device and
servers, foreign language compatibility, and third party data intervention (ie. MS Outlook). The high
level approach to Functionality2testing was approved by the PMT, prior to development of the PRD.
The following table identifies the devices that are planned for testing.
Device

QATUTORIAL

Device
Firmware

Outlook
Server

Device
Langua
ge

App
Langua
ge

Outloo
k
Server
Langua
ge

APP Name

Device1

1.1

Exchange
2000

Device2

2.1

Exchange
2000

en_US
da_DK
de_DE
es_ES
fi_FI
fr_FR
it_IT
pt_BR
no_NO
sv_SE
en_US
da_DK
de_DE
es_ES
fi_FI
fr_FR
it_IT
pt_BR
no_NO
sv_SE

en_US
da_DK
de_DE
es_ES
fi_FI
fr_FR
it_IT
pt_BR
no_NO
sv_SE
en_US
da_DK
de_DE
es_ES
fi_FI
fr_FR
it_IT
pt_BR
no_NO
sv_SE

en_US
da_DK
de_DE
es_ES
fi_FI
fr_FR
it_IT
pt_BR
no_NO
sv_SE
en_US
da_DK
de_DE
es_ES
fi_FI
fr_FR
it_IT
pt_BR
no_NO
sv_SE

The following test cases are further defined in the functionality2 test case, however they are listed here
to present a high level summary of what testing is planned.
1. Introduction................................................................................................................................. 3
1.1 Document Purpose & Scope................................................................................................... 3
1.1.1 Purpose ......................................................................................................................... 3
1.1.2 Scope.............................................................................................................................. 3
1.2 References............................................................................................................................. 3
1.3 Deliverables ......................................................................................................................... 3
1.4 Program Change Requests (PCR)........................................................................................... 3
1.5 MTP Document Location......................................................................................................... 4
2. Requirements Traceability Summary.......................................................................................... 4
2.1 Product Overview And Background .......................................................................................4
2.2 Product Requirements / Traceability.......................................................................................4
2.2.1 Adding functionality 1 for certain devices.......................................................................4
2.2.2 Expanding device support for HTC wildfire, Samsung Galaxy, etc..................................4
2.2.3 Implementation of functionality 2...................................................................................4
2.2.4 Enhanced functionality for...........................................................................................4
2.2.5 Integration of xxxxxxx hot fix release.............................................................................4
2.2.6 Customer Support defects..............................................................................................5
2.2.7 The following items have been added through approved PCRs;.....................................5
2.2.8 Unapproved release changes.........................................................................................5
Small description.................................................................................................................... 5
2.3 Installation/Upgrade Testing................................................................................................... 5
Small description.................................................................................................................... 5
2.4 Features or Requirements Not to be tested............................................................................5
Small description.................................................................................................................... 5
3. Testing strategy and Process ..................................................................................................... 5
3.1 Overview................................................................................................................................ 5
3.2 Development Process Model.................................................................................................. 5
3.3 Product program M Milestones...............................................................................................6

QATUTORIAL

APP Name

3.4 Reporting Responsibilities...................................................................................................... 6

3.5 Testing Phases ...................................................................................................................... 6
3.5.1 Unit Testing.................................................................................................................... 6
3.5.2 Integration Testing......................................................................................................... 6
3.5.3 Functional Testing.......................................................................................................... 6
3.5.4 Installation and Upgrade testing.....................................................................................9
3.5.5 Platform1........................................................................................................................ 9
3.5.6 Intel based enterprise server/RHEL 3............................................................................10
3.5.7 Device Regression Testing............................................................................................ 10
3.5.8 Final Regression testing................................................................................................ 10
3.5.9 Beta Testing/UAT.......................................................................................................... 10
3.6 Test Case Modification.......................................................................................................... 10
3.7 Localization.......................................................................................................................... 11
3.8 Automation Tests................................................................................................................. 11
3.8.1 Smoke tests.................................................................................................................. 11
4. Risk and Change Management.................................................................................................. 11
4.1 Risk Management................................................................................................................. 11
4.2 Change Management........................................................................................................... 11
5. Test Organization and Resources.............................................................................................. 12
5.1 Roles & Responsibilities........................................................................................................ 12
5.2 Testing Schedule.................................................................................................................. 12
6. Quality assurance..................................................................................................................... 12
6.1 Reviews and Inspections...................................................................................................... 12
6.2 Test Meetings....................................................................................................................... 12
6.3 Tracking Of Test Execution................................................................................................... 12
7. Testing Environment and Infrastructure....................................................................................13
7.1 Test Environment................................................................................................................. 13
7.2 Device Requirements........................................................................................................... 13
7.3 Test Tools............................................................................................................................. 13
7.3.1 Unit Test Tools.............................................................................................................. 13
7.3.2 Bug Tracking ................................................................................................................ 13
7.3.3 Automated Test Tools................................................................................................... 14
7.3.4 Performance Test Tools ............................................................................................... 14
7.3.5 Build And Source Control.............................................................................................. 14
8. Metrics...................................................................................................................................... 14
9. Glossary.................................................................................................................................... 14
3.5.3.3

Functionality3 functional testing

Small description
3.5.4

Installation and Upgrade testing

Installation and upgrade testing of the application is performed on two separate platforms; Platform1
and Platform2. Preservation of system configuration, internationalization configuration, and user
configuration is validated for all upgrades.
3.5.5

Platform1

Platform1 installation and upgrade testing consists of server re-imaging with application installation,
fresh application installation, and upgrade installation.

QATUTORIAL

APP Name

3.5.6

Intel based enterprise server/RHEL 3

Platform1 installation and upgrade testing consists of server re-imaging with application installation,
fresh application installation, and upgrade installation. Testing is performed on the following hardware
configuration;

1
2
3

Testing is also performed with operating system variants as follows;

OS1

OS2

3.5.7

Device Regression Testing

The following supported devices will be regression tested using the DeviceCheclist(Short) test case.
Device

Firmware

Device1
Device2
DevicM3
DevicM4

1.1
1.1
1.1
1.1

3.5.8

Device
Brows
er
Yes
Yes
Yes
Yes

Client
Email
(IMAP/SM
TP)
No
No
No
No

Functi
onality
1
No
No
No
No

Final Regression testing

After the final software change is submitted for phase discovered defects, a broad regression test is
performed in an attempt to confirm system degradation has not occurred from resolved defects.
Defects encountered during this testing are evaluated for release-blocking or deferral candidates. If a
release blocking defect is encountered, the resolution is provided, retested and the final regression test
restarts (ie. The clock is reset).
3.5.9

Beta Testing/UAT

Description
3.6

Test Case Modification

QATUTORIAL

APP Name

The following table identifies complete suite of QA test cases and the required test cases for the App
Name test effort. The test cases are revised to include scenarios for App Name feature enhancements
and defect verification.
Test Case Name

Summary

Justification

Func1

Summ1

Due to 1

3.7

Assigned
Resource
Res 1

Localization

Localization testing planned for App Name consists of;

Small description
3.8

Automation Tests

The automation tests planned for App Name consist primarily of functional tests. Small desc
3.8.1

Smoke tests

Smoke tests are run on each new software build to ensure the build integrity is maintained from
progressive builds. Smoke tests exercise basic system functionality. The following table identifies the
functionality exercised by the smoke test for the App Name release.
Smoke test
Name

Functionality Exercised

N1

Func1
Func2
Func3

4.

RISK AND CHANGE MANAGEMENT

4.1

Risk Management

A risk tracking spreadsheet is administered at each PMT meeting. Each project group is responsible for
identifying, mitigation, and tracking risks in their area.
4.2

Change Management

At M1, when the PRD is approved/frozen, no changes in the scope of App Name are allowed without
approval of a PCR. PCR scope includes: removal of functionality, addition of functionality, and the fixing
of defects found in earlier versions of Unifi.

QATUTORIAL

APP Name

5.

TEST ORGANIZATION AND RESOURCES

5.1

Roles & Responsibilities

Role

5.2

Name/quantity

Responsibilities

%allocat
ed

QA Lead

qatutorial

Coordination and participation

of the overall QA testing
activities for App Name

100%

Test
Member

qatutorial

Revision of Test Case

documentation during M2
phase, Test Case execution
and defect reporting during M3
phase

100%

Testing Schedule

See the App Name schedule is available on..

6.

QUALITY ASSURANCE

6.1

Reviews and Inspections

The following reviews of deliverables are performed during the phases of App Name:
Deliverable

Author(s)

Review/approv
al By

When

Application name
Master Test Plan

PMT

M1

App Name Test

cases

QA, Engineering

M2 and M3

Final Test Report

PMT

M4

6.2

Test Meetings

Test meetings are asynchronously scheduled based on necessity. Instant messenger sessions are
asynchronously instantiated upon necessity.
6.3

Tracking Of Test Execution

Test execution is tracked using a spreadsheet that is shared and version controlled in the Perforce
_TestProgress.xls. Status updates are provided by the QA lead. The spreadsheet contains the following
columns;
Functional Area

QATUTORIAL

APP Name

QA Test Case
Test Resource
Passed Test Scenarios
Planned Test Scenarios
Date Testing is complete
Test Status
Blocking Bug #
Comments
7.

TESTING ENVIRONMENT AND INFRASTRUCTURE

7.1

Test Environment

Small description
7.2
Device Requirements
The following table identifies the devices, firmware, planned test coverage for the testing effort.
Device

Firmware

7.3

Test Tools

7.3.1

Unit Test Tools

7.3.2

Bug Tracking

Device
Browse
r

Client Email
(IMAP/SMTP
)

Functio
nality1

Defect reporting for App Name is performed using the defect management system. When an observed
result deviates from an expected result, a defect is entered into the system. There is a triage meeting
that analyzes each defect and assigns the defect appropriately. Once a defect is resolved, it is returned
to the reporter for verification testing.
The following information is mandatory when generating a defect during the M3 phase.
Bugzilla
Field
Version
Priority
Severity

QATUTORIAL

Description

Possible Values

app Version
Turnaround time required for resolution of the
defect
Perceived impact on the external customer

1.1
P1, P2, P3, P4, P5
Blocker
Critical
Major
Normal
Minor

APP Name

Summar
y
Keyword
s
Descripti
on

Abbreviated statement characterizing the system

behavior
Identifies the phase where the bug was detected
App Name
Build Number
Description of Problem
Expected Result
Steps to Reproduce

Trivial
Enhancement
Character
M3
Character

It is also strongly encouraged that defect reporters attach the log file that resides in directory on the
system under test, jpg snapshots of aberrant behavior, pointers to a backed up copy of the database,
properties files, and urls of associated websites. If possible the defect reporter should determine if the
defect has been introduced during the current release or prior releases.
7.3.3

Automated Test Tools

Quick Test Professional

7.3.4

Performance Test Tools

Tool1
7.3.5

Build And Source Control

Perforce
CVS
8.

METRICS

The following metrics will be provided on a periodic basis during M3 phase;

Test progress as a percentage of passed test cases / planned test cases
Defect discovery
Defect resolution
Defect verification
Defect deferral
9.

GLOSSARY

TBD To Be Determined

QATUTORIAL