FPT SOFTWARE

<Quiz Practice>
Test Plan

QP: <QP>

Document Code: QP_Test Plan_ v1.0

<Hanoi, Oct 2023>

<QP>-Test plan v<xxx>

RECORD OF CHANGE

*A - Added M - Modified D - Deleted

Effective Changed Items A* Change Description New Version

Date M, D

10/18/23 A Create new 1.0

25/10/23 A Finish Plan 1.1

G1/QP/SWP391 v1.1 2/16

<QP>-Test plan v<xxx>

SIGNATURE PAGE

ORIGINATOR: Nguyễn Phú Quý Oct 18, 2023

Test Leader

REVIEWERS: Đặng QUốc KHánh Oct 18, 2023

Quality Assurance

Vu Dinh Khiem Oct 18, 2023

Project Manager

APPROVAL: Vu Dinh Khiem Oct 18, 2023

Project Manager

G1/QP/SWP391 v1.1 3/16

<QP>-Test plan v<xxx>

TABLE OF CONTENTS

1 INTRODUCTION............................................................................................................5

1.1 Purpose.............................................................................................................................5
1.2 Background information......................................................................................................5
1.3 Scope of testing.................................................................................................................5
1.4 Constraints........................................................................................................................5
1.5 Risk list.............................................................................................................................6

2 REQUIREMENTS FOR TEST...........................................................................................6

3 TEST STRATEGY............................................................................................................6

3.1 Test types.........................................................................................................................9

3.1.1 Functional Testing...................................................................................................9
3.1.2 Performance testing...............................................................................................12
3.1.3 Security and Access Control Testing........................................................................15
3.1.4 Regression Testing................................................................................................16
3.2 Test stage.......................................................................................................................16
3.3 Tools...............................................................................................................................17

4 RESOURCE..................................................................................................................17

4.1 Human Resource..............................................................................................................17

4.2 System............................................................................................................................17

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

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

G1/QP/SWP391 v1.1 4/16

 <QP>-Test plan v<xxx>

1 INTRODUCTION

1.1 Purpose

This is the comprehensive test plan of the Quiz Practice 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 Background information

Quikk is a Education Company which need a web application in order to access to more
customers and to provide course more efficient and convenient. The Web application has the
following main functions:

 Learning Lession of Course

 Practice Quizzes

 Doing Exam

1.3 Scope of testing

i. Target of Test

Functional items and Non-functional items will be verified and passed by FPT development
team, including the requirements of the following primary functions:

 Find a Course  Learning Lessons

 Quiz Handle  Quiz Review

G1/QP/SWP391 v1.1 5/16

 <QP>-Test plan v<xxx>

ii. Test Stage

No Test Stages Description

1 Unit Test Unit Test will be performed by development team.

2 Integration Test Integration Test will be performed by QA team.

After the Unit Test is finished, testers will execute the UT Gate 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 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 FPT’s responsibilities during Acceptance Test phase are:

 Facilitate completion on the application deployment

 Support fixing bugs

 Support Final User Acceptance Test

iii. Test Assumption

The following assumptions are made for test process:

 Verification from project team for test execution, documenting and results

 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

G1/QP/SWP391 v1.1 6/16

<QP>-Test plan v<xxx>

1.4 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

1.5 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]
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 18. View Profile

2. Courses List 19. Edit Profile

G1/QP/SWP391 v1.1 7/16

 <QP>-Test plan v<xxx>

3. Course Detail 20. Delete Profile

4. Find Courses by Name 21. Course Register

5. Find Courses by Subject 22. User’s Registration

6. Login 23. Blog List

7. Quiz Practice 24. Blog Detail

8. Forgot Password 25. Quiz Handle

9. Reset Password 26. Quiz Review

10. Dashboard 27. Question List

11. Authorization 28. Question Detail

12. Create An Account 29. Quizzes List

13. Create a Profile 30. Quizzes Detail

14. Registration List 31. Course Management

15. Registration Detail 32. Blog Management

16. User List 33. User Management

17. User Detail

iv. Non functional Items

1. In the normal condition (could be 100 concurrent users or less), each page should load in 4

seconds or less.

2. 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.

G1/QP/SWP391 v1.1 8/16

<QP>-Test plan v<xxx>

4 Acceptance Test Acceptance Test will be conducted and approved by El Camino 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

3.1.1 Functional Testing

[Link] 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

G1/QP/SWP391 v1.1 9/16

<QP>-Test plan v<xxx>

- 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 not
Considerations: executed unit test before passing application to testers

