Preview environments

01Choose the environment you intend to test

ColdVisit looks for preview deployments on recent pull requests. Review the detected URL and host before exploring. If no preview is found, setup provides a host-specific guide and lets you check again.

Production deployment success is not a substitute for a pull-request preview. ColdVisit needs a working preview of the code in the pull request.

02Protected previews

A deployment password or hosting-provider access wall is different from your application’s sign-in screen. Supply the requested preview bypass token or header, then let ColdVisit verify access.

Keep bypass values scoped to test environments. You can update environment access in repository settings when the token changes.

03When a preview is unavailable

An unreachable or expired preview is reported as couldn’t run. Check deployment health, access credentials, and the target URL before retrying. It is not counted as a confirmed application regression.