Enable Caching
When creating or editing a test, locate the Advanced Configurations section and check the Cached checkbox under it.
How Caching Works
When caching is enabled, the Spur Agent stores successful test execution data. On subsequent runs, cached results are reused when test configuration remains unchanged, significantly reducing execution time and resource consumption. Benefits:- Faster test execution for unchanged tests
- Reduced load on testing infrastructure
- More efficient use of test run quotas
When to Cache Tests
Caching accelerates tests with stable early steps, but becomes counterproductive when variability occurs early in the sequence.When Caching Works Well
Stable setup followed by variable steps
Tests with consistent initial sequences (login, navigation, data preparation) followed by randomization later benefit most.
Minimal expected changes
Cache tests when you anticipate few changes to cached steps and have confirmed test stability through at least one successful run.
When NOT to Cache
Early randomization
Random elements in early steps (such as product selection at step 2) create cascading changes through subsequent steps, preventing cache hits entirely.
High variability throughout
Tests with multiple random or dynamic elements become slower with caching enabled. Poor caching strategy adds overhead from failed cache attempts while still requiring full execution.