Skip to navigation
Set Up Your Project

Test Accounts and Files

View as Markdown

Test accounts

Use dedicated test accounts for journeys that require sign-in. Keep credentials separate from Test names, steps, screenshots, and notes.

Never paste a real password, access token, or customer credential into a Test. Give each account only the permissions required for its journey and rotate it when access changes.

Governed Test Accounts can supply authorized credentials to supported Web Runs. Use a configured account reference instead of copying its secret into a Test. This does not establish support for managed email, one-time-code, phone, or SMS testing.

Files

Managed Project files for use during execution are not currently available. Prepare clearly named, synthetic fixtures for upload journeys, and confirm that the supported workflow can access them before relying on a Run.

Do not use real customer data in test fixtures.