Creating Jira issues for the test results
You can create Jira issues for the tests that ran in HCL OneTest™ Server. The issues are created in the project in Jira that you configured in HCL OneTest™ Server.
Before you begin
- Ensured that you are assigned a role as a Project Owner or Tester in the project. See Managing access to the server projects.
-
Configured Jira as a change management system for your project in HCL OneTest™ Server. See Configuring Jira as a change management system.
- Configured a test run. See Test run configurations.
- Viewed the results of the completed test runs on the Results page. See Test results.
About this task
When you want to create a Jira issue in HCL OneTest™ Server, the issue types that display in the Create an issue in Jira dialog depend on the configuration done by the administrator of the Jira server.
- Issue Type
- Summary
- Description
- Attach Reports
If you want to view any additional fields in the Create an issue in Jira dialog from HCL OneTest™ Server, then you must inform your Jira server administrator to configure those additional fields as the required fields in the project on the Jira server. You can then use those fields in the Create an issue in Jira dialog when you create a defect from HCL OneTest™ Server.
You can refer to the Related information section to know more about Jira field configuration.
Procedure
-
Log in to HCL OneTest™ Server.
The team space that contains your project is displayed.
-
Click
to open the project that contains the test assets.
The Overview page of the project is displayed.
-
Click
.The Results page is displayed and all the test assets that were run earlier are displayed in tabs, as listed in the following table:
Tab Description SUITES Lists all suites, Compound Tests, JMeter tests, JUnit tests, Postman tests, Rate Schedules, Selenium tests, or VU Schedules that are in the selected branch of the repository. TESTS Lists all API tests, functional tests, or performance tests that are in the selected branch of the repository. ADVANCED Lists all assets that are displayed when custom filters are applied for assets in the selected branch of the repository. Note: You can click the relevant tab to view the tests that were run earlier. -
Perform any of the following actions to identify the test asset:
- Scroll through the list.Tip: You can hover over the icon in the Type column to know the type of the test asset.Note: You can also identify the type of the asset from the icon that represents the test type as shown in the following table:
Icon Represents Listed in the SUITES tab Listed in the TESTS tab Listed in the ADVANCED tab API test Functional test Performance test AFT Suite API Suite Compound Test HCL AppScan CodeSweep JMeter Test JUnit Test Postman test Rate Schedule Selenium test VU Schedule - Search for the test by entering any text that is contained in the test asset name in the Search field.
-
Select the time interval within which the test was run.
For example, you can select the Last 24 hours option to view the tests that were run in the previous 24 hours.
-
Select the range of dates within which the test was run.
You can click the calendar icon to select the date in the first image as the start date, and then select the date in the second image as the end date.
Note: You can select the range of dates only when you select the time interval as Custom. -
Click the Filter icon in the SUITES or TESTS tab, and then select the test type.
All the tests based on the selected test type are displayed.
For example, you can select API Suite in the SUITES tab to display all the API suites or you can select Functional Test in the TESTS tab to display all the functional tests.
- Click the Filter icon in the ADVANCED tab, and
then perform the following actions to create a filter
query:
- Click New filter.
- Enter a name for the filter.
- Select an operator, and then select Add rule to add a rule or Add group to add a group of rules.
- Select or enter the relevant parameters, and then
either select or enter the condition and the
criteria for the condition.You can select a parameter from the following list:
- ID
- Type
- Test
- Version
- Result
- Started on
- Finish on
- Duration
- Status
- Verdict
- Labels
- Locked
- Repository
- Branch
- Text
- Click Save.
The filter query is saved and all the tests that match the filter criteria are displayed.
- Perform the following actions in the
ADVANCED tab to retrieve and
apply a previously saved filter query:
- Click the Filter icon .
All the filter queries that you created and saved earlier are displayed.
- Click the filter query that you want to apply.
All the tests that match the filter criteria are displayed.
- Click the Filter icon .
You have identified the test that you want to use.
- Scroll through the list.
-
Select the step that depends on the role assigned to you in the project on HCL OneTest™ Server:
- If you are a member with a role assigned as Owner, go to Step 6.
- If you are a member with a role assigned as Tester, and if you did not complete the one-time authorization process, go to Step 7.
- If you are a member with a role assigned as Tester and completed the one-time authorization process, go to Step 8.
-
Perform the following steps as the project Owner:
-
Perform the following steps as a member assigned the Tester
role and if you have not yet completed the one-time authorization process:
Note: You must complete the one-time authorization process if you are not a project owner.
-
Perform the following steps as a member assigned the Tester
role and completed the one-time authorization process:
-
Perform the following steps in the Create an issue in Jira
dialog:
Results
You have created issues in the Jira project for the test results from HCL OneTest™ Server.
The Jira issues are created in the Jira project and the links to the issues are displayed in the Details panel of the test result on the Results page.
What to do next
- View details of the Jira issues that you created in Jira for the test. See Viewing details of the Jira issues.
- Modify the configuration that you set for Jira on HCL OneTest™ Server. See Managing the Jira server configuration.