Testplan 1 9 thực hành kiểm tra phần mềm

UNIVERSITY OF TECHNOLOGY HCMC
Faculty of Computer Science and Engineering

TESTING SOFTWARES ASSIGNMENT

TESTING FUNCTIONS AND SERVICES IN
YOUTUBE
TEST PLAN

Group CS09
1. Bùi Đức Hiếu
2. Trần Duy Khoa
3. Phạm Duy Tiến
4. Nguyễn Ngọc Hoàng


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

This test approach document describes the appropriate strategies, process, workflows and
methodologies used to plan, organize, execute and manage testing of software projects for testing
functions and services in />
1.1

Purpose

Testing some main functional requirements and the most used services in a video-

sharing website .
1.2

Scope

1.2.1. In Scope
Some services /function must be tested



1. Youtube account:
a. Create an new account.
b. Modify information of an account.
c. Login to site.
2. Upload a video:
a. Upload a video
b. Remove a video in this site.
3. Write some comment in a video:
a. Set a comment in a video.
b. Modify a comment.
c. Remove a comment.
d. Reply a comment .
4. Searching a video in Youtube.
a. Basic searching.
i.
Searching by a word or keys.
ii.

Searching by a word or keys with special character ? *
iii.
Searching and return result by a word in key values.
b. Advance searching.
i.
Make more conditions in basic searching to limit return results.
1.2.2. Out Scope:
The following are considered out of scope for YouTube system Test Plan and
testing scope:
Functional requirements testing for systems outside requirements


1.3

Check qualify of videos in YouTube.

Definitions and Abbreviations/Acronyms
1.3.1 Definitions

Terms

Definition


1.3.2 Abbreviations/Acronyms
Abbreviation /
Acronyms

Description

Acc

Account of a user on Youtube

Pass

Password of a user on Youtube

Customers

A user who use some services on Youtube

1.4

Users of the Document

1.4.1

Test Approach Document
The Test Approach document is derived from the Project Plan,
Requirements and Functional Specification documents. This document defines
the overall test approach to be taken for the project. The Standard Test Approach
document that you are currently reading is a boilerplate from which the more
specific project Test Approach document can be extracted.
When this document is completed, the Test Lead will distribute it to the
Product Manager, Development Lead, User Representative, Program Manager,
and others as needed for review and sign-off.
1.4.2

Test Plan

The Test Plan is derived from the Test Approach, Requirements,
Functional Specs, and detailed Design Specs. The Test Plan identifies the details
of the test approach, identifying the associated test case areas within the specific
product for this release cycle.
The purpose of the Test Plan document is to:










Specify the approach that Testing will use to test the product, and the
deliverables (extract from the Test Approach).
Break the product down into distinct areas and identify features of the product
that are to be tested.
Specify the procedures to be used for testing sign-off and product release.
Indicate the tools used to test the product.
List the resource and scheduling plans.
Indicate the contact persons responsible for various areas of the project.
Identify risks and contingency plans that may impact the testing of the
product.
Specify bug management procedures for the project.
Specify criteria for acceptance of development drops to testing (of builds).

1.4.3

Test Schedule
This section is not vital to the document as a whole and can be modified or
deleted if needed by the author.


The Test Schedule is the responsibility of the Test Lead (or Department
Scheduler, if one exists) and will be based on information from the Project
Scheduler (done by Product Manager). The project specific Test Schedule may
be done in MS Project.
1.4.4

Test Specifications
A Test Specification document is derived from the Test Plan as well as the
Requirements, Functional Spec., and Design Spec documents. It provides
specifications for the construction of Test Cases and includes list(s) of test case
areas and test objectives for each of the components to be tested as identified in
the project’s Test Plan.


2

3

References and Related Documents


Project Specification document anf Requirements



Test Case Template



Test Schedule

Schedules and Milestone
Milestone

4

Deliverables

Duration
(day)

Start Date

End Date

Begin

13

May 27,2012

June 8,2012

Revision

4

May 27,2012

May 31,2012

Survey

7

May 27,2012

June 2,2012

Execution

7

June 1, 2012

June 8,2012

Resource Requirements
4.1

Hardware

PC Specific Requirements:
 Processor: 500MHz or faster
 RAM: 128MB or more



Video Card: at least 64MB of video memory



Sound Card: at least 16-bit

Mac Specific Requirements:
 Processor: 1.83MHz Intel Core Duo or faster
 RAM: 128MB or more


