Software Test Specification
Software Test Specification
YouTube Project
1 Page
YouTube
Table of Contents
1 Introduction
1.1
Purpose
1.2
Scope
1.3
Definitions, Acronyms and
Abbreviations
1.4
References
1.5
Overview of Contents of Documents
2. Test Plan Description
2.1
2.2
2.3
Product Summary
Responsibilities
Schedule
Test Procedures
Test Procedure Conventions
Test Data
Use case Testing
Use Case:YouTube player I Frame
Use Case:Accounts
Use Case:Delete button issues, or not properly
functional
4.44
Appendix A
1. INTRODUCTION:
YouTube is a video-sharing website, created by three former
PayPal employees in February 2005 and owned by Google since
late 2006, on which users can upload, view and share videos. The
company is based in San Bruno, California, and uses Adobe Flash
Video and HTML5 technology to display a wide variety of usergenerated video content, including video clips, TV clips, and
music videos, and amateur content such as video blogging, short
.original videos, and educational videos
Most of the content on YouTube has been uploaded by
individuals, but media corporations including CBS, the BBC,
Vevo, Hulu, and other organizations offer some of their material
via YouTube, as part of the YouTube partnership
program.Unregistered users can watch videos, and registered users
can upload an unlimited number of videos. YouTube, LLC was
bought by Google for US$1.65 billion in November 2006 and now
.operates as a Google subsidiary
PROJECT SPONSOR:
Name: Mr. Saad Mehmood
Title: Assistant Manager
Organization Name: Energy Tower, Doha, Qatar.
Contact Information: Cell: 0097455618841
Email: [email protected]
YouTube Project Development Team
Kanza Sana
+923039221938
HiraBatool
+923363030107
AlmasShahzadi
+923316406131
EzzaRiaz
+923497766562
3 Page
YouTube
Halima Sadia
+923679901094
1.1 Purpose
The purpose of the STS are: 1)to describe the plan for testing the YouTube
project, and 2) to specify the testcases and test procedures necessary to
demonstrate that the YouTube project satisfies the requirements as
specified in the project's System Requirements Specification Document.
1.2 Scope
This document contains a list, and brief description of use cases to be
tested and the software components associated with each test case. The
software testing plan also provides a schedule for the testing and also
provides the assignment of team members to their respective testing
tasks. The process for documenting and resolving software errors or
anomalies that are found during the testing is also specified. The test
specification includes a list of features to be tested for each of use cases,
along with test procedures, and steps necessary to execute each of the
test cases.
1.3.1 Definitions:
YouTube-The name of the software being developed.
Software feature- A distinguishing characteristic associated with use
case e.g. its functionality, performance, ease of use, performance etc.
Software problem report- A document reporting on any event that
occurs during the testing process which requires investigation.
Software test report- A document summarizing testing activities and
results. It also contains an evaluation of the degree which the software
product satisfies to the system requirements for each of the use cases.
Test case specification- A specification of inputs, expected results, and
a set of execution steps associated with the testing of a feature or
features associated with a use case.
Test log- A chronological record of relevant details about the execution of
tests.
1.3.2. Acronyms:
API: Application Program Interface.
1.4 References:
Features
Pause button
Play button
Next button
Previous button
Accounts
Create account
Data Fields
Delete Button
Components
5 Page
YouTube
2.2. Responsibilities:
The following table contains a listing of each Use Case, the team member
who will be
testing that Use Case, and finally the team member who developed the
Use Case.
Use case
Accounts
EzzaRiaz , Kanzasana,
Halima Sadia
HiraBatool ,
AlmasShahzadi
HiraBatool ,
AlmasShahzadi
Kanza Sana
All testing is to be preformed on Gaia at the completion of the base line coding. All test
cases will be followed explicitly, following any prerequisites that are required to
sufficiently test that specific testcase.
2.3 Schedule:
This subsection contains the testing schedule for YouTube Project. It specifies the date
on which testing will begin and the date that testing will be completed. At the end of
testing on the sponsors server the software will be ready for delivery.
Date Start
Complete
Single Pages
23rd Jan
27th Jan
Integration
27th Jan
5th Feb
Whole
Program
5th Feb
16th Feb
7 Page
Repair Start
Repair
Complete
YouTube