Skip to support content

Automation & visual tests

Use URLs and paths in a visual test journey

Navigate across public websites or reuse a base URL for relative paths.

Use full URLs for different sites

A navigation step accepts a full HTTP or HTTPS URL. To visit different public websites in one journey, enter the full URL in each navigation step. A base URL is optional when every navigation step has a full URL.

Use a base URL for paths

Paths beginning with / resolve against the selected environment’s base URL. They do not automatically resolve against the most recently visited website. Create separate environments to run the same paths against production and staging.

Keep credentials scoped to the intended site

Use a credential or secret scoped to the exact origin required by the step. Visiting another domain does not make credentials for the previous domain suitable for that site. If navigation is rejected, check the full URL and whether it resolves to a private-network destination.

Documentation

Related support articles

Need help with this issue?

Email support with this article, your request or capture ID, and the result you expected. Remove credentials and private information first.

Email [email protected]
Back to support