Differences

This shows you the differences between two versions of the page.

--- alm_integration [2017/12/18 01:37] – [Steps to Enable ALM Integration] admin
+++ alm_integration [2020/05/10 16:35] (current) – removed admin
@@ Line 1: / Line 1: @@
-===== ALM Integration =====
-TestOptimal supports integration with your requirements and defects ALM systems.
-  * Requirements - bring in requirements into model and IDE
-  * Defect - automatically create issues in defect system and visualize the test path on the model to reproduce existing defects
-----
-==== Steps to Enable ALM Integration ====
-Three simple steps to enable ALM integrations:
-  - Set up ALM AddOn to point to your ALM systems: requirements and/or defect tracking systems.
-  - Enable ALM Plugin in [[modelnode| Model Property]]
-  - Configure ALM for the model with [[alm_configuration | ALM Configuration]]
-Step 1 just needs to be performed once and it's good for all models in //TestOptimal// installation.
-Perform steps 2-3 for each model that requires ALM integration.
-==== Requirement System Integration ====
-The first step is to configure this integration using the //Model / Configure ALM// menu.  Once it's configured, you can start accessing the requirements in State and Transition Property dialog as well as [[mscripteditor| MScript Editor]] (ctrl-R).
-=== Configuration ===
-Requirements can be brought in from excel document, text file, sql database, url and Jira, Jama Contour, Polarion through [[ALMPlugin | ALM Plugin]].
-  * Text file - read the text file of the specified format.
-  * Excel - read the requirement from an Excel file.
-  * [[ALMPlugin|ALM Plugin]] - reads requirements and raise defects from ALM systems.
-== Text/Excel File ==
-Connection Info Examples:
-  * Text File - enter the name of the file that contains the requirements, e.g. myReqList.txt
-  * Excel File - enter the name of the excel file. By default "Sheet 1" will be read. If you have changed the sheet name or want to read a specific sheet within the Excel document, specify the sheet name prefixed by ";", e.g. myReqList.xls;ReqListSheet
-Both text file and Excel file must reside in //dataset// folder within the model folder and must contain these columns (some are optional):
-  * tag - requirement tag/code, required column
-  * name - requirement short name
-  * priority - H for high, M for medium, L for low
-== ALM Configuration ==
-  * JIRA - setup JIRA connection with the following in //config.properties//. Check out [[jira_addon | JIRA AddOn]] for more details about the configuration.
-    * ADDON.MYJIRA.CLASS=com.webmbt.plugin.alm.jira.AddOnJira
-    * ADDON.MYJIRA.CONNURL=url to JIRA server
-    * ADDON.MYJIRA.USERNAME=username
-    * ADDON.MYJIRA.PASSWORD=password
-    * ADDON.MYJIRA.BUG.ENABLED=true
-    * ADDON.MYJIRA.REQ.ENABLED=true
-  * HP QA/ALM - set up HP QC/ALM connection with the following in //config.properties// - currently in beta.
-    * ADDON.myQC.CLASS=com.webmbt.alm.qc.AddOnQC
-    * ADDON.myQC.URL=url to HP QC/ALM server
-    * ADDON.myQC.DOMAIN=DEFAULT
-    * ADDON.myQC.USERNAME=xyz
-    * ADDON.myQC.PASSWORD=abc
-    * ADDON.myQC.REQ.ENABLED=true
-    * ADDON.myQC.BUG.ENABLED=true
-=== Using Requirements ===
-Once the configuration is completed, you can bring up the list of requirements in various part of IDE:
-  * [[statenode | State Property]] - Tags field
-  * [[transnode | Transition Property]] - Tags field
-  * [[mscripteditor|MSCript Editor]] - (shortcut key ctrl-R).
-=== Requirements Change Handling ===
-The first when the requirement integration is set up, the requirements are automatically brought in and saved with the model.  This allows you to continue to use the requirements that have been brought in and not affected by the future changes to the requirements.
-When requirements are changed, you can bring in the changes using the //Sync// button on //Requirements View//.  Select the changes and click on //Import & Save// button to bring the selected changes into the model.
-----
-==== Defect System Integration====
-Defects detected during the model execution can be automatically raised in the defect system.  Such integration is provided through the ALM plugins.  //TestOptimal// provides plugin to integrate with JIRA, but you can create your own plugin to integrate with other defect tracking system.