QMetry Glossary

API Key

A unique identifier used to authenticate and authorize API requests.

Archive

An operation that removes a test asset (and its versions) from active folders without permanently deleting it. Archived items can be restored or viewed via the Show Archived Recordsfilter.

Automated Test Case

A test case created through Automation APIs.

BDD (Behavior-Driven Development)

A test-authoring approach using Given-When-Then scenarios. The BDD section appears only when a version control system is configured for the project.

Bug

A defect or issue identified during testing that affects the expected behavior of the application.

Build

A named scope level used to track a specific compiled version of the software under test, linked alongside Release and Cycle for execution and reporting.

Cycle

The smallest unit of scope used for test planning and execution. Each cycle operates independently, and its results do not impact other cycles.

Dashboard

A visual representation of key testing metrics and reports, built from configurable gadgets.

Data Parameterization

The reuse of a single test case across multiple sets of test data, reducing duplication.

Entity Key

The unique identifier assigned to a test asset (e.g., a test case or test suite), used to reference and link assets in bulk.

eSignature

A feature that regularizes the approval workflow of test cases and test executions, enabling multilevel and forced approvals.

Execution Time

The total duration taken to execute a test case.

Flaky Test

A test case that produces inconsistent results, passing or failing unpredictably despite no changes in the code or test environment.

Folder/SubFolder

The hierarchical structure used to organize test assets such as test cases, suites, and requirements within a project.

Gadget

A configurable component placed on a Dashboard that displays a specific testing metric, chart, or report.

Granular Permissions

Module-wise, role-based access that grants permission for individual tasks (View, Create, Modify, Delete, Import, Export, Link, Copy, Versioning) to users or groups.

Issue

A problem reported during testing that needs to be addressed; also referred to as a Defect or Bug, logged when the actual result deviates from the expected result.

Manual Test Case

A test case created through the UI or imported from Excel. QMetry sets this classification automatically; the field is read-only.

Module

Requirements, Test Cases, Test Suites, or Test Execution.

Platform

Any hardware or software that is tested against, from a simple browser to a complex configuration. A platform can have multiple attributes such as BIOS, browser, carrier, CPU, OS, and resolution.

Project

The top level of scope, acting as the central repository or library, since all test assets are held within it.

QI (QMetry Intelligence)

QMetry’s built-in AI engine that powers features such as auto test-case generation from requirements and flaky-test detection

Release

A specific version of the software under test, tracked in QMetry for test execution and reporting. Often used as the second level of scope.

Requirements

A documented need that defines what a product or service should be or do, specifying the necessary attributes, capabilities, characteristics, or qualities a system must have.

Requirement Traceability Matrix (RTM)

A view that maps requirements to their linked test cases and execution status, used to confirm test coverage and identify gaps.

Role

A view that maps requirements to their linked test cases and execution status, used to confirm test coverage and identify gaps.

Shareable Test Steps

Reusable test steps that can be referenced across multiple test cases to reduce duplication and ease maintenance.

Sprint

A time-boxed development cycle in Agile methodology, during which specific features and tests are completed.

Story

A user requirement or functionality defined in Agile development.

Test Assets

Reusable test steps that can be referenced across multiple test cases to reduce duplication and ease maintenance.

Test Case

A time-boxed development cycle in Agile methodology, during which specific features and tests are completed.

Test Case Versioning

A user requirement or functionality defined in Agile development.

Test Data

The input values used when executing a test case, often supplied through parameterization.

Test Execution

The process of running test cases and recording results. The module shows only test suites linked to at least one Release, Cycle, and Platform.

Test Plan

A document that outlines the test strategy, objectives, schedule, and scope.

Test Run

The execution instance of a test suite with recorded results. A run is archived when its associated Platform, Release, Cycle, or Test Suite is archived.

Test Suite

A collection of test cases grouped for execution, run against a platform.