/
QMetry Glossary - Key Terms Explained

QMetry Glossary - Key Terms Explained

 

New to QMetry? Let’s familiarize you with the key terms that will help you navigate the platform with ease.

 

Key Terminologies in QMetry


A

API Key - A unique identifier used to authenticate and authorize API requests.

B

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

Build - A build is another term used by organizations, it refers to a combination of multiple software or hardware builds or configurations.

C

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

D

Dashboard - A visual representation of key testing metrics and reports.

E

Execution Time - The total duration taken to execute a test case.

eSignature - eSignature feature helps organizations regularize the Approval Workflow of test cases and test executions.   

F

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

I

Issue - A problem reported during testing that needs to be addressed.

P

Project - It is referred as the top level of scope and can be considered your central repository or library since all test assets are held within it. 

Platform - A "platform" is any hardware or software that is tested against. This could be as simple as a browser, or complex like a computer with specific "configuration" of hardware or software. A platform can have multiple attributes (like BIOS, browser, carrier, CPU, OS, resolution, etc.)

Q

QMetry Intelligence (QI) - An AI-powered feature that provides smart recommendations, automated insights, and predictive analytics to enhance test management and decision-making.

R

Release - A specific version of the software under test, tracked in QMetry for test execution and reporting.

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

S

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.

T

Test Assets - Test cases, test suites, and test runs that help in planning, executing, and managing software testing activities.

Test Case - A set of steps and conditions used to verify a specific functionality in the application.

Test Execution - The process of running test cases and recording results.

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

Test Suite - A collection of test cases grouped for execution.

Test Run - The execution instance of a test suite with recorded results.


This glossary will be continuously updated to include more QMetry-specific terms and definitions as needed.