TestOptimal supports integration with your requirements and defects ALM systems.

• Requirements - bring in requirements into model: Jira, TFS/VSTS, HP QC, Files and Excel.
• Defect - automatically create issues in defect system and visualize the test path on the model to reproduce existing defects: Jira, TFS/VSTS, HP/QC and Fogbugz.

Three simple steps to enable ALM integrations:

1. Configure ALM Data Source (ALM AddOn)
2. Enable ALM Plugin with Model Property
3. Select ALM Data SOurce for models with 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.

ALM Data Source is defined in config.properties file. ALM systems supported are:

1. Atlassian Jira
2. Microsoft TFS/VSTS (Visual Studio Team Service, Azure service)
3. HP QC/ALM
4. Fogbugz
5. File and Excel

• ADDON.MYJIRA.CLASS=com.webmbt.plugin.alm.jira.AddOnJira
• ADDON.MYJIRA.URL=url to JIRA server
• ADDON.MYJIRA.AUTH.USERNAME=username
• ADDON.MYJIRA.AUTH.PASSWORD=password
• ADDON.MYJIRA.AUTH.BUG.ENABLED=true
• ADDON.MYJIRA.AUTH.REQ.ENABLED=true

See JIRA AddOn for more details.

• ADDON.MYQC.CLASS=com.webmbt.alm.addon.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

Requirements can be brought in from excel document, text file, sql database, url and Jira, Jama Contour, Polarion through ALM Plugin.

• Text file - read the text file of the specified format.
• Excel - read the requirement from an Excel file.
• ALM Plugin - reads requirements and raise defects from ALM systems.

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

Once the configuration is completed, you can bring up the list of requirements in various part of IDE:

• State Property - Tags field
• Transition Property - Tags field
• MSCript Editor - (shortcut key ctrl-R).

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.