Skip to main content

What are properties?

Properties let you parameterize your tests with environment-specific values like URLs, credentials, API keys, and configuration settings. A property is a key-value pair associated with specific environments that automatically applies when tests run in those environments.

Variable types

Store base domains and full URLs for your Application.
URL variables are validated to ensure they’re valid URLs. They must include the protocol (http:// or https://).
Store a username and password combination to be used in all HTTPS requests.
Plain-text variables that store values you can use in test steps, such as a test account email or a product name.You can view and edit a variable’s value at any time. Use them for values that aren’t sensitive.
Encrypted variables to store sensitive values usable in test steps, such as passwords or API tokens.
Encrypted variables are write-only after creation. You can replace them but cannot view the current value.
Custom HTTP headers sent with every request in that environment.
Headers are useful for feature flags or routing requests to specific backend services.

Signature header expiry warnings

Some sites with bot protection let verified agents through when each request carries an HTTP message signature, such as a Shopify Web Bot Auth signature. You add these as Header properties, including a Signature-Input header. Each signature stops working at its own expiry time, and the site can then block runs that send it. Spur reads the expires= value in any Signature-Input header and warns you when the signature has expired or expires within 7 days. For example, Spur flags this header value once its expiry (a Unix timestamp in seconds) is less than 7 days away:

Where warnings appear

  • Environments page: The property shows an Expired <date> badge in red, or an Expires <date> badge. Hover over the badge to see the exact expiry time.
  • Dashboard: An alert lists every affected header and its environment. Each header links to its property. Click Dismiss to hide the alert. It appears again if a header changes, a new header is affected, or a header that was expiring soon has now expired.
  • Run modals: When you start a manual run or a Test Plan run that sends an expired header, Spur lists the header and disables Start Runs. Click Run anyway to start the run without updating the header. If a header only expires soon, the run starts and Spur shows a warning toast with an Update header link.
  • Scheduler: Schedules that send an affected header show a warning icon on their card or row, and the Scheduler link in the sidebar shows one too. A banner names the affected Test Plans and links each header. Click Show schedules to jump to the next affected run. See Scheduler.
Spur only blocks runs you start from a run modal. Runs started from CI, MCP, or chat, and scheduled runs, start without a prompt.

Fix an expiring signature

  1. Generate a new signature with your signing tool or provider.
  2. On the Environments page, open the Properties tab and select the header. Each warning links straight to it.
  3. Paste the new value into the header for each affected environment and save.
The warnings clear once the new expires= value is more than 7 days away.

How to create properties

1

Navigate to environment and change tabs

Navigate to the Environments page and switch from the Web URL tab to the Properties tab.
Navigate to Environment and Change Tabs
2

Click + add property button

Click the + Add Property button on the right to begin creating a new property.
Click + Add Property Button
3

Select property type

Select a property type: Variable, Encrypted Variable, Header, or HTTPS Credential. Each type serves different purposes as explained in the Variable Types section above.
Select Property Type
4

Name the property

Enter a descriptive name for your property.
Name the Property
5

Configure values for each environment

All configured environments display in the table. For each environment, enter the appropriate value. Leave an environment empty if the property doesn’t apply there.
You can also apply the same value to other environments automatically by clicking the Apply value to all environments option.
Configure values for each environment
Only URL properties require a value. Other property types can be saved without one.
6

Choose whether to apply to all tests

For Header, HTTPS Credential, and route override properties, the property details panel shows an Apply to all tests switch. Turn it on to use the property on every test run, in every environment. See Apply to all tests.
7

Click create property

Click Create Property to finalize creation. The new property is available to all tests running in the configured environments.
Click Create Property
8

Using properties in tests

Once created, properties automatically apply to tests running in their configured environments.The Spur Agent uses the appropriate property value based on which environment the test executes in.

Apply to all tests

Apply to all tests is a key-level setting for Header, HTTPS Credential, and route override properties. When it’s on, Spur sends the property with every test run, in every environment, without selecting it on each test or suite. The switch is on by default when you create a new header. Spur picks which headers, credentials, and route overrides to use for a run in this order of precedence:
  1. The test’s own selection. If the test selects its own headers, credential, or route overrides, Spur uses those.
  2. The suite’s selection. If the test has no selection, Spur uses the suite’s Default Environment Properties.
  3. All tests. If neither the test nor the suite selects any, Spur uses the properties with Apply to all tests turned on.
A property with Apply to all tests on shows All in its Connected Tests tab. In the suite’s Default Environment Properties modal and in the test editor’s Headers and HTTPS Credentials sections, these properties appear with an All tests chip. The chip is dimmed when a test or suite selection overrides it.
An environment only sends a header that has a value in that environment. If a header has no value in the environment you’re previewing, the test editor shows No value in this environment — not sent here.

Keys not set in this environment

The Properties and Web URLs tables list keys that have values in other environments but not in the current one. These keys appear in a collapsed Not set in this environment group at the bottom of the table. Expand the group and click a row to open the property panel and enter a value for this environment.

Using variables in test steps

You can reference a Variable or an Encrypted Variable inside any test step.
  1. In the step editor, type { to open the variable menu.
  2. Select an existing variable, or create a new one.
  3. To create one, set Variable Type to Variable or Encrypted Variable. Both types save to Environments.
The variable appears as a chip in the step. At run time, Spur replaces it with the value set for the environment the test runs in. Plain variables and encrypted variables display differently:
Hover over a plain variable chip to see where its value comes from. In the editor, the tooltip shows From preview of environment:. In results, it shows Value in this run:.
For more on sensitive values, see Encrypted variables.

Best practices

  • Use descriptive names: Make property names self-explanatory for team collaboration
  • Apply to all tests deliberately: Turn on Apply to all tests only for headers, credentials, and route overrides every test needs. Use test or suite selections for the rest
  • Use encrypted variables for sensitive data: Store passwords, API keys, and tokens as Encrypted Variable properties. Use plain Variable properties only for values that are safe to show in results
  • Validate URL variables: Ensure all URL variables include the protocol (https://)
  • Apply values across environments strategically: Use “apply to all environments” only when values are truly universal