Skip to main content

Testing & UAT

Introduction​

User Acceptance Testing (UAT) documentation is a required step for all partners once the testing process is complete. This documentation serves as proof that the integration complies with the defined standards and is a key prerequisite for moving to production. The YUKK Activation Team will provide and send the required spreadsheets to your team upon completion of the onboarding process.

Functional Testing​

info
His testing is mandatory for the following products:

Functional Testing is a technical validation process conducted on the main API endpoints using the credentials provided by YUKK.

  • Objective: To ensure that the integration flow complies with specifications and that each service responds accurately.

  • Testing Reference: The test cases outlined in the Functional Testing Spreadsheet provided by YUKK.

  • Partner Responsibility:

    • Execute all listed test scenarios.
    • Record test outcomes directly in the spreadsheet.
    • Complete the spreadsheet and return it to YUKK as part of the UAT submission.

By completing this step, partners demonstrate that their system has successfully interacted with YUKK’s core APIs under real conditions.

Developer Site Testing​

info
This testing is mandatory for the following products:

Developer Site Testing is a technical validation carried out between the Partner’s system and ASPI’s Developer Site to verify compliance with the SNAP (National Open API Standard for Payments).

  • Objective: Confirm that the partner system meets ASPI's SNAP standards.

  • Testing Reference: The Developer Site Testing Spreadsheet, which contains both positive and negative scenarios.

  • Scope:

    • Positive Scenarios: Validate proper behavior of the system when valid data and flows are used.
    • Negative Scenarios: Validate error handling when invalid data or error conditions occur. Each API must be tested with different error variations to avoid duplication of negative test cases.

  • Partner Responsibility:

    • Execute all test scenarios listed in the Developer Site spreadsheet.
    • Document results in the provided UAT spreadsheet.
    • Download the PDF test report directly from the ASPI Developer Site.
    • Submit both the UAT spreadsheet and the PDF test report to YUKK as official evidence of completed testing.