Skip to navigation

Authenticated Journeys

View as Markdown

Managed email, one-time-code, phone, and SMS testing are unavailable.

Model the customer outcome

Keep the Test focused on what the customer must accomplish: receive a message, use the expected code or link, and reach the correct signed-in state. Do not put passwords, codes, inbox contents, or phone numbers directly in Test steps.

Prepare safely

  • Use accounts created only for testing.
  • Give each account the minimum product permissions required.
  • Keep recovery paths separate from routine sign-in coverage.
  • Use synthetic data rather than real customer records.

Governed Web Test Account references can supply authorized credentials without placing their values in Test steps. Managed email, one-time-code, phone, and SMS testing remain separate unavailable capabilities.