A baseline is a logical name that can be attached to a certain state of a branch of your project. Normal, the state of your project is identified by the timestamp of the run that computed the project state. A baseline is a convenient way to refer to such a state (instead of a date).

A baseline can be used to compare the last run to (otherwise, the last run is compared to the run 30 days ago). A baseline can be used to mark a milestone in your development process.


Baselines can be made visible in trend diagrams as plot-lines
Baselines can be used to compare the latest measurements to

It is even possible to associate multiple consecutive runs with the same baseline. This makes it possible to schedule metric calculation over multiple points in time, while still making it appear as a single logical run in the viewer.

For example, separate the metric calculation into three phases:

  1. All TQI metrics except Abstract Interpretation and Code Coverage:
    TICSQServer -setbaseline MyBaseline -calc ALL -nocalc ABSTRACTINTERPRETATION,UNITTESTCOVERAGE ...
  2. Abstract Interpretation
    TICSQServer -setbaseline MyBaseline -calc ABSTRACTINTERPRETATION ...
  3. Code Coverage
    TICSQServer -setbaseline MyBaseline -calc UNITTESTCOVERAGE ...

By giving these consecutive runs the same baseline, the viewer will show a single measurement point (with the date of the first of these runs).

Setting Baselines

To set a baseline, see TICSMaintenance -setbaseline.

It is also possible to automatically set a baseline after branch calculation: TICSQServer -setbaseline.