CAPSTONE PROJECT 2

TEST PLAN DOCUMENT

Music Recommendation
CODE: TEST PLAN
Date : February 26, 2023

Submitted by
Lam, Nguyen Viet Minh
Thi, Pham An
Thanh, Nguyen Tan
Huy, Chau Ngoc

Approved by Mentor
Man, Nguyen Duc PhD

Test Plan Review Panel Representative:

Name Signature Date

Capstone Project 2 - Mentor:

Name Signature Date

 Test Plan Document | C2SE.23

PROJECT INFORMATION

Project acronym MR
Project Tittle Music Recommendation
Start Date 17 March 2023 End Date 20 May 2023

Lead Institution International School, Duy Tan University

Project Mentor Man, Nguyen Duc, Ph.D.
Email: mannd@duytan.edu.vn
Phone: 0904235945
Project Manager Lam, Nguyen Viet Minh
& contact details Email: minhlamnguyenviet@gmail.com
Tel: 0935040813
Partner
Organization
Team members Name Email Tel
Lam, Nguyen Viet Minhlamnguyenviet@g 0935040813
Minh mail.com
Thi, Pham An Binc234@gmail.com 0787350188

Thanh, Nguyen Tan Thanhdatofficial4@gmai 0848999299

l.com
Huy, Chau Ngoc chaungochuy0801@gmai 0905293654
l.com

C2SE.23 TEAM 2
 Test Plan Document | C2SE.23

TEST PLAN DOCUMENT

Document Title Test Plan Document

Author(s) C2SE.23

Role C2SE.23-TestPlan

Date February 26, 2023 File name: C2SE.23-TestPlan-MR

URL

Access Project and CMU Program

REVISION HISTORY
Version Person(s) Date Description

Initiate document, finish

1.0 Huy February 26, 2023
content of document

1.1 Huy March 13, 2023 Update estimate

1.2 Huy April 1, 2023 Finally document

C2SE.23 TEAM 3
 Test Plan Document | C2SE.23

SIGNATURE

Document Approvals: The following signatures are required for approval of this
document.
Signature:
Mentor Man, Nguyen Duc, PhD
Date:

Signature:
Scrum master Lam, Nguyen Viet Minh
Date:

Signature:
Thi, Pham An
Date:

Team Signature:
Thanh, Nguyen Tan
member(s) Date:

Signature:
Huy, Chau Ngoc
Date:

C2SE.23 TEAM 4
 Test Plan Document | C2SE.23

I. Introduction............................................................................................................7

1. Purpose................................................................................................................7

2. Scope....................................................................................................................7

3. Out of Scope:.......................................................................................................7

4. Document Terminology and Acronyms............................................................7

5. References...........................................................................................................8

II. Target Test Areas...............................................................................................8

III. Test Specification................................................................................................8

1. Features to be Tested..........................................................................................8

2. Feature not to be Tested.....................................................................................9

3. Test Deliverables.................................................................................................9

IV. Test Schedule....................................................................................................10

V. Test Cycle Entry and Exit Criteria.................................................................17

1. Entry Criteria...................................................................................................17

2. Exit Criteria......................................................................................................17

VI. Environment Needs..........................................................................................17

1. Hardware and Software...................................................................................17

2. Productivity and Support Tools......................................................................18

VII. Roles and Responsibilities................................................................................18

C2SE.23 TEAM 5
 Test Plan Document | C2SE.23

Table

Table 1: Document Terminology and Acronyms 6

Table 2: References 7

Table 3: Test Schedule 13

Table 4: Hardware and Software 14

Table 5: Productivity and Support Tools 15

Table 6: Roles and Responsibilities 15

C2SE.23 TEAM 6
 Test Plan Document | C2SE.23

I. Introduction

1. Purpose

The document provides an overview of the project includes the purpose and scope of
project.

In addition, identifying business needs, problems or situation related to the

initialization and construction projects.

Provide solution for business needs and give the overview of system architecture.

Provide overview about resources, schedule, solution and budget for the project.

2. Scope

This document provides an overview of project will be developed. It includes

overview of the product, overview of the process and overview of the project team.

This document provides a plan for each stage of software development process based
on Scrum process included: start time, end time and number of working days. This is
the general plan and will be updated with detail of the software development process
in the next document.

Proposal includes the introduction of solutions, determine the best way to develop
software that we make, the total estimated costs, payback period, break-even volume
for the project.

3. Out of Scope:
Security Testing

4. Document Terminology and Acronyms

ID. Item Description

MR Music Recommendation

Table 1: Document Terminology and Acronyms

C2SE.23 TEAM 7
 Test Plan Document | C2SE.23

5. References

No. References Document Information

https://scrum.org/resources/what-
1 Scrum Process
is-scrum

Proposal Document

Product Backlog Document

2 Document
Project Plan Document

Table 2: References

