Terms and Concepts

Terms and Concepts

Starting December 5, 2025 (QMetry Test Management for Jira v4.15.1), the QMetry Test Management for Jira documentation moved from its location on Atlassian to a dedicated, standalone QMetry Test Management for Jira documentation page. For the latest updates, refer to Terms and Concepts.


The following are the major terms and concepts used by QMetry Test Management for Jira.

Term
Description
Bug A defect or issue identified as an error or unintended behavior in the application that causes it to function incorrectly or produce incorrect results.
BuildA Build is a specific iteration of the product/project to be tested. Other common names for a Build are "Drop" or "Iteration".
EnvironmentTest Environments are platforms, configurations, and hardware and software setups against which test cases are executed. 
Exploratory TestingExploratory Testing is a Chrome Extension designed to empower users to conduct testing while they explore websites.
QMetry IntelligenceAI-powered features that enable you to accelerate the test management process through the utilization of Artificial Intelligence (AI) and Machine Learning.
Test Case

A Test Case is a sequence of steps to validate the acceptable functioning of a module, requirement, or user scenario.

Test Cycle

A Test Cycle is an exercise in which an ordered list of test cases assigned to individual testers is executed for a specific build of the product or artifact being tested. Usually, test cycles are bound to a platform or environment, although they can span multiple environments.

Test Plan

A Test Plan is a high-level strategy that drives end-to-end comprehensive testing before a release can be deployed in production.

Test ResultTest Result is an outcome of the testing process that includes the status (Pass, Fail, etc.) of the test case.


The following diagram shows a high-level overview of the relationship between QMetry Test Management and Jira.