This implementation guide walks you through seamlessly implementing QMetry within the organization, aligning with standard QA processes for optimal efficiency.

This documentation is particularly useful for the QMetry administrators, managers and end-users.

Step 1: Organizational Planning and Preparation

As you prepare to implement QMetry in your organization, follow these steps to ensure a smooth setup.

Open

Build your team and chose the right QMetry administrator

Build your team by bringing the right stakeholders on board to utilize QMetry. Users in QMetry can assume one or more roles across different projects within the application. The key roles include:

• Admin: Admin holds complete control over the entire QMetry application, with the ability to assign roles and rights to other users.

• QA Manager: The QA Manager oversees a team of testers and is responsible for managing project related tasks.

• Tester: The Tester role is focused on creating, managing and executing the testing aspects of the project.

The administrator is crucial to the successful implementation of QMetry within your organization. Key qualities to look for in an administrator include:

→ Deep understanding of business processes and organizational structure

→ Strong leadership skills

→ User advocate

→ Analytical approach

Define Your Organization’s Vision

Understand the benefits of implementing QMetry and clarify the objectives you aim to achieve. Engage all key stakeholders in the process and establish clear communication to ensure they understand and align with the process.

Set your Goals and Prioritize them

Establish well-defined goals to create a structured approach for breaking down the testing process into manageable steps. Since different stakeholders have varying objectives, ensure their involvement in the planning process.

• For example:

  • Testers aim to enhance task allocation and streamline test execution.

  • QA Managers seek better visibility into testing activities and access to insightful reports.

  • Admins focus on efficiently managing and controlling processes to ensure compliance with QMetry.

Develop a QMetry Roll out Plan

A phased roll out strategy ensures a smooth implementation of QMetry. Start by introducing essential features that users need for their daily tasks, allowing them to get comfortable with the platform. Additional functionalities can be introduced gradually in later phases for a seamless learning experience.

For example, QMetry implementation can be structured in two phases:

• Phase 1: Core QMetry features for fundamental test management.

• Phase 2: Customizable QMetry apps for enhanced functionality.

Get the Blueprint for Your Test Process

For seamless implementation of QMetry test management, it is very essential to analyze your existing testing workflow.

• Identify key aspects of your organization's business processes.

• Create a visual representation of the test process.

• Define test expectations, test data, assignments, and evaluation criteria.

• Map your business processes to QMetry’s workflow

Understand Key QMetry Terminology

• Requirements: A Requirement is a documented need of what a particular product or service should be or perform. It is a statement that identifies a necessary attribute, capability, characteristic, or quality of a system in order to have value and utility to a user. Requirements show what elements and functions are necessary for the particular project.

• Test Case: A test case is a set of conditions or variables under which a tester will determine whether an application or software system is working correctly or not. It is a specific executable test that examines all aspects including inputs and outputs of a system and then provides a detailed description of the steps that should be taken, the results that should be achieved, and other elements that should be identified. The Test Case module allows you to create Test Cases for manual and automated tests. 

• Test Suite: A Test Suite contains a set of the test cases that should be run together, often in a specific order. A test suite must be executed against a platform.  

• Issue: Issue, in other terms, Defect or Bug, is logged when actual result deviates from the expected result as an outcome of testing activity.

• Test Execution: The Test Execution module in QMetry contains only those test suites which have at least one Release, Cycle and Platform linked with them. QA team can perform Manual Testing and schedule test for Automation Testing.

• 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. 

• Release: Release is the default nomenclature for the second level of scope. The release is most often used to define requirements and test cases needed for an internal and/or external release of software and/or hardware.

• Cycle: It is short form of Test Cycle and is the lowest level of scope.  The cycle is used for test planning and execution.  The results from one cycle do not affect other cycles.

• Build: A build is another term used by organizations for a drop, often it refers to a combination of multiple software and/or hardware builds and/or configurations.

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

• eSignature: If the organization wants to have restricted workflow, the eSignature feature helps them regularize the Approval Workflow of test cases and test executions.   

Create Your Process Overview

Most of the organizations follow the testing process with the following key aspects.

• Requirement Study: Define requirements or specifications in the Requirement module.

• Test Case Design and Implementation: Design test cases and assign them to develop further or to execute. Create test suites from test case itself.

• Test Case Execution: Execute test suites against Platforms that are set as environment and linked to test suites.

• Defect Management: Raise defect against the executions and retest them post closure.

• Test Closure with Report: QMetry provides various reports that sync with the latest application data and produce reports.

The goal of this step is to come up with a visual overview of your test processes. The following is an example of a testing process.

Open