II. Target Test Areas

● Unit Testing

● Integration Testing

● System Testing

III. Test Specification

1. Features to be Tested

FE01: The Login

FE02: The Logout

FE03: Register

FE04: Homepage

FE05: Emotion recognition

FE06: List friend

FE07: Play Music

C2SE.23 TEAM 8
 Test Plan Document | C2SE.23

FE08: Delete song in playlist

FE09: Music recommendation

FE10: Playlist

FE11: Create playlist

FE12: Search music

FE13: Find sympathizers

FE14: Manage playlist

FE15: Show recently listened songs

FE16: Bot Automation

FE17: Management Mood

FE18: Management Users

FE19: Management Songs

FE20: Statistics Sashboard

FE21: Chat Bot

FE22: Aotumation Bot

2. Feaure not to be Tested

Not Applicable as all features will be tested.

3. Test Deliverables

● Test Plan Document

● Test Case Document

● Test Summary Report

C2SE.23 TEAM 9
 Test Plan Document | C2SE.23

IV. Test Schedule

Duration
No. Task Name Start Finish Resource
(Hour)

1 Sprint 1

Create Test Plan

1.1 1 Mar 6, 2023 Mar 6, 2023 Huy
Document for Sprint 1

1.2 Design Test Case

Design Test case of “The Huy

2 Mar 6, 2023 Mar 6, 2023
Login”

Design Test case of “The Huy

2 Mar 6, 2023 Mar 6, 2023
Logout”

Design Test case of Huy

2 Mar 6, 2023 Mar 6, 2023
“Register”

Design Test case of Huy

2 Mar 6, 2023 Mar 6, 2023
“Homepage”

Design Test case of Huy

“Face recognition 2 Mar 6, 2023 Mar 6, 2023
framework”

Design Test case of “List Huy

1 Mar 6, 2023 Mar 6, 2023
friend”

Design Test case of “Play Huy

2 Mar 6, 2023 Mar 6, 2023
Music”

1.3 Testing

C2SE.23 TEAM 10
 Test Plan Document | C2SE.23

Mar 22, Mar 22,

Test feature “The Login” 2 Huy
2023 2023

Mar 22, Mar 22,

Test feature “The Logout” 1 Huy
2023 2023

Mar 22, Mar 22,

Test feature “Register” 2 Huy
2023 2023

Mar 22, Mar 22,

Test feature “Homepage” 1 Huy
2023 2023

Test feature “Face Mar 23, Mar 23,

2 Huy
recognition framework” 2023 2023

Mar 23, Mar 23,

Test feature “List friend” 1 Huy
2023 2023

Mar 23, Mar 23,

Test feature “Play Music” 2 Huy
2023 2023

1.4 Re-Testing

Mar 27, Mar 27,

Re-test feature “The Login” 2
2023 2023

Re-test feature “The Mar 27, Mar 27,

1
Logout” 2023 2023

Mar 27, Mar 27,

Re-test feature “Register” 2
2023 2023

Re-test feature Mar 27, Mar 27,

1
“Homepage” 2023 2023

C2SE.23 TEAM 11
 Test Plan Document | C2SE.23

Re-test feature “Face Mar 27, Mar 27,

2
recognition framework” 2023 2023

Mar 27, Mar 27,

Re-test feature “List friend” 1
2023 2023

Re-test feature “Play Mar 27, Mar 27,

2
Music” 2023 2023

2 Sprint 2

Create Test Plan Mar 29, Mar 29, Huy

2.1 1
Document for Sprint 2 2023 2023

2.2 Design Test Case Huy

Design Test case of “Music Apr 1,2023 Apr 1,2023 Huy

2
recommendation”

Design Test case of Apr 1,2023 Apr 1,2023 Huy

2
“Playlist”

Design Test case of “Create Apr 1,2023 Apr 1,2023 Huy

2
playlist”

Design Test case of Apr 1,2023 Apr 1,2023 Huy

1
“Search music”

Design Test case of “Find Apr 1,2023 Apr 1,2023 Huy

2
sympathizers”

Design Test case of Apr 1,2023 Apr 1,2023 Huy

2
“Manage playlist”

Design Test case of 2 Apr 1,2023 Apr 1,2023 Huy

“Delete song in

C2SE.23 TEAM 12
 Test Plan Document | C2SE.23

playlist”

Design Test case of “Show Apr 1,2023 Apr 1,2023 Huy

2
recently listened songs”

2.3 Testing

Test feature “Music Apr Huy

2 Apr 14,2023
recommendation” 14,2023

Apr Huy
Test feature “Playlist” 2 Apr 14,2023
14,2023

Test feature “Create Apr Huy

2 Apr 14,2023
playlist” 14,2023

Test feature “Search Apr Huy

1 Apr 14,2023
music” 14,2023

Test feature “Find Apr Huy

