Managing Zuora environments
Learn how to develop a testing approach and determine the necessary environments for executing a testing strategy in Zuora, including development, merging, and production stages.
Develop a testing approach and determine the environments required to execute the testing strategy. A good practice is to have at least three or more stages in the deployment process before releasing to production.
-
Development sandbox - The environment where the developers will pursue development and testing. You can have multiple sandboxes for different testing environments.
-
Merging environment - Integrating environment where the code from all the development environments is synced before the User Acceptance Testing (UAT) is done. Zuora Central Sandbox mirrors production data, making it the ideal environment for testing the integration and syncing all the isolated developments into one and testing how they will function in Production.
-
Production environment - This is an operationally live environment where subscribers access the Catalog and Services. It must be highly stable and reliable for handling large volumes of transactions as it directly impacts the customer experience.
The Developer environments should be used for development, testing new and existing customizations and ensuring that Production data, integrations, and applications are not compromised.
There may be a merging environment, often named the SIT environment, where all the changes from various developers are merged and tested. The UAT environment is a production-like environment for understanding how the changes will work in the Production environment.