Cloud Services

DevOps Intelligence

QMetry configuration and user documentation
Published On Nov 05, 2024 - 1:34 PM

QMetry configuration and user documentation

Learn about how to configure QMetry and use it to collect and observe test data in DevOps Intelligence.
The setup for DevOps integration with QMetry, requires several procedures, most of which are in DevOps Intelligence, but the initial procedure requires access to the QMetry console. Further, the following prerequisites are required:
  • QMetry Account:
     The administrator should have an active QMetry account on the specific QMetry instance user want to connect to. If user don't have one, user need to sign up for a QMetry account.
  • Access to a QMetry Instance:
     Ensure that User have access to the specific QMetry instance where the projects, test suites and test cases are hosted. Users need the URL or web address of the QMetry instance user want to connect to.
  • Project Membership:
     Users must be part of the QMetry projects user intend to access. Ensure that users have the necessary project membership to retrieve information about projects, test suites and test cases.
  • Access Policy as Platform Administrator and DevOps Intelligence Administrator:
     Ensure that the user has the necessary access policies.The user should have the Platform Administrator role to create and manage connections effectively. The user needs the DevOps Intelligence Administrator role, which allows them to create and manage configurations.
Review and execute the content in the following sections in the order they are presented.

Create a QMetry API token

In order to establish a connection, the first configuration procedure, you must first acquire a QMetry API token, which is available only from the QMetry console. Use the following procedure:
  1. Navigate to the sub menu "Open API" from the "Integrations" menu on the left hand side of the page. QMetry will automatically generate an API token.
  2. Click the Copy API Key icon to copy the existing key.

Create a DevOps Intelligence connection to QMetry

Establishing a DevOps Intelligence connection to QMetry is prerequisite to configuring the service. Use the following procedure:
  1. Click on
    Settings
     →
    Service IAM
     →
    Connections
     →
    Add New
     →
    Add connection
    .
  2. Choose
    Platfrom
     from the connection type dropdown list.
  3. Select
    QMetry
    .
  4. Provide a local account name for reference.
  5. Add the Host QMetry API URL of the QMetry Host (e.g.,
    https://testmanagement.qmetry.com/
    ).
  6. Paste the API KEY created in the previous section,
    Create a QMetry API token
    .

Configuring QMetry

Having established a connection, you must complete the configuration procedure. Take note of the following caveats:
  • QMetry tool can only be configured at the project level.
  • Multiple Test Suites can be selected against projects.
  • Test Suites are just a way to restrict what all data user needs for a given project.
  • QMetry will only sync data available with connection configured against it.
  • At the project level, technical services are always configured as mutually exclusive.
  • If two users having same privileges tries to onboard the technical service for the same project only the first user can create the technical service. It will not be listed for the second user to onboard.
Use the following procedure to complete the configuration:
  1. Navigate to DevOps Intelligence → Settings & Utilities → Application Configurations.
  2. Select an existing application or create a new application.
  3. Navigate to "Add Tools" step.
  4. Select the phase as
    Test
    .
  5. Click
    Add Tool Configuration
    .
  6. From
    Tool engine
    , select
    QMetry
    .
  7. Map your execution status to four levels. Passed, Failed, Skipped and Blocked.
  8. Select the respective statuses into the respective categories.
  9. Click
    Add Configuration.
The presented practice is for organizations that were onboarded before 6 June 2024. If your organization was onboarded on 6 June 2024 or after, you are subject to a new process driven by a new onboarding mechanism.The configuration mechanisms that require these processes are in a transition phase driven by the fact that each tool must be individually adapted for the new mechanism, which is more efficient than the legacy mechanism. Both processes are supported until the transition of all supported tools from the old mechanism to the new mechanism is complete.
Click the following link to review the procedure for the new mechanism: Application configuration: recent customers

Edit Configuration

Use the following procedure to edit the configuration:
  1. Click on overflow menu and select "Edit" option to edit the tool.
  2. Modify the execution status.
  3. Click
    Save Configuration
    .

Click Delete Configuration

Use the following procedure to delete the current configuration.
  1. Click on overflow menu and select "Delete" option to delete the tool.
  2. Click Delete on the confirmation modal to proceed to delete.

Onboarding the QMetry technical service

After configuring DevOps for QMetry, you must onboard it as a technical service. Note the following caveats:
  • QMetry tool can only be configured at project level.
  • Multiple Test Suites can be selected against projects.
  • Test Suites are just way to restrict what all data user needs for a given project.
  • It will only sync data available with connection configured against it.
  • At project level, technical services are always configured as mutually exclusive.
  • If two users having same privileges tries to onboard technical service for the same project only the first user is allowed to create the technical service, as the project is already on-boarded, it will not be listed for the second user to onboard.
Use the following procedure:
  1. Navigate to DevOps Intelligence -> Settings & Utilities -> Application Configurations.
  2. Click on Overflow menu for the chosen application and click
    Onboard Technical Service
    .
DevOps Intelligence displays all the phases for which the tool has been configured for the application. - Select the phase as Test. - Select the tool engine as QMetry. - Connection - select connection name from the dropdown menu.

Deleting the QMetry technical service

The administrator may, at will, delete the QMetry technical service. Use the following procedure:
  1. Navigate to DevOps Intelligence → Settings & Utilities → Application Configurations.
  2. Expand the application to see all the associated phases.
  3. Click the Overflow menu associated with the Test phase
  4. Click
    Delete Technical Service
    .

Reviewing test suite data in DI

After DevOps Intelligence has been fully configured, DevOps Intelligence displays all test suites being tracked by QMetry in the table view at the bottom of the Test page. The view provides general information about each test suite such as status (how many tests were Skipped, Passed, Failed, and Blocked), Total number of tests in the suite, and the execution date.
Detailed information about each suite are available by clicking the overflow menu for that test suite and selecting
View Details
. DevOps Intelligence responds by navigating to the Details page for that suite, where additional information regarding activity and history is available. The Activity tab presents a graphic presentation of the tabular data on the table. The Historical details tab presents additional details such as Code Smells and Bugs. On both tabs you have the option of selecting a time frame for testing from the Duration control located in the upper right.
Do you have two minutes for a quick survey?
Take Survey