CKO2:Tests Organization · 12 / 22 CKO2: Tests Organization Not possible before 01/12/2010 Several tests possible depending on the kind of connection : to webservices using participant

CKO2:Tests OrganizationBrussels, 25/10/2010 Update 03/11/2010

Leo D'HAESEPatrick BISSOT

CKO2: Tests Organization2 / 22

Plan

► Purposes

► Tests: for whom?

► Planning/schedule

► Access requirements

► Certificates policy

► Products

► Stress tests

► Test environment

► Clean up of the database

► Connectivity tests

► Debtor identification numbers & data

► Credit data

► Consultation

► Data storing principles

► Testcases

► Contacts

► Question Time


► This meeting

● Giving information on the tests organization

● Answering the questions raised among participants

► The tests

● Assurance for the NBB that participants will comply

with the requirements

● Opportunity for the participants to test their

application (beyond the testcases)

► The document describing the tests

● Giving all the needed information

● Commitment NBB - participants

● New version published on 04/11/10

Purposes


► Current participants: banks & insurance Cies

► New participants: leasing & factoring Cies

which will effectively report data themselves

Asap from 01/12/2010

► A2A automated file upload

► U2A Internet manual file upload via browser

Later

► U2A Internet interactive application via browser

(data entry)

Tests: for whom?


Periods

► Reporting tests: 01/12/2010 to 31/05/2011

► Consultation & outputs: 01/02/2011 to 31/05/2011

Opening days & hours (minimum)

► Wednesday 8:00 am to Friday 10:00 pm(to be extended if possible)

► Weekends reserved for stress tests

Guarantee of any type of support

► Weekdays 8:00 am to 5:00 pm

Test environment will

► stay open after 01/06/2011

► be cleaned up on 01/06/2011

Planning/Schedule


► Possibility of using userid/password in test

environment

► Mandatory use of certificates class 3 (===>

physical identity check of the certificate holder) in test

environment before 01/06/2011

► Same channel to be used to perform the

testcases in test like in prod environment (if

A2A, U2A can also be used in addition)

Access requirements


► A2A: only NBB certificates specific for A2A (1 for all servers)

● already used for other applications (even KCP), or

● newly issued for CKO2

► U2A (by user):

● existing NBB certificates used for other applications, or

● third party certificates (Isabel, Global Sign, Certipost)

► Phasing out NBB certificates but

● A2A certificates will still be issued (limited term) or extended (if needed)

and, afterwards, accepted until validation date

● U2A certificates still accepted until validation date

► Certificates for test environment ≠ production environment

► Possibility to move the authorization of a certificate from Test to Prod

(needs to contact the CCCR)

► Same rules applying in test & prod

► Remark: A2A users will also need U2A certificates in test & prod

environments

Certificates policy (test & prod)


All participants:

► monthly report upload/sending

► feedbacks download/viewing + solving the problems

(technical, validation, identification errors) ===>

resending

Participant interested in consultation: request

sending/answers viewing

Participant interested in subscribing outputs:

download of

► Automatic return

► Statistics