2 Apr 15,2023
sympathizers” 15,2023

Test feature “Manage Apr Huy

2 Apr 15,2023
playlist” 15,2023

Test feature “Delete song Apr Apr 15,2023 Huy

2
in playlist” 15,2023

Test feature “Show recently Apr Apr 15,2023 Huy

2
listened songs” 15,2023

2.4 Re-Testing

Re-test feature “Music Apr Apr 19,2023

1
recommendation” 19,2023

C2SE.23 TEAM 13
 Test Plan Document | C2SE.23

Apr Apr 19,2023

Test feature “Playlist” 1
19,2023

Re-test feature “Create Apr Apr 19,2023

1
playlist” 19,2023

Re-test feature “Search Apr Apr 19,2023

1
music” 19,2023

Re-test feature “Find Apr Apr 19,2023

1
sympathizers” 19,2023

Re-test feature “Manage Apr Apr 19,2023

1
playlist” 19,2023

Re-test feature “Delete Apr Apr 19,2023

2
song in playlist” 19,2023

Re-test feature “Show Apr Apr 19,2023

2
recently listened songs” 19,2023

3 Sprint 3

Create Test Plan Apr

3.1 1 Apr 21,2023 Lâm
Document for Sprint 3 21,2023

3.2 Design Test Case

Design Test case of “Bot Apr 24, Apr 24, Huy

2
Automation” 2023 2023

Design Test case of Apr 24, Apr 24, Huy

2
“Management mood” 2023 2023

Design Test case of Apr 24, Apr 24, Huy

2
“Management users” 2023 2023

C2SE.23 TEAM 14
 Test Plan Document | C2SE.23

Design Test case of Apr 24, Apr 24, Huy

2
“Management songs” 2023 2023

Design Test case of Apr 24, Apr 24, Huy

2
“Statistics dashboard” 2023 2023

Design Test case of “Chat Apr 24, Apr 24, Huy

2
Bot” 2023 2023

Design Test case of Apr 24, Apr 24, Huy

2
“Aotumation Bot” 2023 2023

3.3 Testing

Test feature “Bot May 10, May 10, Huy

2
Automation” 2023 2023

Test feature “Management May 10, May 10, Huy

2
mood” 2023 2023

Test feature “Management May 10, May 10, Huy

2
users” 2023 2023

Test feature “Management May 11, May 11, Huy

2
songs” 2023 2023

Test feature “Statistics May 11, May 11, Huy

2
dashboard” 2023 2023

May 11, May 11, Huy

Test feature “Chat Bot” 2
2023 2023

Test feature “Aotumation May 11, May 11, Huy

2
Bot” 2023 2023

C2SE.23 TEAM 15
 Test Plan Document | C2SE.23

3.4 Re-Testing

Re-test feature “Bot May 15, May 15,

2
Automation” 2023 2023

Re-test feature May 15, May 15,

2
“Management mood” 2023 2023

Re-test feature May 15, May 15,

2
“Management users” 2023 2023

Re-test feature May 15, May 15,

2
“Management songs” 2023 2023

Re-test feature “Statistics May 15, May 15,

2
dashboard” 2023 2023

May 15, May 15,

Re-test feature “Chat Bot” 2
2023 2023

Re-test feature May 15, May 15,

2
“Aotumation Bot” 2023 2023

Table 3: Test Schedule

C2SE.23 TEAM 16
 Test Plan Document | C2SE.23

V. Test Cycle Entry and Exit Criteria

1. Entry Criteria

● All test 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.

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.

VI. Environment Needs

1. Hardware and Software

Resource Configuration Installed OS, Software

C2SE.23 TEAM 17
 Test Plan Document | C2SE.23

Laptop Internet Access Chrome

Table 4: Hardware and Software

2. Productivity and Support Tools

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

Project Management Drive Google N/A

Project Documented Microsoft Office Microsoft 10

Table 5: Productivity and Support Tools

VII. Roles and Responsibilities

Roles Responsibilities

Ensure the project is delivered to schedule, budget & quality.

Regularly review Testing progress with Test Leader.

Raise and manage issues/risks relating to project or outside.

Management Team
Test Teams control.

Review Test approach plans and schedule.

Provide technical support.

Develop Team Review high level / detailed test plans.

Resolve design issues.

Resolve development issues.

Support user acceptance testing.

Develop Unit test scripts.

C2SE.23 TEAM 18
 Test Plan Document | C2SE.23

Make Unit test.

Fix bugs.

Identifies, prioritizes, and implements test cases.

Generate test plan.

Generate Test Suite.

Evaluate effectiveness of test effort

Execute tests

QA Team Log results

Recover from errors

Document defects

Regularly review Testing progress

Manage issues/risks relating to System Test Team

Identify Test Data

Table 6: Roles and Responsibilities

C2SE.23 TEAM 19