PRODUCT GUIDE
Test accounts and sessions
Give signed-in journeys dedicated access without using customer accounts.
01Use a dedicated test identity
When ColdVisit encounters a sign-in wall, setup can request credentials or a browser storage-state import. Use an account intended for automated testing, with only the data and permissions the selected flow needs.
Credentials, session values, and bypass tokens should never be entered into a flow description or public feedback.
02Import or refresh a session
A browser storage-state import lets ColdVisit reuse a signed-in test session. Sessions can expire or be revoked. If a run requests refreshed access, update the session in Test accounts and verify that the account can reach the required pages.
A session is not permanently valid merely because an earlier run succeeded. Home surfaces access problems separately from product failures.
03Data and parallel runs
Review the flow’s fixture strategy: no setup, fresh account, existing test account, or a configured reset strategy. ColdVisit coordinates access where a test account must be exclusive.
Additional dedicated accounts can support concurrent journeys. Never reuse a real customer’s account to increase test capacity.
Ready to put it into practice?
Open your workspace, or walk through setup with the founder.