Skip to content

Environments

Connect Personas to named Environment groups.

View as Markdown

Create Personas for your test roles, then connect them to an Environment. Personas can be shared across Environments in the same project.

Shell
smoketest personas create --name Admin --description "Manage billing and team access"
smoketest environments create --name Staging --persona Admin
smoketest environments edit Staging --persona Admin --persona Viewer
smoketest environments list
smoketest environments get Staging

--persona can be repeated. On edit it replaces the full membership list; --clear-personas disconnects all members. --project accepts an ID, short ID or exact project name; otherwise the default project is used. Environment and Persona arguments accept IDs, short IDs or exact names.

Shell
smoketest tests create --name Billing --url https://staging.example.com --description "Check billing" --env Staging --persona Admin
smoketest tests edit Billing --env Preview --persona Admin
smoketest environments delete Staging --yes

Changing a Test's --env clears an incompatible Persona; use --persona to select a different one. Referenced Environments and Persona memberships are protected from deletion. Boards select one Environment in the app and automatically choose its highest-probability Persona for each ticket Attempt. Reusable Tests always use their explicit selection.

The former smoketest env commands are now smoketest personas, without aliases.

Shared variables

Shell
smoketest environments set Staging BASE_URL=https://staging.example.com
smoketest environments set Staging SHARED_TOKEN --secret
smoketest environments unset Staging BASE_URL

--secret prompts securely for the value. Environment variables are available to every Persona when running in that Environment. Persona values override matching keys. Use smoketest personas set for a variable that should only apply to one Persona.

On this page