Caching

Cache That Adapts

The agent's smart enough to know when its memory needs updating. Changed your button text? Redesigned that form? The agent detects significant changes and refreshes its cache automatically.

Only successful test runs update the cache. If something fails, the agent keeps the last known good configuration—protecting you from cascading failures.

When Fresh Eyes Matter

Some steps always run fresh, without cache:

• AI assertions that check dynamic content
• Data extraction that pulls fresh values each time
• Variable-driven actions using session variables like Type {{username}} in login field

These steps need to see the current state of your app, so the agent evaluates them from scratch every time. This ensures you're always testing against real, live data—not yesterday's snapshot.

Best of Both Worlds

You get speed where it counts and accuracy where it matters. Routine interactions blaze through cached elements. Dynamic validations take a fresh look every time. The agent knows the difference—you don't have to think about it.

How to Enable or Disable Caching

Caching is enabled by default for all test cases. You can control it at the test case level:

• Open a test case
• Go to test case settings
• Toggle caching on or off

When caching is disabled, every step runs fresh on every execution. This is useful for tests where the entire flow depends on dynamic state.

What Gets Cached

The agent caches its understanding of how to interact with elements on the page:

• Element locations — Where buttons, inputs, and links are on the page
• Interaction patterns — How to click, type, or select on specific elements
• Navigation paths — How to get from one page to another

The cache is keyed to the page structure. When the agent detects significant changes (new elements, redesigned layout), it automatically invalidates the relevant cache entries.

Cache Invalidation

The cache updates automatically when:

• A test run succeeds with a different interaction pattern than what's cached
• The page structure changes significantly between runs
• You manually disable and re-enable caching on a test case

You don't need to manually clear the cache in most cases. The agent handles invalidation intelligently based on what it sees in the browser.

When Caching Helps Most

• Stable UI — Tests against pages that don't change layout frequently benefit most
• Slow third-party services — Cached element detection avoids re-analyzing complex pages
• Large test suites — Caching compounds savings across many test runs
• Repeated flows — Login sequences, navigation, and setup steps that run identically every time