BÀI TẬP LỚN MÔN TESTING
Đề tài: Web site âm nhạc Nhaccuatui.com
Người hướng dẫn: Hai Ho
Nhóm thực hiện:
o Trương Cơng Vũ – 50802688
o Trịnh Hoàng Vũ – 50802687
o Võ Thành Tài – 50801862
o Lê Tuấn Sơn – 50801809
o Nguyễn Hoàng Thế Vinh – 50802629
Hồ Chí Minh, tháng 06 năm 2012
Revision History
Date
Version
Description
Prepared by
Reviewed by Approved By
22/05/2012 1.0
Test 4 functions of
nhactuatui.com website
vuholmes
group
vuholmes
group
vuholmes
group
22/06/2012 1.1
Test 4 functions of
nhactuatui.com website
vuholmes
group
vuholmes
group
vuholmes
group
[The section below is to keep track the revision history of this template itself. Remember
to delete this section when using this template
Content
1
Introduction......................................................................................................4
1.1
Purpose............................................................................................................4
1.2
Scope...............................................................................................................4
1.3
Definitions and Abbreviations/Acronyms.........................................................4
1.4
1.3.1
Definitions............................................................................................4
1.3.2
Abbreviations/Acronyms......................................................................4
Users of the Document....................................................................................4
2
References and Related Documents...............................................................4
3
Schedules and Milestone.................................................................................4
4
Resource Requirements..................................................................................4
4.1
Hardware.........................................................................................................4
4.2
Software...........................................................................................................5
4.3
Tools used for Testing.....................................................................................5
4.4
Test Environment.............................................................................................5
4.5
Staffing.............................................................................................................5
5
4.5.1
Roles and Responsibilities...................................................................5
4.5.2
Training................................................................................................5
Test Scope.......................................................................................................5
5.1
Features to be tested.......................................................................................5
5.2
Features not to be tested.................................................................................5
6
Test Strategies.................................................................................................5
6.1
6.2
6.3
Test Stages......................................................................................................6
6.1.1
Unit Testing..........................................................................................6
6.1.2
Integration Testing...............................................................................6
6.1.3
System Testing....................................................................................7
6.1.4
Acceptance Testing.............................................................................7
Types of Testing..............................................................................................8
6.2.1
Functionality Testing............................................................................8
6.2.2
Regression Testing..............................................................................8
6.2.3
Security and Access Control Testing...................................................9
Other Testing.................................................................................................10
6.3.1
Hot Fix / Patch Testing......................................................................10
6.3.2
Data-Migration Testing......................................................................10
7
Acceptance Criteria........................................................................................10
8
Defect Tracking..............................................................................................10
8.1
Defect Classification......................................................................................10
8.2
Defect Life Cycle............................................................................................10
9
Test Deliverables...........................................................................................10
9.1
Test Cases.....................................................................................................10
9.2
Test Reports..................................................................................................10
1
Introduction
1.1 Purpose
The purpose of the Iteration Test Plan is to gather all of the information necessary
to plan and control the test effort for a given iteration. It describes the approach to
testing the software, and is the top-level plan generated and used by managers to
direct the test effort.
This Test Plan for the website nhaccuatui.com the following objectives:
-
Identify the scope, environment, features to be tested and not to be tested,
risk and contingency, resources
-
List the recommended test requirements
-
Recommend and describe the testing approach to be employed
1.2 Scope
This document provides test requirements, test strategies for:
- Plan Test
- Design Test Case
- Report Test
In 4 test case type:
- Tìm kiếm
- Tạo tài khoản
- Quản lý hồ sơ cá nhân
- Mở bài hát/video/playlist
1.3 Definitions and Abbreviations/Acronyms
[Define the required definitions and Abbreviations /Acronyms]
1.3.1 Definitions
Terms
Definition
1.3.2 Abbreviations/Acronyms
Abbreviation / Description
Acronyms
1.4 Users of the Document
Testing was performed under the operating of team-leader Truong Cong Vu; all
Members of team group are:
- Truong Cong Vu
- Trinh Hoang Vu
- Vo Thanh Tai
- Nguyen Hoang The Vinh
- Le Tuan Son
2
References and Related Documents
Slides testing 2012 are written by Nguyen Van Hiep, Hochiminh City University of
Technology
3
Schedules and Milestone
Milestone
4
Deliverables
Duration
Start Date
End Date
Begin
Develop Test cases
18 days
20/05/2012
08/06/2012
Review
Test Case Review and fix
4 days
18/06/2012
21/06/2012
End
Complete Defect Reports
1 days
22/06/2012
22/06/2012
Resource Requirements
[Mention the Hardware/Software/Tools/Test environment/Staffing details required for this
project.]
4.1 Hardware
1 nhaccuatui.com server – provide by customer, pc– provide by tester
4.2 Software
3 browser: google chrome 10 up to, firefox 4 up to, internet explorer 8 – provide by
tester.
4.3 Tools used for Testing
3 PC, 1 wireless access point – provide by tester.
4.4 Test Environment
Windows 7 operation system, PC
4.5 Staffing
[Mention staffing details of this Project, this includes Roles and Responsibilities of
each individual and the Training Details]
4.5.1 Roles and Responsibilities
Human Resources
Role
Minimum
Recommended
Resources
(number of full-time roles allocated)
Specific Responsibilities or Comments
Test leader
Provides management oversight.
Responsibilities include:
Test Analyst
planning and logistics
agree mission
identify motivators
acquire appropriate resources
present management reporting
advocate the interests of test
evaluate effectiveness of test effort
Identifies and defines the specific tests to be
conducted.
Responsibilities include:
Test Designer
identify test ideas
define test details
determine test results
document change requests
evaluate product quality
Defines the technical approach
implementation of the test effort.
to
Responsibilities include:
Tester
define test approach
verify test techniques
structure test implementation
Implements and executes the tests.
Responsibilities include:
implement tests and test suites
execute test suites
log results
document incidents
4.5.2 Training
[If training is required for the quality control engineers to coordinate with the
project will be listed here]
5
Test Scope
5.1 Features to be tested
Test
Functional
Security
Performance
sanity
the
Type
Feature
Tìm kiếm
Tạo tài khoản
Quản lý hồ sơ cá nhân
Mở bài hát/video/playlist
Y
Y
Y
Y
N
Y
Y
N
Y
N
Y
Y
Y
Y
N
N
5.2 Features not to be tested
[List out all the features and significant combinations of features which will not be
tested in this project.]
6
Test Strategies
[Mention the levels of testing and techniques that will be used in this project for each
type of test, provide a description of the test and why it is being implemented and
executed.
If a type of test will not be implemented and executed, indicate this in a sentence stating
the test will not be implemented or executed and stating the justification, such as “This
test will not be implemented or executed. This test is not appropriate.”
Add/Remove/Modify sections below as per your project type]
6.1 Test Stages (only for Acceptance Testing)
6.1.1 Unit Testing
Inputs/ Entry
Criteria
Automation Tool
Used*
Suspension
Criteria**
Resumption
Criteria***
Outputs/Exit Criteria
Responsibility
(Developer / tester /
Customer, etc)
How to perform
(Manual /
automated , etc)
When to perform
(During interim build
/ iteration release /
project release, etc)
6.1.2 Integration Testing
Inputs/ Entry
Criteria
Automation Tool
Used
Suspension Criteria
Resumption
Criteria
Outputs/Exit
Criteria
Responsibility
(Developer / tester /
Customer, etc)
How to perform
(Manual /
automated , etc)
When to perform
(During interim
build / iteration
release / project
release, etc)
6.1.3 System Testing
Inputs/ Entry
Criteria
Automation Tool
Used
Suspension Criteria
Resumption
Criteria
Outputs/Exit
Criteria
Responsibility
(Developer / tester /
Customer, etc)
How to perform
(Manual /
automated , etc)
When to perform
(During interim
build / iteration
release / project
release, etc)
6.1.4 Acceptance Testing
Inputs/ Entry
Criteria
Automation Tool
Used
Browser: Google chrome, firefox, internet explorer
Suspension Criteria
Result is displayed or time out
Resumption
Criteria
Time remaining
Outputs/Exit Criteria
Responsibility
(Developer / tester /
Customer, etc)
tester
How to perform
Manual
(Manual / automated ,
etc)
When to perform
Project release
(During interim build /
iteration release /
project release, etc)
6.2 Types of Testing
6.2.1 Functionality Testing
Inputs/ Entry
Criteria
Automation Tool
Used
Browser: Google chrome, firefox, internet explorer
Suspension Criteria Result is displayed or time out
Resumption
Criteria
Outputs/Exit
Time remaining
Criteria
Responsibility
Tester, customer
(Developer / tester /
Customer, etc)
How to perform
(Manual /
automated , etc)
Manual
When to perform
(During interim
build / iteration
release / project
release, etc)
Project release
6.2.2 Regression Testing
Inputs/ Entry
Criteria
Automation Tool
Used
Suspension Criteria
Resumption
Criteria
Outputs/Exit
Criteria
Responsibility
(Developer / tester /
Customer, etc)
How to perform
(Manual /
automated , etc)
When to perform
(During interim
build / iteration
release / project
release, etc)
6.2.3 Security and Access Control Testing
Inputs/ Entry
Criteria
Automation Tool
Used
Browser: Google chrome, firefox, internet explorer
Suspension Criteria Result is displayed or time out.
Resumption
Criteria
Time remaining
Outputs/Exit
Criteria
Responsibility
tester
(Developer / tester /
Customer, etc)
How to perform
(Manual /
automated , etc)
Manual
When to perform
(During interim
build / iteration
release / project
release, etc)
project release
6.3 Other Testing
6.3.1 Hot Fix / Patch Testing
6.3.2 Data-Migration Testing
7
Acceptance Criteria
It satisfies the scope of the work described in this document, and it contains the content
described in the Deliverables section; or
Achievement of the specified test result for each test specified in the Acceptance Test
Plan
8
Defect Tracking
8.1 Defect Classification
Functional test only, performance test is hard to do
Only have four testers and their knowlegde are limited
We don’t know the technical of nhaccuatui.com website
8.2 Defect Life Cycle
[Mention the defect life cycle in this project from defect reporting to defect closure.]
9
Test Deliverables
9.1 Test Cases
[Provide link to the Test Cases document for this project here]
9.2 Test Reports
[Provide link to the Test Reports/Test Metrics generated for this project here]