Share this page

# Last runs

You can view the last runs for each manual or Gherkin test. The information from the last run is the most relevant and can be used to analyze the quality of the areas covered by the test.

In this topic:

## Display last runs

This section describes where to view last run information. Last run data is stored for each unique combination of the following fields: Release, Milestone, Program, and Environment tags.

Example: If a test was run on Chrome in `Milestone A` and `Milestone B`, and on Firefox in `Milestone A` and `Milestone B`, the test's Last Runs field represents the last run for each combination, four runs in total.

To view last runs:

1. In the Tests tab of Requirements, Features, User Stories, or Application Modules, display the Last runs field.

   The Last runs field contains a color bar where each color represents the statuses of the last runs.

2. Hover over the bar to view a summary of the test run statuses.

3. Click the View runs link to open the details of the last runs.

Back to top

## Definition of last and planned run

The following are definitions of last and planned runs.

Terminology | Definition
--- | ---
Last run | The run that started latest.
Planned run | A planned run is counted as a separate last run, even if its Release, Milestone, Program, and Environment tags match those of a completed run. The planned run is distinguished by its Planned status.
Last planned run | The planned run that was created last.

Back to top

## Filtering last runs

You can filter the last runs according to the following test run attributes: Release, Milestone, Program, Environment tags, Status, Run By. The Last Runs field then includes last runs from the selected filter criteria.

Depending on which Tests tab you are in, apply test run filters as in the table below.

View | How to apply Last Run filters
--- | ---
Requirements > Tests Backlog > Tests Team Backlog > Tests Quality > Tests | Use the Run filters in the Quick Filter sidebar.
Feature > Test User Story > Tests | Click the Advanced Filter button in the toolbar. Select the Last Runs field, and cross-filter by any of these fields: Release, Milestone, Program, Environment tags, Status, or Run By.
Quality > Tests | If you select a program in the context filter, you can see Last Runs only for the selected program.

The Dashboard module has several widgets based on the last run, such as Last run status by browser and Last run status by application module. For details, see Dashboard.

Back to top

## Exceptions to the calculation of last runs

In some cases, Last runs ignores field filters that are applied to the runs. This is true of fields in the Tests tab shown in the Quality and Requirement modules, and the related widgets.

The exception occurs when using an `OR` condition in cross field filters for runs, where only part of the `OR` conditions include such a cross filter.

Examples:

Cross filter | Filter applied / not applied
--- | ---
`(Last runs.Release: ...) OR (Last runs.Status: ...)` | Runs filters are applied.
`(Last runs.Release: ...) OR (Author ...)` | Runs filters are not applied. This results in a larger set of runs.

Back to top

See also:

- Plan and run manual tests
- Manual test run options

https://admhelp.microfocus.com Software Delivery Management 8942
Tips to improve your search results... OpenText™ Software Delivery Management Help Center OpenText™ Software Delivery Management Help 26.1 All View Local Help Center View Online Help Center Version: