Quick Start

  • Introduction

  • Test Authoring

    • Define self-sufficient, modular, reusable Test Cases

    • Organizing Test Case library

    • Using Custom fields

    • Version controlling

    • Data Parameters

  • Test Planning

    • Defining Test Plan

    • Tracking Execution Progress on Test Plan

    • Organizing Test Plans

  • Test Execution

    • Test Cycle

    • Define Custom Status

  • Tracking the Testing Progress

  • Automation

    • Automation API/Maven/Jenkins

    • Reusability

    • Automation Reports

    • Open API

  • Configuration

  • Project Permissions

  • Enable QMetry in a Project

  • Enabling Jira issues as Story and Defect

Introduction

QMetry Test Management for Jira has been designed for Agile Development & Testing teams. The goal is to bring together the teams and help them collaborate. This document highlights how agile teams with diversified and specialized roles can come together and make great software products.

Relationship between QMetry Test Management and Jira.

The extensive integration between QMetry Test Management and Jira provides users to use one platform to manage the testing processes along with the development process.

Enabling Jira issues as Story and Defect

A Project admin can decide the issue type of Jira that should be considered as a Story or a Bug. Generally, all your requirement issue types such as Story, Epic, Task should be considered as Story, and defect issue types such as Bug should be considered as Bug. Other than Jira custom issue types, custom issue types can also be enabled as Story or Bug.

Publication date: