Restaurant Review

Test Plan

Project Code: PRR

Document Code: PRR_Test Plan_v1.0

Hanoi, March 2024

FMO-Test plan v1.0

RECORD OF CHANGE

*A - Added M - Modified D - Deleted

Effective Changed Items A* Change Description New Version

Date M, D

07/27/11 A Create new 1.0

02e-BM/PM/HDCV/FSOFT v1.8 Internal use 2/18

FMO-Test plan v1.0

SIGNATURE PAGE

ORIGINATOR: Nguyen Quy Hung Mar 16, 2024

Test Leader

REVIEWERS: Tran Khanh Tung Mar 16, 2024

Quality Assurance

Mai Tien Thanh Mar 16, 2024

Project Manger

APPROVAL: Ta Quang Nhat Mar 16, 2024

Project Manger

02e-BM/PM/HDCV/FSOFT v1.8 Internal use 3/18

FMO-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/18

FMO-Test plan v1.0

5 TEST MILESTONES....................................................................................................17

6 DELIVERABLES.................................................................................................................18

02e-BM/PM/HDCV/FSOFT v1.8 Internal use 5/18

FMO-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 is to describe 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/18

FMO-Test plan v1.0

1.3 References

Title/File name Author Version Effective Date

ECH_MobileWeb_0722.pdf WCG 4 07/26/11

iPhone_App_Concepts_Presentation_by_E WCG 01/01/11

CH_201101.pdf

iPhone_App_Research_Presentation_by_E WCG 01/26/11

CH_20110126.pdf

Mobile_Optimized_Website_Strategy_Pres WCG 1 03/28/11

entation_v1_20110328.pdf

Mobile_POV_v2_20110208.pdf WCG 2 02/08/11

Project_History_Timeline_20110713.pdf FPT 07/13/11

FMO_Questions and Answers FPT 07/26/11

Management Sheet_20110722.xslx

FMO_WO_v1.0.doc FPT 1.0 07/22/11

FMO_Project Plan_v1.0.doc FPT 1.0 07/11/11

FMO_Functional Requirement FPT 1.0 07/27/11

Specification_v1.0

1.4 Background information

El Camino Hospital (ECH) is a not-for-profit organization with hospital campuses in Mountain View
and Los Gatos, California. The hospitals have served communities in the South San Francisco Bay
Area for nearly 50 years.

ECH has a website that is currently serving the desktop users. In order to better serve the mobile
consumers with a many different kinds of platforms such as iPhone and Android mobile devices,
ECH is in need of new version to serve the mobile users. 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/18

FMO-Test plan v1.0

1.5 Scope of testing

The scope of the test will be limited to testing three applications: the HTML 5 applications and
two hybrid applications (on iPhone and Android).

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 Test The Integration Test will be performed by the FPT QA team.

After the Unit Test is finished, testers will execute the UT Gate based on
the UT Gate checklist for each function. The 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 Test The Acceptance Test will be conducted by El Camino Hospital.

02e-BM/PM/HDCV/FSOFT v1.8 Internal use 8/18

FMO-Test plan v1.0

No Test Stages Description

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 the 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/18

FMO-Test plan v1.0

1.7 Risk List

# Description Source Probabilit Exposur Trigger

y e

1 Depends on the UI design and Critical 0.7 5.6

requirement documents from WCG World Dependencies

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:
http://research.microsoft.com/en-us/downloads/d2279651-
851f-4d7a-bf05-16fd7eb26559/default.aspx
2. W3school validator: http://validator.w3.org/mobile/
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: https://www.owasp.org/

1. Ethereal/WireShark
2. http://www.wedi.org/snip/public/articles/
testing_whitepaper082602.pdf
3. http://www.macadamian.com/images/uploads/
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/18

FMO-Test plan v1.0

• View wait time 14. My Family & Me - Delete Profile/ Account

• Call Emergency Room 15. My Family & Me- Delete Account

• Call Nurses' Station 16. ECH Resources - Vital Signs

• Get Directions 17. ECH Resources - Common Warning Signs

3. ER Checklist 18. Visiting ECH - Pt 1 of 2

4. Find a Physician by Last Name • Call main line.

5. Find a Physician by Specialty • Get Directions

6. Find a Physician by Location • View Campus Map

7. My Family & Me - Login • Visitor Information

8. My Family & Me - Forgot Password • Get Directions nearby.

9. My Family & Me - Dashboard 19. Visiting ECH - Pt 2 of 2

10. My Family & Me - Create An Account • Get Directions nearby.

11. My Family & Me - Create a Profile 20. ECH News

B. Nonfunctional Items

1. System must be HIPAA and TRUSTe compliance.

