Health Care for Covid’s Patients at
Home System Test Plan
Project Code: HCCPHS
Document Code: HCCPHS _Test Plan_v1.0
Hanoi, Sep 2021
HCCPHS -Test plan v1.0
RECORD OF CHANGE
*A - Added M - Modified D - Deleted
Effective Changed Items A* Change Description New Version
Date M, D
08/09/21 A Create new 1.0
10/2021 M Modification 1.1
02e-BM/PM/HDCV/FSOFT v1.8 Internal use 2/19
HCCPHS -Test plan v1.0
SIGNATURE PAGE
ORIGINATOR: Pham Tuan Anh Jul 26, 2011
Test Leader
REVIEWERS: Doan Thi Thuy Linh Jul 27, 2011
Quality Assurance
Nguyen Tien Chien Jul 27, 2011
Project Manger
APPROVAL: Nguyen Tien Chien Jul 27, 2011
Project Manger
02e-BM/PM/HDCV/FSOFT v1.8 Internal use 3/19
HCCPHS -Test plan v1.0
TABLE OF CONTENTS
1 INTRODUCTION......................................................................................6
1.1 Purpose..................................................................................................................... 6
1.2 Definitions, Acronyms, and Abbreviations.................................................................6
1.3 References................................................................................................................ 7
1.4 Background information............................................................................................ 7
1.5 Scope of testing........................................................................................................ 8
A. Target of Test................................................................................................. 8
B. Test Stage....................................................................................................... 8
C. Test Assumption.............................................................................................9
1.6 Constraints................................................................................................................ 9
1.7 Risk List................................................................................................................... 10
1.8 Training Needs........................................................................................................ 10
2 REQUIREMENTS FOR TEST.....................................................................10
2.1 Test Items............................................................................................................... 10
A. Functional Items...........................................................................................10
B. Non functional Items.....................................................................................11
2.2 Acceptance Test Criteria......................................................................................... 11
3 TEST STRATEGY...................................................................................12
3.1 Test Types............................................................................................................... 12
A. Function Testing...........................................................................................12
B. User Interface Testing...................................................................................13
C. Load Testing................................................................................................. 13
D. Security Testing............................................................................................ 14
E. Regression Testing.......................................................................................14
3.2 Test Stages............................................................................................................. 15
3.3 Tools....................................................................................................................... 16
4 RESOURCE...........................................................................................16
4.1 Human Resource..................................................................................................... 16
4.2 Hardwares and Softwares.......................................................................................17
02e-BM/PM/HDCV/FSOFT v1.8 Internal use 4/19
HCCPHS -Test plan v1.0
5 TEST MILESTONES................................................................................17
6 DELIVERABLES........................................................................................................ 18
02e-BM/PM/HDCV/FSOFT v1.8 Internal use 5/19
HCCPHS -Test plan v1.0
1 INTRODUCTION
1.1 Purpose
This is the comprehensive test plan of the Family Medical Officer project. The purpose
of the document describes scopes of test and activities which need to be taken
during test process of project. It addresses the following items:
Scopes of Testing Test Resources
Requirements for Testing Test Milestones
Test Strategy Test Deliverables
1.2 Definitions, Acronyms, and Abbreviations
Abbreviations Description
AT Acceptance Test
DMS Defect Management System (a FPT in-house tool)
IT Integration Test
ST System Test
PM Project Manager
PTL Project Technical Leader
QA Quality Assurance
FRS Functional Requirement Specification
TP Test Plan
TC Test Case
TR Test Report
UAT User Acceptance test
UT Unit Test
ECH El Camino Hospital
HIPAA Health Insurance Portability and Accountability Act
TRUSTe Privacy Seals, Online Trust & Safety service
WCG World The third-party who will be with ECH to do UI Design
02e-BM/PM/HDCV/FSOFT v1.8 Internal use 6/19
HCCPHS -Test plan v1.0
1.3 References
Title/File name Author Version Effective Date
Capstone Project Report [Link] SWP490_G30 4 07/26/11
Capstone Project Report [Link] WCG 01/01/11
Capstone Project Report [Link] WCG 01/26/11
1.4 Background information
In the situation that we have to live with the current COVID epidemic, the number of cases
is
increasing due to the lack of facilities as well as human resources. The management
system of
medical stations as well as those in charge of isolation is still weak. Therefore, our
team decided
to create a system to help, care for and guide patients to self-isolate at home. This
project will
provide F0 patients with specific, detailed instructions when isolating at home. In
addition, it
also provides health indicators of patients isolated at home for doctors to be able to
react
promptly when the patient is in danger.
This new version has the following main functions:
Emergency Room ECH Resources
Find a Physician Visiting ECH
My Family & Me ECH News
The purpose of this project is to develop a HTML5 based web application so that it
can function well on both iPhone and Android mobile phones then develop the iPhone
and Android applications to link with the HTML5 web app.
02e-BM/PM/HDCV/FSOFT v1.8 Internal use 7/19
HCCPHS -Test plan v1.0
1.5 Scope of testing
The scope of test will be limited to testing three applications: the HTML 5
applications..
A. Target of Test
Functional items and Non-functional items will be verified and passed by FPT
development team, then be validated and approved by El Camino Hospital via test
stages, including the requirements of the following primary functions:
Emergency Room ECH Resources
Find a Physician Visiting ECH
My Family & Me ECH News
B. Test Stage
No Test Stages Description
1 Unit Test Unit Test will be performed by FPT development team.
2 Integration Integration Test will be performed by FPT QA team.
Test
After the Unit Test is finished, testers will execute the UT
Completion Criteria based on the UT Gate checklist for each
function. Integration Test will only start if the result of UT Gate is
Passed.
This test stage focuses on specific areas of use cases when all
requirements are completed, integration test should be
performed to ensure all components incorporate well.
3 System Test System Test will be executed by FPT QA team.
Testers will perform complete, end-to-end system testing staged
in pre-production environment to validate that functions and
system interfaces perform properly in production environment.
4 Acceptance Acceptance Test will be conducted by El Camino Hospital.
02e-BM/PM/HDCV/FSOFT v1.8 Internal use 8/19
HCCPHS -Test plan v1.0
No Test Stages Description
Test FPT’s responsibilities during Acceptance Test phase are:
Facilitate completion on the application deployment
Support fixing bugs
Support Final User Acceptance Test
C. Test Assumption
The following assumptions are made for test process:
El Camino Hospital is to validate and approve for final software
product, test procedures and results
Verification from FPT project team for test execution, documenting and
results
FPT project managers to approve and commit for test resources
Requirements for test are limited to functional and non-functional
requirements specified in Section 2 of this document
Test will be executed on specific hardwares and softwares as defined in
Section 4.2
1.6 Constraints
The following constraints may apply when testing is performed on system:
Deadline for testing only can be met if development progress is on time
Test execution can be performed when system passes Unit Test Inspection
At least one round of testing must be performed for requirements
Complete testing needs support from El Camino Hospital for production
environment set-up
02e-BM/PM/HDCV/FSOFT v1.8 Internal use 9/19
HCCPHS -Test plan v1.0
1.7 Risk List
# Description Source Probabili Exposu Trigger
ty re
1 Depends on the UI design and Critical 0.7 5.6
requirement documents from WCG Dependenci
World es
1.8 Training Needs
No Training items Description
1 Unit Test Learn & study from internal: FPT's other teams
Learn & study from external:
1. Microsoft Pax:
[Link]
9651-851f-4d7a-bf05-16fd7eb26559/[Link]
2. W3school validator: [Link]
3. Microsoft Visual Studio 10 ultimate
2 System Test Learn & study from external:
1. Load test: Open STA, Jmeter, IBM Rational Robot
3 Security Test Learn & study from external: [Link]
1. Ethereal/WireShark
2. [Link]
testing_whitepaper082602.pdf
3. [Link]
whitepapers/HIPAA_TestStrategies.pdf
2 REQUIREMENTS FOR TEST
2.1 Test Items
A. Functional Items
1. Homepage 12. My Family & Me - View Profile
2. ER Wait Time 13. My Family & Me - Edit Profile
02e-BM/PM/HDCV/FSOFT v1.8 Internal use 10/19
HCCPHS -Test plan v1.0
• View wait time 14. My Family & Me - Delete Profile/
• Call Emergency Room Account
• Call Nurses' Station 15. My Family & Me- Delete Account
• Get Directions 16. ECH Resources - Vital Signs
3. ER Checklist 17. ECH Resources - Common Warning
4. Find a Physician By Last Name Signs
5. Find a Physician By Specialty 18. Visiting ECH - Pt 1 of 2
6. Find a Physician By Location • Call main line
7. My Family & Me - Login • Get Directions
8. My Family & Me - Forgot Password • View Campus Map
9. My Family & Me - Dashboard • Visitor Information
10. My Family & Me - Create An Account • Get Directions nearby
11. My Family & Me - Create a Profile 19. Visiting ECH - Pt 2 of 2
• Get Directions nearby
20. ECH News
B. Non functional Items
1. System must be HIPAA and TRUSTe compliance.
2. In the normal condition (could be 100 concurrent users or less), each page should
load in 4 seconds or less.
3. In the stress condition (could be more than 100 concurrent users), each page
should load in 12 seconds or less.
2.2 Acceptance Test Criteria
No Test Stages Qualified ratios
1 Unit Test To pass this stage, all unit test cases must be tested and passed
100%. All defects should be fixed and re-tested. Average of 11
bugs/KLOC.
2 Integration To pass this stage, all test cases must be tested and passed
Test 100%. All defects should be fixed and re-tested. Average of 4
02e-BM/PM/HDCV/FSOFT v1.8 Internal use 11/19
HCCPHS -Test plan v1.0
bugs/KLOC.
3 System Test To pass this stage, all test cases must be tested and passed
100%. All defects should be fixed and re-tested. Average of 0.5
bugs/KLOC.
4 Acceptance Acceptance Test will be conducted and approved by El Camino
Test Hospital.
1 Functional requirement 100% of all requirement defined on part 2.1 A
2 Non-functional requirement 100% of all requirement defined on part 2.1 B
3 TEST STRATEGY
3.1 Test Types
A. Function Testing
Test Verify the application and its internal processes by interacting
Objective: with the application via the Graphical User Interface (GUI) and
analyzing the outputs or results
Technique: - Testers will create test scenarios against the requirements provided by
customer. Test scenarios will be created based on black box test
technique.
- Testers execute test based on test scenarios and create report.
Common defects will be collected for improved checklist.
- Execute each case, using valid and invalid data, to verify the following:
Get the expected results when valid and invalid data is used
Valid input data is updated correctly into database
The appropriate errors or warning messages are displayed when invalid
data is used
- Execute each case, using boundary data, to verify the following:
Get the expected results when boundary data is used
Data is updated correctly to database
The appropriate errors or warning messages are displayed when invalid
data is used
02e-BM/PM/HDCV/FSOFT v1.8 Internal use 12/19
HCCPHS -Test plan v1.0
- Each valid data input is updated correctly into database.
- Each business rule is properly applied.
Completion All functional test cases have been executed to verify proper data
Criteria:
acceptance, processing, and retrieval, and the appropriate
implementation of the business rules, and passed
The appropriate activities will be performed when valid data is used
The corresponding error/warning message mechanism is applied for each
specific case
All bugs found must be fixed
Special Functional testing will NOT be started in case of developers have
Consideration not executed unit test before passing application to testers
s:
B. User Interface Testing
Navigation through the target-of-test properly reflects business
functions and requirements, including screen to screen, field-to-
Test
field, and use of access methods. Objects and characteristics,
Objective:
such as menus, size, position, state, and focus conform to
standards.
- Testers will create specific test scenarios against UI prototypes
approved by customer.
- Testers execute test based on test scenarios and create report.
Technique: Common defects will be collected for improved checklists.
- Execute each case, using valid, invalid and boundary data, to
verify the expected results display when valid, invalid and
boundary data is used.
- All GUI test cases have been executed and passed
Completion - Any defects related to GUI are fixed, except those accepted by
Criteria: customer
- All defects found by tester are addressed in DMS
Special
Consideration N/A
s:
02e-BM/PM/HDCV/FSOFT v1.8 Internal use 13/19
HCCPHS -Test plan v1.0
C. Load Testing
Verify the application and its internal processes should be met:
Test In the normal condition could be 100 concurrent users or less, each page
Objective: should load in four seconds or less
In the stress condition could be more than 100 concurrent users, each
page should load in 12 seconds or less
- Testers will create test scenarios, test scripts against the requirements
provided by customer. Test scenarios will be created based on black box
test technique, and be supported by one of the following tools: IBM
Rational Robot & Manager.
- Testers execute test based on test scenarios and create report.
Common defects will be collected for improved checklists.
Technique: - Execute each case, using valid and invalid data, to verify the following
on a random device:
In the normal condition could be 100 concurrent users or less, each page
should load in four seconds or less
In the stress condition could be more than 100 concurrent users, each
page should load in 12 seconds or less
In the normal condition could be 100 concurrent users or less,
each page should load in four seconds or less.
Completion
In the stress condition could be more than 100 concurrent users,
Criteria:
each page should load in 12 seconds or less
All performance requirements must be met
Special
Numbers of 100 virtual users should be available for Microsoft
Consideration
Visual Studio
s:
D. Security Testing
Test Verify that the application is HIPAA & TRUSTe compliance
Objective:
- Testers will create test scenarios against the requirements which
Technique:
are based on HIPAA & TRUSTe compliance. Test scenarios will be
created based on black box test technique. Refer to:
[Link]
[Link]
[Link];
[Link]
whitepapers/HIPAA_TestStrategies.pdf for more detail.
- Testers execute test based on test scenarios and create report. Use
WireShark tool to validate transaction encrypted or not. Common defects
will be collected for improved checklists.
- Execute each case, using valid and invalid data, to verify the following:
The expected results occur when valid HIPAA & TRUSTe compliance.
02e-BM/PM/HDCV/FSOFT v1.8 Internal use 14/19
HCCPHS -Test plan v1.0
Completion All test cases have been executed to verify proper data
Criteria:
acceptance, processing, and retrieval, and the appropriate
implementation of the HIPAA & TRUSTe compliance rules, and
passed
Special HIPAA & TRUSTe compliance requirement
Consideration
s:
E. Regression Testing
Test Verify the application on new build/ after bug fixing, and be sure
Objective: that other functions is not affected by fixed parts each iterations
- Testers will select some test scenarios against functional test
- Testers execute test based on test scenarios and create report.
Common defects will be collected for improved checklists.
- Execute each case, using valid and invalid data, to verify the following:
Get the expected results when valid and invalid data is used
Valid input data is updated correctly into database
The appropriate errors or warning messages are displayed when invalid
Technique: data is used
- Execute each case, using boundary data, to verify the following:
Get the expected results when boundary data is used
Data is updated correctly into database
The appropriate errors or warning messages are displayed when invalid
data is used
- Each valid data input is updated correctly into database.
- Each business rule is properly applied
Specified function test cases have been executed to verify proper
data acceptance, processing, and retrieval, and the appropriate
implementation of the business rules, and passed
Completion The appropriate activities will be performed when valid data is used.
Criteria:
The corresponding error/warning message mechanism is applied for each
specific case.
All bugs found must be fixed.
Some of other functions is not affected by fixed code
Special N/A
02e-BM/PM/HDCV/FSOFT v1.8 Internal use 15/19
HCCPHS -Test plan v1.0
Consideration
s:
3.2 Test Stages
Types of Test Stages of Test
Integratio
Unit System Acceptance
n
Functional Testing x x x X
Non-functional Testing X X X X
… X X
Confirmation Testing X X X
Regression Testing X X X
3.3 Tools – for Testing
Purpose Tool Vendor/In- Version
house
Defect log DMS FPT tool
Collect test effort Timesheet FPT tool
Documenting MS Word, Excel Microsoft 2010
Unit Testing Pax Microsoft
Function Testing Manual Manual
Load Testing IBM Rational Robot & Microsoft 2010
Manager
Security Testing WireShark <open source> 1.6.1
Database SQL Server Microsoft 2008
4 RESOURCE
4.1 Human Resource
This table shows the staffing assumptions for the project.
Worker/ Role Specific Responsibilities/Comments
Doer
02e-BM/PM/HDCV/FSOFT v1.8 Internal use 16/19
HCCPHS -Test plan v1.0
Anh Pham Test Leader Manage test resources and assign test tasks
Create Test Plan, Test Cases (IT, ST), Test Scripts (IT, ST)
Review Test Data
Create Test Reports
Hien Nguyen Tester Review Test Cases (IT, ST)
Create Test Data and Execute Test (IT, ST)
Report Test Results
Linh Doan Quality Final Inspection Test Cases, Test Plan, Test Reports
Assurance
Chien Project Manager Approve Test Cases (UT, IT, ST), Test Plan, Test Results,
Nguyen Test Reports
Nam Le Project Review Test Cases (UT, IT, ST)
Technical
Leader
Anh Vu Developer Create UT Cases, UT Reports
Tung Tran Developer Create UT Cases, UT Reports
Dat Nguyen Developer Create UT Cases, UT Reports
4.2 Hardwares and Softwares
The FMO HTML5 web-based application and iPhone, Android Hybrid applications will
require testing on the following iPhone and Android devices:
Hardware OS Version
iPhone 4 iOS 4
Motorola DROID 2 Android OS, v2.2 (Froyo)
Samsung Galaxy S II Android OS, v2.3 (Gingerbread)
HTC Sensation Android OS, v2.3 (Gingerbread)
Software Version
Microsoft Windows 2003 SP2
Server
Microsoft IIS 6.0
Microsoft SQL Server 2008
Microsoft .NET 4.0
Framework
02e-BM/PM/HDCV/FSOFT v1.8 Internal use 17/19
HCCPHS -Test plan v1.0
5 TEST MILESTONES
Milestone Task Effort (pd) Start Date End Date
Create Test Plan 5 07/15/11 07/26/11
Review & Update Test Plan 2 07/26/11 07/27/11
Create IT&ST Test Cases 13 07/27/11 08/12/11
Review & Update IT&ST Test 2 08/09/11 08/15/11
Cases
Create & Execute & Report UT 15 08/08/11 09/05/11
for Software Package version
1.0
Create test data for Software 1 08/31/11 09/02/11
Package version 1.0
UT Gate for Software Package 0.5 09/05/11 09/06/11
version 1.0
Execute IT for Software 16 09/05/11 09/17/11
Package version 1.0
Execute ST for Software 4 09/17/11 09/19/11
Package version 1.0
Create IT&ST Test Report for 1 09/20/11 09/20/11
Software Package version 1.0
Create & Execute & Report UT 22 09/19/11 10/10/11
for Software Package version
1.1
UT Gate for Software Package 0.5 10/11/11 10/11/11
version 1.1
Create test data for Software 1 10/05/11 10/08/11
Package version 1.1
Execute IT for Software 17 10/10/11 10/22/11
Package version 1.1
Execute ST for Software 5 10/22/11 10/24/11
Package version 1.1
Create IT&ST Test Report for 1 10/24/11 10/24/11
Software Package version 1.1
Create & Execute & Report UT 16 09/10/11 10/04/11
for Software Package version
1.2
UT Gate for Software Package 0.5 10/20/11 10/20/11
version 1.2
Create test data for Software 1 10/17/11 10/19/11
Package version 1.2
Execute IT for Software 20 10/20/11 11/04/11
Package version 1.2
02e-BM/PM/HDCV/FSOFT v1.8 Internal use 18/19
HCCPHS -Test plan v1.0
Execute ST for Software 3 11/04/11 11/07/11
Package version 1.2
Create IT&ST Test Report for 0.5 11/07/11 11/07/11
Software Package version 1.2
Execute System Test for 8 11/03/11 11/12/11
Software Package final
version
Create Test Report for 1 11/14/11 11/14/11
Software Package final
version
6 DELIVERABLES
No Deliverables Delivered Delivered by Delivered to
Date
1 Test Plan 08/01/11 FPT ECH
2 Test Reports for 9/20/11 FPT ECH
Software Package
version 1.0
3 Test Reports for 10/24/11 FPT ECH
Software Package
version 1.1
4 Test Reports for 11/7/11 FPT ECH
Software Package
version 1.2
5 Test Reports for 11/17/11 FPT ECH
Software Package final
version
02e-BM/PM/HDCV/FSOFT v1.8 Internal use 19/19