You can discuss the sample process with your product/project team and modify it to suit your organization. If you don't have a defined test process, QMetry implementation is a good time to set one up.

Analyze your Needs

1. Custom Fields and Integrations: Map your testing processes to QMetry by configuring custom fields to align with your workflows. Identify the ideal Requirement and Bug Tracking integration tools for seamless connectivity.

2. Reports and Insights: Leverage QMetry’s system reports to gain valuable insights into test activities and results. Create custom reports tailored to your specific requirements.

Train your Administrator

Administrators play a key role in managing both projects and users within test projects.

Sync the Team

Foster open communication within the team, include all stakeholders to ensure a smooth implementation of QMetry in your organization.

Final Checklist

Tick off each item on the checklist to ensure a seamless implementation.

Step 2: Set Up QMetry Application

Once your team is ready, it's time to explore the tool. Follow below sequence of tasks to get started:

Project Setup

Adding users

User access and permissions

Customization

Importing data

Integration with Jira

Project Set Up

For setting a new project navigate to: Project Management > Projects and follow the below mentioned steps:

1. Add Projects

Create a new project by entering project details and configuring project related settings.

Learn More- Help Document on Managing Projects

2. Define Release/Cycle

3. Define Builds

4. Define Platforms and Platform Attributes

Define Platforms and Platform Attributes based on your testing environment

Learn More- Help Document on Managing Platform

5. Define Labels

Define Labels that would be used to identify test assets or group them.

Learn More - Help Document on Managing Labels

Creating and Adding Users

When setting up QMetry for the first time, the super admin needs to create new users and assign them roles corresponding to their rights and responsibilities

Automatic password is generated for new users (other than LDAP/SAML users) which is then sent to their respective email address. LDAP/SAML users are automatically created after their first login into the QMetry.

Create User has 3 main steps:

• Add User details: It includes user details like Username, Alias, First Name, Last Name, Email, Time zone, Language Preference. 

• Select Authentication Type: 

  • QMetry: QMetry database is the default Authentication Type unless it is changed to LDAP/SAML. So, whenever a user logs into QMetry, the credentials are verified against QMetry database.

  • LDAP/SAML: LDAP/SAML users get created automatically, however in case they are created manually, admin needs to set the Authentication Type as LDAP/SAML and set it to “Active” from Integration > LDAP/SAML. Whenever a user logs into QMetry, the credentials are verified against LDAP/SAML.

• Assign Project and Role: Admin can assign Projects and Roles to the user that is being created.

Learn more: Help Document on QMetry Users

User Access and Permissions 

There are some key components that determine a user's access to data and the operations they can perform within QMetry. You can set user’s Role and Rights from Customization .

1. Understanding User Roles

2. Understanding Rights

Customization

Customization allows you to customize your QMetry's General Settings, Lists, System and Custom fields, Email Notifications and SMTP settings. Below is a quick overview of the settings you can modify under each section:

1. General Settings

   1. Page Limit: Maximum number of records displayed per page.

   2. Login Limit: Maximum incorrect login attempts before a user is locked out of QMetry.

   3. Reactivation after: Time after which a locked-out user gets reactivated in QMetry.

   4. Expiry Time: Password expiry period

   5. Manual Edit of last executed date time: Allowed/Disabled.

2. Execution Status: Default Execution Statuses available in QMetry are:

   1. Blocked

   2. Failed

   3. Not Run

   4. Passed

   5. Not Applicable

3. Custom Fields

4. Lists

5. Notifications

The customization of Notifications is available under: Customization >> Notifications.

Learn More - Help Documentation for customizing notifications.

Customization Tips & Tricks

By default, QMetry includes basic and pre-defined settings as per the industry wide best practices. We recommend that users stick to the default settings available in QMetry unless there is a need to customize the Notification Settings, Fields and Lists for the best experience with QMetry Application.

Jira Integration 

Jira can be configured with QMetry modules as an external system and based on it, users can perform module wise activities. If Jira is configured with QMetry, the Issues module will not be available in QMetry.

• If Jira is configured with the Issue module in QMetry, then users can -

  • link issue with test cases (from Execution screen)

  • create issue from test case run (from Execution screen)

• If Jira is configured with the Requirement module in QMetry, then users can sync Jira stories as requirements in QMetry.

Flow Chart

Open

Resources: Integration of QMetry with Jira

Configure Jira Integration in QMetry

• Install Add on: "JIRA Integration - QMetry Enterprise"

• Configuring JIRA add-on with QMetry Admin

• Enable QMetry Test case and BDD panels for Jira Projects

• Verify the QMetry - Jira Integration is Active

Install Jira Add-on

