Qualitia gives you provision to create issues in JIRA after the test case executions from the Qualitia bot. In order to do so, you need to configure Qualitia bot accordingly.
...
To create issues in JIRA after Qualitia bot execution:
- Log on to Qualitia as a project administrator.
- Under the Admin section, click Projects.
A list of existing Qualitia projects appear. - In the Defect Management section, click Configure next to the project for which you want to configure JIRA as a defect management tool.
A new window appears to fill-up the information about JIRA. - Fill-up all the information related to JIRA and defects that you want to create.
- Create a Qualitia bot (erstwhile Qualitia Offline Package) [from File > Offline Package].
- Add test cases to Qualitia bot and execute based on your requirements.
...
Following is the list of properties from the qualitia.properties file that help you adding issues in JIRA. While creating Qualitia bot, system fill-up values for all these properties based on the values exist in the Configuration Setting (Defect) sectionadded while configuring projects to add defects in JIRA.
| Property Name | Property Value |
|---|---|
| AutoCreateJiraDefect | Specify whether you want automatically to create issues for the defected test cases after test case execution. |
| JiraUrl | This is the URL to JIRA host. For example: https://abcd.atlassian.net In case you are using JIRA Server, enter http:// followed by Host name and port number. |
| JiraUserId | Enter the JIRA username for the account which you want to use for creating the defect. |
| EncryptedJiraPasskey | Enter the JIRA password for the account which you want to use for creating the defect. JIRA password entered by the user in Qualitia will be auto-encrypted at the time of creating Qualitia bot. |
| JiraProject | Enter the JIRA project name in which you want to add the issue. This is not mandatory. |
| JiraProjectKey | Enter the JIRA project key under which you want to create the issue. It is generated when creating JIRA project and unique to each project. For more information about how to find JIRA project keys, refer to the Atlassian JIRA documentation. |
| JiraBugPriority | Enter the bug priority. |
| AttachReportToJiraDefect | Specify whether you want to attach Qualitia test execution report to the JIRA issue. |
| IncludeScreenshotsInJiraAttachment | Specify whether you want to add screenshots when attaching the report to the JIRA issue. |
...
| Keywords to search | |
|---|---|
To view the information about successfully logged issues in JIRA | Successfully attached report to JIRA. Defect Link: |
| Creating JIRA defect for Iteration | |
Since AttachReportToJiraDefect is true | |
| Created temp zip for report attachment at | |
To view the information about failures occurred during logging issues in JIRA | Error occurred while creating JIRA defect for Iteration |
| Error details: org.apache.http.conn.HttpHostConnectException | |
| Error occurred while attaching the report for Iteration | |
| Bad request error | |
Error details: |
| Info |
|---|
At the time of executing Qualitia Bot, in case there are problems in connecting to JIRA, defects occurred in the test cases will not be logged in JIRA. Qualitia users then manually have to collect such defects referring to execution reports and add them in JIRA, if required. |
...