0% found this document useful (0 votes)
72 views4 pages

Take One Project Like A website/web-application/Android-App and Submit A Test-Plan Document For It Following The IEEE Format of Test Plan Template

This document provides a test plan template for testing a website/web application/Android app according to IEEE standards. It outlines the introduction, scope, quality objectives, roles and responsibilities, test methodology, deliverables, resources, and terms/acronyms. The scope defines what will and won't be tested. The test methodology section describes the test levels, bug triage process, and suspension/resumption criteria. Test deliverables, tools, and environment needs are also specified.

Uploaded by

RITESH Chauhan
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
Download as docx, pdf, or txt
0% found this document useful (0 votes)
72 views4 pages

Take One Project Like A website/web-application/Android-App and Submit A Test-Plan Document For It Following The IEEE Format of Test Plan Template

This document provides a test plan template for testing a website/web application/Android app according to IEEE standards. It outlines the introduction, scope, quality objectives, roles and responsibilities, test methodology, deliverables, resources, and terms/acronyms. The scope defines what will and won't be tested. The test methodology section describes the test levels, bug triage process, and suspension/resumption criteria. Test deliverables, tools, and environment needs are also specified.

Uploaded by

RITESH Chauhan
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1/ 4

AIM:- Take one project like a website/web-application/Android-App and

submit a Test- plan Document for it following the IEEE format of Test Plan Template.

1 INTRODUCTION.......................................................................................................2
1.1 SCOPE......................................................................................................................2
1.1.1 In Scope...........................................................................................................2
1.1.2 Out of Scope....................................................................................................2
1.2 QUALITY OBJECTIVE...............................................................................................2
1.3 ROLES AND RESPONSIBILITIES................................................................................2
2 TEST METHODOLOGY...........................................................................................3
2.1 OVERVIEW...............................................................................................................3
2.2 TEST LEVELS...........................................................................................................3
2.3 BUG TRIAGE............................................................................................................3
2.4 SUSPENSION CRITERIA AND RESUMPTION REQUIREMENTS....................................3
2.5 TEST COMPLETENESS..............................................................................................4
3 TEST DELIVERABLES............................................................................................4
4 RESOURCE & ENVIRONMENT NEEDS..............................................................4
4.1 TESTING TOOLS.......................................................................................................4
4.2 TEST ENVIRONMENT...............................................................................................4
5 TERMS/ACRONYMS................................................................................................5
Introduction
Brief introduction of the test strategies, process, workflow and methodologies used
for the project

Scope

In Scope

Scope defines the features, functional or non-functional requirements of the software


that will be tested

Out of Scope

Out Of Scope defines the features, functional or non-functional requirements of the


software that will NOT be tested

Quality Objective

Here make a mention of the overall objevtie that you plan to achive withou your
testing
Some objectives of your testing project could be

 Ensure the Application Under Test conforms to functional and non-functional


requirements
 Ensure the AUT meets the quality specifications defined by the client
 Bugs/issues are identified and fixed before go live

Roles and Responsibilities


Detail description of the Roles and responsibilities of different team members like
 QA Analyst
 Test Manager
 Configuration Manager
 Developers
 Installation Team
Amongst others

Test Methodology

Overview

Mention the reason of adopting a particular test methodology for the project. The test
methodology selected for the project could be
 WaterFall
 Iterative
 Agile
 Extreme Programming
The methodology selected depends on multiple factors.

Test Levels

Test Levels define the Types of Testing to be executed on the Application Under
Test (AUT). The Testing Levels primarily depends on the scope of the project, time
and budget constraints.
Bug Triage

The goal of the triage is to

 To define the type of resolution for each bug


 To prioritize bugs and determine a schedule for all “To Be Fixed Bugs’.

Suspension Criteria and Resumption Requirements

Suspension criteria define the criteria to be used to suspend all or part of the testing
procedure while Resumption criteria determine when testing can resume after it has
been suspended

Test Completeness
Here you define the criterias that will deem your testing complete.
For instance, a few criteria to check Test Completeness would be
 100% test coverage
 All Manual & Automated Test cases executed
 All open bugs are fixed or will be fixed in next release

Test Deliverables

Here mention all the Test Artifacts that will be delivered during different phases of
the testing lifecycle.

Here are the sample deliverables


 Test Plan
 Test Cases
 Requirement Traceability Matrix
 Bug Reports
 Test Strategy
 Test Metrics
 Customer Sign Off

Resource & Environment Needs

Testing Tools
Make a list of Tools like
 Requirements Tracking Tool
 Bug Tracking Tool
 Automation Tools
Required to test the project

Test Environment
It mentions the minimum hardware requirements that will be used to test the
Application.

Following software’s are required in addition to client-specific software.

 Windows 8 and above


 Office 2013 and above
 MS Exchange, etc.

Terms/Acronyms
Make a mention of any terms or acronyms used in the project

TERM/ACRONY DEFINITION
M
API Application Program Interface
AUT Application Under Test

You might also like