GitHub
Two ways to connect TestKase with GitHub -- API integration for searching and linking GitHub Issues, and Chrome Extension for browser-based access.
Overview
TestKase offers two connection types for GitHub, each tailored to different workflows. The API integration lets you search GitHub Issues from TestKase and link them to test cases, while the Chrome Extension gives your team a lightweight browser side panel for managing test cases and executing tests directly from any GitHub issue page. A TestKase project uses one of them at a time.
API Integration
Search GitHub Issues from TestKase and link them to test cases as requirements
Chrome Extension
Browser side panel for test management from any GitHub page
On-demand refresh
Pull the latest GitHub issue state into TestKase when you refresh -- there is no background sync
Coverage comments
Linking a test case posts a comment on the GitHub issue so developers see coverage
Search and link
Search your GitHub issues live and link them to test cases as requirements
Full traceability
End-to-end coverage from backlog through test execution
Connection Types at a Glance
| Feature | API Integration | Chrome Extension |
|---|---|---|
| Where configured | GitHub card under API Integrations on the Requirement Integration page | GitHub card under Chrome Extension, plus install the extension and log in with a PAT |
| Covers requirements | Yes (one-way sync) | Yes (automatic) |
| Covers defects | Push to GitHub not yet available -- link existing issues only | Configuration covers both types; no defect UI in the panel |
| 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 |
| Best for | Teams managing tests in TestKase | Quick access from any GitHub page |
Which Should I Use?
- API Integration -- Best when your team primarily works inside TestKase and needs to search GitHub issues and link them to test cases. This approach requires a GitHub Personal Access Token (classic) with the
reposcope -- plusread:orgif the repository is owned by an organization -- and is configured once per project on the Requirement Integration page. - Chrome Extension -- Best for team members who spend most of their time in GitHub and want to manage test cases and run executions without leaving the browser. Install once, authenticate with a TestKase PAT, and access TestKase from a side panel on any GitHub issue page.
If you are unsure, start with the API Integration for searching and linking GitHub issues. You can change to the Chrome Extension later, but it replaces the API configuration rather than adding to it -- see below.
Choosing One Connection Type
A TestKase project uses one connection type at a time. Selecting API Integration, Chrome Extension or Built-in on the Requirement Integration page replaces whatever was configured before -- TestKase warns you before it does.
The API Integration is configured separately for requirements and for defects. The Chrome Extension always covers both types with a single configuration, so connecting it also replaces the other type's setup.
Each surface only recognises projects connected through its own card. A repository connected through the GitHub card under API Integrations is invisible to the Extension, and vice versa.
Switching is destructive when the option you replace is Built-in. Connecting either option -- the API Integration or the Chrome Extension -- to a project whose requirement integration is Built-in permanently deletes that project's requirements and requirement folders; on the Defect Integration page it deletes the project's built-in defects. The Extension covers both types at once, so it deletes the other type's built-in data too. Nothing is migrated to GitHub and nothing can be recovered. See Built-in before you switch.