Environments

Environments tell Runner where to actually execute tests against, per project. They're managed under Settings → Environments (Admins only).

Create an environment

1. Pick a project — the dropdown lists your watched repositories.
2. Choose a type: Staging, Preview, Production, or Other.
3. Enter a base URL — must be a valid https:// URL.
4. Optionally add test credentials so Runner can authenticate as a real user: a test user email, a password, and/or an auth token. All three are optional — an environment with none configured is treated as a public target that needs no authentication.

Test credentials are encrypted at rest and are never redisplayed once saved — editing an environment shows whether a credential is configured, not its value.

Multiple environments per project

A project can have more than one environment (e.g. Staging and Production). There's no per-run environment picker yet — when a run needs one, PilotX resolves it deterministically to the oldest environment configured for that project. If you only need one environment per project, this doesn't matter; if you configure more than one, be aware the first one you create is the one Runner uses today.

Deleting an environment

If you delete the only environment configured for a project, you'll be warned before confirming, since Runner will have nowhere to execute tests for that project until a new one is added.