Overview

This document outlines the process for testing integrations before moving to production. The goal is to ensure that the client’s system integrates smoothly with the platform by following a structured testing, monitoring, and communication process.

Integration Testing Process

1. Access to Test Platform (QA Stage)

• The partner will be granted access to a test platform as part of the QA environment.
• The platform will serve as the initial stage for testing the integration.

2. Test Stage: Initial Testing and Setup

• A checklist will be provided to the partner outlining specific tests to be performed. See checklist here.
• We will prepare Trac for testing, following this guide.
• A test date should be agreed in advance with the partner.
• If the partner system handles credits, no overnight testing is required, however, if Trac manages credits, the overnight testing will be necessary to make sure that credits are correctly reallocated. Overall testing shouldn’t take more than two working days.
• The partner will be responsible for testing each type of transaction generated from and received to their system to ensure the Trac integration is functioning correctly.

4. Approval to Move to Production

• Once the client and Pebble both confirm they are satisfied with the results of the test, the Trac integration will be prepared to move to production.
• After approval, the integration will go live in the production environment.

5. Onboarding

• All organisational and platform setups for the partner will be completed in preparation for going live.
• The partner’s platform configuration will be ready for full production use.

6. User Acceptance Testing (UAT)

The User Acceptance Testing (UAT) phase is a five-day process where the system is deployed live for one selected organisation. During this phase, the partner uses the system in a real-world environment to ensure it meets their specific requirements. A member of the Pebble service team will work closely with the partner, monitoring the system for any issues and providing support to resolve them quickly. This ensures the system functions correctly before broader deployment.