Create Test Repositories
Test Repositories allow LiveCompare to connect to the following testing tools.
Test Repositories are used by actions that require access to their associated test projects. For example, the Search Test Repository action is used to find test assets in the associated project that match a supplied set of tokens.
If you have LiveCompare Administrator privileges, a Test Repository may be created by carrying out the following steps. LiveCompare Editors may also create Test Repositories if this has been permitted by your installation.
- Select the Administration/Test Repositories folder in the LiveCompare hierarchy and choose ‘New > Test Repository…’ from the context menu.
- Complete the Add Test Repository screen as follows:
| Field | Description |
|---|---|
| Name: | A unique name that will identify the Test Repository. |
| Description: | A description for the Test Repository. |
| Type: | Select the type of Test Repository to create, then complete the remaining screen fields as described in the sections below. |
| Add to Resource Groups: | If LiveCompare is resource group-controlled, deselect the appropriate check boxes to exclude the Test Repository from one or more resource groups. If you have LiveCompare Editor privileges, the check box for your current resource group may not be deselected. If you have LiveCompare Administrator privileges, a Test Repository will not be accessible unless it is assigned to at least one resource group. |
For Tosca
LiveCompare integrates with Tosca test repositories using two methods.
Local
If you use the Local integration method, Tosca Commander must be installed on the LiveCompare server. Use Tosca Commander to create a managed workspace that will be used by LiveCompare exclusively. This provides a performance improvement over the REST integration method described below.
To use the Local integration method, carry out the following steps to apply a Tosca license to the LiveCompare account on the LiveCompare server. You should perform these steps only once. They are not necessary if you licensed Tosca Commander while logged in to the LiveCompare server using the LiveCompare account.
-
On the LiveCompare server the Tosca Commander app in the Windows Start menu and select ‘Open file location’ from the context menu.
-
Select ‘Tosca Commander’ in the Start menu folder, hold down the Shift key and select ‘Run as a different user’ from the context menu.
-
In the ‘Run as a different user’ dialog, enter the username and password for the LiveCompare account. The username should have the format .\<account name>.
-
Use the Tosca License screens to apply a Tosca license to the LiveCompare account.
| Field | Description |
|---|---|
| Integration Method | Select ’Local’. |
| Workspace | Select the workspace to which to connect. |
| Client ID | The client ID to use for the connection (required). |
| Client Secret | The client secret to use for the connection (required). |
| Workstates | A comma-separated list of Tosca workstates to be searched for by the Search Test Repository action, for example, COMPLETED. If this field is left blank, the following Tosca workstates are searched for by the Search Test Repository action: PLANNED, COMPLETED, IN_WORK. |
| Configuration | The node path of the Tosca configuration object to be used by the Execute Test Cases action when executing test cases, for example /Execution/Configurations/Any. The node path may be found in Tosca’s ‘Execution’ tab. |
| Search Methods | The search methods to be used by the Search Test Repository action when searching the Tosca Test Repository. |
REST
If you use the REST integration method LiveCompare connects to the specified URL using a REST API. Use Tosca Commander on the Tosca server to create a managed workspace that will be used by LiveCompare exclusively.
| Field | Description |
|---|---|
| Integration Method | Select ‘REST’. |
| Url | The URL used to access Tosca, for example, http://<server name>:<port number>/rest. |
| Workspace | The name of the Tosca Server workspace to which to connect. |
| Client ID | The client ID to use for the connection (required). |
| Client Secret | The client secret to use for the connection (required). |
| Workstates | A comma-separated list of Tosca workstates to be searched for by the Search Test Repository action, for example, COMPLETED. If this field is left blank, the following Tosca workstates are searched for by the Search Test Repository action: PLANNED, COMPLETED, IN_WORK. |
| Configuration | The node path of the Tosca configuration object to be used by the Execute Test Cases action when executing test cases, for example /Execution/Configurations/Any. The node path may be found in Tosca’s ‘Execution’ tab. |
| Search Methods | The search methods to be used by the Search Test Repository action when searching the Tosca Test Repository. |
Avoid timeout errors when using the REST integration method
If timeout errors occur when connected to a Tosca Test Repository using the REST integration method, you may configure the Tosca REST client timeout value by setting a ‘RestClientTimeout’ value in the Configuration - General screen. This should be set to a Tosca REST client timeout value in seconds.
To avoid ‘499’ errors when using the REST integration method, Tosca Server’s Gateway Service must be updated as described in this knowledge base article.
Tosca Test Repository search methods
For qTest
qTest versions 10.0.1 and above are supported.
| Field | Description |
|---|---|
| Url: | The URL used to access qTest. |
| Project: | The name of the qTest project to which to connect. |
| Username: | The qTest username to use for the connection (required). |
| Password: | The qTest password to use for the connection (required). |
| Confirm Password: | Enter the same password for confirmation. |
For ALM
ALM versions 11 and above are supported. Note that ALM 12.50 requires Patch Level 1.
Before creating your first HP ALM Test Repository, carry out the following steps:
- Log in to HP ALM at least once from your LiveCompare server machine to download the appropriate HP ALM client components.
- Select the Administration/Test Repositories folder in the LiveCompare hierarchy and choose Discover ALM Clients from the context menu. Click ‘OK’ to close the following message box:
| Field | Description |
|---|---|
| Client: | Select one of the discovered ALM clients. Each client is identified by the hostname of the machine from which the client components were downloaded. |
| Url: | The URL used to access HP ALM. |
| Project: | The name of the HP ALM project to which to connect. |
| Domain: | The HP ALM domain. |
| Username: | The HP ALM username to use for the connection (required). |
| Password: | The HP ALM password to use for the connection (required). |
| Confirm Password: | Enter the same password for confirmation. |
| API Key: | The HP ALM 15 API key to be used for API key-based authentication. If an API Key and API Secret are specified, these are used for the connection instead of any supplied username and password. If an API key is required, you must enter it every time you change the ALM Test Repository settings. |
| API Secret: | The HP ALM 15 API secret to be used for API key-based authentication. If an API Key and API Secret are specified, these are used for the connection instead of any supplied username and password. If an API secret is required, you must enter it every time you change the ALM Test Repository settings. |
| Requirement Type: | This value is used to set the RequirementType attribute of ALM requirements created for test gaps by the Create Requirements action. |
| Requirement Author: | This value is used to set the Author attribute of ALM requirements created for test gaps by the Create Requirements action. |
For Azure DevOps
| Field | Description |
|---|---|
| Url: | The URL used to access Azure DevOps. |
| Project: | The name of the Azure DevOps project to which to connect. |
| Team: | The name of the Azure DevOps team to use for the connection. |
| Personal Access Token: | Paste in your Azure DevOps personal access token. |
| Confirm Personal Access Token: | Paste in the same personal access token for confirmation. |
For Certify
| Field | Description |
|---|---|
| Project: | The name of the Certify project to which to connect. |
| External Data Source: |
This field should be set to a SQL Server External Data Source which connects to a Certify database. The External Data Source should be configured to read a small table in the database, for example, CertifyVersion. |
For Excel
An Excel Test Repository stores test assets that have exported to an Excel worksheet. The Excel worksheet should include columns that store a test case ID, a test case name, and one or more columns that will be used by the Search Test Repository action to find matching tokens.
Before you create an Excel Test repository, the worksheet containing the test data should be used to create an Excel External Data Source. The first row in the worksheet should contain heading descriptions, for example Test Case ID, Test Case Name… The additional rows should contain test assets.
When creating an Excel Test Repository, columns are referred by the character identifiers in their headings, for example, A, B, C... The letter format should be used in LiveCompare even if Excel has been configured to display numeric identifiers for the column headings.
| Field | Description |
|---|---|
| External Data Source: |
An Excel External Data Source containing a set of test assets. The test assets should include a test case ID column, a test case name column, and one or more columns that will be used by the Search Test Repository action to find matching tokens. |
| Test Case Id Column: | The character identifier of the column that stores the test case ID, for example, A. |
| Test Case Name Column: | The character identifier of the column that stores the test case name, for example, B. |
| Test Case Path Column: (optional) | The character identifier of the column that stores the test case path, for example, C. |
| Search Columns (separate with ,): | A comma-separated list of the column identifiers to be used by the Search Test Repository action to find matching tokens, for example, D,E. Note that there should be no spaces after each comma. |
For SAP Solution Manager
SAP Solution Manager 7.2 is supported.
| Field | Description |
|---|---|
| Url: | The URL used to access SAP Solution Manager, including the port number, for example, http://myserver.example.com:50000. |
| Client: | The SAP Solution Manager client number (required). |
| Solution: | The name of the SAP Solution Manager solution to which to connect, for example, MainSolution. |
| Branch: | The SAP Solution Manager branch to which to connect, for example, Maintenance. |
| Username: | The SAP username to use for the connection. |
| Password: | The SAP password to use for the connection (required). |
| Confirm Password: | Enter the same password for confirmation (required). |
| RFC Destination: | Select the RFC Destination for the appropriate SAP Solution Manager system. |
- Click ‘Save’ to create the Test Repository.
When a Test Repository has been created, it appears in the LiveCompare hierarchy underneath the Administration/Test Repositories folder.
To access a Test Repository from a workflow, assign it to a Test Repository parameter.