Scribd
Upload
177 views

Software Test Specification

The document provides a test specification for testing a YouTube project. It includes an introduction, test plan description, test design specification, test specification, and requirements traceability sections. The test plan describes the product being tested, responsibilities of team members, and a schedule for testing. It also provides use cases and their associated features and components to be tested.

Uploaded by

Hira Naqvi
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
177 views

Software Test Specification

The document provides a test specification for testing a YouTube project. It includes an introduction, test plan description, test design specification, test specification, and requirements traceability sections. The test plan describes the product being tested, responsibilities of team members, and a schedule for testing. It also provides use cases and their associated features and components to be tested.

Uploaded by

Hira Naqvi
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

Software Test Specifications

YouTube Project

SOFTWARE TEST SPECIFICATION


Version 1.0

Institute Of Business & Information Technology, Punjab


University New Campus, Lahore.
Advisor: Ma'm Natalia Ahmad

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

3. Test Design Specification


3.1
Testing Approach
3.2
Features or combination of features
not to be tested
3.3
Environmental Needs
3.4
Suspension/ Resumption /criteria
3.5
Risks and /contingencies
4. Test Specification
4.1
4.2
4.3
4.4
4.41
4.42
4.43

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

Use Case:Full HD resolution issue

5. System Tests / Requirements Traceability


5.1
Matrix

Design Component Traceability

6. Approval Signature Page

Software Test Specifications

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

[email protected].
pk

HiraBatool

+923363030107

[email protected].
pk

AlmasShahzadi

+923316406131

[email protected].
pk

EzzaRiaz

+923497766562

[email protected].
pk

3 Page

YouTube

Halima Sadia

+923679901094

[email protected].
pk

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 Definitions, Acronyms, and Abbreviations


This subsection serves as a glossary for the document. All technical terms
used as well as all the acronyms and abbreviations used are arranged in
alphabetical order. The purpose of this subsection is to provide all reader
with quick access to the technical references used throughout the
document.

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:

Document was prepared using:

Software Test Specifications


YouTube projects Requirement Specification Document.

1.5 Overview of Contents of Document


Test Plan Description, Test Design Specification, Test Specification,
Requirements Traceability, Approvals, Software Problem Report
2. TEST PLAN DESCRIPTION
The intent of system test is as follows
To specify the activities required to prepare for and conduct the system test.
To identify the tasks that must be performed, the team members assigned to each
of the tasks, and the schedule to be followed in performing the tasks.
To identify the sources of information used to prepare the plan.
To identify the test tools and environmental needs for conducting the tests.
2.1 Product Summary:
Four different issues are to be discussed here i.e You Tube player I Frame which states
that different overlays are visible on the screen at the end when the video finishes these
overlays are coinciding with other buttons that itself no longer remain clickable.
Secondly for making an account date of birth issue is there for one specific date that I
valid. Thirdly its not possible to delete the copyright tagged videos i.e delete button is not
properly functioning. Fourthly, there is an issue related to resolution while reviewing video
on IPAD the 1080 P is not workable.
Use Case

Features

YouTube player I frame

Pause button
Play button
Next button
Previous button

Accounts

Create account
Data Fields

Delete button issues or


Not properly functional

Delete Button

Components

Pane for copyrighted videos


log in

5 Page

YouTube

Full HD resolution issue

I pad supporting internet


features.
Video player.

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

Team Member (s) Tester

YouTube player I frame

Halima Sadia , EzzaRiaz

Accounts

EzzaRiaz , Kanzasana,
Halima Sadia

Delete button issues or


Not properly functional

HiraBatool ,
AlmasShahzadi

Full HD resolution issue

HiraBatool ,
AlmasShahzadi
Kanza Sana

Team Member (s)


Developer

Table 2.2 Programmers and testers responsibilities

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.

Software Test Specifications


Type of test

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

You might also like