​
Overview

Step caching optimizes test execution by remembering and reusing input selectors from previous runs. This makes subsequent test runs faster and more cost-effective when the UI elements haven’t changed.

​
How It Works

  1. First Run: The system executes the step normally and caches the input selector
  2. Subsequent Runs: The system uses the cached selector, skipping LLM calls

​
Supported Steps

Caching works only for Explicit step types that perform single actions, such as:

  • Click actions
  • Input text operations

Multi-step or complex actions cannot be cached, which is why caching is limited to Explicit steps that perform one discrete action at a time.

​
Input Text Caching

To enable caching for input text steps, wrap the text in double curly braces:

// This will be cached
input {{test@user.com}} into email field

// This won't be cached
input test@user.com into email field

​
Benefits

  • ⚡️ Faster test execution
  • 💰 Reduced costs (fewer LLM calls)
  • 🎯 More consistent element selection

​
Important Notes

  • Caching only works when the UI elements remain unchanged
  • Only single-action Explicit steps support caching
  • Input text must use the {{text}} syntax to enable caching
  • Complex or multi-step actions cannot be cached