XPRESSO

History Tracking

About History Tracking

XPRESSO keeps a historical record of all significant events for all user actions in the system when they are saved or when a background action executes. History tracking also monitors all changes and actions to registered objects. For example, if you update a registered Job, it tracks who made the change, when it was made, which metadata was changed, and the reason why.

You can access history tracking information to help you debug any test automation failures that occur due to improper settings, system or operational requirements, or human error.

NOTE 1:
History information for all registered objects and events are retained for the life of the object with one exception; Job Request(s) history data is limited to six months.
NOTE 2:
XPRESSO does not provide History tracking for default (system) Registered objects until the object is modified. XPRESSO will track any changes to the object from this point forward.

Why History Tracking Matters?

You can use History Tracking data to:

  • Trace all changes made to registered objects.

  • Monitor Job Request execution through out every state.

  • Troubleshoot Job Run Request failures from the details tracked in the history. You can then use this information to take the necessary corrective action before executing the job again.

Which Activities are Tracked by XPRESSO?

History tracking is provided for most registered objects; it provides the following details:

  • When - the date/time of the event.
  • Who - who performed the action.
  • Where - which site (location) the event took place.
  • What - what action was performed, the results of the action and any related micro-service or metadata information.

Who can View History Tracking Details?

History Tracking details are restricted to current Group Members. All Group Membership roles (including Guest Members) can view the full history tracking details for all supported objects.

Accessing History Tracking Details

You can view the history details in the registered object detail page under the History tab or History icon button. When you access the history information, a summary of each significant event is provided. Click the Chevron icon button adjacent to History summary to see all details. The information that displays is dynamic based on which object-type history file you are viewing.

On some history details forms, you can click the metadata button to display additional information about the event (again, the information shown is dynamic based on the object-type). For example, if you look at the metadata associated with a Registered Job, it will show which testbed was used, the engine or harness instance used, and other important parameters necessary to run the Job.

System Admin History Tracking Tasks

The System Administrator can perform the following additional tasks with History data including:

  • Search History events by specific dates
  • Filter History events by specific micro-services
  • Perform advanced search and filtering techniques to locate specific history details.
Next