Sync Test Steps of a Test CaseĬonnectALL supports syncing of Test Steps of a Perforce Helix ALM Test Case. If you need to add any more filters to restrict the records to be synced by ConnectALL, you will need to define them in the Filter above. The Filter will pull the records from the Modified Items folder. Select "Add to folder" in Action, and select the folder Public/ModifiedItemsĪ filter needs to be created as defined in the table below, the filter name should match the issue type selected in the automation.Navigate to "Actions" tab and click on "Add" button.In the opened window, enter the Rule name and navigate to the "Trigger When" tab and check the "After save" checkbox and then select "Issue is created".Select "Issues" as Type and navigate to the Triggers tab and click the Add button to create a new trigger. ![]() Navigate Tools -> Administration -> Automation Rules.The trigger copies new or updated issues to a special folder called /Public/ModifiedItems. Normally, ConnectALL polls an application by using a query that finds all the records updated since the last sync. Below are the list of steps that need to be configured.Ĭlick on "Folders" and add a new folder under the "Public" folder called ModifiedItems as shown below The Perforce Helix ALM instance needs some specific configurations for ConnectALL to sync records. Perforce Helix ALM Specific Configuration Once you select the "List Type," ConnectALL will pull the allowed values for this field to be used when value mapping.For select lists, you should be able to select the list name in the "Source List Type" dropdown.In the pop-up window that opens, select the data type for the Perforce Helix ALM field, and click "Save".Select the fields to be mapped and click on the "+" icon as shown in the graphic.Perforce Helix ALM is not able to pull metadata of the datatype of the specific field, so the user will need to select the corresponding type when field mapping. The smallest time interval for a query in Perforce Helix ALM is one hour, so instead, we use a trigger approach. ![]() Poll sync of Perforce Helix ALM will not be able to pull the records based on the last sync time it will need specific configuration in the Perforce Helix ALM Instance to pick the modified records. Refer to the Perforce Helix ALM configuration section for more details. ![]() Perforce Helix ALM adapter does not use the filters similar to other adapters, unlike other adapters, we need to define the filters in the Test Track with a specific name to use the API for polling the defects. In addition, you can also map multiple projects in one automation as documented in the multi-project configuration page. The Perforce Helix ALM adapter lets you select the project and test track type. Select "Perforce Helix ALM" from the application drop down box along with the destination application as shown in the graphic below (we are using Quality Center 11+ as an example), give it a name, and click the Map Apps button. Standard and Custom fields in Perforce Helix ALM records.Defects, Requirements, Test Cases, Test Run records.ConnectALL uses Perforce Helix ALM's SOAP API to perform the sync operation. ConnectALL supports syncing of records from Perforce Helix ALM.
0 Comments
Leave a Reply. |