Integrations
Connect TestKase with Jira, GitHub, GitLab, or use built-in management for requirements and defects.
Overview
TestKase integrates with your existing tools to keep test management connected with your development workflow. Connect your issue tracker to search issues and link them to test cases, use the Chrome extension for quick access, install the Jira plugin for full test management inside Jira, or use built-in management for a self-contained workflow.
There is a single TestKase Chrome extension that automatically detects whether you are on a Jira, GitHub, or GitLab issue page -- not three separate extensions. Install it once and it works across all three platforms.
A project uses one option at a time, and switching away from Built-in is destructive. Requirement integration and defect integration each hold a single connection, and connecting a new one replaces whatever was configured before. If the option being replaced is Built-in, TestKase permanently deletes that project's requirements and requirement folders (or, on the Defect Integration page, its built-in defects) -- and that is true of every replacement, including the Jira, GitHub and GitLab cards under API Integrations, not just the Plugin and the Extension. Connecting the Jira Plugin or a Chrome Extension card replaces both types at once, so it deletes the other type's built-in data as well. Resetting a Built-in integration deletes the same data. Nothing is migrated and nothing can be recovered, so export anything you need first -- see Built-in.
Where You Configure This
Every option on this page is configured from the same two pages in TestKase: Requirement Integration and Defect Integration. Each page lists four sections and asks you to select any one:
| Section | Cards |
|---|---|
| API Integrations | Jira, GitHub, GitLab |
| Plugin Integrations | Jira Plugin |
| Chrome Extension | Jira, GitHub, GitLab |
| TestKase Built-in | TestKase requirement / defect management |
Built-in is one of the four choices, not the absence of a choice. It is stored the same way an external connection is, which is why it has a Reset action -- and why resetting it deletes the requirements or defects it holds.
An external project can be connected to one TestKase project at a time. Connecting a Jira project, GitHub repository or GitLab project that is already attached to a different TestKase project is refused with "This project is already configured with another testkase project" -- disconnect it there first.
No Background Sync
None of the external integrations run on a schedule. TestKase does not receive webhooks and does not poll your issue tracker:
- Issues are searched live when you open the issue picker on a test case, and returned 10 at a time with pagination.
- Nothing is imported in bulk. You link issues individually, so there is no long-running import to wait for.
- Status is pulled only when you press refresh, and refresh works on the issues linked to the one test case you are looking at.
Platform Integrations
Choose your platform to see all available connection types and setup guides.
Jira
API integration, Forge plugin, and Chrome extension. Jira Cloud only.
GitHub
API integration and Chrome extension for GitHub Issues.
GitLab
API integration and Chrome extension for GitLab Issues on gitlab.com.
Built-in
Manage requirements and defects natively in TestKase without external tools.