11. Subject7 JIRA Plugin (Beta)

Subject7 JIRA plugin provides the ability to map tickets with one or more test cases or execution sets which helps users keep track of issues related to test cases or execution sets. The plugin can also update the status of a ticket based the status of execution (On Pass or On Fail). The plugin also allows users to see the execution videos, logs and other related information directly from JIRA.

Installation Guide

In order to set up Subject7 JIRA plugin, please follow these steps:

1- Log into JIRA plugin with a user that privilege to manage addons

Open

2- On the top right of your user, click on Administration (Gear icon) and select Manage Apps. If you are asked for a password again, please enter it.

Open

3- Click Manage apps on the left side of your screen.

4- Click Upload App

5- Once the Subject7 JIRA plugin is selected, click Upload.

6- Once the plugin is installed, you should see a message like this. Click Close.

Granting Access to Subject7

Before mapping your test cases using Subject7 JIRA plugin, follow these steps:

1- Select the project under which you want to use the plugin from Projects, or create a project.

2- From the bottom left corner of the screen, click Project Settings

3- Click Subject7 Integration as highlighted below.

4- Enter the Subject7 credentials that will be used to access the test cases and execution sets.

5- Click Save and wait for a confirmation message to confirm that access is granted

6- The buttons on the left allow you to perform the below actions:

A- Subject7 Credentials: allows you to enter your Subject7 credentials

B- Subject7 Cloud Run Credentials: stores your Subject7 credentials that are used to run test cases in the cloud directly from JIRA

C- Mapping: allows you to manage all mappings of test cases/execution sets on one screen where you can delete mappings added to a specific issue/ticket

D- Plugin Config: allows you to set an interval for background job that updates JIRA ticket statuses

Mapping Test Cases and Execution Sets

1- Navigate to any ticket/issue that you would like to map to a test case or execution set

2- On the right side of your screen, you will notice Subject7 Addon has been added. Click Mappings

3- You will see a dropdown list asking you to select a project. Select a project or select Common.

4- From this menu, you can now select whether you would like to map test cases or execution sets.

5- This menu will show every folder, test suite, test case and execution set same as you can see under the platform. The image below shows the path same as you see in the platform and you can click on any part of the breadcrumb to traverse to different folders or suites. You can make your selection by clicking on the check box next to a test case/execution set.

6- You can use asterisks to search for a specific test case/execution set as shown below:

7- Once you have made your selection, click Submit

8- You will now see chain icon next to Mappings to indicate that you have test cases/execution sets mapped.

9- To view executions, click on Mappings, then click View Executions icon.

10- If you selected an execution set, you will see its ID that you can click on.

11- On the next screen, you will see all information related to the executions. You can click on Artifacts to view logs and videos same as you do in the platform. You can click on View under Variables and Datasets to view them respectively.

12- In case you want to show more columns, click on the gear icon on the top left of the screen.

13- The icons checked in green indicate columns that are already added while the ones in grey are disabled. Once you have enabled all columns you wish to show, click Save.

Mapping Test Cases with Specific Datasets

Subject7 JIRA plugin allows you to map test cases with specific datasets in mind. You can do this if you want to map several test cases with several tickets depending on their datasets used.

1- To do this, click on the Edit icon next to the selected test case name as shown below:

2- The next menu will show you all the data templates and datasets. By default, "Any" will be selected which means this ticket is showing all executions for all datasets. 

3- To change the mapping to include only specific datasets, you can click the checkbox next to Data Sets Selection to deselect it which will allow using the checkboxes for all the datasets. Then you can select which specific ones to use.

4- When you click Submit, this ticket will now only show executions where the specific dataset you selected was used. Every other execution will be excluded. 

Changing Ticket Status Based on Execution Results

You can use Subject7 JIRA plugin to automatically change the status of the ticket mapped to a test case/execution set as below:

1- On your ticket, take a look at the current status in order to determine what the next status will be. Afterwards, click on Mapping and click on the checkbox next to "Update Ticket Status".

2- You can now use the two dropdown lists titled "On Pass" and "On Fail". Select a status for one or both of these. Once the test case/execution set is executed, the result of the execution will change the status of the ticket according to the selection you make here.

Executing in the Cloud

To run the selected test case(s)/execution set(s) in the cloud directly from JIRA, you can click on the cloud run icon highlighted below. You will be asked once to provide your Subject7 credentials to and they will be saved under Subject7 Cloud Run Credentials tab in plugin settings.

Additional Information:

1- If at least one of the latest executions has "Fail" status, the plugin will set the ticket status that was selected under "On Fail"

2- If none of the latest executions has "Fail" status, the plugin will set the ticket status that was selected under "On Pass"

3- If the status of the ticket gets changed to the status under "On Fail", the history of the execution will be added as a tooltip and the chain icon color will change to blue as below:

4- If your test case is mapped to specific datasets, changing the ticket status will only be done if the execution was performed using those specific datasets only.