Caching of Test Runs and Test Run Explorer

Optimizing performance and shorten loading times

To optimize the user experience and provide short load times, the Test Run Explorer content as well as the Test Runs are cached.

The cache is populated when a user displays the Test Run Explorer or a given Test Run for the first time after an application restart. Therefore, this first load can take some time to complete.

Once the Test Run Explorer / Test Run is loaded into the cache, navigating to the Test Run Explorer or the test run is faster.

Updating the cache

The cache is continuously updated based on events emanating from save actions in Aligned Elements.

As a result, the Test Run cache does not automatically update on changes made to external issue objects, such as Jira, GitHub and Azure Dev Ops tickets, since Aligned Elements cannot register to the update events in these systems.

The cache is rebuilt after an application restart (which is performed by the IIS server periodically and/or after extensive idle times).

To force a reload of the cache, click Refresh in the Test Run Explorer or the Test Run, respectively.

The cache has a default lifetime of 120 minutes and is reloaded once this limit has been reached.

The lifetime can be modified in the web.config.