Caching

All steps that require locating an element on the page have caching turned on by default, including CLICK, TYPE, and SELECT steps. Steps that always require up-to-date information on the page such as AI CHECK and VISUAL DIFF steps, are never cached.

Momentic caches a variety of contextual identifying data about the element interacted with, from CSS selectors to attributes to screenshots.

Caching can be turned off on a per-step basis using the “Disable cache” option in the test editor. This can be useful for descriptions that should always resolve to a different element on the page, such as “the last item in the list” or “a random option in the dropdown”.

Disabling caching can have latency and pricing implications - please contact your Momentic support representative for more information.

The cache key Momentic uses is rather complex, but ultimately depends on the following data:

• The step’s ID.
• The ID of any module invocations in the step’s parent chain (if applicable). If you are manually copying tests or changing step files locally, please ensure that step IDs remain unique across different tests.

Step caches are generated whenever steps succeed in a Momentic test run. Caches are saved in both interactive test editing sessions, as well as scheduled runs (this includes both runs triggered in Momentic Cloud and runs triggered by the Momentic CLI).

Only successful invocations of steps are cached.