GitLab
Two ways to connect TestKase with GitLab -- API integration for requirement sync and defect push, and Chrome Extension for browser-based access.
Overview
TestKase offers two connection types for GitLab, each designed for different workflows. The API integration provides server-side requirement sync and defect push between TestKase and GitLab Issues, while the Chrome Extension gives your team a lightweight browser side panel for managing test cases, executing tests, and pushing defects directly from any GitLab page.
API Integration
Server-side sync for requirements and defects between TestKase and GitLab Issues
Chrome Extension
Browser side panel for test management from any GitLab page
Real-time sync
GitLab issues imported and kept in sync as requirements
Defect push
Create GitLab issues directly from TestKase defects
Bidirectional sync
Status, labels, and comments stay synchronized
Self-hosted support
API integration works with self-hosted GitLab instances
Connection Types at a Glance
| Feature | API Integration | Chrome Extension |
|---|---|---|
| Where configured | TestKase Settings | Install Chrome extension, login with PAT |
| Covers requirements | Yes (one-way sync) | Yes (automatic) |
| Covers defects | Yes (push to GitLab) | Yes (automatic) |
| Scope per setup | Requirements OR defects separately | Both together |
| Test case management | In TestKase only | Browser side panel |
| AI test generation | In TestKase only | From side panel |
| Test execution | In TestKase only | From side panel |
| Self-hosted support | Yes (any instance URL) | gitlab.com only |
| Best for | Teams managing tests in TestKase | Quick access from any GitLab page |
Which Should I Use?
- API Integration -- Best when your team primarily works inside TestKase and needs GitLab issues synced as requirements or defects pushed back to GitLab. This approach requires a Personal Access Token with
apiscope and supports both gitlab.com and self-hosted GitLab instances via a configurable instance URL. - Chrome Extension -- Best for team members who spend most of their time in GitLab and want to manage test cases, run executions, and push defects without leaving the browser. Install once, authenticate with a PAT, and access TestKase from a side panel on any gitlab.com page.
If your team uses a self-hosted GitLab instance, the API integration is the recommended starting point since it supports custom instance URLs. The Chrome Extension currently works with gitlab.com.
Using Both Connection Types
The two connection types complement each other and can be used simultaneously on the same project:
- Set up the API Integration in TestKase Settings to keep requirements and defects in sync automatically. This is especially useful for self-hosted GitLab instances.
- Install the Chrome Extension for team members who prefer to manage test cases and execute tests directly from gitlab.com.
All changes made through either connection type are reflected in TestKase, so your test data stays consistent regardless of which integration your team uses.