👨‍🔬Test vs Production Environments 👩‍🔬

The official Test Environments Knowledge Base article documents most of the differences between production and test Slate environments.

This article assumes you're already familiar with test environments. It aims to become a quick reference list of things that do and don't function in various environments.

❌ Things That Don't Work in Test

• Saved query runs are not automatically cleaned up in Test.
• Liaison CAS documents do not attach overnight in Test.
• HTTP GET initialized by a Source Format

✔ Things That Do Work in Test

• Old Sources attached to Source Formats marked as Cumulative / Replaceable are cleaned up in Test.
• Ping (in other words, you can enable in Test first)
  
• Form Consent
  
• Ping Consent
  

⚠ Other Notes

• Only test payment methods can be used in Slate Payments in a test environment. The payment provider is automatically switched to test mode.
• Direct SQL access is not immediately available after a test environment finishes provisioning. It appears that a background job copies the production SQL access settings to test; try waiting an hour if you're unable to connect.
  
• Technolutions says nightly cleanup processes will not automatically run in test environments. However, you can force some process to run via the "Cleanup / Scrub Address Records" tool under Database.