Project title/2021

Addis Ababa Institute of Technology

School of Information Technology and Engineering
Department of IT/SW Eng.
<Project Name>
Test Plan Document
Team Members
1.xxx
2.xxx
Advisor:

Month 2021

Contents
 Project title/2021
List of Tables..........................................................................................................................................................iii
List of Figures.........................................................................................................................................................iv
Introduction............................................................................................................................................................1
1.1 Purpose of the document..............................................................................................................................1
2. Features to be tested/not to be tested..................................................................................................................1
2.1. Features to be tested....................................................................................................................................1
2.2. Features not to be tested..............................................................................................................................2
3. Pass/Fail criteria.................................................................................................................................................2
4. Approach/Strategy..............................................................................................................................................2
5. Test cases with specifications.............................................................................................................................4
Reference...............................................................................................................................................................9
 Project title/2021
List of Tables
Table 1: Test case specification for Login................................................................................................................3
Table 2: Test case Specification for Mobile client...................................................................................................4
 Project title/2021
List of Figures
Fig: 1 xxxxxxx
 Project title/2021
Introduction
Software testing is an investigation conducted to provide stakeholders with information about the
quality of the product or service under test. Testing evaluates a software product to ensure that it
satisfies its planned purpose. A test that is modified to and consistent with development methodologies
provides an observable and structured approach for verifying requirements and quantifiable
performance.

1.1 Purpose of the document

The purpose of our test plan is to uncover and report as many bugs as possible to increase our system
reliability and to ensure the right product is developed.

2. Features to be tested/not to be tested

2.1. Features to be tested
This is a listing of what is to be tested from the USERS viewpoint of what the system does. This is not
a technical description of the software, but a USERS view of the functions. Set the level of risk for
each feature. Use a simple rating scale such as (H, M, L): High, Medium and Low. These types of
levels are understandable to a User. You should be prepared to discuss why a particular level was
chosen. It should be noted that Section 4 and Section 6 are very similar. The only true difference is the
point of view. Section 4 is a technical type description including version numbers and other technical
information and Section 6 is from the User’s viewpoint. Users do not understand technical software
terminology; they understand functions and processes as they relate to their jobs.
This section describes the system features to be tested.
The following is features to be tested
///sample for testing functional and nonfunctional requirements
Functional testing: test functionality of the system such as
 Create user account
 update user account

Nonfunctional requirements to be tested

 User interface
 Hardware and software that the system will run
 Security
 Performance

Test Plan Document (TPD)

1
 Project title/2021
2.2. Features not to be tested
This is a listing of what is NOT to be tested from both the Users viewpoint of what the system does and
a configuration management/version control view. This is not a technical description of the software,
but a USERS view of the functions.
Identify WHY the feature is not to be tested, there can be any number of reasons.
 Not to be included in this release of the Software.
 Low risk, has been used before and is considered stable.
 Will be released but not tested or documented as a functional part of the release of this version
of the software.

3. Pass/Fail criteria
//here you will write the pass and fail criteria set by the team you can write in the following manner

The success /fail criteria are the following: -

 If the actual output and the expected result are the same the pass/fail criteria is “success or pass”
 If the actual output and the expected result are different the pass/fail criteria is “fail”.

4. Approach/Strategy
This section of the test plan describes the overall approach/strategy for testing of the system and why
you choose the approach.
This is your overall test strategy for this test plan; it should be appropriate to the level of the plan
(master, acceptance, etc.) and should be in agreement with all higher and lower levels of plans. Overall
rules and processes should be identified.
 __Are any special tools to be used and what are they?
 __Will the tool require special training?
 __What metrics will be collected?
 __Which level is each metric to be collected at?
 __How is Configuration Management to be handled?
 __How many different configurations will be tested?
 __Hardware
 __Software
 __Combinations of HW, SW and other vendor packages
 __What levels of regression testing will be done and how much at each test level?
 __Will regression testing be based on severity of defects detected?
 __How will elements in the requirements and design that do not make sense or are untestable be
processed?

If this is a master test plan the overall project testing approach and coverage requirements
Test Plan Document (TPD)
2
 Project title/2021
must also be identified.
Specify if there are special requirements for the testing.
 __Only the full component will be tested.
 __A specified segment of grouping of features/components must be tested together.
 Other information that may be useful in setting the approach are:
 __MTBF, Mean Time Between Failures - if this is a valid measurement for the test involved
 and if the data is available.
 __SRE, Software Reliability Engineering - if this methodology is in use and if the
 information is available.

Test Plan Document (TPD)

3
 Project title/2021
5. Test cases with specifications
A test case is a set of input data and expected results that exercises a component with the purpose of
causing failures and detecting faults.
//here is sample set of test case so replace by your own system functional requirement you specified in the
function tons to be tested //

Table 1: Test case specification for reset password

Name: reset Password

Purpose: to reset the password
Test Data = Username(invalid username, valid username, empty)

Confirm username(invalid , valid, empty)

New password(invalid , valid, empty)

Confirm password(invalid , valid, empty)

Input Expected result Data Actual output Pass/fail

