GitHub
Two ways to connect TestKase with GitHub -- API integration for requirement sync and defect push, and Chrome Extension for browser-based access.
Overview
TestKase offers two connection types for GitHub, each tailored to different workflows. The API integration provides server-side requirement sync and defect push between TestKase and GitHub 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 GitHub page.
API Integration
Server-side sync for requirements and defects between TestKase and GitHub Issues
Chrome Extension
Browser side panel for test management from any GitHub page
Real-time sync
GitHub issues imported and kept in sync as requirements
Defect push
Create GitHub issues directly from TestKase defects
Bidirectional sync
Status, labels, and comments stay synchronized
Full traceability
End-to-end coverage from backlog through test execution
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 GitHub) | 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 |
| 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 GitHub issues synced as requirements or defects pushed back to GitHub. This approach requires a Personal Access Token with
reposcope and is configured once per project in TestKase Settings. - Chrome Extension -- Best for team members who spend most of their time in GitHub 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 GitHub page.
If you are unsure, start with the API Integration for requirement sync and defect push. Add the Chrome Extension later for team members who want to work directly from GitHub.
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.
- Install the Chrome Extension for team members who prefer to manage test cases and execute tests directly from GitHub.
All changes made through either connection type are reflected in TestKase, so your test data stays consistent regardless of which integration your team uses.