Anda di halaman 1dari 4

TEST SPECIFICATION DOCUMENT

1 Introduction

1.1 Background

This document provides the specification for the testing activities required for the user acceptance
testing of the " Hsh platform".

The Application Under Test(AUT) is developed as a music distribution platform for the purpose of
effectively distributing music content of upcoming artists. This is to provide an avenue for them to be
heard and also earn a source of income from the sales of their works.

The version being tested is v2.0

1.2 Scope

The scope of this testing addresses only the user acceptance testing of the AUT;focusing on ease of use;
how well the features functions; ability to complete tasks as a user.

2 Test Requirement

2.1 Introduction

This chapter documents the test requirement for conducting User acceptance testing on the "HSH
platform".

Testing will be against the Functional specification, plus any other test instructions specified within this
document.

2.2 Test Philosophy

2.2.1 Overview

The objective of this User acceptance Test is to confirm that the application under test (AUT) meets it's
business requirements and to provide confidence that the system works correctly and is usable.

The individual user acceptance test will be derived from the Functional specification document.

Acceptance testing will be performed on the final delivered system (v2.0).

2.2.2 Functional Areas

a) user interface

b) Features of the platform

c) artists area

d) downloading of songs

e) friends invitation
f) blog

g) gift cards

2.2.3 Test Result Category

*Pass( test results conforms to expected specification)

*Acceptable ( differs from agreed specs but is acceptable, requires no changes to features but changes to
specifications)

*Tolerable( application is workable; observed results is incorrect but fault must be rectified within an
agreed time)

*intolerable ( incorrect observed results; fault must be corrected b4 end of test)

*Test Error ( observed result is correct, but expected result is incorrect)

2.2.4 Exclusions

The user acceptance test will exclude testing of the system administration functions.

2.3 Test Environment

2.3.1 Overview

The testing will take place at the comfort of the users location. This would be done on the users personal
mobile devices or laptops.

2.3.2 Hardware

The acceptance test will be conducted using users personal mobile smart phones; tablets or laptops
using different screen sizes.

2.3.3 Software

The acceptance test will be conducted using:

a) HSH platform(v2.0)

b) iOS (various versions)

c) android 4.0 os and above

d)windows os (various versions)

2.3.4 Test Data

The acceptance test will be conducted using live data.


2.4 Test team roles and responsibilities

a) Test analyst

Would be responsible for writing the test scripts and coordinating the testing

Would analyse test results and communicate to project manager.

b) testers

Would be users making use of the application during the period of test

Would undertake the test of application

2.5 Test Identification

2.5.1 Test script

This test will have a script describing how the test will be conducted and the expected result. The script
will contain the following information:

a) a unique test identifier

b) a description of the purpose of the test

c) a brief description of the state of the AUT prior to the test

d)precise steps required to execute the test

e) a brief description of the expected results.

2.5.2 Result Reporting

The test results/observations will be recorded on a Test Result Record Form. This form will record the
following information:

a) the AUT title and version

b) the testing phase

c) date of test

d) a unique test identifier

e)the time of execution of test

f) observed test result

g)the assigned test result category

h) a test error description

i) email of tester
3 Test Procedure

3.1 Introduction

This chapter describes how the user acceptance test will be performed.

3.2 Pre-Test activities

3.2.1 Test Environment

The test team leader will contact the developer to ensure that the live system will be available for the
testing and the live system data are available for the acceptance test.

3.2.2 Test Timescales

The "Hsh application" user acceptance test start date will be agreed-on in consultation with the
developer, test team lead and test analyst.

The period allowed for the completion of the test will be 5-15mins

3.2.3 Test Liaison

The Test team leader will liaise with the developer to agree the delivery date of the AUT for testing.

The test team leader will liaise with the users to ensure that the time for the test is suitable to all.

3.2.4 Test Script Preparation

The test analyst will with reference to the functional specification for the AUT and any other specific
instructions, prepare a Test Script and component test cases.

3.3 Conducting the Test

3.3.1 Test Execution Procedure

The testers will execute the individual test cases comprising the user acceptance test in the order in
which they appear in the test script.

For each test case, the Tester will follow the instructions specified in the test script for executing that test
case.

Following the completion of each test case, the tester will complete a test result record form, assigning a
test result category for that test case by observation and interpretation of the test result.

3.3.2 Filing of completed test result record forms

Completed test result record forms will be sent via email to the test analyst for post testing review.