Testing Environment
This document provides third-party integrators with comprehensive information on how to effectively utilize our testing environments to ensure smooth integration and deployment of your applications with Unifize's systems.
What is a Testing Environment?
At Unifize, our testing environments are standalone organizations (orgs) created specifically for integration purposes, distinct from typical "sandbox" environments. While sandboxes often share settings and data structures with production environments, each Unifize testing environment is an entirely separate org that can be configured as a clone of your live environment upon request.
This ensures that you can test integrations with settings and data that mirror your actual production setup but without affecting live operations.
Requesting a Testing Environment
To request access to a testing environment,
Contact Us
Reach out to your assigned customer success representative, or contact our support team at support@unifize.com.
Request Details
Specify your requirements, including whether you need a clone of the live environment. This configuration helps ensure that the testing environment closely resembles your production environment for accurate testing.
How to Test with Mock Data
Once your testing environment is set up,
Initialize your Environment
Authenticate using the provided credentials specific to your testing org. Note that these credentials will differ from those used in the live environment.
Mock Data Configuration
Configure your test scenarios using the unique identifiers (e.g., Process ID, Org ID, etc.) relevant to your testing org. Remember, these IDs will differ from the live environment.
Testing
Execute your integration scenarios as you would in the live environment. Utilize the extensive logging and debugging tools available within the testing environment to monitor interactions and tweak performances.
Preparing for Live Deployment
Before deploying your integration to the live environment,
ID Mapping
Ensure all references to Unifize identifiers such as Org ID, Process ID, Field ID, and others are correctly mapped to their corresponding live environment values. This step is crucial to prevent mismatches and errors in the live system.
Modifying Credentials
Switch from the testing API credentials to the live environment API credentials, ensuring all API interactions are authenticated correctly.
Validation
Conduct thorough tests to confirm that all integrations function as expected with the correctly mapped IDs and API keys.
Push to Production
Contact your customer success representative to guide you through the necessary steps and approvals needed for transitioning from the testing environment to the live environment.
Troubleshooting
If you encounter issues during integration,
Immediate Assistance
Contact your customer success representative or our API support team for real-time troubleshooting.
Support Documentation
Refer to the API documentation for common issues and troubleshooting tips.
Feedback and Improvements
We welcome feedback on API functionalities and support requests for future features. While not all feature requests may be immediately implemented, they are essential for our continuous improvement.
Last updated