Telefonica (UK)

Confidential

Telefonica UK
SYSTEM TEST EXIT REPORT
CD42260 IPHONE PRE
ORDER BACKORDER FILES
FOR BUSINESS ESSENTIALS
INFOGIX
Executive Summary & Recommendation

We have created *.csv.gz.gpg as an input file manually and placed

in internal test server.

Script pulled the file from internal test server and performed
operation like (decryption and decompression and finally *.csv file
moved to required incoming location.

System test has been successfully completed.

We have used gprsmed2 server as DMZ server for system testing.

Recommend Acceptance

All functional targets met, so good to go live.

ALL RIGHTS RESERVED

Project: TUK_CD42120_Trading Drop 2 2015_NGN Access Charge Change

Test Exit Report
Issue: V 0.4

Page 1 of 13

Telefonica (UK)

Confidential

This is an unpublished work. No part of this document may be copied, photocopied, reproduced, translated or
reduced to any electronic or machine-readable form without the prior permission of O2

DOCUMENT INFORMATION
Document name:

Activity Test Exit Report

Brief description:

TUK_CD42260_Iphone pre order backorder files for bussiness

essentials_Infogix_System_Test_Exit_report

Document Author:

Dinesh Kumar Yamali

Owner while
current:

Dinesh Kumar Yamali

Next review date:

Retention period:

1 Year

CHANGE HISTORY
Template
used

Activity_Test_Exit_Report_Template.doc

Versio
n

Date

Changed by

Changes

0.1

24-08-2015

Dinesh Kumar Yamali

Initial draft version

0.2

26-08-2015

Dinesh Kumar Yamali

Updated as per Sheetal comments

1.0

26-08-2015

Dinesh Kumar Yamali

Initial Version

RELATED DOCUMENTS
Name

Versi
on

Date

Attachment

Hyperlink

TUK_CD42260_Iphone pre
order backorder files for
business
essentials_Infogix_System_Te
st_Approach_V1.0

1.0

24082015

TUK_CD42260_Iphone pre
order backorder files for
TUK_CD42260_Ipho business
essentials_Infogix_System_Te
ne pre order backorder
files for business essentials_Infogix_System_Test_App
st_Approach_V1.0

TUK_CD40837_KENTUCKY_FIL
E_TRANSFER_INFOGIX_DD_V
17

1.0

24082015

TUK_CD40837_KENTUCKY_FIL
E_TRANSFER_INFOGIX_DD_V
TUK_CD40837_KENT 1 7
UCKY_FILE_TRANSFER_INFOGIX_DD_V 1 7.docx

CIRCULATION LIST (individual and role)

Philip Heeds

Project Manager

Neill Lovell

Accenture Test Manager Onshore

Sanjeeb K
Satapathy

Accenture Manager

Kishor
Toshniwal

Project Designer

Brian Mattey

Quality Assurance

Tiny Thomas

Accenture Test Manager

Sanjeet Kumar

Accenture
Development

Project: TUK_CD42120_Trading Drop 2 2015_NGN Access Charge Change

Test Exit Report
Issue: V 0.4

Page 2 of 13

Telefonica (UK)

Confidential

SIGN-OFF
It is important that the sign off authority is inserted in the document together with
document file path (SOX compliance)

Name:

Philip Heeds

Role
:

Project Manager

Tiny Thomas

Role
:

Accenture Test Manager - Offshore

Brian Mattey

Role
:

Quality Assurance

Graham Kenworthy

Role
:

Wholesale B&M Lead

Sign Off
Authority
Sign off
Document
File Path
Name:
Sign Off
Authority
Sign off
Document
File Path
Name:
Sign Off
Authority
Sign off
Document
File Path
Name:
Sign Off
Authority
Sign off
Document
File Path
As a minimum the test lead should seek the following as a minimum level of
approval
o

Leads Test Analyst

Operations representative

Design Authority

PTL where appropriate

Project: TUK_CD42120_Trading Drop 2 2015_NGN Access Charge Change

Test Exit Report
Issue: V 0.4

Page 3 of 13

Telefonica (UK)

Confidential

CONTENTS
1

INTRODUCTION.......................................................................................................................................5
1.1
1.2

BACKGROUND.........................................................................................................................................5
OBJECTIVES.............................................................................................................................................5

VARIANCE FROM THE PROJECT TEST APPROACH..............................................................5

PROJECT TEST SCOPE.........................................................................................................................5

3.1
3.2

IN SCOPE................................................................................................................................................5
OUT OF SCOPE.......................................................................................................................................5

TEST EXIT CRITERIA.........................................................................................................................6

TEST RESULTS.........................................................................................................................................6
5.1
5.2

TEST EXECUTION SUMMARY..................................................................................................................6

OPEN FAULTS.........................................................................................................................................7

DEFECT KPI METRICS..........................................................................................................................7

6.1

TOTAL NUMBER OF DEFECTS RAISED DURING TEST EXECUTION OF THE ACTIVITY (PRIORITY AND
STATUS)................................................................................................................................................................7
6.2
ROOT CAUSE ANALYSIS OF DEFECTS RAISED DURING TEST EXECUTION FOR THE ACTIVITY..........7
6.3
TEST PROCESS LIFE CYCLE ACTIVITY...................................................................................................7
7

OUTSTANDING RISKS..........................................................................................................................7

CONCLUSION............................................................................................................................................7

APPENDIX A..............................................................................................................................................8

Project: TUK_CD42120_Trading Drop 2 2015_NGN Access Charge Change

Test Exit Report
Issue: V 0.4

Page 4 of 13

Telefonica (UK)

Confidential

INTRODUCTION
As part of CD42260 Kentucky Project, there is requirement to transfer files from SFDC
to Infogix Landing strip server using SFTP/FTP protocol. The encrypted input files
should be decrypted also using gpg before sending it to destination directories. This
testing will be performed to confirm whether the newly introduced script meets all
the functional requirements.

1.1 Objectives
The objectives of this document are to:

Report on the conformity against what was defined in the System Test
Approach.

Re-iterate the scope of testing and the exit criteria for System Test.

Consolidate and report the results of testing from this test activity as defined
in the ST Test Approach.

Summarise the reported test metrics.

Confirm to the project any outstanding quality issues or risks relating to ST

Test.

Provide to the project and the test community any recommendations for
future test activities.

Project: TUK_CD42120_Trading Drop 2 2015_NGN Access Charge Change

Test Exit Report
Issue: V 0.4

Page 5 of 13

Telefonica (UK)

Confidential

2 VARIANCE FROM THE PROJECT TEST APPROACH

None

Project: TUK_CD42120_Trading Drop 2 2015_NGN Access Charge Change

Test Exit Report
Issue: V 0.4

Page 6 of 13

Telefonica (UK)

Confidential

3 PROJECT TEST SCOPE

3.1 In Scope
The following test activities addressed the test objective, project deliverable or
business requirements detailed in the activity test approach.

Validating functionality of the Kentucky script against the requirements with

respect to sfdc back order files.

Validating whether script picks the test files.

Validating the files placed in respective locations.

Validating regression files by executing the Kentucky script.

3.2 Out of Scope

The following areas are out of scope of System Testing:

Functionality of gpg utility.

Functionality of SFTP

PRT

Project: TUK_CD42120_Trading Drop 2 2015_NGN Access Charge Change

Test Exit Report
Issue: V 0.4

Page 7 of 13

Telefonica (UK)

Confidential

TEST EXIT CRITERIA

The following table details compliance against the project test exit criteria detailed
in the Activity Test Approach.
Test Exit Criteria

Criteria
Met?

If Criteria has not been met

detail
reasoning
and
mitigation
if
recommendation
is
to
implement.

100% Requirements coverage has been

achieved.

NA

100% Test execution completed and

95% tests are passed.

NA

0-0-2-2 defect criteria is met (0 critical

and high defect, 2 medium and low
defect are acceptable).

NA

Any open defects are deferred and

agreed with the stake holders.

NA

Project: TUK_CD42120_Trading Drop 2 2015_NGN Access Charge Change

Test Exit Report
Issue: V 0.4

Page 8 of 13

Telefonica (UK)

Confidential

TEST RESULTS

3.3 Test Execution Summary

The System test was conducted to validate the Kentucky script functionality with
respect to SFDC back order files. Below are the high level scenarios
Kentucky script is able to collect the SFDC back order files from gprsmed2
server.
Kentucky script is able to gunzip and decrypt the SFDC back order files in
Infogix landing strip server.
Decrypted SFDC files are placed in Incoming location by Kentucky script.
All the test case is executed and passed as the part of system testing.

Identified Test Activity

Number of
Test basis
items
Identified

Number
of Test
basis
items
Passed

Number
of Test
Basis
items
Failed

Test cases

Number
of Test
Basis
items
Deferre
d
0

Results are given in the below link:

Within ACN

Within TUK

TUK_CD42260_Iphone pre order backorder files for business

essentials_Infogix_System_Test_Results

TUK_CD42260_Ipho
ne pre order backorder files for business essentials_Infogix_System_Test_Results_V1.0.docx

3.4 Open Faults

There are no open defects.

Project: TUK_CD42120_Trading Drop 2 2015_NGN Access Charge Change

Test Exit Report
Issue: V 0.4

Page 9 of 13

Telefonica (UK)

Confidential

DEFECT KPI METRICS

3.5 Total Number of Defects Raised during Test Execution of the activity
(priority and status)
None

3.6 Root Cause Analysis of Defects Raised during Test Execution for the
activity.
None

3.7 Test Process Life Cycle Activity

None

Project: TUK_CD42120_Trading Drop 2 2015_NGN Access Charge Change

Test Exit Report
Issue: V 0.4

Page 10 of 13

Telefonica (UK)

Confidential

OUTSTANDING RISKS
None

Project: TUK_CD42120_Trading Drop 2 2015_NGN Access Charge Change

Test Exit Report
Issue: V 0.4

Page 11 of 13

Telefonica (UK)

Confidential

CONCLUSION
The System testing for CD42260_Iphone pre order backorder files for business
essentials has been carried out successfully for all the test cases executed and the
exit criteria have been met. All functional targets met and changes are
recommended to be deployed in live.

Project: TUK_CD42120_Trading Drop 2 2015_NGN Access Charge Change

Test Exit Report
Issue: V 0.4

Page 12 of 13

Telefonica (UK)

Confidential

APPENDIX A
ROOT CAUSE ANALYSIS
Vendor software - Where a fault occurs as a result of an error in the code requiring
a patch or rebuild to address the issue. Applies to external or 3rd party software.
Vendor Hardware - Where an unexpected issue occurs on a physical or virtual
hardware element e.g. disk failure or interface card. Applies to external or 3rd party
hardware.
Vendor Documentation - Omissions for the release notes or documentation or
Method of Procedure leading to faults or mistakes).
Vendor Implementation - Incorrect Implementation or configuration of the design
leading to faults (including incorrect reference data). E.g. where a vendor creates
the implementation plan and runs the MOP.
O2 developed software - Where a fault occurs as a result of an error in the code
requiring a patch or rebuild to address the issue. Applies to internal development
teams e.g. Wholesale development teams, GAS team.
O2 design - Omissions, ambiguities or lack of detail from the design leading to
faults that require additional configuration or software to address.
O2 implementation and configuration of design - Incorrect Implementation or
configuration of the design leading to faults (including incorrect reference data). E.g.
where an O2 project manager creates the implementation plan.
Test environment, planning and execution - Incorrect implementation of the test
environment leading to faults including physical cabling/build, incorrect reference
data, incorrect Test Cases and faults raised in error.

Project: TUK_CD42120_Trading Drop 2 2015_NGN Access Charge Change

Test Exit Report
Issue: V 0.4

Page 13 of 13