Create Test Repository Cache

This workflow finds transport tasks created on the specified development system over the last 6 months, and then retrieves the executable objects associated with the tasks. These are combined with performance history data retrieved from the specified RFC Destination, and the results are filtered to exclude any objects to ignore, obtained from the UsedObjectsToIgnore External Data Source.

The final set of objects is used to search the specified Test Repository to find matching test assets The matching test assets are then written to a cache associated with the Test Repository. The cache is used by the Smart Impact App and template workflows when searching for test assets for the most-at-risk objects.

Note that when a new cache is stored for a Test Repository, any existing cache data stored for the Test Repository will be overwritten.

Prerequisites

Before you begin, you will need to make sure that performance history data is available for the ‘Performance History System’ that will be used when running the Smart Impact App or Smart Impact Analysis workflow. See the Retrieving Performance History Data help topic for details.

You will also need to create a Test Repository for the project from which to retrieve test assets.

Preparing the Workflow

To prepare the Create Test Repository Cache workflow, drag its workflow template from the Templates folder into your own workspace, and modify the workflow as follows:

To specify the development system:

  1. Select the Dev System parameter and choose ‘Edit RFC Destination’ from the context menu to display the RFC Destination dialog.

  2. Select the Analysis system that will be used when running the Smart Impact App or Smart Impact Analysis workflow, and click ‘Save’.

To specify the system from which to retrieve performance history data:

  1. Select the Performance History System parameter and choose ‘Edit RFC Destination’ from the context menu to display the RFC Destination dialog.

  2. Select the Performance History system that will be used when running the Smart Impact App or Smart Impact Analysis workflow, and click ‘Save’.

To specify the Test Repository from which to retrieve test assets:

  1. Select the Test Repository parameter and choose ‘Edit Test Repository’ from the context menu to display the Test Repository dialog.

  2. Select the Test Repository from which test assets will be retrieved, and click ‘Save’.

To specify the root folders in the specified Test Repository project from which to begin the search for test assets:

  1. Select the Search Paths parameter and choose ‘Edit String List’ from its context menu to display the String List Editor dialog.

  2. Specify one or more root project folders to search, using a backslash to separate folder names, for example Subject\Release 1. Note that trailing backslash characters will be removed, and the string ‘Subject\’ will be added if it is missing from the beginning of the search path. Each root project folder should be stored as a separate string entry.

  3. Click ‘Save’ to close the String List Editor dialog.

Save the workflow using the ‘Save’ toolbar button.

Running the Workflow

To run the Create Test Repository Cache workflow, click the 'Run' toolbar button, choose ‘Run Now’ from the diagram’s context menu, or press F5. The currently running workflow action is marked with an animated display. When the workflow execution has completed, the cache associated with the specified Test Repository will be populated with a set of test assets that match either the used objects, or the executables associated with the retrieved transport tasks.