Using CA Continuous Application Insight › Creating Baselines › Consolidated Baseline Tab

Consolidated Baseline Tab

The Consolidated Baseline tab in DevTest Workstation lets you monitor and update baseline test cases at run time.

When you do either of the following tasks, the Consolidated Baseline tab appears in the Test Monitor window:

• Perform a quick test on a baseline test case
• Stage and run a baseline test case

The following graphic shows the Consolidated Baseline tab for a baseline test case that contains three scenarios. In the test run, the last scenario failed. The diff viewer shows where the issue occurred in the last scenario.

The left portion of the tab contains the rows of the baseline test case's Large Data data set. Each row includes a status icon:

• The color gray indicates that the scenario has not yet been run.
• The color green plus a white arrow indicates that the scenario is running.
• The color green indicates that the scenario succeeded.
• The color red indicates that the scenario failed.
• The color orange indicates that the scenario stopped.
• The color yellow indicates that the expected response was updated with the actual response.

After the baseline test case is run, you can select a row to display the results. If the scenario succeeded or failed, the diff viewer shows the expected response and the actual response. Any differences are highlighted. If the scenario stopped, the cycle history appears instead.

You can use the Settings tab to change the comparison options.

Note: For information about the comparison options, see the documentation for the Graphical XML Side-by-Side Comparison assertion in Using CA Application Test.

The toolbar at the bottom contains the following buttons:

Enable

Includes the scenario in subsequent test runs. Be sure to click Save afterward.

Disable

Prevents the scenario from running in subsequent test runs. Be sure to click Save afterward.

Update

Updates the expected response with the actual response. You can perform this action when a scenario failed not because of a functional error but because the system under test has changed. Be sure to click Save afterward.

Undo

Reverses the most recent change.

Redo

Performs the most recent change again.

Save

Saves any changes that were made.