5.4 CCN2 Conformance Testing

4.
4 CCN2 Conformance Test

Strategy
IT Technology & Infrastructure
21/01/2016
CCN2 CT Strategy
Agenda
Agenda
• Introduction
• Conformance Test Approach R1 Platform
• CT R1 Platform Deployment and Requirements
• Features to be tested
• Test Approach R1 Reference Applications
• Ref. apps Deployment and Requirements
• High level Conformance Test Planning
2
CCN2 CT Strategy
Introduction
Introduction
Purpose of the CCN2 Conformance testing is to

verify that
• the CCN2 concepts for exchanging information on
the Common Domain using SOA principles are well
established for all Partners
• The CCN2 Partner application environments are
ready to host CCN2 applications and interact with
other CCN2 Partners.
• The CCN2 conformance environment is operational
and ready for the performance of conformance
activities for CCN2 enabled TES, such as Customs
Decision
3
CCN2 CT Strategy
Introduction
CCN2 Evolution
• Release 1.5
• The CCN2 release 1.5 has been introduced to provide
additional features to the platform not included in
release 1 (MFT, EDIFACT support)
• Release 1.5 will be issued as a functional extension
right after the SAT of the Release 1.
• Practically the CCN2 Conformance testing will
starting in Q1 2017 and include Release 1.5
features
• During 2016, the Conformance testing scope will be
extended with additional 1.5 features.
• This presentation cover the Release 1 (R1) features
only at this stage
4
CCN2 CT Strategy
Conformance test Roadmap
MS MS
Connectivity Connectivity
testing CT testing CT
Start Start Finished Finished
21/10/16 09/03/17 29/05/17
9/01/17
2016 2017
May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep
16/09/16 23/09/16 04/11/16

Hardware CCN2 CONF
Installation Installation Installation
Start Start testing Start
Hardware Installation
CCN2 Installation (R1) CCN2 R1.5 upgrade

CONF Installation
testing
MS Connectivity testing
CT
CCN2 CT Strategy
Approach
Conformance Test Approach R1

Introduction
• Test functionalities in scope of CCN2 Platform Release
1 for Partners on Conformance Environment.
• Reference Applications
• As Partner Applications are not implemented yet they will be
simulated by them;
• Serves as a Partner Application seen from CCN2 Platform
Perspective.
6
CCN2 CT Strategy
Approach
Partner #1 DC DG TAXUD DC
Ref. Appl. Client
CCN2 Platform (AP + Ref. Appl.

MH) (Simulated Partner)
CCN
Ref. Appl. Server WAN
7
CCN2 CT Strategy
Approach

Conformance Testing
• Formal tests with DG TAXUD;
• Partner reruns set of tests under control of ITSM & QA
Contractor;
• Testing using Client/ Server Reference application deployed
in Partner premises, CCN2 Conformance environment and
Client/ Server Reference application deployed in TAXUD
premises
• Partners need connection to CCN-WAN to connect to CCN2
Platform Release 1 on CT Environment (tested in mode 1 CT)
and configure related CCN2 traffic;
• Covered by Master Test Plan (MTP), Acceptance Test Plan
(ATP) and dedicated Test Design Specifications for CT (TDS).
8
CCN2 CT Strategy
Approach

Relationship between MTP, ATP and TDS
MTP used as main testing document
ATP contains a reference to test containing details of overall test
scenarios/test cases from TDS coverage/scope, approach/strategy,
that will be executed during test planning, environments, resourcing, etc.
phase, including installation
tests.
TDS is a library of Test cases

and scenarios with detailed
descpritions of test cases.
9
CCN2 CT Strategy
Approach
Test Strategy R1 – Scope TDS/ATP

• TDS CT
• A specific Test Design Specification (TDS) is created for the conformance
testing.
• TDS is a library of test cases and test scenarios required to test application.
• In addition it contains information on environmental needs and approach
followed when creating test cases/scenarios.
• During testing test team should use detailed descriptions of test
scenarios/cases provided in TDS.
• ATP CT
• For every test phase within a new release of an application, an Acceptance
Test Plan (ATP) is written and agreed upon as part of the preparation for
testing.
• Essentially the ATPs have the same structure as the Master Test Plan (MTP)
and should avoid containing duplicate information. Where applicable, the
ATP references the MTP except where there is a deviation in information and
in these cases the ATP describes the deviation. 10
CCN2 CT Strategy
Deployment
Conformance Environment
• CCN2 Platform Conformance environment encompasses active
Conformance deployment hosted in the primary DG TAXUD
datacenter.
• Conformance Environment is as close as possible to production

