HANOI UNIVERSITY OF SCIENCE AND TECHNOLOGY

School of Information and communications technology

Test Plan
Version 1.0

<Project
Name>
Subject: <Name of subject>

<Group Number>
<List of participants>

Hanoi, <month, year>

<All notations inside the angle bracket are not part of this document, for its
purpose is for extra instruction. When using this document, please erase all
these notations and/or replace them with corresponding content as instructed>

<This document, written by Asst. Prof. NGUYEN Thi Thu Trang, is used as a
case study for student with related courses. Any modifications and/or utilization
without the consent of the author is strictly forbidden>
 Table of Contents

1 Instructions
2 Overall Description
3 Testing Approach Strategy
4 Unit Testing Summary
5 Test Case Details
1. Introduction
1.1. Objective
<Identify the purpose of this document, its intended audience, and expected
evolution of the document. Identify if this Test Plan covers all test functions for
the project (i.e., main test plan for the project) or if it is only specific to a
particular test phase(s) (e.g., Development Testing) or a specific test function(s).
Also describe any security or privacy considerations associated with use of the
Test Plan.>

1.2 Scope
<In this subsection:
(1) Identify the software product(s) to be produced by name
(2) Explain what the software product(s) will, and, if necessary, will not do
(3) Describe the application of the software being specified, including relevant
benefits, objectives, and goals
(4) Be consistent with similar statements in higher-level specifications if they exist

This should be an executive-level summary. Do not enumerate the whole requirements

list here
Note that this will be similar to what was written in the SRS.>

1.3. Glossary
<Listing and explaining the terms appearing in the software’s profession and this
document. Any assumption of the reader’s prior knowledge or experience on the
subject is ill advised>

1.4. References
Centers for Medicare & Medicaid Services. (n.d.). Test Case Specification. Retrieved
from Centers for Medicare & Medicaid Services: https://www.cms.gov/Research-
Statistics-Data-and-Systems/CMS-Information-Technology/XLC/Downloads/
TestCaseSpecification.docx

Centers for Medicare & Medicaid Services. (n.d.). Test Plan. Retrieved from Centers for
Medicare & Medicaid Services: https://www.cms.gov/Research-Statistics-Data-and-
Systems/CMS-Information-Technology/XLC/Downloads/TestPlan.docx

guru99. (n.d.). Download Sample Test Case Template: Example Excel, Word Formats.
Retrieved from guru99: https://www.guru99.com/download-sample-test-case-template-
with-explanation-of-important-fields.html

<Listing the referenced material used in this document, including the one related to the
project>
2. Overall Description
2.1. General Overview
< Briefly describe the purpose and context for the system or situation, and summarize
the history of its development. Include the high-level context diagram(s) for the system
and subsystems previously provided in the Software Requirements Specification (SRS)
and/or System Design Document (SDD), e.g., use case diagrams, activity diagram,
package diagram, updated as necessary to reflect any changes that have been made
based on more current information or understanding. If the high-level context diagram
has been updated, identify the changes that were made and why.>

2.2. Assumptions/Constraints/Risks
2.2.1. Assumptions
<If the testing approach/strategy is based upon any assumptions, please list and
describe them. For example, identify dependencies with other systems and the
assumption that they will be ready to test when needed, assumptions regarding
availability of defined test environments, etc.>

2.2.2. Constraints
< Describe any limitations or constraints that have a significant impact on the
testing of the system, application, or situation. Such constraints may be imposed
by any of the following (the list is not exhaustive):
• Hardware or software environment
• End-user environment
• Availability of resources
• Interoperability requirements
• Interface/protocol requirements
• Data repository and distribution requirements.>

2.2.3. Risks
< Describe any risks associated with the testing and proposed mitigation
strategies.>
3. Testing Approach/Strategy
< Describe the overall approach that will be used to test all functions, features, and
requirements of the automated system, application, or situation for which the Test
Plan applies. As applicable to this Test Plan, describe the measures to be taken to
ensure all aspects of the system are successfully tested and can be implemented.
Document key aspects of the testing approach, such as content, methodology,
prioritization, and progression of development, validation, implementation, and
operational testing activities to be performed during the corresponding lifecycle
phases
For example, will some unit and application integration testing be done, and then
some more development, and so on? Is a prototype being built that will be usability
tested before the releasable software is developed? Also include plans for testing
related documentation (e.g., installation instructions, User Manual, Operations &
Maintenance (O&M) Manual, Training Artifacts, etc.) and for conducting applicable
readiness reviews. Also, if applicable, describe how reuse will be applied to the
testing effort to make testing more efficient and less costly.>
4. Unit Testing Summary
4.1. Traceability from Test Cases to Use Cases
<Mark the cell with an "x" where the Test Case tests.>

USE CASE ID UC001 UC002 UC003 UC004 UC005 …

Test
Test CaseTitle Totals 2 1 2 0 1 1
Case ID
TC001 1 x
TC002 3 x x x
TC006 1 x
TC007 1 x
… 1 x
Table: Test Case-to-Use Case Traceability Matrix

4.1.1. Test Suite for UC002-"Use Case Name"

Test
Test Suite Title Description Test Cases
Suite ID
<Test Case ID, Test
TS001 <Test Suite Title> <Briefly describe the test suite>
Case ID>

4.2. Traceability from Test Cases to Requirements

<Mark the cell with an "x" where the Test Case tests.>

REQUIREMENT ID RQ001 RQ002 RQ003 RQ004 RQ005 …

Test
Test CaseTitle Totals 1 1 1 0 1 1
Case ID
TC001 1 x
TC002 3 x x x
TC003 1 x
TC004 1 x
TC005 2 x x
… 1 x
Table: Test Case-to-Requirement Traceability Matrix
4.2.1. Test Suite for RQ001-"Requirement Title"
Test
Test Suite Title Description Test Cases
Suite ID
<Test Case ID, Test
TS004 <Test Suite Title> <Briefly describe the test suite>
Case ID>
5. Test Case Details
5.1. Test Case Specification for "Test Case Title"
Test Case ID TC001 Test Case Description Test the
Created By A Reviewed By …
B Version 1.0

QA Tester’s Log Review comments from Reviewer incorprate in version 1.0

Tester's Name C Date Tested 22/11/2020 Test Pass

<B and C can be the same person> Case
# Prerequisites: (Pass/Fail
1 Access to Chrome Browser /Not
2

# Test Data Value

1 Userid dominhhieu
2 Pass 123456789
3

Test Scenario Verify on entering valid userid and password, the customer can login

Step # Step Details Expected Results Actual Results Pass / Fail / Not executed /
Suspended
1 Navigate to Site should open As Expected Pass
https://www.google.com/
2 Enter Userid & Password Credential can be entered As Expected Pass

3 Click Submit Cutomer is logged in Not Expected Fail

5.2. Test Case Specification for "Test Case Title"

Test Case ID Test Case Description
Created By Reviewed By Version

QA Tester’s Log
Tester's Name Date Tested Test
Case

# Prerequisites:
1

# Test Data Value

1

Test Scenario

Step # Step Details Expected Results Actual Results Pass / Fail / Not executed /
Suspended
1