TestKase Docs
ConfigurationProject Settings

Integrations

Connect your TestKase project to external tools for requirement syncing, defect tracking, notifications, CI/CD, and API access.

Overview

TestKase integrates with a range of external tools to streamline your testing workflow. Integrations are configured at the project level, meaning each project can have its own set of connected services. This page serves as a central hub linking to the detailed integration guides located alongside the features they enhance.

Requirement Integration

Sync requirements from your issue tracker directly into TestKase. Linked requirements stay connected to their source for traceability.

  • Jira Integration — Connect Jira Cloud to import and sync requirements from Jira issues.
  • GitHub Integration — Import GitHub issues as requirements and maintain traceability.
  • GitLab Integration — Import GitLab issues as requirements with bidirectional linking.

Requirement integrations are configured from SettingsJira Integration (or GitHub/GitLab) within your project. You need Project Admin or Owner permissions to set up integrations.

Defect Integration

Push defects discovered during testing directly to your issue tracker, or import existing issues as defects in TestKase.

Notification Integration

Receive real-time notifications about test execution events, defect updates, and other project activities in your team's communication channels.

  • Webhook Integration — Set up webhooks for Slack, Discord, Microsoft Teams, Google Chat, or custom HTTP endpoints.

CI/CD Integration

Automatically report test results from your CI/CD pipelines into TestKase test cycles. Supports 15+ test frameworks and 5 CI/CD platforms.

  • Automation — Configure the @testkase/reporter CLI to push automated test results from Jenkins, GitHub Actions, GitLab CI, CircleCI, and more.

API Keys

Generate Personal Access Tokens (PATs) for API access and CI/CD authentication.

  • API Keys — Create and manage API keys for programmatic access to TestKase.

API keys are generated per user but managed at the organization level. You need them for CI/CD integration setup and for building custom integrations with the TestKase REST API.