environment;
• CCN2 Platform architecture supports central deployment of

Access Points and Main-HuB
• In the Conformation environment there is a central deployed

Reference Application to simulate a Partner.
11
CCN2 CT Strategy
CT Modes
• Conformance testing phase is made up of three

phases:
• Mode 1 testing connectivity;
• Mode 2 testing functionalities by simulating another
Partner;
• Mode 3 testing end to end scenarios with multiple Partners.
(optional)
12
CCN2 CT Strategy
CT Modes
• CCN2 Conformance Mode 1 schema

CT Mode 1: Connectivity Testing
Ref. Appl. CCN2 Platform (AP + Ref. Appl.
CCN
WAN
13
CCN2 CT Strategy
CT Modes
• CCN2 Conformance Mode 1

• Aim is to test connectivity and configuration of the
Partner;
• Specific subset of test cases is run to ensure
connectivity and configuration of Partners are correct;
• CCN2 Reference Applications are used to test
connectivity and configuration between the Partner and
the CCN2 Platform.
14
CCN2 CT Strategy
CT Modes
Conformance Test Mode 1

Synchronous End to End message exchange
1. Service Consumer
Partner #1 DC sends a valid requests
to CCN2 Platform
Ref. App. 2.Service Consumer
Consumer DG TAXUD DC
CCN2 Platform
receives an
acknowledgement from
Ref. App
CCN AP CCN2 Platform
Provider
WAN
Partner #2 DC
Ref. App
Consumer
Central Deployed Ref Apps

Ref. App
Provider
Ref. App.
Consumer
Ref. App.
Provider
15
CCN2 CT Strategy
CT Modes

3. Request will be sent
Partner #1 DC to Service Provider
4. Service Provider will
Ref. App.
Consumer DG TAXUD DC receive request
CCN2 Platform message
5. Service Provider will
Ref. App AP
Provider CCN send response
WAN message to Service
Consumer Partner
application
Partner #2 DC
Ref. App
Consumer

Ref. App
Provider
Ref. App.
Consumer
Ref. App.
Provider
16
CCN2 CT Strategy
CT Modes
CT Mode 2 : Testing the functionalities by simulating another Partner

CCN
WAN
17
CCN2 CT Strategy
CT Modes

• Aim is to test functionality by using Reference
Applications;
• All CT test cases are run;
• Reference Applications are used to test functionalities of
CCN2 Platform Release 1;
• Other Partners are simulated by reference applications at
DG-TAXUD DC and managed by Operation Contractor.
• Tests access and configuration of the CCN2 Platform
central functionality such as User, Service deployment
and management as well as Business/ Service Monitoring
Partner 18
CCN2 CT Strategy
CT Modes

Partner #1 DC
1. Service Consumer
Ref. App.
sends a valid requests
Consumer DG TAXUD DC to CCN2 Platform
CCN2 Platform
2.Service Consumer
Ref. App receives an
Provider CCN AP acknowledgement from
WAN CCN2 Platform
Partner #2 DC
Ref. App
Consumer
Ref. App Ref. App

Provider Consumer
Ref. App
Provider
19
CCN2 CT Strategy
CT Modes

Partner #1 DC
3. Request will be sent to
Ref. App.
Consumer DG TAXUD DC Service Provider
CCN2 Platform 4. Service Provider will
receive request
Ref. App
Provider CCN AP
message
WAN 5. Service Provider will
send response
message to Service
Partner #2 DC Consumer Partner
application
Ref. App
Consumer
Ref. App Ref. App

Provider Consumer
Ref. App
Provider
20
CCN2 CT Strategy
CT Modes

Asynchronous End to End message exchange
Partner #1 DC 1. Service Consumer will

send request message
Ref. App. to CCN2 Platform
CCN2 Platform
2. Service Consumer
receives an
Ref. App
2. R/C Callback Message
CCN acknowledgement
AP
Provider message from CCN2
WAN
Platform
1. R/C Req uest Message

Partner #2 DC
Ref. App
Consumer
Ref. App Ref. App

Provider Consumer
Ref. App
Provider 21
CCN2 CT Strategy
CT Modes

Partner #1 DC 4. CCN2 Platform will

send request message
Ref. App.
Consumer DG TAXUD DC to Service Provider
CCN2 Platform Partner application;
5. Service Provider
Partner application
Ref. App
Provider
CCN AP
WAN mock service will
receive the request
message;

Partner #2 DC 6. The CCN2 Platform
will receive an
Ref. App acknowledgement
Consumer
message from the
Central Deployed Ref Apps Service Provider.
Ref. App Ref. App
Provider Consumer
Ref. App
Provider 22
CCN2 CT Strategy
CT Modes

Partner #1 DC
Ref. App.
CCN2 Platform

Ref. App
Provider
CCN AP
WAN

Partner #2 DC
Ref. App
Consumer
Ref. App Ref. App 7. Construct

Provider Consumer
Callback message
Ref. App
Provider 23
CCN2 CT Strategy
CT Modes

Partner #1 DC
8. CCN2 Platform sends
Callback message to Ref. App.
Provider through a CCN2 Platform
synchronous Web
Service call; Ref. App
CCN AP
9. Provider has received Provider
WAN
Callback message.
Synchronous call from
7. Consumer sends the

CCN2 Platform is
Partner #2 DC Callback message as a
finished.
Web Service request
Ref. App
Consumer
synchronously to the
CCN2 Platform.
Ref. App Ref. App

Provider Consumer
Ref. App
Provider 24
CCN2 CT Strategy
CT Modes

(optional)
CT Mode 3 : Testing the functionalities with other Partners
Partner #1 DC DG TAXUD DC Partner #2 DC

MH)
CCN CCN
WAN WAN
25