• The Jira Integration – QMetry Enterprise add-on, which is available on Atlassian Marketplace, should be installed in your Jira Instance. Administrator login is required to be able to install the add-on.

Learn More : Install & Configure QMetry's Jira Integration Add-On

Link QMetry & Jira Project

• To set up Jira Integration - Go to Project Management > Projects.

• Open Project details by clicking the project name.

• Open the Jira Integration tab on the project detail page.

• Select Jira instance from the Jira Integration drop-down on the screen.

• Jira Project: The Jira Project drop-down lists all your Jira projects. Select a project from the list to integrate it with your current QMetry project.

• Once the Project is selected, select Jira Issue Type(s) for QMetry Modules - Requirements and Issues. The Jira issue type is a multi-select list. It is mandatory to map Issue module with at least one Jira Issue Type.

• Click on the Save & Active button to sync the issues.

Learn More: Map Jira projects, Issue type and Fields with QMetry Project

Import Data

This feature allows you to import test assets into QMetry from Excel or Jira. This feature helps you to import bulk of requirements & test cases quickly. 

Import from Excel

QMetry provides Import utility to import test assets in QMetry that are stored in traditional Excel format or comma separated format (CSV).

Import from excel is available for below entities:

• Requirements

• Test Cases

• Issues

Learn More:  Help documentation for Import from Excel

Sync Requirements and Issues from Jira:

QMetry supports integration of Jira. Users can sync Jira issues as requirements and issues in QMetry.

Flow of Import from Jira:

1. Configure Jira within QMetry. Explained above in Jira integration steps.

2. Map Jira projects, Issue Types and fields with QMetry project.

3. Once Jira Issue Type is mapped with QMetry modules, Jira issues are synced into Requirements and Jira Issues are available to link on Execution screen in QMetry.

Learn More: Sync Requirements & Issues

Checklist: Set Up QMetry

In this section, you learned how to define the basic QMetry settings for your company, including the company profile, the organization-wide defaults, and the role hierarchy.

Step 3: Engage 

You've done your due diligence to follow a clear plan, set up and customized QMetry to fit your needs, and scrubbed and added/imported your data. Now it’s time to focus on training your users and driving adoption.

Develop a Training Strategy

The training strategy summarizes the overall plan. It captures business objects, documents key requirements and pain points, identifies challenges, and outlines the types of training as well as the actual training delivery schedule.

By developing a training strategy, you will provide users with clear direction on what is expected and how they’ll use the QMetry Application.

Right before training, you'll need to generate usernames and passwords for everyone who will attend.

• To generate usernames and passwords, admin can add users and assign them roles corresponding to their rights and responsibilities from User Management (Administration >> Users). Automatic password is generated for new users (other than LDAP users) which is then sent to their respective email address. New users have to provide the same username and password on their first login. 

Understand Your Audience

Knowing your audience is critical to the success of training. Different kinds of users will have distinct roles and perform different tasks in QMetry, so it’s important to focus your training based on their roles.

For example, you should train your management or admin team separately from your end users/testers, since they will interact with the application in different ways. This also applies to different lines of business. 

Provide Relevant Content

Your users will be more engaged with the training if it’s relevant to them. Be sure to incorporate scenario-based training using real data so that users walk through examples they face in their daily lives. Start with an audience analysis to make sure you develop the right materials for the right users.

Always keep in mind the burning question that your users will have: “What’s in it for me?” Your curriculum should answer that question. Your materials should match the learning style of your users. The following materials are tried and-true approaches:

• Facilitator guides – Include detailed instructor notes on what to emphasize, details of timing, and so on. Be sure to map these guides to your participant guides.

• Participant guides – Provide end-to-end, detailed training documentation. Interactive, hands-on exercises are a great way to provide realistic training.

• Quick reference cards – Give users something to use when they’re on the job. Use the cards during training for reference and consider publishing them online later.

• Slide shows – Use such presentations to give your users the big picture. And remember: Keep it simple! 

Encourage User Adoption

The key to increasing user adoption is supporting users and being responsive to their needs, tracking usage trends over time, and actively encouraging adoption. Understanding what works and what doesn't is critical, both immediately after going live and over the long term.

Here are some key steps you can take to increase adoption:

1. Support users: Supporting users is an ongoing process. It involves getting user feedback, providing ongoing training, and identifying user champions who'll help their co-workers day to day.

2. Measure adoption: Before you can improve adoption, you have to measure it. The most common measurement of adoption is the login rate, number of test cases created, and executions carried out.

3. Encourage adoption: Create a communication plan to establish an ongoing dialogue about future training sessions, process changes, and upcoming QMetry features.

Step 4: Extend