[Link] 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 customer.

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

[Link] Data and Database Integrity Testing

G1/QP/SWP391 v1.1 10/16

<QP>-Test plan v<xxx>

Ensure the quiz practice project's database access methods and processes
Test Objective:
function properly and without data corruption.

- Invoke each database access method and process related to the quiz
practice project, providing valid and invalid data or requests for data.
Technique:
- Inspect the database to ensure the data has been populated as intended,
all database events occurred properly, or review the returned data to ensure
that the correct data was retrieved for the correct reasons.

All database access methods and processes of the quiz practice project function
Completion Criteria:
as designed and without any data corruption.

- Testing may require a DBMS development environment or drivers to enter

or modify data directly in the quiz practice project's database.

Special
Considerations: - Processes should be invoked manually.

- Small or minimally sized databases (limited number of records) should be

used to increase the visibility of any non-acceptable events.

3.1.2 Performance testing

[Link] 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 load
Test Objective: 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 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

G1/QP/SWP391 v1.1 11/16

<QP>-Test plan v<xxx>

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:

3.1.3 Security and Access Control 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:
[Link]
[Link]
[Link];
[Link]
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:

3.1.4 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

G1/QP/SWP391 v1.1 12/16

<QP>-Test plan v<xxx>

- 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

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

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

G1/QP/SWP391 v1.1 13/16

<QP>-Test plan v<xxx>

3.3 Tools

Purpose Tool Vendor/In-house Version

Defect log GitLab

Collect test effort Excel Microsoft

Documenting MS Word, Excel Microsoft 2010

Unit Testing JUnit

Function Testing Manual Manual

Load Testing IBM Rational Robot & Manager Microsoft 2010

Security Testing WireShark <open source> 1.6.1

Database SQL Server Microsoft 2022

4 RESOURCE

4.1 Human Resource

This table shows the staffing assumptions for the project.

Worker/Doer Role Specific Responsibilities/Comments

Thien Nguyen Test Leader Manage test resources and assign test tasks

Create Test Plan, Test Case

Review Test Data

Create Test Reports

Hieu Pham Tester Review Test Cases

Create Test Data and Execute Test

Report Test Results

Khiem Vu Project Manager Approve Test Case, Test Plan, Test Result, Test Reports

Khanh Dang Quality Assurance Final Inspection Test Cases, Test Plan, Test Reports

Quy Nguyen Developer Create UT Cases, UT Reports

4.2 System

Software Version
Microsoft Windows Server 2003 SP2

G1/QP/SWP391 v1.1 14/16

<QP>-Test plan v<xxx>

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 11/05/23 11/10/23

Review & Update Test Plan 2 11/10/23 11/18/23

Create IT&ST Test Cases 13 11/18/23 11/28/23

Review & Update IT&ST Test 2 11/28/23 11/30/23

Cases

Create & Execute & Report UT for 15 11/30/23 12/02/23

Software Package version 1.0

Create test data for Software 1 12/02/23 12/10/23

Package version 1.0

UT Gate for Software Package 0.5 12/10/23 12/11/23

version 1.0

Execute IT for Software Package 16 12/10/23 12/20/23

version 1.0

Execute ST for Software Package 4 12/20/23 12/24/23

version 1.0

Create IT&ST Test Report for 1 12/24/23 12/25/23

Software Package version 1.0

Create & Execute & Report UT for 22 12/25/23 01/05/24

Software Package version 1.1

UT Gate for Software Package 0.5 01/05/24 01/05/24

version 1.1

Create test data for Software 1 01/06/24 01/07/24

Package version 1.1

Execute IT for Software Package 17 01/07/24 01/12/24

version 1.1

Execute ST for Software Package 5 01/13/24 01/15/24

version 1.1

Create IT&ST Test Report for 1 01/15/24 01/16/24

Software Package version 1.1

G1/QP/SWP391 v1.1 15/16

<QP>-Test plan v<xxx>

Execute System Test for Software 8 01/19/24 01/24/24

Package final version

Create Test Report for Software 1 01/25/24 01/25/24

Package final version

6 DELIVERABLES

No Deliverables Delivered Date Delivered by Delivered to

1 Test Plan 11/20/23 G1 Quikk

2 Test Reports for Software 01/01/24 G1 Quikk

Package version 1.0

3 Test Reports for Software 01/15/24 G1 Quikk

Package version 1.1

4 Test Reports for Software 01/31/24 G1 Quikk

Package final version

G1/QP/SWP391 v1.1 16/16