Testing Guide

Test Environment

EDIconnect provides a fully isolated test environment for testing the integration before going live in production.

Credentials for the test environment are provided during the integration process. Messages sent in the test environment do not affect production data.

Test Scenarios

Complete the following test scenarios before going live in production:

ORDERS (Inbound)

• Send a valid ORDERS with a single line — verify that a sales order was created in CRMconnect
• Send an ORDERS with multiple lines — verify that all lines were created correctly
• Send an ORDERS with an unknown EAN — verify that error EDI-007 is returned
• Send a duplicate ORDERS (same order number) — verify that error EDI-003 is returned
• Send an ORDERS with an invalid GLN — verify that error EDI-002 is returned

ORDRSP (Outbound)

• After receiving an ORDERS, confirm full acceptance → verify that an ORDRSP of type 231 was sent
• Partially confirm an order (reduce the quantity on a line) → verify ORDRSP of type 232
• Reject an order line → verify ORDRSP of type 232 with LineStatus = Rejected
• Reject an entire order → verify ORDRSP of type 233

DESADV (Outbound)

• Create a delivery in CRMconnect → verify that a DESADV was generated and transmitted
• Partial delivery (less than the ordered quantity) → verify the correctness of quantities
• Delivery with multiple parcels → verify SSCC per parcel
• Delivery with lot/expiry date (food/pharma) → verify the lot and expiry date in DESADV

INVOIC (Outbound)

• Issue an invoice in the Finance module → verify that an INVOIC was generated
• Verify amounts: line totals, VAT and grand total match the invoice
• Credit note → verify BGM qualifier 381
• Invoice with multiple VAT rates → verify the correctness of each TAX segment

RECADV (Inbound)

• Send RECADV with full acceptance → verify that reconciliation was updated
• Send RECADV with partial acceptance (goods shortage) → verify that a credit note suggestion was generated
• Send RECADV with rejection → verify that a return order was created

PRICAT (Outbound)

• Send a complete PRICAT → verify that the partner receives all active products
• Add a new product in CRMconnect → verify that a differential PRICAT was sent within 24 hours
• Discontinue a product → verify PRICAT with ItemStatus = Discontinued

Sample Test Messages

Sample XML and EDIfact files for all message types are available at:

GET https://edi-test.azuvio.io/api/v1/samples/{message}.xml
GET https://edi-test.azuvio.io/api/v1/samples/{message}.edi

Replace {message} with: orders, ordrsp, desadv, invoic, recadv, pricat

Validation Tool

Test and validate a message without actually sending it:

POST https://edi-test.azuvio.io/api/v1/validate
Content-Type: application/xml
Authorization: Bearer {test-token}
X-EDI-MessageType: ORDERS

<Order xmlns="urn:azuvio:ediconnect:orders:v1">
  ...
</Order>

Response:

{
  "valid": true,
  "errors": [],
  "warnings": [
    "Line 1: BuyerArticleCode is empty — optional but recommended"
  ]
}

Production Go-Live Checklist

Before switching to production:

• All 6 message types have been fully tested end-to-end
• GLN mapping confirmed in the production environment
• Transport (AS2/SFTP/API) configured for production endpoints
• Certificate exchange completed (AS2 only)
• First PRICAT sent to the partner in production
• Partner has confirmed the test messages
• SLA response times agreed (ORDRSP within X hours, DESADV within X hours of dispatch)
• Escalation contact exchanged with the partner's EDI team