Tosca Distributed Execution Early Access

Tricentis offers early access features that are in the early adopter phase, still under development.

Note that Tricentis does not guarantee full usability in this or future Tricentis Tosca versions.

AOS Caching

AOS Caching is available for Tosca Distributed Execution with Automation Object Service (AOS). It speeds up executions.

What does it do?

When a user triggers the execution of tests, the AOS collects all necessary execution objects from the repository. It then forwards these objects to the Tosca Distribution (DEX) Server for distribution to the Agents.

With AOS Caching, the AOS caches execution objects at run-time. It checks the repository every 10 minutes. If there are changes to the cached objects, the AOS loads them into the cache.

So when a user triggers the execution, the AOS doesn't need to collect all objects from the repository. It only collects any new objects, for instance a new TestEvent.

The AOS then forwards the cache and the new objects to the DEX Server.

Note that if you make a change to a cached object and trigger the execution before the AOS could cache the new change, Tosca executes the cached version, not the most recent changes.

If you use AOS Caching, you cannot execute TestCases in parallel.

Activate the feature

By default, AOS Caching is turned off. To activate it, follow the steps below:

  1. On the DEX Server machine, set the system environment variable TRICENTIS_AOS_USE_CACHING to True.

  2. Restart the service Tricentis.ToscaAutomationObjectService in Windows Task Manager.