Empty username and “cannot leave Empty username and “cannot leave
Valid confirmation empty” Any valid confirmation empty” Fail
username username
Invalid username and “User name does Invalid username and “User name does
Valid confirmation not exist” Any Valid confirmation not exist” Fail
username username
Mismatch username and “Username doesn’t If username= Tolosa “Username doesn’t
confirmation username match” confirmation match” Fail
username=Chala
Empty username and Cannot leave Cannot leave empty
Empty confirmation empty user name user name Fail
username
Valid username and “Displays Any valid data for both “Displays password
valid confirmation password reset username and reset link” Pass
username link” confirmation username
Invalid password and “Enter Strong If Password length<3 “Enter Strong
Valid confirmation password” password” Fail

Test Plan Document (TPD)

4
 Project title/2021
password
Miss match password and “Password doesn’t If Password= Lamessa “Password doesn’t
confirmation password match” confirmation match”
username=Chalchisa Fail
Empty password and Empty password “cannot leave empty Empty password “cannot
Empty Confirmation and password ” and leave
Password Valid confirmation Valid confirmation empty
password password password
”
Valid password and “Password reset any valid data password “Password reset Pass
valid confirmation successfully” and valid confirmation successfully”
password password

Table 2: Test case specification for create account

Name = Create Account

Purpose=To authorize users to the system
Test Data = Name (invalid name, Valid name, empty)
User name(invalid User name, valid user name)
Email (Valid Email, invalid Email)
Confirm Email (Valid Email, invalid Email)
Password (invalid password, valid password)
Confirm Password (invalid password, valid password)
Input Expected result Data Actual output Pass/fail
Empty name and all “Enter correctly Empty name and Any “Enter correctly
other fields are valid formatted name” valid data for
formatted name” Fail
other fields
Invalid Name If Name=875333
and all other fields are
Or
valid
“Enter correctly If Name<2 characters
formatted name”
Or
“Enter correctly
If Name>50 characters formatted name” Fail
and
Any valid data for other
fields
Test Plan Document (TPD)
5
 Project title/2021
Empty User Name “Enter correctly Empty User Name and
and formatted username” Any valid data for other
Other fields are valid fields “Enter correctly
formatted username” Fail

invalid User Name If User Name is occupied “user name is

and all other fields are “Enter correct occupied so try
valid user name” another” Fail
If User name>25
characters
“Enter correct user
name”
Empty email and all “Enter correct Empty email and Any
other fields are valid formatted email” valid data for other fields “Enter correct
Fail
formatted email”

Invalid email and all “Enter correct Invalid email and Any “Enter correct
other fields are valid formatted email” valid data for other fields formatted email”
Fail
Empty Confirmation “Email does not Empty Confirmation
Email and match” Email and Any valid data “Email does not
Fail
all other fields are for other fields match”
valid
Invalid Confirmation “Email does not If email =
Email and match” [email protected]
Fail
all other fields are
valid If confirmation email= “Email does not
[email protected] match”
And Any valid data for
other fields

Empty password And “Enter strong Empty password “Enter strong Fail
all other fields are Password with And any valid data for Password with
valid length greater than other fields length greater than
three” three”

Invalid password And “Enter strong “Enter strong

all other fields are Password with If password< 3 Password with
Fail
valid length greater than And any valid data for length greater than
three” other fields three”

Test Plan Document (TPD)

6
 Project title/2021
Empty confirmation Empty confirmation
password and all “Password does not password and Any valid
other fields are valid match” data for other fields “Password does not
match” Fail

Invalid confirmation “Password does not Invalid confirmation “Password does not
password and all match” password and any valid match”
other fields are valid data for other fields
Fail

All fields are empty “all fields are “all fields are
If all fields are empty
required” required” Fail
all valid fields “Account created Any valid data for all “Account created
successfully” fields successfully” Pass

Table 3: Test case specification for Update user account

Name: Update user account

Purpose: enable users to update their user account
Test Data= Name(invalid name, valid name, empty)
User name(invalid User name, valid user name, empty)
Email (Valid Email, invalid Email)
Password (Valid password, invalid Password)
Input Expected result Data Actual output Pass/fail
All fields “fill all fields” All fields are empty “fill all fields” Fail
are empty
Empty “Enter Correct name” Empty name “Enter Correct name” Fail
name And any valid data for
And all other fields
other
fields are
valid

invalid “Enter Correct name” If Name=87 Fail

name and
all other Or
fields are If Name<2 characters
valid
Or
If Name>50 characters “Enter Correct name”
Test Plan Document (TPD)
7
 Project title/2021
and
Any valid data for
other fields
invalid If User Name is Fail
username occupied “user name is occupied
and all so try another”
other User name must be If User name>25
fields are valid
characters
valid
“Enter correct user
name”
Empty “Enter correct Empty Email and all “Enter correct formatted Fail
Email and formatted email ” other fields are valid email ”
all other
fields are
valid
Invalid “Enter correct If email [email protected] “Enter correct formatted Fail
Email and formatted email ” and all other fields are email ”
all other valid
fields are
valid
All fields “Account updated Any valid data for the “Account updated Pass
successfully” all fields successfully”
are valid

Reference
[1] xxx,xxx,xxx,xxx(entire book info or document info)

[2] tutrials point,http://ccc.ccc.cc. accssedate 12/09/2016

Test Plan Document (TPD)

8
 Project title/2021

Test Plan Document (TPD)

9