Testing & Go-Live

Testing is a joint responsibility between YAPU and the client. This page explains how testing is structured, what the go-live criteria look like, and what to expect after production deployment.

Testing environments

YAPU provides two environments:

Environment	Purpose	Access
Staging	Integration development and testing	Provided during the specification phase
Production	Live system	Activated after successful staging testing

warning

Never use the production environment for development or exploratory testing. Always validate in staging first.

Testing phases

1. Internal testing (both parties, independently)

Before any joint testing, each party tests their own implementation:

• YAPU tests its side of the integration against the agreed specification.
• Client tests their integration client against the staging environment using the credentials provided by YAPU.

This phase catches integration errors on each side before joint testing begins.

2. Mutual staging integration testing

Both parties connect their systems and run the integration end-to-end in the staging environment:

• Test all defined use case scenarios
• Verify request formats, response handling, and error cases
• Confirm data flows correctly in both directions
• Resolve any discrepancies against the agreed technical documentation

Both parties must sign off on staging results before production deployment.

3. Production deployment

Once staging testing is complete:

• YAPU deploys its changes to the production environment.
• The client deploys their integration to their production system.

Deployment is coordinated between both teams.

4. Mutual production integration testing

A final round of integration testing is conducted in the production environment:

• Run a defined set of test scenarios to confirm live behavior
• Verify that production credentials and endpoints are correctly configured
• Confirm that the system behaves as expected under live conditions

Once both parties confirm successful production testing, the integration is ready to use.

Go-live checklist

Before signing off on production go-live, confirm the following:

• Staging testing completed and approved by both parties
• All test scenarios passed without errors
• Production credentials are correctly configured on the client side
• Production deployment completed by both YAPU and the client
• Production integration testing completed and approved
• Client team knows how to reach YAPU support for post-launch issues
• Monitoring or alerting is in place on the client side for API failures

After go-live — stabilization

After production go-live, a stabilization period begins. During this period:

• The YAPU team monitors the integration for unexpected issues.
• The client team monitors their side for errors or unexpected behavior.
• Your YAPU contact remains available for escalation and support.

If issues arise during stabilization, contact your YAPU representative immediately. See Support & Contact for escalation options.

Common testing mistakes to avoid

Mistake	Why it matters
Skipping staging testing	Production issues are harder and slower to resolve
Using production for development	Risk of exposing real client data; may disrupt live systems
Testing only the happy path	Edge cases and error scenarios must also be validated
Not confirming outgoing data conversion	YAPU returns strings — ensure your system converts them correctly
Mismatching staging and production credentials	Each environment has separate credentials; do not mix them