2. In normal conditions (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 Test To pass this stage, all test cases must be tested and passed 100%. All
defects should be fixed and re-tested. Average of 4 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 Test Acceptance Test will be conducted and approved by El Camino Hospital.

02e-BM/PM/HDCV/FSOFT v1.8 Internal use 11/18

FMO-Test plan v1.0

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 Objective: Verify the application and its internal processes by interacting 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

- 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

02e-BM/PM/HDCV/FSOFT v1.8 Internal use 12/18

FMO-Test plan v1.0

case

All bugs found must be fixed

Special Functional testing will NOT be started in case of developers have not
Considerations: executed unit test before passing application to testers

B. User Interface Testing

Navigation through the target-of-test properly reflects business functions

and requirements, including screen to screen, field-to-field, and use of
Test Objective:
access methods. Objects and characteristics, such as menus, size, position,
state, and focus conform to standards.

- Testers will create specific test scenarios against UI prototypes approved

by customers.

- Testers execute test based on test scenarios and create report. Common
Technique:
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 customer
Criteria:
- All defects found by tester are addressed in DMS

Special
N/A
Considerations:

C. Load Testing

Verify the application and its internal processes should be met:

In the normal condition could be 100 concurrent users or less, each page should
Test Objective: 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

Technique: - 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.

- Execute each case, using valid and invalid data, to verify the following on a

02e-BM/PM/HDCV/FSOFT v1.8 Internal use 13/18

FMO-Test plan v1.0

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, each
Criteria:
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 Visual Studio
Considerations:

D. Security Testing

Test Objective: Verify that the application is HIPAA & TRUSTe compliance

- Testers will create test scenarios against the requirements which are
Technique:
based on HIPAA & TRUSTe compliance. Test scenarios will be created
based on black box test technique. Refer to:
https://www.owasp.org;
http://www.wedi.org/snip/public/articles/testing_whitepaper08260
2.pdf;
http://www.macadamian.com/images/uploads/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.

Completion All test cases have been executed to verify proper data acceptance,
Criteria:
processing, and retrieval, and the appropriate implementation of the HIPAA
& TRUSTe compliance rules, and passed

Special HIPAA & TRUSTe compliance requirement

Considerations:

E. Regression Testing

Verify the application on new build/ after bug fixing, and be sure that other
Test Objective:
functions is not affected by fixed parts each iterations

02e-BM/PM/HDCV/FSOFT v1.8 Internal use 14/18

FMO-Test plan v1.0

- 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 data is
Technique: 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
Considerations:

3.2 Test Stages

Types of Test Stages of Test

Unit Integration System Acceptance

Function Test X X X X

User Interface test X X X X

Load test X X

Security test X X X

Regression test X X X

02e-BM/PM/HDCV/FSOFT v1.8 Internal use 15/18

FMO-Test plan v1.0

3.3 Tools

Purpose Tool Vendor/In-house Version

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 & Manager Microsoft 2010

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/Doer Role Specific Responsibilities/Comments

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 Assurance Final Inspection Test Cases, Test Plan, Test Reports

Chien Nguyen Project Manager Approve Test Cases (UT, IT, ST), Test Plan, Test Results, Test
Reports

Nam Le Project Technical Review Test Cases (UT, IT, ST)

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

02e-BM/PM/HDCV/FSOFT v1.8 Internal use 16/18

FMO-Test plan v1.0

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 Server 2003 SP2

Microsoft IIS 6.0

Microsoft SQL Server 2008

Microsoft .NET Framework 4.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 for 15 08/08/11 09/05/11

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 Package 16 09/05/11 09/17/11

version 1.0

Execute ST for Software Package 4 09/17/11 09/19/11

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 for 22 09/19/11 10/10/11

02e-BM/PM/HDCV/FSOFT v1.8 Internal use 17/18

FMO-Test plan v1.0

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 Package 17 10/10/11 10/22/11

version 1.1

Execute ST for Software Package 5 10/22/11 10/24/11

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 for 16 09/10/11 10/04/11

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 Package 20 10/20/11 11/04/11

version 1.2

Execute ST for Software Package 3 11/04/11 11/07/11

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 Software 8 11/03/11 11/12/11

Package final version

Create Test Report for Software 1 11/14/11 11/14/11

Package final version

6 DELIVERABLES

No Deliverables Delivered Date Delivered by Delivered to

1 Test Plan 08/01/11 FPT ECH

2 Test Reports for Software 9/20/11 FPT ECH

Package version 1.0

3 Test Reports for Software 10/24/11 FPT ECH

Package version 1.1

4 Test Reports for Software 11/7/11 FPT ECH

Package version 1.2

5 Test Reports for Software 11/17/11 FPT ECH

Package final version

02e-BM/PM/HDCV/FSOFT v1.8 Internal use 18/18