Skip to main content
Reusing the same credentials is fine for getting started, but it does not scale. Parallel sessions can overwrite each other’s account data, and repeated runs can accumulate stale test data.

​
Create a unique test account for each session

The recommended approach is:
  1. Add an internal endpoint that creates a test account, deterministically seeds the required test data, and returns its credentials.
  2. Call that endpoint from a setup hook and export the credentials.
  3. Use the exported credentials in the suite’s Auth Instructions.
  4. Delete the account and its data in a teardown hook.
When Run flows in parallel is enabled, Autosana runs the suite’s hooks independently in each session. This gives every flow its own account and data. If dynamic account creation is not available, use a pool of dedicated automation accounts and reserve a different account for each concurrent session.

​
Keep dependent flows sequential

Keep flows sequential when a later flow intentionally uses state created by an earlier flow, such as creating an order and then verifying that same order. Otherwise, give each flow independent setup and cleanup, then enable Run flows in parallel.