Monitoring Period

Concept

The Monitoring Period defines the timeframe which is used to evaluate stability of components. It is defined in "number of days" or "number of Squore versions".

Squore analyses the history of component Stability (SI) and determines if the component has changed during this monitoring period. This is very useful in different cases:

  • Test Strategy: in order to detect if how long components have been stable

  • Unstable Complexity highlight (in order to list only components which have changed in the monitoring period)

  • Unstable Code Coverage highlight (in order to only list components which have changed during the monitoring period)

  • Test Gap Analysis (in order to detect which components are unstable)

Settings

During the project creation, it is possible to change the Monitoring Period parameters:

SWAN monitoring period settings
Figure 1. Monitoring Period - settings

  • Define the monitoring period unit The time period can be defined as a number of days meaning the "n" days before the last Squore analysis or as a number of "n" squore versions regarding the last Squore analysis. By default, the "number of days" unit is used.

Choice of the unit may depend on the development process maturity and the level of automation of the Squore analysis (ie, daily analysis in continuous integration vs. manual trigger analysis from the GUI).

  • Define the monitoring period The monitoring period duration can be set, depending on the monitoring period unit