► (Participant's directory)

Products


Principles:

► tests of upload/download of

● files of high volumes and/or

● numerous files

► files not really processed and rejected by

CKO2

► only during weekends

► in consultation with NBB (CCCR back office)

Stress tests


► (Nearly) same functions as prod environment:

as well for OneGate as for CKO2

► Except:

● url's

● opening days and hours

● upload/download of big/numerous files

● certificates

● resident natural persons: no link with NRNP ==>

only dummy n°s in Annex of document will be

processed (rejection otherwise)

Test environment


► No global clean up

► Only individual clean up of the participant’s

own data

► Only on demand addressed to CCCR back

office

Clean up of the database


► Not possible before 01/12/2010

► Several tests possible depending on the kind of

connection :

● to webservices using participant programs, SOAPUI or

Curl

● with https entrypoints using participant programs or Curl

● to web applications of Onegate using an internet

browser and the url of the OneGate appl. in test

● to web applications of CKO2 consultation using an

internet browser and the url of the CKO2 consultation

application in test

► Urls and WSDL for the tests: published on the

CKO2 part of the CCCR website

Connectivity tests


Linkage CKO2 database for tests

● to CBE (only production data)

● in the beginning not to NRNP (legal/confidentiality reasons),

but link hopefully later

● to actual codes tables (postcode, legal form, ...)

► Resident legal entities: only actual enterprise (CBE)

numbers & data

► Resident natural persons:

● actual enterprise numbers & data

● test id numbers & data listed in Annex of document or passed

on in a file to NBB by the interested participants

● internal numbers & actual/dummy data

Debtor identification numbers & data (1)


► Non-resident legal entities: only internal id

numbers & actual/dummy data

► Non-resident natural persons:

● actual enterprise numbers & data

● internal numbers & actual/dummy data

► Associations: internal id numbers &

actual/dummy n°s & data for the individual

debtors

Debtor identification numbers & data (2)


► Actual or dummy data

► Credit amounts with their dimensions

► Risk data

► Will be given back in the answers to requests

Credit data


► Same principles of identification (id number or

id data as for reporting)

► Credit data given back:

● those loaded by NBB (will be later specified to

participants) and/or

● those reported by participant self and/or other

participants

Consultation


Data storing principles in test environment

Debtors reported

with Possible cases of

person type

Other official number

retrieved Data stored in the CKO2 data base

Other database linked to the

CKO2 database where id data is

stored

Enterprise number

Resident legal entity no Enterprise n° and, if the case, non-official data related to the HQ of the branch of a foreign company as reported by the participant self

CBE

Resident natural person NRNP n° (1) Enterprise n°, date of birth and NRNP n° CBE

Non-resident natural person

no Enterprise n°, date of birth, NACEBEL code reported by the participant self

CBE

NRNP number

Resident natural person no NRNP n° and all id data STORED in the CKO2 Database by the NBB or on demand of a participant

no

Resident natural person Enterprise n° (2)

NRNP n°, enterprise n° and date of birth (2) CBE (2)

Internal number

Resident natural person Enterprise n° and NRNP n°

Internal n°, enterprise n°, NRNP n° and date of birth CBE

Resident natural person NRNP n° Internal n°, NRNP n° and all id data STORED in the CKO2 Database by the NBB or on demand of a participant

no

Resident natural person no Internal n° and all id data reported by the participant self

no

Non-resident legal entity no Internal n° and all id data reported by the participant self

no

Non-resident natural person

no Internal n° and all id data reported by the participant self

no

(1) A NRNP should always exist if an enterprise number also exists.

(2) Possibility not offered in a first stage for privacy reasons and no official link to the NRNP. The CCCR will try to be allowed to

download data of the NRNP before the go live of CKO2.


► Reporting: mandatory (at first sight)

Consultation & outputs: optional

► Test cases must be successful for acceptance

by CCCR before going into production

► Reporting:

● All action codes must be tested

● Same channel as this used in prod

To be notified to the CCCR back office

Warning: developing main action codes (DEB, CRED) in

file upload (A2A & U2A) but temptation not to develop the

others and to use data entry channel: can be a very bad

idea

● Same types of id numbers & data as in prod

Test cases (1)


► DEB: upload of reports with new debtors of

possible types of persons, id numbers and

data

Exceptions:

if certain types of persons are not foreseen for some

types of participants: e.g. leasing Cies (known by CCCR)

if certain cases never occur among some participants,

e.g. use of enterprise n° for non-resident natural person

► DEB: download of the feedbacks IAR & DAR

► CRED1: linked to the reported debtors and

with reporting date M (upload report &

download feedbacks)

Test cases (2)


► CRED2: linked to the reported debtors and

with reporting date M+1

► DELDEB: of an existing debtor

► STOPCRED: with reporting date M+2

► MODIDDEB

► CORCRED: of existing credit data

► CONS1: by use of an id number

► CONS2: by use of id data

► Outputs: details will be passed on later

Test cases (3)

The more you test, the best it is for you and us


► NBB

● Business issues (question on CKO2, functional problem, general

topic, administration, userid/password for OneGate test environment

access, ...) & application issues : [email protected]

using the words “business” or “IT” according to the topic

● Connectivity problems: [email protected] or +32 2 221 40 60

● Application problems (not awaited functioning): IT Test coordinator

Johan Vanbilloen +32 2 221 45 57

● Functional questions: Business Test coordinator Marc Ghysels

+32 2 221 46 40

● OneGate access administration: [email protected] or

+32 2 221 54 86

► Participants

URGENTLY to be passed on to [email protected] (with

word "business" in the subject):

at least one tests responsible person (name, e-mail & phone

number + CKO2 participant code + channel if possible)

Contacts

mailto:[email protected]




Thank you for your attention

QuestionTime

Documents

CKO2:Tests Organization · 12 / 22 CKO2: Tests Organization Not possible before 01/12/2010 Several tests possible depending on the kind of connection : to webservices using participant