• Test functionalities in scope of CCN2 Platform Release 1
for Partners with multiple Partners;
• A subset of test cases is run to ensure that CCN2
functionalities are working properly
• Reference Applications are used to test functionalities
of CCN2 Platform Release 1;
• Other Partners are using Reference Applications at the
other Partners own DC.
26
CCN2 CT Strategy
CT Modes

Synchronous End to End Message Exchange
1. Partner#1 Service
Consumer sends a valid
Partner #1 DC requests to CCN2
Platform
DG TAXUD DC
2. Partner#1 Service
Ref. App.
Consumer CCN2 Platform Consumer receives an
acknowledgement from
Ref. App
Provider CCN AP CCN2 Platform
WAN
Partner #2 DC
Ref. App
Consumer

Ref. App
Provider
Ref. App
Consumer
Ref. App
Provider
27
CCN2 CT Strategy
CT Modes

Synchronous End to End Message Exchange
3. The request will be
Partner #1 DC
sent to Partner #2
Service Provider
Ref. App. DG TAXUD DC 4. The Service Provider
Consumer CCN2 Platform will receive request
Ref. App
message
Provider CCN AP 5. The Partner#2
WAN Service Provider will
send response
message to
Partner #2 DC Parnter#1 Service
Consumer Partner
Ref. App
Consumer
application

Ref. App
Provider
Ref. App
Consumer
Ref. App
Provider
28
CCN2 CT Strategy
Features to be tested
Features to be tested – CCN2 Platform

Features CT
Managed Service Interactions

Service Connectivity Services 
Sync. Req./Resp. 
Async. “ One-way” 
Async. Req./Call-Back 
Pub/Sub 
Managed Access to Web Applications
Web Access Manager Services 
Security Enforcement
Access Management 
Authentication 
Authorisation 
Identity Propagation 
Data Security 
Encryption/ Decryption 
Digital Signatures 
Identity Sharing 
•: feature fully covered in test phase;
•: feature partially covered in test phase. In context of CT this means, testing all
functionalities exposed to Partners. In ATP for each specific test phase detailed 29
coverage is elaborated;
•: feature not covered in test phase.
CCN2 CT Strategy

Features CT
Federated Governance
Identity Management Services 
Services Life Cycle Services 
Service Discovery Services 
Communication Services
Subscription Manager 
Transformation & Validation Interactions 
Routing Services 
Monitoring Interactions
Business Activity Monitoring 
System Activity Monitoring 
Service Monitoring 
General Monitoring 
: feature partially covered in test phase. In context of CT this means, testing all
functionalities exposed to Partners. In ATP for each specific test phase detailed 30
coverage is elaborated;
CCN2 CT Strategy

Features CT
Configuration Management 
Deployment 
Error Handling 
Back up and Archiving 
Connectivity 
High Availability and Fail Over 
Disaster Recovery 
Performance and Stress Testing 
• : feature partially covered in test phase. In context of CT this means, testing all
functionalities exposed to Partners. In ATP for each specific test phase detailed
coverage is elaborated; 31
• : feature not covered in test phase.
CCN2 CT Strategy
Responsibilities
CT test approach – CCN2 Platform

