Duration Timespan Filter

Document created by B-F-F08DRX Employee on Jul 19, 2017
Version 1Show Document
  • View in full screen mode

The user has two options to filter their metrics:

  1. Effective – Effective duration includes only that time it took to execute resources from point A to point B in time. This measure is the overall amount of time doing “real work” as opposed to the “overhead” created by ancillary tasks (i.e. time spent doing validations, scripts, IF statements, etc.).
  2. Full – The full amount of time including the overhead of ancillary tasks for the given container from beginning to end.


Note: When Duration Timespan is used, the underlying Maestro server will provide a number that includes only transport times for each container type. If no Duration Timespan filter exists then the default behavior is to show Effective duration for tests created after the introduction of this feature and Full durations for tests run prior to this.