Providing an in-editor baseline

In a supported language editor, you can run a baseline code review in which a local history of the opened source code file serves as the baseline version. The process does not require a baseline analysis configuration.

Creating an in-editor baseline

Before you begin

A source code file is open in the COBOL, LPEX, or PL/I editor and has one or more local histories.

Procedure

To create an in-editor baseline, see the following steps.

  1. Right-click the editor and click Software Analysis > In-Editor Baseline > Use Local History.
  2. In the Select Historic Baseline window, select the local history to be used as the baseline version of the source code and click Select Baseline.

Results

The selected local history serves as the baseline version in in-editor baseline code reviews.

Running an in-editor baseline code review

Procedure

To run a in-editor baseline code review, see the following steps.

  1. Right-click the editor, then click Software Analysis.
  2. Click a software analysis configuration. The menu of configurations contains only software analysis configurations. Each is marked with a special icon In-editor baseline to indicate that it is a software analysis configuration that can be applied in an in-editor baseline code review.

Results

The code review runtime component scans only for rule violations that are introduced by changes to the local history that serves as the baseline version.

Closing an in-editor baseline

Procedure

To close an in-editor baseline, see the following steps.

Right-click the editor, then click Software Analysis > In-Editor Baseline > None.

Results

The in-editor baseline is closed.

Feedback