FUJ00090436
FUJ00090436
Fujitsu Services Operation Launch Ref: NB/UTR/OO1
Version: 2.0
Date: 12/01/2005
Document Title: Operation Launch
Document Type: Unit Test Report
Release: BI3 (S70)
Abstract: This is the Unit Test Report for Operation Launch
Document Status: APPROVED
Originator & Dept: Gerald Barnes, APDU Counter Development
Contributors: Erica Johnson, APDU Counter Development
Reviewed By: Walter Wright, Mark Scardifield
Comments By:
Comments To:
Distribution:
© 2003 Fujitsu Services Page: I of 1
FUJ00090436
FUJ00090436
Fujitsu Services Operation Launch Ref: NB/UTR/OO1
Version: 2.0
Date: 12/01/2005
¢ Document Control
e Document History
Version No. I Date Reason for Issue Associated
CP/PinICL
0.1 15/02/2002 I The first issue produced after running all the
tests.
: 22/03/2002 The approved version.
Ll 21/06/2004 Ran latest versions of Unit Test Plan CP/3612
CP/3729
2.0 12/01/2005 Correct version number of approved Test Plan
e Approval Authorities
Name Position Signature Date
Walter Wright I APDU EPOSS Development
Team Leader
(Substitute correct Development Team Leader where appropriate)
e Associated Documents
Reference Version _I Date Title Source
PA/TEM/001 ICL Pathway Document PVCS
Template
NB/LLD/001 3.2 16/06/04 Operation Launch Low PVCS
Level Design
NB/UTP/001 2.2 18/06/04 Operation Launch Unit Test I PVCS
Plan
Unless a specific version is referred to above, reference should be made to the current
approved versions of the documents.
e Abbreviations/Definitions
Abbreviation Definition
Operation Launch The component described in “Operation Launch Low Level Design*
Root VSS The root of the VSS directory used in these tests —
Baselines/BI3/NB.
UTP Unit Test Plan — For this document this will refer exclusively to the
plan in the associated document “Operation Launch Unit Test Plan”.
UTR Unit Test Report
VSS Visual Source Safe
e Changes in this Version
© 2003 Fujitsu Services Page: 2 of 1
FUJ00090436
FUJ00090436
Fujitsu Services Operation Launch Ref: NB/UTR/OO1
Version: 2.0
Date: 12/01/2005
Version Changes
1.0 This version was approved. No changes were made from 0.1.
2.0 Update/correct Header & footer
e Changes Expected
Changes
None at present.
© 2003 Fujitsu Services Page: 3 of I
FUJ00090436
FUJ00090436
Fujitsu Services Operation Launch Ref: NB/UTR/001
Version: 2.0
Date: 12/01/2005
e Table of Contents
0.0 DOCUMENT CONTROL.
0.1 DOCUMENT HIsTOoRY..
0.2. APPROVAL AUTHORITI
0.3 ASSOCIATED DOCUMENTS
0.4 ABBREVIATIONS/DEFINITIONS.
0.5 CHANGES IN THIS VERSION...
0.6 CHANGES EXPECTED.
0.7 TABLE OF CONTENTS.
1.0 INTRODUCTION......
BRwWwWNNNN
2.0 PRE-REQUISITES...
3.0 TEST HARNESS, TOOLS AND DATA.
4.0 TEST ENTRY CRITERIA...
5.0 DETAILS.
5.1 PREPARATION.. coco oe sossseseeeeneeeeeneeente 5
5.2 FUNCTIONALITY TESTS......0.cccccccssssssssssssseseesssssssneseeeeeenen sescteccssssssseneeeseenensunsssssneseeeesensesesnsssssseeee
5.3. NON-FUNCTIONAL TESTS. 6
5.3.1 Performane: 6
5.3.2 Resilienc
5.3.3 Security.
5.3.4 Time-Rel
6.0 TEST COVERAGE
ated Issues.
7.0 TEST EXIT.
7.1 SUMMARY OF PROBLEMS FOUND. 7
© 2003 Fujitsu Services Page: 4 of 1
FUJ00090436
FUJ00090436
Fujitsu Services Operation Launch Ref: NB/UTR/001
Version: 2.0
Date: 12/01/2005
e Introduction
This document describes the unit testing done on “Operation Launch” following the
instructions given in the UTP.
e Pre-Requisites
The prerequisites are all listed in section 2.0 “Pre-Requisites” of the UTP.
e Test Harness, Tools and Data
The test harness, tools and data are all described in section 3.0 “Test Harness, Tools
and Data” of the UTP.
e Test Entry Criteria
© Code inspection and consequent code updates complete Vv
¢ Unit Test Plan reviewed and approved Vv
e All necessary test harnesses, test tools and test data available Ni
e Test environment ready Vv
¢ Details
e Preparation
The preparation is all described in section 5.1 “Preparation” of the UTP.
With regards to step I listed there the build was actually a BI2 build (WR2.1.0) of
which the last work package installed was 13334.
With regards to the other steps all Operation Launch components used which are in
VSS are labelled “NB/LLD/001 V 0.2 Test Complete” — this includes two binaries the
source of which were not yet in VSS — NBSwitcher.exe and NBComLib.dll. The other
components used are listed in the table below
Directory relative to File Version
“Root VSS”
NBSharedFiles modNBAttributeGrammarConstants.bas_I 2
NBSharedFiles modNBGenericConstants.bas 1
NBSharedFiles modNBMessages.bas 2
NBCommon NBCommon.dil 4
NBCommon NBHelpers.dll 4
e Functionality Tests
© 2003 Fujitsu Services Page: 5 of 1
FUJ00090436
FUJ00090436
Fujitsu Services Operation Launch Ref: NB/UTR/001
Version: 2.0
Date: 12/01/2005
All the tests listed in section 5.2 “Functionality Test” of the UTP were run.
e All tests completed as expected
e Event log entries checked
e Minor bug fixes made!
e Test coverage completed
ale}ela
e Non-Functional Tests
e Performance
Pool paged bytes for both Desktop and Riposte were monitored with Performance
Monitor for 7212 cycles of the soak test (see section 5.3.1 “Performance” in the UTP
for details of this) which meant over 14000 operations were launched. No memory
leakage was detected in the Desktop at all — for Riposte the figures are given in the
table below
Pool Paged Bytes
When Min Max
Start 22432.000 22464.000
Finish 22560.000 22592.000
This is much more likely to be a problem with Riposte than with Operation Launch
since Operation Launch shares its memory with the Desktop.
© Resilience
The test described in section 5.3.2 “Resilience” of the UTP
e Security
NA
Time-Related Issues
NA
‘In this cases there were no minor bugs to fix.
© 2003 Fujitsu Services
Page: 6 of 1
FUJ00090436
FUJ00090436
Fujitsu Services Operation Launch Ref: NB/UTR/001
Version: 2.0
Date: 12/01/2005
e Test Coverage
As UTP
e Test exit
e All tests specified in the UTP have been run, or a justification V
provided in this document for those, if any, which have not been run
e No major incidents (A or B priority) outstanding v
e Incidents raised Unit Testing have been recorded (in a local Vv
spreadsheet) and summarised in the UTR /if necessary).
e All minor incidents (C priority or lower) outstanding at the end of the I J
Unit Test have been formally raised as PinICLs
e UTP updated and re-issued /if necessary) Vv
e Summary Of Problems Found
The only possible problem found was that Riposte may have a memory leak. It is
considered beyond the scope of this module test to progress this further.
© 2003 Fujitsu Services Page: 7 of 1