TestKase GitHub Chrome Extension: Complete Setup & Feature Guide
TestKase GitHub Chrome Extension: Complete Setup & Feature Guide
TestKase is the first test management tool to offer a dedicated Chrome extension for GitHub. Instead of switching between your issue tracker and your test management platform, you can now manage test cases, test cycles, and test execution directly from a browser side panel — without ever leaving your GitHub issues.
This guide covers everything you need to know: installation, setup, features, and best practices.
Why a Chrome Extension for GitHub?
Development teams that use GitHub for issue tracking face a common problem: test management lives in a separate tool. Every time a developer files an issue or a QA engineer needs to verify test coverage, they switch tabs, lose context, and waste time navigating between platforms.
The TestKase Chrome Extension eliminates this friction. It adds a side panel to your browser that appears alongside any GitHub issue. You see the issue on the left and your test cases on the right — in the same window, at the same time.
Industry first
TestKase is the first test management tool to provide a Chrome extension specifically for GitHub issue-to-test-case workflows. No other TMT offers this level of browser-native integration.
Installation
Step 1: Install from Chrome Web Store
- Open the Chrome Web Store
- Search for "TestKase"
- Click "Add to Chrome"
- The TestKase icon appears in your browser toolbar
The extension requires three permissions:
- activeTab — to detect when you're on a GitHub issue page
- storage — to save your PAT and project mappings
- sidePanel — to render the test management interface
Step 2: Enter Your Personal Access Token (PAT)
When you first click the TestKase icon, the extension prompts you for a Personal Access Token:
- Log in to app.testkase.com
- Go to My Profile → API Keys
- Click Generate New Key
- Copy the token (starts with
xyz_) - Paste it into the extension and click Save & Continue
Your PAT is stored securely in Chrome's extension storage (encrypted by the browser) and is only sent to TestKase API servers over HTTPS.
Step 3: Map Your GitHub Repository
Navigate to any GitHub issue. The extension detects the repository and prompts you to map it to a TestKase project:
- Select your TestKase organization
- Choose the project that corresponds to this repository
- The mapping is saved — you won't be asked again for this repo
Pro tip
You can map multiple GitHub repositories to different TestKase projects. Each mapping is remembered independently, so you can work across repos seamlessly.
Step 4: Start Using the Side Panel
Click the TestKase icon on any GitHub issue page. The side panel opens on the right side of your browser, showing:
- Linked Test Cases — test cases mapped to this specific GitHub issue
- Test Cycles — cycles that contain test cases linked to this issue
- Action buttons — Create, Link, and AI Generate
Feature Walkthrough
Creating Test Cases
Click "+ Create Testcases" to open the creation modal. You can fill in:
- Title (required)
- Summary / Description
- Preconditions
- Test Data
- Expected Result
- Priority (Critical, High, Medium, Low)
- Status (Draft, Active, Deprecated)
- Labels and Features
- Environment
- Folder — organize into your project's folder hierarchy
- Owner — assign to a team member
- Test Steps — add step-by-step instructions with expected results
The test case is created in your TestKase project and automatically linked to the current GitHub issue.
AI-Powered Test Case Generation
Click "Generate Testcase" to let AI analyze the GitHub issue context and generate test cases automatically:
- The AI reads the issue title, description, and labels
- Choose which fields to include (title, summary, precondition, test data, expected result, priority)
- Select the number of test cases to generate
- Review the generated test cases — expand, edit, or remove individual ones
- Select a target folder and click create
AI usage
AI generation uses your organization's AI credits. Credit usage is tracked and visible in the TestKase dashboard. Contact your admin if AI features are disabled.
Linking Existing Test Cases
Click "Link Testcases with Issue" to browse your TestKase project library:
- Navigate through your folder hierarchy
- Search by test case ID or title
- Select multiple test cases
- Click Link to map them to the current GitHub issue
Once linked, test cases appear in the "Linked Testcases" table on the side panel. You can unlink them at any time.
Test Cycle Management
The bottom section of the side panel shows Test Cycles linked to the current issue:
- Create Cycle — create a new test cycle with a name and description
- Link Testcase with Cycle — add test cases to a selected cycle
- Add All — bulk-add all linked test cases to a cycle
- Search — find cycles by ID or title
- Progress tracking — visual progress bars showing pass/fail/blocked/not-executed ratios
Test Execution
Click the Execute button on any test cycle to enter execution mode:
- Navigate through test cases with previous/next controls
- View test steps, preconditions, and expected results
- Set execution status: Pass, Fail, Blocked, or Not Executed
- Add comments and notes
- Upload evidence attachments (screenshots, logs, documents)
- See real-time execution summary and progress percentage
Attachments and Evidence
You can upload files to both test cases and test executions:
- Supported formats — images (PNG, JPG), documents (PDF, DOCX), spreadsheets (XLSX, CSV), videos (MP4)
- Drag-and-drop or click to upload
- Files are stored securely via presigned S3 URLs
- View, download, or delete attachments from the side panel
Features Available Today vs Coming Soon
Security and Privacy
The Chrome Extension is designed with security as a priority:
- HTTPS only — all API calls use TLS encryption
- No data collection — the extension doesn't collect analytics or usage data
- Secure token storage — your PAT is stored in Chrome's encrypted extension storage, never in localStorage
- Minimal permissions — only
activeTab,storage, andsidePanel— no broad browsing data access - Content Security Policy — explicit CSP prevents script injection attacks
- Auto-cleanup — your PAT is automatically cleared if it expires or returns a 401 error
Troubleshooting
Extension doesn't detect the GitHub issue
Make sure you're on a GitHub issue page (URL pattern: github.com/{owner}/{repo}/issues/{number}). The extension only activates on issue pages, not on pull requests, discussions, or repository home pages.
"Project Not Configured" error
This means the GitHub repository hasn't been mapped to a TestKase project yet. Click Refresh and follow the mapping flow to connect your repo.
PAT expired
If you see a "PAT expired" screen, generate a new token from app.testkase.com/api-keys and enter it in the extension.
AI generation is disabled
AI features require your organization to have AI credits enabled. Contact your TestKase admin to enable AI features from the organization settings.
Getting Started
- Install the extension from the Chrome Web Store
- Enter your TestKase PAT
- Navigate to any GitHub issue and click the TestKase icon
- Start creating and managing test cases from the side panel
Stay up to date with TestKase
Get the latest articles on test management, QA best practices, and product updates delivered to your inbox.
SubscribeShare this article
Related Articles
Why Most Test Management Tools Are Overpriced and Outdated in 2026
Legacy test management tools charge $30-50/user/month for decade-old UIs with no AI. Learn why QA teams are switching to modern, affordable alternatives like TestKase — starting free.
Read more →TestKase MCP Server: The First AI-Native Test Management Platform
TestKase ships the first MCP server for test management — connect Claude, Cursor, GitHub Copilot, and any AI agent to manage test cases, cycles, and reports.
Read more →The Complete Guide to Test Management in 2026
Master test management with this in-depth guide covering planning, execution, metrics, tool selection, and modern best practices for QA teams of every size.
Read more →