Users and test data

Most tests need a signed-in user in a known state. Start with sign-in and user state, which recommends an approach for your app, then set up the secrets and custom tools it relies on.

• Sign-in and user state — Recommended approaches for sign-up, sign-in and user state, combining the device's built-in accounts, secrets and custom tools.
• Secrets and credentials — Manage the user accounts, sandbox accounts, and freeform strings your agents use at runtime.
• Custom tools — Give Semaloop agents custom API calls they can use to set up or clean up test state.