Video Card: at least 64MB of video memory



Sound Card: at least 16-bit


4.2

Software
General System Requirements:



Adobe Flash Player 10.0.22+ plug-in
Firefox 1.1+, Internet Explorer 7.0+, Safari 1.0+, Google Chrome, or Opera



Broadband connection with 500+ Kbps

PC Specific Requirements:
 Platform: Windows 2000 or higher with latest updates installed
Mac Specific Requirements:
 Platform: Mac OS X 10.3 or higher with latest updates installed
Ubuntu Specific Requirements:
 Platform: Ubuntu 10.10 or higher with latest updates installed
Optimal system requirements (recommended for movies on YouTube and Live
Streaming Content):
 Flash Player: Adobe Flash Player 11.2+
 Browser: Firefox 12.0+, Internet Explorer 9.0+, Safari 5.0+, or Google
Chrome 18.0+

4.3



Operating System: Windows 7+, Mac OS X 10.7+, Ubuntu 10+ and Linux OS
11+ (64-bit)



Internet Connection: 1 Mbps or higher
Tools used for Testing

Tools: FireFox 10.0, Google Chrome 18, IE 7, IE8

4.4

Test Environment

Window 7 32bit 6.1 build 7600, Ubutu 11.04 32bit with Adobe Flash Player 11.2+

4.5 Staffing
4.5.1 Roles and Responsibilities
Revision

Execution


4.5.2 Training

5



White Box testing



Function testing



Facility testing



Volume testing



Usability tesing



Security testing



Configuration testing

Test Scope
5.1

Features to be tested


Youtube accounts



Create a new account.



Edit an account.



Login the system.



Upload a video



Upload a video.



Delete a video.



Comments



Create a comment.



Edit a comment.



Delete a comment.



Reply of another user.

5.2 Features not to be tested


Create account
o



Create an account by using Google+ account.

Update information
o

Edit user information don’t check correctly of Capcha.





Delete
o



Don’t check action that cancel a video when it is being uploaded.

Search
o

6

Update avatar choose image uncorrectly.

Don’t check advanced search when system at safe mode.

Test Strategies
6.1

Test Stages
6.1.1 Unit Testing

Inputs/ Entry Criteria An action interact with the services: Create/edit a account, Login,
Upload/delete a video, create/edit/ delete/ reply comments …
Automation Tool
Used*

Some browser: FireFox 10.0, Google Chrome 18, IE 7, IE8

Suspension Criteria** An error is displayed on the monitor and breaks the browser
when a user implement the services.
Resumption
Criteria***

After the developer announce to the manager and receive the new
requires.

Outputs/Exit Criteria

A confirm message displays on screen or some information is
updated in user page.

Responsibility
(Developer / tester /
Customer, etc)

Developer

How to perform
Manual
(Manual / automated ,
etc)
When to perform
(During interim
build / iteration
release / project
release, etc)

When the services finishes a completely functions of its.


6.1.2 Integration Testing
Inputs/ Entry Criteria Some action interact with some services after it is integrated:
Create/edit a account, Login, Upload/delete a video, create/edit/

delete/ reply comments …
Some browser: FireFox 10.0, Google Chrome 18, IE 7, IE8
Automation Tool
Used
Suspension Criteria

An error is displayed on the monitor and breaks the browser when
a user implement the services.

Resumption
Criteria

After the developer announce to the manager and receive the new
requires.

Outputs/Exit Criteria A confirm message displays on screen or some information of
services are updated in user page.
Responsibility
(Developer / tester /
Customer, etc)

Tester

How to perform
Automated
(Manual / automated ,
etc)
When to perform
(During interim
build / iteration

release / project
release, etc)

After some of services is integrated on the system and it will
repeat if some new services is updated on Youtube.

6.1.3 System Testing
Inputs/ Entry Criteria A video with big capacity, some simultaneous requires,
Automation Tool
Used

Some Operation System like Windows, Linux and Mac OS
Some browser: FireFox 10.0, Google Chrome 18, IE 7, IE8

Suspension Criteria

When Internet is cutted off

Resumption
Criteria

Restart the system.

Outputs/Exit Criteria A confirm message displays on screen.
Responsibility
(Developer / tester /

Tester

Customer, etc)
How to perform
Manual
(Manual / automated ,
etc)
When to perform
(During interim
build / iteration
release / project
release, etc)

