PINT MY-Testing-User-Guide-v1.0
PINT MY-Testing-User-Guide-v1.0
User Guide
Table of Contents
1 Introduction ........................................................................................................ 2
1.1 Glossary ....................................................................................................... 2
1.2 Process Overview......................................................................................... 3
2 Prerequisites and preparation .......................................................................... 3
2.1 Prerequisites................................................................................................. 3
2.1.1 Peppol PKI Test Certificate ................................................................... 3
2.1.2 Access Point deployment ...................................................................... 3
2.2 Supported browsers ..................................................................................... 4
2.3 Preparation ................................................................................................... 4
3 PINT MY test suite user interface overview .................................................... 4
4 PINT MY Test Suite Walkthrough ................................................................... 10
4.1 PINT MY test suite...................................................................................... 10
1 Introduction
This document provides information related to the Testbed’s PINT MY accreditation test
suite. Its purpose is to demonstrate and to provide a guide on how to use the PINT MY
test suite’s User Interface. It describes the prerequisites as well as the key steps in carrying
out the various test cases. The target audience for this document is Service Providers
(SPs) that are interested in implementing PINT MY and wish to test their implementations
by using the Testbed’s PINT MY test suite.
1.1 Glossary
Abbreviations used in this document:
Abbreviation Meaning
SP Service Provider
AP Access Point
SMP Service Metadata Publisher
UI User Interface
Table 1 glossary
2.1 Prerequisites
SPs must meet the following requirements before doing any testing.
1
To obtain access to the Malaysian SMP service, please contact the Malaysian PA
2.3 Preparation
A Peppol PKI AP Test Certificate must be installed in your browser before visiting the PINT
MY accreditation test suite for the first time.
Client certificate authentication must be setup in your browser according to the following
instructions:
Windows Google Chrome
Windows Mozilla Firefox
OS-X Generic
When the PINT MY test configuration is created, the user is navigated to the profile page
as shown in Figure 2. The next section provides a general overview of the UI.
The UI consists of the following pages (as shown in Figure 2):
1. PINT MY
2. Documentation
3. Profile
1. The PINT MY page (shown in Figure 3) is used to enroll to the PINT MY test suite.
After enrolling to the PINT MY test suite, the user can choose test cases to execute, as
shown in Figure 4, label 1. As illustrated in Figure 4 label 2, the user may also view details
about the enrolled configuration.
2. The Documentation page (shown in Figure 5) collects and makes available useful links
and resources (e.g., environment documentation, user guide, etc.)
3. The Profile page (shown in Figure 6) provides details about the user account that the
Testbed creates using the Peppol PKI Test Certificate that was imported into the
browser.
You will be presented with the available test cases for this test suite once you have
successfully enrolled. Figure 8 illustrates this. The following are the test cases included in
the PINT MY test suite:
• PINT-TC-AP1: PINT MY Invoice reception
• PINT-TC-AP2: PINT MY Credit Note reception
• PINT-TC-BISC1-1: PINT MY Invoice submission to MY Recipient
• PINT-TC-BISC1-2: PINT MY Credit Note submission to MY Recipient
• PINT-TC-BISC1-3: PINT MY Self Billing Invoice submission to MY Recipient
• PINT-TC-BISC1-4: PINT MY Self Billing Credit Note submission to MY Recipient
• PINT-TC-MY: PINT MY Business Document Validation
It’s worth noting that the PINT MY test suite’s test cases don’t have to be performed in
order. Instead, every test case is ready to be run at any moment. The sole restriction is
that only one test case may run at a time. Once a test case is running, the remainder of
the test cases become unavailable until the current one is finished.
Figure 9 provides a complete visual representation of each test case UI element. As shown in
Figure 9, label 2, each test case contains a title, a status, and a description.
When conducting each test case, make sure to follow the test case description. You can start
a test case by pressing the “Start” button showcased in Figure 9, label 3. The configuration
created by the user during the test suite enrolment is shown in Figure 9, label 4. As illustrated
in Figure 9, label 5, audit logs of events are available that comprise the timing of the
occurrence, the action done, a description and a status. Finally, if you wish to re-enrol in a
new PINT MY test suite configuration and reset the current test suite and all of its test case
progress, select the “RESET TEST SUITE” button (Figure 9, label 6) and re-enrol in a new
test suite.
In the “PINT-TC-AP1: PINT MY Invoice reception” test case, the Testbed environment
will generate an SBD artifact containing a PINT MY Invoice payload and send it to the
under-test AP using eDelivery.
The participant’s addressing information will be dynamically discovered via the SMK/SMP.
The transaction will be addressed to the receiver identifier provided during the test suite
enrolment (participant id and scheme id). To properly receive the message sent by the
testbed AP, you must register your enrolled participant to the centralized Malaysian SMP2,
with the capabilities of receiving PINT MY specification-based Invoices. More specifically:
Document identifier:
busdox-docid-qns::urn:oasis:names:specification:ubl:schema:xsd:Invoice-
2::Invoice##urn:peppol:pint:billing-1@my-1::2.1
Process identifier:
2
To obtain access to the Malaysian SMP service, please contact the Malaysian PA
cenbii-procid-ubl::urn:peppol:bis:billing
Figure 11, shows the successful reception of the message through the eDelivery network
and passing the test.
In the “PINT-TC-AP2: PINT MY Credit Note reception” test case, the Testbed
environment will generate an SBD artifact containing a PINT MY Credit Note payload and
send it to the under-test AP using eDelivery.
The participant’s addressing information will be dynamically discovered via the SMK/SMP.
The transaction will be addressed to the receiver identifier provided during the test suite
enrolment (participant id and scheme id). To properly receive the message sent by the
testbed AP, you must register your enrolled participant to the centralized Malaysian SMP3,
with the capabilities of receiving PINT MY specification-based Credit Notes. More
specifically:
Document identifier:
busdox-docid-qns::urn:oasis:names:specification:ubl:schema:xsd:CreditNote-
2::CreditNote##urn:peppol:pint:billing-1@my-1::2.1
Process identifier:
cenbii-procid-ubl::urn:peppol:bis:billing
Figure 13, shows the successful reception of the message through the eDelivery network
and passing the test.
3
To obtain access to the Malaysian SMP service, please contact the Malaysian PA
A failed audit log entry will notify you in the event of a failed test attempt. By pressing the
button labeled 3 in Figure 14, you can get further information about the mistakes that
occurred, like shown in Figure 15. Examine the errors in the audit log, make any necessary
corrections, and restart the test case till successfully passing the test case.
generated according to the test case’s instructions provided by the Testbed, as illustrated in
the test case description in Figure 16, label 1 and “START” audit log instructions shown in
Figure 16, label 2. The sender will be the participant provided during enrolment (participant
id and scheme id), and the receiver will be the Testbed’s environment AP. Start the test
case, and read the information given in the “START” audit log as shown in Figure 16, label
2. The generated PINT MY based Credit Note payload needs to contain the instance
identifier from the test case “START” audit log description so that the Testbed environment
can correlate the sent document correctly. Once the document is received, the Testbed
environment performs schematron checks to the received document and provides back the
validation results, as the examples shown in Figure 16, labels 3 (fail) and 4 (pass).
A failed audit log entry will notify you in the event of a failed test attempt. By pressing the
button labeled 3 in Figure 16, you can get further information about the mistakes that
occurred, like shown in Figure 17. Examine the errors in the audit log, make any necessary
corrections, and restart the test case till successfully passing the test case.
A failed audit log entry will notify you in the event of a failed test attempt. By pressing the
button labeled 3 in Figure 18, you can get further information about the mistakes that
occurred, like shown in Figure 19. Examine the errors in the audit log, make any necessary
corrections, and restart the test case till successfully passing the test case.
Figure 20 PINT MY self billing credit note submission test case example
A failed audit log entry will notify you in the event of a failed test attempt. By pressing the
button labeled 3 in Figure 20, you can get further information about the mistakes that
occurred, like shown in Figure 21. Examine the errors in the audit log, make any necessary
corrections, and restart the test case till successfully passing the test case.
The “PINT-TC-MY: Business Document Validation” test case, verifies that the under test
AP has configured mechanisms to validate outgoing PINT MY specification based Invoices
and Credit Notes and reject sending invalid ones. Download the zip package, containing
ready-to-send XML artifacts, as marked in Figure 22, label 1. The zip package includes 15
XML artifacts to be sent. Please send them in any order you like and be observant if any errors
occur. Some of the 15 XML artifacts contain schematron errors and your AP implementation
should be able to recognize those invalid artifacts and reject sending them. Before sending
the files, do not alter them in any way, as the Testbed environment may have trouble
correlating them appropriately.
The Testbed environment will inform the user every time it receives a file as shown in Figure
23. The test case will automatically be completed when all expected files are received.
If the Testbed environment receives any invalid artifact the test case execution will fail and
you’ll have to examine the error, correct it and then restart the test case, as shown in Figure
24.
When the test suite is complete (all test cases have been passed) you may also download a
pdf report as shown in Figure 22, label 2.