Variables
Encrypted Variables
How to securely store and use sensitive data like passwords in your tests
Overview
Spur supports Encrypted Variables, allowing you to securely handle sensitive information like passwords or API tokens in your test flows—without exposing them in plain text in test steps or results.
Why Use Encrypted Variables?
Values like passwords or tokens have to be typed directly into test steps:
This exposed sensitive information in:
- The test definition
- The test results page
- Shared test results
How Encrypted Variables Work
Encrypted variables allow you to define secret values that:
- Are stored securely
- Are not shown in results or shared test links
- Appear as
********
on the test result page - Cannot be retrieved after being saved
Creating an Encrypted Variable
You can create an encrypted variable just like any other variable:
- Open the variable menu by using
{
- Click Create new variable
- Select the Secret option
- Name your variable (e.g. password)
- Enter your secret value
- Click Create
This variable will now be stored securely and replaced at runtime.
Encrypted Variables in Results
When the test runs, Spur ensures the encrypted values:
- Are masked as
********
- Are scrubbed from test step reasoning
Notes
- Encrypted variables cannot be viewed or edited once created—only deleted and replaced
- They are intended for one-way use (write-only)
- Perfect for passwords, access tokens, or keys