Test organisation
Test DG TAXUD Partners CCN2DEV QA ITSM2 Network
Phase Provider
Decides if phase
is started and Participat
CT later on Responsible - es and Supports Supports
concluded monitors
• ITSM2 contractor guides and supports and organise testing

activities
• Test are executed by Partners
• QA Monitors the testing
32
Organisation of Conformance testing
• The coordination and support of the conformance
testing activities will be performed by the ITSM
contractor
• CCN2DEV will provide 3rd level support
• ITSM will provide details on the organisation of the
CCN2 conformance testing activities
• Conformance test training with hands-on exercise
will be organised around September 2016
How to install a Ref App
How to connect to CT
How to run a Ref App
Main test cases
What are the results
33
CCN2 CT Strategy
Responsibilities
Test Approach R1 - CCN2 Platform

• Test case execution runs will be recorded in Synergia and results
will be consolidated at the end of each planned run to gauge
progress of this testing cycle;
• During CT closure meeting (for CT Campaign) results of testing

activities are discussed and actions on outstanding issues (if any)
are assigned by opening appropriate defects;
• It is also decided if there is any need for another release of the

application before next phase;
• If DG TAXUD agrees with test results, application delivery is then

recommended for production and this marks the end of the CT
campaign.
34
CCN2 CT Strategy
RefApp Overview
Business Reference Applications

Business Reference Applications implement complex processing scenario
depicted in the diagram.
35
CCN2 CT Strategy
Ref Apps

• Business Reference Applications illustrate usage of CCN2 communication
patterns within a business process.
• As visible on diagram above all of System to System communication
patterns are covered by interactions between applications.
• User to System interaction is exercised within “Take Customs Decision”
step
• There are four Business Reference Applications
• Jtrader
• jDecision
• jConsultation
• jCustoms
36
CCN2 CT Strategy
Ref Apps

4 Business Reference Applications
jTrader jDecision jConsultation jConsultation
Implements Implements Implements Implements

behaviour of behaviour of behaviour of behaviour of
trader Decision Central Customs Customs
Authority Consultation Authority
Service
Type: Type: Type: Type:
• Standalone • Web • Standalone • Standalone
Interaction: Interaction: Interaction: Interaction:
• R/R • R/R • R/C • P/S
• F&F • R/C • F&F
• F&F • P/S
• U2S
37
CCN2 CT Strategy
Ref Apps

Standalone vs. Web Applications
Standalone Java-Based Ref

Apps Java Web Application
• Compatible with any HW and OS • Running within Weblogic server or
that may run a Java Virtual any other web server supporting
Machine (JVM) deployment of web based
• Deployment will be on file system applications
• They use Windows batch files for • Operational capabilities
operational purposes • Deployment via WLS
• Operational capabilities administration console
• Start/stop via provided • Start/Stop via WLS
batch files administration console
• Monitoring via OS and JVM • Monitoring via WLS
capabilities administration console
38
Reference Applications
Infrastructure
Infrastructure Requirements (IRD)

• Supported Operating Systems
• Any Java Compliant Operating Systems
• Java Virtual Machine (JVM)

• Memory > 512Mb / Disk Space > 1Gb
• JRE 6 (jdk 1.6 / jre 6) or higher with latest patch set
• Java Web Server

• For the Web Application components
39
Backup Slides
40
CCN2 CT Strategy
Ref apps
Test Approach R1 - Reference

Applications
• RefApp will be tested in the loop mode via CCN2
Platform (Sending and Receiving Ref. Apps will be
installed on the same Partner DC);
• And later used to test integration with CCN2 Platform
and other Partners;
• Sender Partner Reference Applications and receiving
Partner Reference Applications will be installed on
Partner DC;
• CCN2 Platform routing configuration needs to be
configured to route incoming messages from Partner
back to same Partner.
41
Reference Applications
Overview
Functional Scope
• Describe how the functional capabilities of the
Reference Applications are realised by the
services offered and what data models support
the realisation of these services.
• Atomic Reference Applications demonstrate use
of S2S and U2S interactions supported by the
CCN2 Platform.
• Business Reference Applications demonstrate use
of those interactions within a simplified business
context of Customs Decision.
42
CCN2 CT Strategy
Ref apps
Test Approach R1 - Reference Apps

