Create Pipelines

Pipelines allow all the resources required for an impact analysis using the Smart Impact app to be stored together in a single object. A Pipeline stores the following:

The Analysis, Comparison, Usage and SAP Solution Manager System RFC Destinations to be used in the analysis.
An External Data Source containing a set of Business Critical objects to be used by the Smart Impact app and Smart Impact Analysis workflow.
The Test Repositories to be searched to find test assets that match most-at-risk objects.
The Test Repository in which test requirements are to be created for most-at-risk objects that do not have matching test assets in the specified search Test Repositories.
The Test Repositories in which tests that match most-at-risk objects are to be executed.
The name of the test executions to be created in each Most-at-risk Execution Test Repository.
The path of the Test Repository folder in which tests are to be executed for each Most-at-risk Execution Test Repository.
The execution list path to reuse when creating test executions using the Create Test Execution action for each Most-at-risk Execution Test Repository.

Pipelines are accessible from the Administration/Pipelines folder in the LiveCompare hierarchy. This folder may contain child Pipelines Folders which allow related Pipelines to be grouped together.

If you have LiveCompare Administrator privileges, a Pipeline may be created by carrying out the following steps (a LiveCompare Editor may also create Pipelines if this has been permitted by your installation). Before you begin, you should make sure that each of the RFC Destinations and Test Repositories to be used in the Pipeline have already been created in LiveCompare.

Select the Administration/Pipelines folder in the LiveCompare hierarchy and choose ‘New Pipeline…’ from the context menu.
Complete the Add Pipeline screen as follows:

Field	Description
Name	A unique name that will identify the Pipeline (required).
Description	A description for the Pipeline (optional).
Tester Business Critical	Select this checkbox to make impact analysis results based on this Pipeline more relevant to testers by marking objects that have associated tests as business critical. Impacted business critical objects that have associated tests will be identified as most-at-risk.
Analysis System	The RFC Destination for the Analysis System to be used in the Pipeline (required).
Comparison System	The RFC Destination for the Comparison System to be used in the Pipeline (optional).
SAP Solution Manager System	The RFC Destination for the SAP Solution Manager System to be used in the Pipeline (optional).
Usage System	The RFC Destination for the Usage System to be used in the Pipeline (required).
Business Critical Objects	Select an External Data Source with TYPE and NAME columns containing the set of Business Critical objects to be used by the Smart Impact app and Smart Impact Analysis workflow (optional).
Most-at-risk Search Test Repositories	Specify the Test Repositories to be searched to find test assets that match most-at-risk objects (optional). For each entry: Select the Test Repository to be searched in the Test Repository field. Optionally, specify one or more search paths in the Search Paths field, for example Subject/Release1 Each search path should be entered on a separate line. Click to add a new Test Repository row, or to delete a row. Note that the Most-at-risk Search Test Repositories section must contain at least one row.
Most-at-risk Gaps Test Repository	Select the Test Repository in which test requirements are to be created for most-at-risk objects that do not have matching test assets in the specified search Test Repositories (optional). Tosca, qTest and ALM Test Repositories are supported.
Requirements Path	The name of an existing folder in which test requirements are to be created. Items in the path should be separated with a ‘/’. If this field is not set, ‘Requirements’ is used as the default (optional).
Most-at-risk Hits Execution Test Repositories	This section defines the Test Repositories in which test runs for tests that match most-at-risk objects are to be created or executed (optional). Tosca, qTest and ALM Test Repositories are supported. Complete the fields as described below. Click to add a new row, or to delete an existing row. Note that the Most-at-risk Hits Execution Test Repositories section must contain at least one row.

If LiveCompare is resource group-controlled, use the ‘Resource Groups’ section to add the Pipeline to one or more resource groups. Click ‘Select All’ to select all resource groups, or ‘Select None’ to select no resource groups. If you have LiveCompare Editor privileges, the Pipeline is always added to the current resource group, so the current resource group may not be deselected.
Click ‘Add Pipeline’ to create the Pipeline. When a Pipeline is saved, LiveCompare discards any Search Test Repositories or Execute Test Repositories that have a blank or (Not Selected) Test Repository field.

Most-at-risk Hits Execution Test Repositories Fields

Field	Description
Test Repository	Select the Test Repository in which test runs for tests that match most-at-risk objects are to be created or executed. You may select any of the Most-at-risk Search Test Repositories, however each Most-at-risk Search Test Repository may be used only once.
Execution Name	Enter the name of the test execution to be created in the specified Test Repository. The test execution is created in a time-stamped folder named <Execution Name>_<YYYY-MM-DD HH:MM:SS>. If this field is not set, a time-stamped name of the form LiveCompare_<YYYY-MM-DD HH:MM:SS> is used as the default.
Execution Path	Enter the path to an existing Test Repository folder in which test executions are to be created and/or run, for example Execution/TestExecutions. If this field is not set, test executions will be created in the default Executions folder.
Execution List Path	For Tosca Test Repositories, enter a path to determine the location where the test executions will be created in the Tosca hierarchy. See the Create Test Execution actions help topic for details.
Test Events Path	For Tosca Test Repositories, enter a path to specify a folder where Test Events will be created, for example /MyFolder/Execution/TestEvents. If this field is not set, /Execution/TestEvents is used as the default.
Options	Select ‘Create Test Runs’ to create test runs in the specified Execution Path folder, or ‘Create and Run Test Runs’ to create and execute the test runs. ‘Create and Run Test Runs’ is supported for Tosca Test Repositories only. If ‘Create and Run Test Runs’ is selected, the execution is performed using a Tosca configuration object that is managed using DEX (Tricentis Distributed Execution Engine).