Showing results for 
Search instead for 
Did you mean: 

How to test pipelines on UAT environment


Snaplogic releases its software 4 times a year to all customers to update the Integration Cloud (Control Plane) and Snaplexes (Data Planes). A separate environment (UAT pod) is provided to customers so they can test their existing pipelines against the latest code base and report issues before the GA. The service is provided to customers free of charge and it is up to customers’ decision on whether to take advantage of the offer.

UAT schedule:
3 weeks before the official release, the latest code base will be made available to customers on UAT environment. The UAT code base will be refreshed in next 2 weekends to include the latest fixes and updates. Take the Fall 2016 release (4.7) which was released on 11/12/2016 as an example:

  1. 10/22/2016: The 1st 4.7 code was made available to customers on UAT environment along with the draft release note on documentation site that details the changes of the release
  2. 10/29/2016: The UAT environment was refreshed with the 2nd update of the 4.7 code base along with updated draft release note.
  3. 11/5/2016: The UAT environment was refreshed with the 3rd update of the 4.7 code base. The release is in code freeze during the last week before the GA which means only P0 defect will be addressed.
  4. 11/12/2016: The official upgrade kicked off at 9:00 PM PST. A 4-hour downtime was planned to complete the upgrade of the Integration Cloud (Control Plane) and the Snaplexes (Data Plane) for every customer (cloud or ground).

How to test on UAT:

  1. Customer requests the access to UAT though their account team.
  2. Snaplogic operation team provisions an org for customer on UAT environment (
  3. Customer setup a groundplex to connect to the UAT environment
  4. Customer exports the pipelines that need to be verified from the production environment and imports into the UAT environment
  5. Customer setup the necessary account credential to connect to data sources and targets
  6. Customer verifies the pipelines work as expected and report to Snaplogic if issues occurred.
  7. Customer to repeat the testing after weekly updates