• Loop Mode
CCN2 Platform
Ref. App.
Consumer CCN
WAN AP
Ref. App
Provider
43
CCN2 CT Strategy
RefApp Overview

depicted in diagram.
jTrader acts as
Trader
jTrader acts as a client in R/R

communication with jDecision. It sends a
request (customs application) to jDecision,
and receives a response
(acknowledgement) from jDecision.
44
CCN2 CT Strategy
RefApp Overview

jDecision implements
jDecision acts as a server in R/R
behaviour of Decision
communication. It receives a request
Authority
(customs application) from jTrader,
processes it, and stores it.
45
CCN2 CT Strategy
RefApp Overview

depicted in the diagram. jConsultation implements
behaviour of Central
Customs Consultation
Service
jConsultation acts as a
server in R/C
communication with
jDecision application. It
jDecision acts as a client receives a request
in R/R communication (consultation requests)
with jConsultation from jDecision, initiates
application. It sends a consultation process,
request (consultation builds a consultation
request) to jConsultation. result message, and
sends a response
(consultation result) to
jDecision.
46
CCN2 CT Strategy
RefApp Overview

jDecision is responsible for U2S
interaction with decision taker, it
presents a user with consultation
result, collects user’s decision,
and stores it. It sends a request
jTrader acts as a (notification of decision taken) to
server in F&F jTrader.
communication with
jDecision application.
It receives a request
(notification of
decision taken) from
jDecision
jDecision also acts also

as a publisher in P/S
interaction with 47
jCustoms application.
CCN2 CT Strategy
RefApp Overview

jCustoms implements
behaviour of
Customs Authority.
jCustoms receives a request

(notification) from jConsultation. It
uses P/S services offered by AP in
order to subscribe to a topic 48
CCN2 CT Strategy
RefApp Overview

jConsultation uses F&F-style

communication with BAM via AP, to
send a request (progress notification)
to BAM.
49

5.4 CCN2 Conformance Testing

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

5.4 CCN2 Conformance Testing

Uploaded by

Copyright:

Available Formats

4.

4 CCN2 Conformance Test

Purpose of the CCN2 Conformance testing is to

16/09/16 23/09/16 04/11/16

CCN2 Installation (R1) CCN2 R1.5 upgrade

Conformance Test Approach R1

Conformance Test Approach R1

CCN2 Platform (AP + Ref. Appl.

Conformance Test Approach R1

Conformance Test Approach R1

TDS is a library of Test cases

Test Strategy R1 – Scope TDS/ATP

• Conformance Environment is as close as possible to production

• CCN2 Platform architecture supports central deployment of

• In the Conformation environment there is a central deployed

Conformance Test Approach R1

• Conformance testing phase is made up of three

Conformance Test Approach R1

• CCN2 Conformance Mode 1 schema

Conformance Test Approach R1

• CCN2 Conformance Mode 1

Conformance Test Mode 1

Central Deployed Ref Apps

Conformance Test Mode 1

Central Deployed Ref Apps

Conformance Test Approach R1

• CCN2 Conformance Mode 2 schema

CT Mode 2 : Testing the functionalities by simulating another Partner

Ref. Appl. CCN2 Platform (AP + Ref. Appl.

Conformance Test Approach R1

• CCN2 Conformance Mode 2

Conformance Test Mode 2

Central Deployed Ref Apps

Ref. App Ref. App

Conformance Test Mode 2

Central Deployed Ref Apps

Ref. App Ref. App

Conformance Test Mode 2

Partner #1 DC 1. Service Consumer will

1. R/C Req uest Message

Central Deployed Ref Apps

Ref. App Ref. App

Conformance Test Mode 2

Partner #1 DC 4. CCN2 Platform will

1. R/C Req uest Message

Conformance Test Mode 2

2. R/C Callback Message

1. R/C Req uest Message

Central Deployed Ref Apps

Ref. App Ref. App 7. Construct

Conformance Test Mode 2

1. R/C Req uest Message

Ref. App Ref. App

Conformance Test Approach R1

CT Mode 3 : Testing the functionalities with other Partners

Partner #1 DC DG TAXUD DC Partner #2 DC

• CCN2 Conformance Mode 3

Conformance Test Mode 3

Central Deployed Ref Apps

Conformance Test Mode 3

Central Deployed Ref Apps

Features to be tested – CCN2 Platform

Managed Service Interactions