After a state of website with some services finish and integrate on
the system.

6.1.4 Acceptance Testing
Inputs/ Entry Criteria

Some questions interact with some services such as: Accounts
Information, Comments …

Automation Tool Used

Google docs

Suspension Criteria

Until the deadline of our survey (1 week after the survey
began).

Resumption

Criteria

When a new version is updated and producer want to ask the
customers.

Outputs/Exit Criteria

Report about opinions of user about Youtube services.

Responsibility
(Developer / tester /
Customer, etc)

Customer

How to perform
(Manual / automated ,
etc)

Contents that was made by tester depends on contents of
services and is released on Social network to get the opinions.
Automated by using Google docs.

When to perform
(During interim build /
iteration release /
project release, etc)

May 27, 2012

6.2

Types of Testing
6.2.1 Functionality Testing

Inputs/ Entry Criteria Login on the system with random accounts, input some data on
search text field or update user profiles
Automation Tool
Used

Some browser: FireFox 10.0, Google Chrome 18, IE 7, IE8


Suspension Criteria

An error is displayed on the monitor and breaks the browser when
a user implement the services.

Resumption
Criteria

After the developer announce to the manager and receive the new
requires.

Outputs/Exit Criteria A confirm message displays on screen or some information of
services are updated in user page.
Responsibility
(Developer / tester /
Customer, etc)

Tester, Database Administrations, Developer

How to perform
Manual, Automated on database
(Manual / automated ,
etc)
When to perform
(During interim
build / iteration
release / project
release, etc)

After a functions complete.

6.2.2 Regression Testing
Inputs/ Entry Criteria An action interact with the services or some questions interact
with some services
Automation Tool
Used

Some Operation System like Windows, Linux and Mac OS
Some browser: FireFox 10.0, Google Chrome 18, IE 7, IE8

Suspension Criteria

An error is displayed on the monitor and breaks the browser when
a user implement the services.

Resumption
Criteria

After the developer announce to the manager and receive the new
requires.

Outputs/Exit Criteria A confirm message displays on screen or some information of
services are updated in user page.
Responsibility
(Developer / tester /
Customer, etc)

Tester, Director of tester

How to perform
Automated, Manual
(Manual / automated ,
etc)
When to perform
(During interim
build / iteration
release / project
release, etc)

After a new version of website or services, code is updated
Iteration release


6.2.3 Security and Access Control Testing
Inputs/ Entry Criteria Upload a new video in a user account, Login on system.
Automation Tool
Used

Some browser: FireFox 10.0, Google Chrome 18, IE 7, IE8

Suspension Criteria

An error is displayed on the monitor and breaks the browser when
a user implement the services.

Resumption
Criteria

After the developer announce to the manager and receive the new
requires.

Outputs/Exit Criteria Check user’s data integrity, check user’s access control.
Responsibility
(Developer / tester /
Customer, etc)

Developer, Tester, Customer

How to perform
Manual
(Manual / automated ,
etc)
When to perform
(During interim
build / iteration
release / project
release, etc)

6.3

Iteration release

Other Testing
6.3.1 Hot Fix / Patch Testing
6.3.2 Data-Migration Testing

7

Acceptance Criteria
- About 80% of customer satisfied in new youtube accounts registration services by
using Google account or Youtube directly.
- About 100% of customer satisfied with the state login on user accounts when they
visit Youtube website.
- About 80% of customer satisfied with mechanism edit accounts of Youtube.
- About 70% of customer satisfied with the speed of uploading a new video on
Youtube.
- About 90% of customer satisfied with the quality of a new video on Youtube.
- About 70% of customer satisfied with mechanism delete a video in their account.
- About 80% of customer satisfied with mechanism create comments.


- About 10% of customer satisfied with mechanism delete comments.
- About 15% of customer satisfied with mechanism edit comments.
- About 80% of customer satisfied with mechanism search services on Youtube.
- About 90% of customer satisfied with mechanism advanced search services on
Youtube.

8

Defect Tracking
8.1

Defect Classification

Although our team try our best but we can’t test all of cases in process interact with
Youtube account, Upload videos, Comments.

8.2

9

Defect Life Cycle

Test Deliverables
9.1

Test Cases

Nhom_CS09_Youtube/Testcase_Final_Version.1.6.xls

9.2

Test Reports

Nhom_CS09_Youtube/Testplan.1.9.doc