UAT Refresh Policy for Customers and Partners

TL;DR

• UAT environment set to be discontinued by the end of 2025 (12/31/2025)

• Refreshes occur once per month unless otherwise communicated

• Submit the request at least 7 business days in advance (Include the business purpose for the refresh)

• Quik! will confirm the scheduled date within 2 business days of request receipt.

• No UAT refreshes will be performed during production release blackout windows or critical development periods.

• Customer requests for UAT refreshes outside our schedule may incur a fee.

Purpose

This policy outlines Quik!'s approach to refreshing the UAT (User Acceptance Testing) environment. The goal is to balance customer and partner testing needs with our internal release cadence, ensuring stability, predictability, and resource availability for all stakeholders.

The primary purpose of Quik!'s UAT environment is for the Quik! development team and customer teams to test new software functionality, bug fixes, and revisions before releasing them into our production systems. We aim to give customers time to test releases, ensuring that any changes in production do not cause challenges for them post-release.

A secondary purpose of the UAT environment is to facilitate customer testing of new forms that have never been published. However, this secondary purpose requires time-consuming data refreshes and is therefore at the discretion of the Quik! team to perform when feasible.

UAT Refresh Cadence

• Refreshes occur once per month unless otherwise communicated.

• Refreshes will be scheduled and announced in advance of a pending software release for customer testing.

• No UAT refreshes will be performed during production release blackout windows or critical development periods.

Requirements for Customer Requests for UAT Refresh

Customers and partners requesting a UAT refresh must:

• Submit the request at least 7 business days in advance

  • Include the business purpose for the refresh (e.g., form validation, testing integrations)

• Quik! will confirm the scheduled date within 2 business days of request receipt.

• Fees may apply in order to perform the refresh and will be communicated in advance

Communication Protocol For Customer Requests

• Quik! will confirm refresh date/time at least 24 hours in advance.

• Customers and partners will receive a post-refresh notification once the environment is available.

Limitations & Expectations

• UAT refreshes are resource-intensive and impact our release velocity.

• We cannot guarantee refreshes during high-priority release windows.

• UAT is not designed for frequent ad-hoc use. It is a shared environment supporting multiple stakeholders.

• UAT data will be erased, and scrubbed data from production will replace it.
  
  

Alternatives to UAT for Testing (API Customers Only)

We encourage customers and partners to use available features outside of UAT when appropriate:

• DraftMode: Ideal for testing new form configurations without impacting production.

• TestFinalFormsMode: Enables you to test forms waiting in FINAL status (pre-PUBLISH status)

• Parent + Child Account: Create a child account in production with separate credentials, configured as a test account (e.g., DraftMode enabled, Docusign test accounts only, or its own mTLS certificate if needed). It can mirror the parent account’s settings (form subscriptions, bundles, etc.) while remaining a distinct account.

If you're unsure which feature to use, please don't hesitate to reach out. We’re happy to help you find the right solution.

Resources:

Testing in Quik!'s UAT EnvironmentPreview