techlist.io
KREN
gitlab

Streamline test management with SmartBear QMetry GitLab component (opens in new tab)

aigitlabci-cddevsecopsapiautomationtest-managementqmetry

The SmartBear QMetry GitLab Component automates the transfer of test results from GitLab CI/CD pipelines into QMetry Test Management Enterprise. By publishing JUnit, TestNG, and other supported results automatically, it removes manual uploads and provides a centralized, traceable view of testing. The integration helps teams accelerate release decisions while supporting compliance and audit requirements.

Why Integrate GitLab with QMetry?

  • Eliminate manual uploads: Test results are transferred automatically after pipeline execution, reducing effort and preventing outdated or inconsistent records.
  • Improve traceability: Teams can connect requirements, test cases, executions, commits, builds, and pipelines in a single audit trail.
  • Accelerate feedback: QA teams, product managers, and stakeholders gain access to results immediately after tests finish.
  • Support regulated development: Centralized, versioned test records help organizations in aerospace, financial services, automotive, and medical-device industries demonstrate test coverage and compliance.
  • Enable AI-driven insights: QMetry can analyze execution history to identify flaky tests, predict failures, and suggest optimization opportunities.

GitLab–SmartBear Integration

  • The component is part of a broader partnership connecting GitLab’s CI/CD and DevSecOps capabilities with SmartBear’s testing and quality-management tools.
  • The integration is intended for organizations that need centralized visibility across complex or regulated software-development lifecycles.
  • QMetry acts as the system of record for test planning, execution, tracking, and reporting.

Requirements and Test Result Flow

Before configuring the integration, teams need:

  • A GitLab project with automated tests that generate JUnit XML, TestNG XML, or another supported format.
  • A QMetry Test Management Enterprise account with API access enabled.
  • A QMetry API key with permission to upload test results.
  • An existing QMetry project.
  • Basic knowledge of GitLab CI/CD and .gitlab-ci.yml.
  • Optionally, a configured QMetry test suite for better organization.

The automated flow is:

  • GitLab runs unit, integration, end-to-end, or other automated tests.
  • The tests generate result files.
  • The QMetry component runs as a pipeline job.
  • It reads the result files and uploads them to QMetry through the API.
  • QMetry processes the results for reporting and analysis.

Obtaining QMetry API Credentials

  • Log in to QMetry Test Management Enterprise.
  • Open the user profile and navigate to Settings or API Access.
  • Generate a named API key, such as GitLab CI/CD Integration.
  • Grant the key write access for test-result uploads.
  • Copy the key immediately because it is displayed only once.
  • Record the QMetry instance URL, typically in the form https://your-company.qmetry.com.

The API key should be treated like a password. It should not be committed to .gitlab-ci.yml or stored in plain text; GitLab CI/CD variables should be used to protect it.

The component provides a practical way to make QMetry the centralized source of truth for pipeline testing. Organizations should secure the API credentials, configure the component in their GitLab pipeline, and continuously publish results so teams can improve visibility, traceability, and release confidence.