Adaptavist Test Management for Jira


Test Management for Jira (TM4J) is a full-featured test management solution, seamlessly integrated into Jira's user interface. From a central location, coordinates all testing activities, including test planning, authoring, execution, tracking and reporting. Supports REST API integration with test automation tools to submit test results to Test Management For Jira.

Test Management for Jira is an app developed by Adaptavist, an Atlassian Expert.

On this page:

Data Import

This documentation page describes the latest eazyBI app version for Jira Server.

Test Management for Jira (TM4J) or by its former name Adaptavist Test Management (ATM) import option is available starting from the eazyBI version 4.4.0 and is supported just for Jira Server (and not for Jira Cloud).

Since eazyBI version 5.3, is changed the naming convention for referring to Test Management for Jira options and specific measures and dimensions.

  • For eazyBI versions from 4.4.0 to 5.2.1, was used the name Adaptavist Test Management and abbreviation ATM.
  • Since eazyBI version 5.3, is used the name Test Management for Jira and abbreviation TM4J.

If you have installed TM4J - Test Management for Jira Server then in Jira import options you will see Test Management for Jira (TM4J) option or for versions prior eazyBI version 5.3 you will see option with former naming Adaptavist Test Management (ATM).

Test Management for Jira Dimensions

After the import the following additional dimension will be added:

TM4J Defect

Defect issues added during the testing. The dimension is organized in Project and Defect levels.

TM4J EnvironmentEnvironments of scheduled, in progress and completed test executions.
TM4J IterationIterations of test cycles.
TM4J RequirementRequirement issues that have linked test cases. The dimension is organized in Project and Requirement levels.
TM4J Test CaseCreated test cases. The dimension is organized by default hierarchy (in Project and Test Case levels) or by folder hierarchy (in Project, Folder, Subfolder and Test Case).
TM4J Test Case LabelCurrent labels of test cases. If several labels are entered for a test case then it is counted for each label.
TM4J Test Case OwnerOwners of test cases. When used with measure TM4J Test Cases created then returns current test case owner. When used with test case execution measures then returns test case owner during test execution.
TM4J Test Case PriorityPriorities of test cases. When used with measure TM4J Test Cases created then returns current test case priority. When used with test case execution measures then returns test case priority during test execution.
TM4J Test Case Status

Statuses of test cases. When used with measure TM4J Test Cases created then returns current test case status. When used with test case execution measures then returns test case status during test execution.

TM4J Test Cycle

Created test cycles. The dimension is organized by default hierarchy (in Project and Test Cycle levels) or by folder hierarchy (in Project, Folder, Subfolder and Test Cycle).

Dimension name prior eazyBI version 5.3 is "ATM Test Run".

TM4J Test Cycle Related Issue

Jira issues related to test cycles. The dimension is organized in Project and Related Issue levels.

Dimension name prior eazyBI version 5.3 is "ATM Test Run Related Issue".

TM4J Test Cycle StatusCurrent statuses of test cycles.
TM4J Test Executed byUsers who have executed tests.
TM4J Test PlanCreated test plans. The dimension is organized by default hierarchy (in Project and Test Plan levels) or by folder hierarchy (in Project, Folder, Subfolder and Test Plan).
TM4J Test Plan StatusStatuses of test plans (current and historical).
TM4J Test Result StatusStatuses of test case executions (Passed, Failed, In Progress, Not Executed, etc)
TM4J Test Script TypeTypes of test scripts (Plain Text, Steps, etc)

Test Management for Jira Measures

The following measures will be imported. These measures can be analyzed by the mentioned Test management for Jira specific dimensions and by few standard dimensions, TimeProject and Fix Version. Note that, measures used in the report defines the context of standard dimensions and represent project, component or version of tests or test cycles.

TM4J Test Cases created

How many test cases are created.

TM4J Test Cycles created

How many test cycles are created.

TM4J Execution timeHow much time in minutes took to execute test cases.
TM4J Test Cases executedHow many test cases are executed within selected dimensions.
TM4J Test Cases executingHow many test cases are currently executed (in progress) within selected dimensions.
TM4J Test Cases scheduledHow many test cases are scheduled within selected dimensions but not yet executed.
TM4J Test Case defectsHow many defects are registered for test executions. Unique count of different defects is returned for each row in a report.
TM4J ExecutionsHow many times test cases have been executed, are executing or scheduled for execution.
TM4J Automated executionsHow many times test cases have been executed, are executing or scheduled for the execution with an automation tool.
TM4J Test Cases with Test Cycles

How many test cases have at least one test cycle scheduled, in progress or completed.

Dimension name prior eazyBI version 5.3 is "ATM Test Cases with Test Runs".

Test Management for Jira Calculated Measures

The following calculated measures will be created.

TM4J Test Case last execution date

Last execution date of the test case.

This is a test case property and should be used together with TM4J Test Case dimension.

TM4J Test Case last executed by

User who did the last execution of the test case.

This is a test case property and should be used together with TM4J Test Case dimension.

TM4J Test Case estimated time

Current estimated execution time in minutes of the test case.

This is a test case property and should be used together with TM4J Test Case dimension.

TM4J Test Case last execution status

Last execution status of the test case.

This is a test case property and should be used together with TM4J Test Case dimension.

TM4J Test Case last execution version

Version of the last execution of the test case.

This is a test case property and should be used together with TM4J Test Case dimension.

TM4J Execution first dateDate when a test case executed for the first time within selected dimensions. 
TM4J Execution last dateDate when a test case executed for the last time within selected dimensions.
TM4J Average execution timeAverage execution time in minutes per completed executions. Average of measure TM4J Execution time within selected dimensions TM4J Test Cases with Test Cycles.
TM4J Estimated execution time

Estimated execution time in minutes.

TM4J Test Cycle planned start date

Planned start date of the test cycle.

This is a test cycle property and should be used together with TM4J Test Cycles dimension.

TM4J Test Cycle planned end date

Planned end date of the test cycle.

This is a test cycle property and should be used together with TM4J Test Cycles dimension.

TM4J Test Plan labels

Current labels of the test plan separated by a comma.

This is a test plan property and should be used together with TM4J Test Plan dimension.

TM4J Requirement status

Current status of the requirement issue.

This is a requirement property and should be used together with TM4J Requirement dimension.

TM4J Test Plan related issues

Keys of the Issues linked to the test plan.

This is a test plan property and should be used together with TM4J Test Plan dimension.

Accumulated TM4J Executions over reporting periodAccumulated amount of TM4J Executions over the selected reporting period in Time dimension.
TM4J Execution summary

List of test result statuses separated by a comma and how many TM4J Executions are for each test result status.

Issues in Fix versionHow many Jira issues with or without any testing coverage or relation to test cycles are assigned to the selected Fix version. This measure is based on predefined measure Issue created and should be used together with dimension Fix Version

Properties

Dimensions TM4J Defect, TM4J Requirement, and TM4J Test Cycle Related Issue are Jira issues which are also represented in Issue dimension. You can define calculated measure to get any issue property which is imported in eazyBI also for those three TM4J specific dimensions. To access issue property use function get(). For example, to get priority for TM4J Defect, copy a formula of issue property Issue Priority and replace dimension name [Issue] with [TM4J Defect] like this:

[Priority].[Priority].getMemberNameByKey(
  [TM4J Defect].CurrentHierarchyMember.get('Priority ID')
)

Another example, to get resolution date for TM4J Requirement, copy a formula of issue property Issue resolution date and replace dimension name [Issue] with [TM4J Requirement] like this:

[TM4J Requirement].CurrentHierarchyMember.get('Resolved at')