International School

Capstone Project 2
CMU-SE 451

Test Plan Document for Sprint 3

Version 1.0
Date: Mar 15th, 2023

Map Travel Assistant Website

Submitted by

Dong, Pham Van

Han, Nguyen Quang
Hieu, Ngo Quoc
Huy, Tran Khanh
Tam, Diep Dinh

Approved by
Thanh, Nguyen Trong M.Sc.

Test Plan Review Panel Representative:

Name Signature Date

Capstone Project 2- Mentor:

Name Signature Date

 PROJECT INFORMATION

Project
MTAW
acronym
Project Title Map Travel Assistant Website
Start Date 21 Feb 2023 End Date 20 May 2023
Lead
International School, Duy Tan University
Institution
Project
Thanh, Nguyen Trong, M.Sc
Mentor
Scrum master
Dong, Pham Van
/ Project
Email: dongpham21082001@gmail.com
Leader &
Tel: (+84) 853390931
contact details
Partner
Organization
Project Web
URL
Team
Name Email Tel
members
25211207283 Dong, Pham Van dongpham21082001@gmail.com 0853390931
Han, Nguyen
25211211605 quanghannguyen14@gmail.com 0335271532
Quang
25211211751 Hieu, Ngo Quoc quochieutb12@gmail.com 0777748073

25211207733 Huy, Tran Khanh tranhuy1st113@gmail.com 0368595273

25211405191 Tam, Diep Dinh dinhtam6102@gmail.com 0378909721

Version Date Comments Author Approval
1.0 15 Mar 2023 Initial Release All Members
 Contents
1. Introduction 4

1.1. Purpose 4

1.2. Scope 4

1.3. Out of Scope 4

1.4. References 4

2. Target Test Areas 4

3. Test Specification 5

3.1. Features to be tested 5

3.2. Feature not to be tested 5

3.3. Test Deliverables 5

4. Test Schedule 6

5. Test Cycle Entry and Exit Criteria 8

5.1. Entry Criteria 8

5.2. Exit Criteria 8

6. Environmental Needs 8

6.1. Hardware and Software 8

6.2. Productivity and Support Tools 8

7. Roles and Responsibilities 10

2. Target Test Areas
- Backend testing
- GUI Testing
- Functional Testing
- System Testing
3. Test Specification
3.1. Features to be tested
- [Frontend] Create Fanpage (Owner)
- [Frontend] View ratting (Owner)
- [Backend] Create Fanpage (Owner)
- [Backend] View ratting (Owner)
- [Frontend] Comment (Owner)
- [Backend] Comment (Owner)
- [Frontend] Create Post (Owner)
- [Backend] Create Post (Owner)
3.2. Feature not to be tested
Not applicable as all features will be tested.
3.3. Test Deliverables
- Test Plan Document.
- Test Case Document.
- Test Summary Report.
4. Test Schedule

Duration Resourc
No Task Name Start Finish
(hrs.) e
All
31
1 Sprint 3 14/04/23 04/05/23 member
s

1.1 Design test case 16/04/23 17/04/23 11

[Frontend] Profile
Fanpage (Owner) 1

[Frontend] View ratting

(Owner) 1

[Backend] Profile 1
Fanpage (Owner)

[Backend] View ratting

(Owner) 2

[Frontend] Comment
(Owner) 1

[Backend] Comment 1
(Owner)

[Frontend] Create Post

2
(Owner)

[Backend] Create Post

(Owner) 2

1.2 Testing 22/04/23 23/04/23 10

[Frontend] Profile
Fanpage (Owner) 1

[Frontend] View ratting

(Owner) 1

[Backend] Profile 1
Fanpage (Owner)
 [Backend] View ratting
(Owner) 2

[Frontend] Comment
(Owner) 1

[Backend] Comment 1
(Owner)

[Frontend] Create Post

2
(Owner)

[Backend] Create Post

(Owner) 1

1.3 Re- Testing 02/05/23 03/05/23 10

[Frontend] Profile
Fanpage (Owner) 1

[Frontend] View ratting

(Owner) 1

[Backend] Profile 1
Fanpage (Owner)

[Backend] View ratting

(Owner) 2

[Frontend] Comment
(Owner) 1

[Backend] Comment 1
(Owner)

[Frontend] Create Post

2
(Owner)

[Backend] Create Post

(Owner) 1

5. Test Cycle Entry and Exit Criteria

5.1. Entry Criteria
 - All testing hardware platforms must have been successfully installed, configured
and functioning properly.
- All the necessary documentation, design, and requirements information should be
available that will allow testers to operate the system and judge the correct
behavior.
- Proper test case is available.
- The test environment such as lab, hardware, software, and system administration
support should be ready.

5.2. Exit Criteria

- All test cases have been run.
- A certain level of requirements coverage has been achieved.
- No high priority or severe bugs are left outstanding.
- All high-risk areas have been fully tested, with only minor residual risks left
outstanding.
- The schedule has been achieved.

6. Environmental Needs
6.1. Hardware and Software

Resource Configuration Installed OS, Software

- CPU: Intel® Core™ i5 - Window 10
Laptop
- Ram: 8 GB. - Visual Studio Code

6.2. Productivity and Support Tools

Tool’s purpose Tool Name Vendor or In-house Version

Test APIs, examine
Postman 10.6.0
responses
7. Roles and Responsibilities

Roles Resources Responsibilities

- Ensure the project is delivered to
schedule, budget & quality.
- Regularly review Testing progress with
Test Leader.
Scrum
- Raise and manage issues/risks relating
Maste Dong, Pham Van
to the project or outside Test Teams
r
control.
- Review Test approach plans and
schedule.
- Provide technical support
- Review high level / detailed test plans
- Resolve design issues
Dong, Pham Van
Devel - Resolve development issues
Han, Nguyen Quang
op Hieu, Ngo Quoc - Support user acceptance testing
Team Huy, Tran Khanh - Develop Unit test scripts
Tam, Diep Dinh
- Make Unit test
- Fix bugs
- Identifies, prioritizes, and implements
test cases
- Generate test plan
- Generate Test Suite
- Evaluate the effectiveness of test effort
Dong, Pham Van
- Execute tests
Han, Nguyen Quang
QA Team Hieu, Ngo Quoc - Log results
Huy, Tran Khanh - Recover from errors
Tam, Diep Dinh
- Document defects
- Regularly review Testing progress
- Manage issues/risks relating to System
Test Team
- Identify Test Data