Test mode and the test runtime clouds
You can use test mode on any Test Runtime cloud to which your account has access.
When you are executing processes in test mode you have the option to run them on any Test Runtime cloud that is provisioned on your account. Processes run on a Test Runtime cloud are subject to the same limits as processes run on any Runtime in test mode.
If you enable environments and test connections in your account and you have test connection licenses, you can deploy processes to a Test Runtime cloud. In that case, test mode limitations do not apply. For more information, see the Test connection licensing topic.
When pending Runtime and connector updates become available during the period, they are also available on the Test Runtime clouds. Therefore, you can use a Test Runtime cloud to test your processes prior to the release.
The logs and data from processes run on the Test Runtime clouds are purged on a daily basis. The Test Runtime clouds use their own IP ranges across nodes and they use forked execution.
You cannot use a Test Runtime cloud for processes with connectors that access local resources (e.g., disk, database). However, you can use the Disk connector to read and write from the account's work and tmp directories. You can also create directories within these two directories.
Running a process in a test runtime cloud
Test your process on the US or EU Test Runtime cloud.
You should have test connection licenses, as well as environments and test connections enabled in your account, in order to deploy a process to a Test Runtime cloud. In this case, test mode limitations do not apply.
-
Open the process on the process canvas.
-
Click Test.
-
In the Test dialog, choose Test Runtime cloud (for the US Test Runtime cloud) or Eu Test Runtime cloud from the drop-down list.
-
Click Run Test.
Your process runs in Test mode on the selected Test Runtime cloud.