Synthetic Strategy – Non-Prod

For non-prod testing, mimic your prod single-page test strategy. This will provide a pre-production understanding of what's to come while balancing expectations of what is observed in production week over week.

Using the API scheduler, the best practice to approach non-prod deployments is to link synthetics to specific pre-prod deployments. This will enable a historical track of how deployments are impacting site performance.

Inside your CI/CD pipeline, your development team should implement automated scheduled tests that link to specific releases. This will allow your operation to see historical pre-prod performance as deployments are pushed throughout environments. For more information, visit: https://help-uji.aternity.com/hc/enus/articles/15843312957971-Synthetic-Monitor-Endpoint.