E-Bulk Connectivity Test Summary
Report<Template>
W0129
MoJ ICT and RB (<text (RBname) to be inserted by RB>)
The RB/ The MoJ ICT must use the template of the Summary report , update it
as necessary and submit a completed version of the report for review and
approval at the end of Connectivity Test Execution . It is envisaged that the RB
should complete a version of the report template completing text where
indicated and submit to DBS. The MoJ ICT should also complete the report
template where appropriately indicated and submit to the DBS. The DBS Test
Co-ordinator will then compile the 2 versions of the report into one completed
version including both RB and MoJ ICT submitted information and comments.
Completed Report -Author
Version Date
Purpose
<text to <text to be
Completed Draft
be
inserted by
inserted RB >
by RB >
<text to <text to be
Completed Draft
be
inserted by
inserted OCJR >
by
OCJR >
Completed Report - Approval
Version
Name
Organisation
<text to <text to be DBS Agency
be
inserted by
inserted
DBS >
by RB >
<text to <text to be DBS Agency
be
inserted by
inserted
DBS >
by OCJR
>
Author
<text to be inserted by RB >
<text to be inserted by OCJR
>
Title
<text to be inserted
by DBS >
Signature
<text to be inserted
by DBS >
Date
<text to
be
inserted
by DBS
>
<text to
be
inserted
by DBS
>
Completed Report -Reviewers
Version
Date
of Name
Organisation
Issue
<text to <text to be <text
to
be DBS Agency
be
inserted by inserted by DBS
inserted RB >
>
by RB >
Title
<text to be inserted
by DBS >
31/07/2017
E-Bulk Connectivity Test Summary Report
2
Not Protectively Marked
Version
Date
of Name
Organisation
Issue
<text to <text to be <text
to
be DBS Agency
be
inserted by inserted by DBS
inserted OCJR>
>
by
OCJR >
Reference Documentation
Document Name
Title
<text to be inserted
by DBS >
Version No.
Location
V2.1
PSO Library
V1.3
PSO Library
V1.0
PSO Library
V0.1
PSO Library
Connectivity Test Specification [CTS]
V1.0
PSO Library
Connectivity Test Plan [CTS]
Code of Connection CJSE-RB (Internet)
[CoCo] [CCG]
V1.0
PSO Library
V2.0
PSO Library
Code of Connection (CoCo) CJSE-RB
(GSi) [CCG]
V 2.0
PSO Library
Registered Body Readiness Check and
Test Guidance [RCT]
Interface Control Document (ICD CJSERB(Internet FTPS)
CJSE Message Delivery Interface
Specification Document [FTPMDI]
RB E-Bulk Onboarding Document [OBD]
Terminology
Term
E-Bulk
Meaning
The term that has been given to the interface described in
this document, named as such because it provides an
electronic mechanism for submitting applications in bulk
(i.e. in batches, as opposed to one at a time). This is
analogous to the current practice of sending paper DAFs
in bulk by post.
eBulkApplicationsBatch (CRB01) XML file generated by RB system and sent to CRM that
represents a batch of up to (a configurable limit ) initially
50 eBulkApplications.
eBulkApplicationBatchRejection XML file generated by CRM that represents a file level
(CRB02)
rejection of a CRB01 message. This file is sent to the RB
system that generated the original CRB01 message.
eBulkApplicationReceiptsBatch
XML file generated by CRM to indicate whether individual
(CRB03)
eBulkApplications from a particular RB have passed or
E-Bulk Connectivity Test Summary Report 3
Commercial
26/06/08
eBulkResultsBatch (CRB04)
eBulkApplication
OCJR
CJSE
failed initial validation. This message is generated to
match the number of eBulkApplications received from a
particular RB.
XML file generated by CRM to indicate the results of
individual eBulkApplications (blank or non blank) from a
particular RB. This message is generated either on a
regular interval or when the number of eBulkApplications
from a particular RB passes a predefined threshold.
An application sent by electronic means. In the context of
this document, this refers to an application sent via the EBulk interface.
Office of Criminal Justice Reform
The Criminal Justice System Exchange – an integration service
used by the interface.
E-Bulk Connectivity Test Summary Report 4
Commercial
26/06/08
CONTENTS
Terminology ......................................................................................................... 3
1 Introduction ...................................................................................................... 6
1.1
Background .............................................................................................. 6
1.2
Purpose .................................................................................................... 6
2 Test Results..................................................................................................... 7
2.1
Summary of Test Conditions for GSI/Internet Connectivity Testing.......... 7
2.2
Test Condition Results ............................................................................. 7
2.2.1
Internet Connectivity Testing ............................................................. 7
2.2.2
GSi Connectivity Testing ................................................................... 9
2.3
Alterations to Test Scripts or Test Conditions......................................... 11
3 Defects Raised During Testing ...................................................................... 12
3.1
Resolved Defects ................................................................................... 12
3.2
Unresolved Defects ................................................................................ 12
3.3
Test Evidence......................................................................................... 12
4 Risk, Assumptions, Issues and Dependancies (RAIDS) ................................ 13
4.1
Risks....................................................................................................... 13
4.2
Assumptions ........................................................................................... 13
4.3
Issues ..................................................................................................... 13
4.4
Dependencies ........................................................................................ 13
5 Test Observations ......................................................................................... 13
6 Successes ..................................................................................................... 13
7 Recommendations......................................................................................... 14
7.1
Updates necessary to RB E-Bulk Onboarding Guide ............................. 14
7.2
Updates necessary to Connectivity Test Specification or Test Plan ....... 14
7.3
Other Recommendations........................................................................ 14
E-Bulk Connectivity Test Summary Report 5
Commercial
26/06/08
1
1.1
INTRODUCTION
Background
The DBS is introducing a facility to enable applications to be bulk-submitted electronically
and to return information regarding the result of those applications by a similar means. This
facility is known as the “E-Bulk” interface.
The Registered Bodies (RBs) who meet the E-Bulk criteria will be invited to use the E-Bulk
facilities. RBs that are using E-Bulk will be referred to as E-RBs. The RBs who wish to use
the E-Bulk facility will sign the Development and Testing Memorandum of Understanding in
the Interchange Agreement to initiate the process of becoming an E-RB.
Use of the E-Bulk interface will alleviate the need for the production and mailing of paper
forms by the E-RBs and form scanning, and data keying by the DBS. It also makes it
possible to reduce the volume of printed Certificates sent by post to the E-RBs
1.2
Purpose
The purpose of this document is to provide a container for both the RB and OCJR to record
their results after test execution.
This document will:
 Provide an overview of testing undertaken
 Show the planned and unplanned activities
 Detail the test results
 Outline all defects found
 Outline any outstanding issues
 Highlight successes
 State conclusions
 State recommendations
 Detail any Risks, Assumptions, Issues and Dependencies (RAIDS) raised by OCJR
or the RB before and during test.
This document will provide the DBS with confirmation that the connectivity testing has been
successfully completed.
Any section of this document containing <text to be inserted> sections require completion by
the relevant party
31/07/2017
E-Bulk Connectivity Test Summary Report
6
Not Protectively Marked
2
TEST RESULTS
2.1
Summary of Test Conditions for GSI/Internet Connectivity Testing
Test Conditions Status
Number
Passed
Failed
Not Tested
Total
<RB to complete>
<RB to complete>
<RB to complete>
<RB to complete>
2.2
Test Condition Results
This section details the result of each condition exercised within this phase of testing. The
tables below show the original test condition number, the condition description and the result
(Pass, Fail or Not Tested). Section 2.2.1 should be completed by Internet RBs and section
2.2.2 should be completed by GSi RBs.
2.2.1 Internet Connectivity Testing
Test
Cond
No.
Test Condition Description
Pass/Fail & Notes
001
001 – RB attempts to establish a TCP socket
connection to the CJS pre production exchange by
entering the appropriate IP Address/ name and port
number into a telnet client.
002 – OCJR opens CJSE firewall for the RB static IP
Address that is supplied to OCJR.
003 - RB attempts to establish a TCP/IP socket
connection to the CJS pre production exchange by
entering the appropriate IP address/domain name
and port number into a telnet client.
004 - RB configures FTPS client with CA certificate
supplied by OCJR.
005 - RB configures FTPS client with client digital
certificate supplied by OCJR.
006 - RB configures FTPS client with user name and
password supplied by OCJR.
007 - RB configures FTPS client with Domain
name/URL of the pre production CJSE FTPS
service.
008 – RB establishes FTPS connection to pre
production CJSE with configured FTPS client.
<RB to complete>
002
003
004
005
006
007
008
E-Bulk Connectivity Test Summary report
7
Commercial
<OCJR to complete>
<RB to complete>
<RB to complete>
<RB to complete>
<RB to complete>
<RB to complete>
<RB to complete>
26/06/08
Test
Cond
No.
Test Condition Description
Pass/Fail & Notes
009
009 – RB validates that the filenames of the 2
sample CRB01 XML files provided by DBS are well
formed and contain the correct test RB reference
number. The RB also validates that the
eBulkMessageHeader /RegisteredBody element
within the files contain the correct test RB reference
number.
010 - RB sends the 2 CRB01 XML files using FTPS
to the /<RB System ID>/in/CRB01 Directory
Structure on the CJSE server
011 - OCJR check /<RB System
ID>/in/CRB01/processed location of the exchange
and retrieve the 2 CRB01 XML files sent by the RB
012 – OCJR places the 6 response XML files,
provided by DBS, (2 X CRB02, 2 X CRB03, 2 X
CRB04) in /<DBS System
ID>/in/[CRB02,CRB03,CRB04] ensuring the
filenames and eBulkMessageHeader
/RegisteredBody elements contain the correct test
RB reference number.
013 – The <DBS System
ID>/in/[CRB02,CRB03,CRB04] directories are polled
and the files are moved through the exchange
014 - RB log on to the CJSE FTPS server output
directory /<RB System ID>/out/CRB02
015 - RB initiates the transfer of the CRB02 files
using the FTPS “get” command
016 - RB log on to the CJSE FTPS server output
directory /<RB System ID>/out/CRB03
017 - RB initiates the transfer of the CRB03 files
using the FTPS “get” command
018 - RB log on to the CJSE FTPS server output
directory /<RB System ID>/out/CRB04
019 – RB initiates the transfer of the CRB04 files
using the FTPS “get” command
020 – RB sends the 6 retrieved files to DBS for
validation
021 – RB generates a new CRB01 file via the RB
test system
022 – RB test system automatically connects to the
exchange and uploads the newly generated CRB01
file to the /<RB System ID>/in/CRB01 Directory
Structure on the CJSE server
023 - OCJR check /<RB System
ID>/in/CRB01/processed location of the exchange
and retrieve the CRB01 XML file sent by the RB
<RB to complete>
010
011
012
013
014
015
016
017
018
019
020
021
022
023
E-Bulk Connectivity Test Summary report
8
Commercial
<RB to complete>
<OCJR to complete>
<OCJR to complete>
<OCJR to complete>
<RB to complete>
<RB to complete>
<RB to complete>
<RB to complete>
<RB to complete>
<RB to complete>
<RB to complete>
<RB to complete>
<RB to complete>
<OCJR to complete>
26/06/08
Test
Cond
No.
Test Condition Description
Pass/Fail & Notes
024
024 – OCJR places the 3 invalid response XML files,
provided by DBS, (1 X CRB02, 1 X CRB03, 1 X
CRB04) with "-" suffix in /<RB System
ID>/out/[CRB02, CRB03, CRB04] directories.
025 – OCJR places the 3 valid response XML files,
provided by DBS, (1 X CRB02, 1 X CRB03, 1 X
CRB04) in /<DBS System
ID>/in/[CRB02,CRB03,CRB04] ensuring the
filenames have a later timestamp than the invalid
response files and no "-" suffix.
026 – The /<DBS System
ID>/in/[CRB02,CRB03,CRB04] directories are polled
and the files are moved through the exchange
027 - RB test system automatically connects to the
exchange and downloads the 3 valid XML files (1 X
CRB02, 1 X CRB03, 1 X CRB04) placed on the
exchange by OCJR.
028 - RB sends the 3 downloaded files to DBS for
validation
<OCJR to complete>
025
026
027
028
<OCJR to complete>
<OCJR to complete>
<RB to complete>
<RB to complete>
2.2.2 GSi Connectivity Testing
Test
Cond
No.
001
002
003
004
005
006
Test Condition Description
Pass/Fail & Notes
001 – RB attempts to establish a TCP/IP socket
connection to the CJS pre production exchange by
entering the appropriate IP Address/ name and port
number into a telnet client.
002 – OCJR opens CJSE firewall for the RB static IP
Address that is supplied to OCJR.
003 - RB attempts to establish a TCP socket
connection to the CJS pre production exchange by
entering the appropriate IP address/domain name
and port number into a telnet client.
004 - RB configures FTP client with user name and
password supplied by OCJR.
005 - RB configures FTP client with Domain
name/URL of the pre production CJSE FTP service.
006 – RB establishes FTP connection to pre
production CJSE with configured FTP client.
<RB to complete>
E-Bulk Connectivity Test Summary report
9
Commercial
<OCJR to complete>
<RB to complete>
<RB to complete>
<RB to complete>
<RB to complete>
26/06/08
Test
Cond
No.
007
008
009
010
011
012
013
014
015
016
017
018
019
020
021
Test Condition Description
Pass/Fail & Notes
007 – RB validates that the filenames of the 2
sample CRB01 XML files provided by DBS are well
formed and contain the correct test RB reference
number. The RB also validates that the
eBulkMessageHeader /RegisteredBody element
within the files contain the correct test RB reference
number.
008 - RB sends the 2 CRB01 XML files using FTP to
the /<RB System ID>/in/CRB01 Directory Structure
on the CJSE server
009 - OCJR check /<RB System
ID>/in/CRB01/processed location of the exchange
and retrieve the 2 CRB01 XML files sent by the RB
010 – OCJR places the 6 response XML files,
provided by DBS, (2 X CRB02, 2 X CRB03, 2 X
CRB04) in /<DBS System
ID>/in/[CRB02,CRB03,CRB04] ensuring the
filenames and eBulkMessageHeader
/RegisteredBody elements contain the correct test
RB reference number.
011 - The <DBS System
ID>/in/[CRB02,CRB03,CRB04] directories are polled
and the files are moved through the exchange
012 - RB log on to the CJSE FTP server output
directory /<RB System ID>/out/CRB02
013 - RB initiates the transfer of the CRB02 files
using the FTP “get” command
014 - RB log on to the CJSE FTP server output
directory /<RB System ID>/out/CRB03
015 - RB initiates the transfer of the CRB03 files
using the FTP “get” command
016 - RB log on to the CJSE FTP server output
directory /<RB System ID>/out/CRB04
017 - RB initiates the transfer of the CRB04 files
using the FTP “get” command
018 - RB sends the 6 retrieved files to DBS for
validation
019 - RB generates a new CRB01 file via the RB test
system
020 - RB test system automatically connects to the
exchange and uploads the newly generated CRB01
file to the /<RB System ID>/in/CRB01 Directory
Structure on the CJSE server
021 - OCJR check /<RB System
ID>/in/CRB01/processed location of the exchange
and retrieve the CRB01 XML file sent by the RB
<RB to complete>
E-Bulk Connectivity Test Summary report
10
Commercial
<RB to complete>
<OCJR to complete>
<OCJR to complete>
<OCJR to complete>
<RB to complete>
<RB to complete>
<RB to complete>
<RB to complete>
<RB to complete>
<RB to complete>
<RB to complete>
<RB to complete>
<RB to complete>
<OCJR to complete>
26/06/08
Test
Cond
No.
022
023
024
025
026
2.3
Test Condition Description
Pass/Fail & Notes
022 – OCJR places the 3 invalid response XML files,
provided by DBS, (1 X CRB02, 1 X CRB03, 1 X
CRB04) with "-" suffix in /<RB System
ID>/out/[CRB02, CRB03, CRB04] directories.
023 – OCJR places the 3 valid response XML files,
provided by DBS, (1 X CRB02, 1 X CRB03, 1 X
CRB04) in /<DBS System
ID>/in/[CRB02,CRB03,CRB04] ensuring the
filenames have a later timestamp than the invalid
response files and no "-" suffix.
024 - The /<DBS System
ID>/in/[CRB02,CRB03,CRB04] directories are polled
and the files are moved through the exchange
025 - RB test system automatically connects to the
exchange and downloads the XML files (1 X CRB02,
1 X CRB03, 1 X CRB04) placed on the exchange by
OCJR.
026 - RB sends the 3 downloaded files to DBS for
validation
<OCJR to complete>
<OCJR to complete>
<OCJR to complete>
<RB to complete>
<RB to complete>
Alterations to Test Scripts or Test Conditions
<RB to complete - This section describes any changes to Test Cases or Test Conditions that
occurred after the Connectivity Test specification was signed off.>
Script No
Detail of Change
E-Bulk Connectivity Test Summary report
11
Commercial
Reason for Change
26/06/08
3
DEFECTS RAISED DURING TESTING
<RB or OCJR to complete as relevant - This section will detail the defects that were raised
during testing. It will detail both resolved and unresolved defects>
3.1
Resolved Defects
Defect
Number
3.2
Defect Description
Comments
Status and Effect on
Operations/
Workarounds
Unresolved Defects
Defect Defect
number Description
3.3
Approx
Severity
Severity Comments
Status and Effect Resolution
on Operations/
timescales and
Workarounds
Owner Name
Test Evidence
<This section should be completed by the RB and OCJR stating what evidence they
have from connectivity testing to prove successful completion. Should include
screenshots, any file(s) sent/received, confirmations etc. Note Due to possible
problems with the size of the document if the evidence was embedded , the evidence
should be separately securely emailed to the DBS. The RB and OCJR will be advised
separately of the email address of the DBS Test Co-ordinator>
E-Bulk Connectivity Test Summary report
12
Commercial
26/06/08
4
RISK, ASSUMPTIONS, ISSUES AND DEPENDANCIES (RAIDS)
4.1
Risks
This section should document all risks (if any) that have been identified before and during
testing.
Risk
No
Risk
Description
Impact
Owner
Mitigation
Severity
Priority
<RB should list any risks identified before or during connectivity testing>
4.2
Assumptions
<RB should list any assumptions made before or during connectivity testing>
4.3
Issues
Date Issues
Identified
Issue
number
Issue
Details
Owner Name
Comments
Current status
(Open/Closed)
<RB should list any Issues found made during connectivity testing>
4.4
Dependencies
<RB should list any dependencies found made during connectivity testing>
5
TEST OBSERVATIONS
<This section should be completed by OCJR or RB to give a summary of any other
information to note>
6
SUCCESSES
<OCJR to confirm success of testing>
<RB to confirm success of testing>
E-Bulk Connectivity Test Summary report
13
Commercial
26/06/08
7
7.1
RECOMMENDATIONS
Updates necessary to RB E-Bulk Onboarding Guide
<OCJR to complete with input from RB>
7.2
Updates necessary to Connectivity Test Specification or Test Plan
<OCJR and DBS to complete if necessary>
7.3
Other Recommendations
<OCJR and DBS to complete if necessary>
E-Bulk Connectivity Test Summary report
14
Commercial
26/06/08