Financial processes implemented on Zuora are highly complex and specific for every single company. Zuora offers a variety of configurable features to allow our customers to implement their unique version. This complexity requires attentive and deep implementation in a development environment and detailed testing from both IT and business teams (UAT).
As IT teams embrace agile processes to enhance the speed of change and go to market, deployment automation is being built to support this.
It will ultimately lead to successful changes without human error, as well as multiple deployments within a week or even a day.
This article aims to provide a set of best practices to assist you in your change management journey.
1. Testing and Deployment Best Practice
1.1 Define a Testing Strategy
Develop a solid testing approach and determine which environments will be required to execute the strategy.
A good practice is to have at least three or more stages in the deployment process.
- Development sandbox(es).
- Merging environment (Integrating environment where the code from all the dev environments are synced).
- UAT sandbox.
- Production environment.
In this way, you can thoroughly test the changes to the configuration and the financial processes supported by the applications. The bad practice would be to test your changes in production, which unfortunately happens more often than you would expect. As a result, users will have no control over errors and failures, which will directly impact the front end.
Usually, the trend is to deploy the last successful set of configurations tested in the UAT environment. Regardless of the approach, don't skip testing.