Encrypted environment variables
10 months ago
Store the credentials your tests need — API keys, tokens, database URLs — encrypted at rest and only decrypted inside test sandboxes.
Tests need access to the same credentials your app uses: API keys, OAuth tokens, database connection strings. Qlane now stores them encrypted at rest and only decrypts them inside the test sandbox at the moment of use.
Secrets are masked by default in the dashboard with a click-to-reveal toggle. They never appear in plain text in logs, screenshots, or session traces — even if your app accidentally logs them, we redact known secret values before storage.
Bulk paste from a `.env` file works as you'd expect, including quoting, escaped newlines, and comment-only lines. Rotating a secret in qlane updates every environment that references it.
Decrypted only inside test sandboxes. Never shown in logs.
- Encrypted at rest; decrypted only inside sandboxes.
- Masked by default with click-to-reveal in the dashboard.
- Bulk paste from `.env` files; quoting and escapes handled.
- Known secret values are redacted from logs and screenshots.