Qase Docs
Help CenterAPI DocsRoadmapSign up for free
  • General
    • Qase docs
    • Get started with the Qase platform
      • Account settings
      • Projects
      • Test suites
      • Test cases
        • Test Case Parameters
        • Test case review
        • Shared steps
        • Import test cases
        • Export test cases
        • Trash bin
        • Muted Tests
        • System fields
        • Nested steps
        • Test case actions
        • Filters
      • Requirements Traceability Report
      • AI Test Case Generator
    • Execute testing
      • Test plan
      • Test runs
      • Configurations
      • Environments
    • Issues tracking
      • Defects
      • Milestones
      • Requirements
    • Analytics
      • Dashboards
      • Queries (QQL, Qase Query Language)
      • Saved queries
    • Webhooks
      • Test Case
      • Test suite
      • Test plan
      • Shared step
      • Milestone
      • Custom field
      • Test run
      • Defect
      • Test review
  • AIDEN
    • AIDEN - QA Architect
  • Guide: Action editor
  • Administration
    • Workspace management
      • Users
      • Invites
      • Groups
      • Roles
      • Fields
      • Custom fields
      • Notifications
      • Tags
      • Attachments
      • Audit logs
      • Hotkeys
    • SSO / SAML instructions
      • AzureAD
      • OneLogin
      • Google Workspace
      • Okta
      • JumpCloud
    • SCIM
      • User lifecycle management with SCIM
      • Enable SCIM
      • Users
      • Discovery features
      • Errors
    • Security
      • SOC 2 Type II / SOC 3
      • ISO/IEC 27001:2022
      • Penetration testing report
      • Subprocessors
      • Qase IP addresses
    • Billing
      • Billing options
    • Subscriptions
      • Free plan
      • Startup plan
      • Business plan
      • Enterprise plan
  • Apps
    • Issue tracking
      • Jira Cloud
      • Jira Server/Datacenter Plugin installation
      • GitHub
      • Asana
      • Linear
      • Monday
      • ClickUp
      • Trello
      • Azure DevOps
      • GitLab
      • YouTrack
      • Redmine
    • CI/CD
      • Jenkins
      • BitBucket
      • GitHub CI
      • GitLab CI
    • Chats
      • Slack
  • Automation
    • Qase API
    • Reporters
      • JavaScript
        • Playwright
        • Cypress
        • Mocha
        • Newman
        • Jest
        • WebDriverIO
        • CucumberJS
        • TestCafe
      • Python
        • Pytest
        • Robot Framework
        • Behave
        • Tavern
      • Java
        • TestNG
        • JUnit 4
        • JUnit 5
        • Cucumber 3 (jvm)
        • Cucumber 4 (jvm)
        • Cucumber 5 (jvm)
        • Cucumber 6 (jvm)
        • Cucumber 7 (jvm)
      • PHP
        • PHPUnit
        • Codeception
      • Kotlin
        • Kaspresso
    • Qase CLI App
      • XCTest
Powered by GitBook
On this page
  • What is GitLab?
  • Installation
  • Usage
  • Linking your Qase Test cases
  • Linking your Qase Test runs
  • Linking your Qase Defects
  • Create a GitLab issue from a Qase Test Run
  1. Apps
  2. Issue tracking

GitLab

PreviousAzure DevOpsNextYouTrack

Last updated 11 days ago

What is GitLab?

is a web-based DevOps lifecycle tool that provides a Git repository manager providing wiki, issue-tracking, and CI/CD pipeline features.

With Qase’s GitLab integration, you can:

Installation

For installation, you will require GitLab URL and the Access token.

  1. First, sign-in to your GitLab account and navigate to the Preferences from the profile menu:

  1. Go to the Access tokens page:

  1. To create a new Personal Access Token, select the scope api and click on the Create Personal Access token:

  1. Copy your token to clipboard.

Here, provide the Access token from the previous step, and URL of your GitLab instance (the field is pre-populated with the default value)

  1. Click the Install button. After a few seconds, you will be redirected to the Apps page with a confirmation message as shown below.

Please note, a Maintainer role is required if you choose to use a Group token

Usage


Linking your Qase Test cases

In your repository, click any test case to open its preview and switch to the Properties tab.

Scroll down to the "Link with Apps" section, and choose the GitLab app. Then, proceed to search and link your issues.

Linked issues can be removed with the ( x ) icon.

2. To unlink the GitLab issue, click "x" next to the card title:

Linking your Qase Test runs

Test runs can be linked to a GitLab issue, from the Run Dashboard.

Under the "External Issues" section, click 'Select an Integration' to proceed. Only one GitLab issue can be linked to the Test run.

Linking your Qase Defects

Defects can be linked to a GitLab issue, from the Defect Dashboard.

Under the "External Issues" section, select the GitLab app to proceed.

Create a GitLab issue from a Qase Test Run

When you assign a negative result to a case during a test run, you will have the option to create or attach a Qase defect.

Additionally, you can select the ‘GitLab’ app from the "Choose Integration" dropdown to either create a new GitLab issue, or link an existing one.

The created or linked issue will be visible in both the defects tab of the test run and the defect section of the project.

  • You can view the link to the GitLab issue in

    • Defects tag of the test run

  • From the Qase defect screen

Link Qase , , and to GitLab issues.

Create a new issue in GitLab when you file a defect and their statuses are automatically synchronized, in both directions. [Qase <> GitLab].

in GitLab from a Qase.

On Qase, navigate to the section, find the GitLab app and click Install now.

test cases
test runs
defects
Execute automated runs
Apps
GitLab
during a test run in Qase