Aligned Elements Web Client User Manual
3.1.272.24402
3.1.272.24402
  • Introduction
  • Basic Concepts
  • Get Started
    • Activate your Aligned Elements Account
    • Log In
    • Open a Project
    • Change Project
    • Create a new Project
    • The Project Start Site
    • Your Assigned Items
    • Manage Your User
    • Log Out
    • Enter Design Control Items
      • Work with Chapters
      • Work with Table Attributes
      • Inserting Images in Attributes
      • Working with Traces
      • Add Issues
      • Add Attachments
      • Collaborate using Comments
      • Favourites
      • Find in... Actions
      • Inconsistencies and Positive Cues
  • Document Object Actions
    • Move and Rearrange Chapters and Document Objects
    • Update Multiple Items
    • Generate Design Control Items
    • Copy Design Control Items
    • Lock Document Objects
    • Generate Reports
    • Export Document Objects
    • Import Document Objects
    • Copy Document Objects between Projects
    • Import Files
  • Explorers and Views
    • Project Explorer
    • File Explorer
    • Trace Explorer
    • Test Run Explorer
    • Project History
    • Chapter View
    • List View
    • Search Result View
    • Export to Excel in Grids
  • Project Status
    • Display Inconsistencies
    • Display Consistency Coverage
    • Display Risk Summary
    • Display DHF Index
  • Queries
    • Run a Query
    • Design a Query
    • Query Filters
  • Charts
    • Display a Chart
    • Design a Chart
  • Trace Tables
    • Run a Trace Table
    • Design a Trace Table
  • Work with Documents
    • Adding Word Document to File Objects
    • The Word Add-in. Adding Design Control Items to Documents
    • Sign Documents with Electronic Signatures
    • Save Files to Disk
    • Released Document View
  • Design Reviews
    • Conduct a Design Review
  • Risk Analysis
    • Perform a FMEA Risk Assessment
    • Perform a Preliminary Hazard Analysis
    • Relative vs. Absolute Mitigations
    • Potential Hazard
    • Using the Risk Analysis to assess the Software Safety Classification
  • Manage Tests
    • Test Runs
      • Planning a Test Run
        • The Burndown Chart
      • Executing a Test Run
      • Completing a Test Run
      • Test Run Functions
      • Test Runs and Linked Projects
      • Caching of Test Runs and Test Run Explorer
    • Classic Tests
  • Work with Tags
    • Add Tags
    • Filter views on Tags
    • Edit Tags
    • Tags and Snapshots
  • Assistants
    • Run an Assistant
  • Snapshots
    • Create a Snapshot
    • Display a Snapshot
    • Compare Snapshots
  • Settings
    • Project Information
    • Manage Users
    • Manage User Groups
    • Project Settings
    • Project Hierarchy
      • Branch Projects
      • Merge Projects
    • Unlock Objects
  • Dashboards
    • Select a Dashboard
    • Create a Dashboard
    • Remove a Dashboard
  • AI Features
    • AI Features in Aligned Elements
  • Aligned Elements Automation Tool
    • The Automation Tool
  • Web Administrator Tools
    • Manage Projects
    • Rename, Copy or Remove Project
    • Manage Users
    • Manage Permissions
    • Register a new Administrator
    • Inspect User Logs
    • Manage Templates
    • Download Log Files
  • Manage Service Configuration
  • Configure a Type Name Change
Powered by GitBook
On this page
  • Optimizing performance and shorten loading times
  • Updating the cache
  1. Manage Tests
  2. Test Runs

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.

PreviousTest Runs and Linked ProjectsNextClassic Tests