Integrations
Integrations for every tool in your stack.
Link defects and requirements to test cases in Jira, GitHub, GitLab, Azure DevOps and Linear. Sign in through your own identity provider. Push automation results in from CI. Let your AI assistant drive the whole thing over MCP.
21-day free trial · No credit card required
Easily integrates with the tools you already use
Testiny was designed to fit the development and project management workflow you already have. With over 25 integrations and a robust REST API, your team keeps its preferred tools and gets proper test management on top – not a second place to do the same work twice.
Integrate with issue trackers
Effortless synchronization across leading development platforms such as Jira, GitLab, GitHub, Linear, Azure DevOps and more, so defects and requirements stay linked to the tests that found them.
Cloud & Data Center Jira
Enhance Jira with Testiny's test management: a two-way integration for issue tracking and bi-directional communication, with a straightforward, license-free setup. Works with Jira Cloud and Jira Data Center.
Jira integration
Issues & pipelines GitLab
Streamline your GitLab projects and test management: effortless issue management, automated CI/CD pipeline integration, and better visibility of what a pipeline actually verified.
GitLab integration
Issues & Actions GitHub
Maximize your GitHub workflow efficiency with direct issue linking, in-app issue creation from a failed result, and results collected straight out of GitHub Actions.
GitHub integration
Boards & Pipelines Azure DevOps
Enhance your Azure DevOps test management experience with easy work item linking and creation, and Azure Pipelines feeding automation results back into Testiny.
Azure DevOps integration
Self-hosted Redmine
Efficiently manage Redmine projects with Testiny's integration, covering issue linking, creation and tracking alongside your test cases.
See documentation for Redmine
Issues Linear
Boost your team's productivity with test management for Linear: issue creation, linking, and status updates that show up inside Testiny.
See documentation for LinearPlus 13 more issue trackers below – see the full list ↓
Linked items
Defects and requirements, linked to the tests that found them.
Attach requirements and defects to test cases and to individual results. Create a new ticket from a failure without leaving the run, and see the tracker's own status on the link, inside Testiny.
- Create defects from a failure.
- Raise the ticket in your tracker straight from the result, already linked to the test case that produced it.
- Live status on the link.
- The issue's current status is shown inside Testiny, so you can tell at a glance whether a known defect is still open.
Setup
Connect it once, and connect it more than once.
Testiny supports several integrations of the same type at the same time, each with its own configuration and its own project mapping. A Jira Cloud site, a Linear workspace and a GitHub org side by side is a normal setup, not a workaround.
- OAuth 2.0 by default on Jira Cloud.
- API-token auth is legacy; a token-based integration can be upgraded to OAuth in place, keeping project mapping and every existing issue link.
- Shared or personal accounts on Jira Cloud.
- Combine both: issues can be created under a shared integration account or as the actual user. Look-up and linking always run through the shared account.
- Your Atlassian app, if you prefer.
- Use Testiny's built-in OAuth app or register your own. Jira Server and Data Center authenticate with a personal access token.
All issue-tracker integrations
Link your favorite issue tracker with Testiny — and if it is not on the list, the custom integration handles it with URL templates.
Asana 
Confluence 
Trello 
Todoist 
ZenDesk 
Wrike 
Trac 
monday.com 
Zoho 
Basecamp 
YouTrack 
Clickup 
Bugzilla 
Shortcut 
Pivotal Tracker 
Custom 
REST API The custom integration links any tool that has an addressable URL for an issue, using URL templates you define. Anything beyond that – including Notion – is covered by the REST API.
Single sign-on providers
Let your identity provider handle who gets in. Users sign in once and land in Testiny with the account your directory already manages.
Microsoft Entra ID 
Google Cloud Identity 
Okta Workforce Identity 
Auth0 by Okta 
Amazon Cognito 
Salesforce Identity JC JumpCloud True SSO 
OneLogin by One Identity 
Any OIDC provider Testiny speaks generic OpenID Connect, so a provider that is not on this list works the same way as one that is.
SSO needs the Business plan or higher. On free plans, accounts sign in with email and password. Once SSO is set up you can require it per user, and administrators can reset a user's SSO authentication data when someone changes identity provider or loses access.
Notifications and webhooks, pushed to your team chat
Organization-wide notification channels push Testiny events into Slack, Teams, Discord, Google Chat, or any custom webhook URL – so the people who care hear about a closed run where they already talk.
Notifications
Three events, five frequencies, per project.
Channels are configured once for the organization by an administrator, then every project can override how often it speaks up.
- Events.
- A test case is assigned to someone, a test run is closed, or a comment lands on a test run.
- Frequency.
- Never, Immediate, Shortly, Hourly or Daily — an organization default with a per-project override where a noisy project needs a quieter channel.
Automation results, from whatever runs them
Your pipeline runs the tests. Testiny imports the results, links them to test cases and requirements, and keeps them next to the manual runs instead of in a separate report nobody opens.
Test frameworks
Documented reporters and result formats, with a dedicated Playwright reporter and JUnit XML for everything that speaks it.
CI/CD providers
The CLI auto-collects the CI environment variables it finds, so a build knows which branch, commit and pipeline a result came from without you wiring it up.
# run your suite however you already run it
PLAYWRIGHT_JUNIT_OUTPUT_FILE=results.xml npx playwright test \
--reporter=junit
# hand the results to Testiny
TESTINY_API_KEY=**** npx @testiny/cli automation \
--project ID_OR_KEY \
--source "e2e-nightly" \
--junit results.xml \
--field-values "environment=staging" Testiny does not run your tests. It imports, manages, links and analyses the results your pipeline produces. Automation
sources are created automatically the first time a name is used and are scoped per project, and --field-values adds your own custom fields to an import. For anything a built-in connector does not cover there
is a full REST API and scoped API keys.
More about test automation → Testiny CLI docs → REST API quickstart →
AI-powered test management with the MCP server
Connect AI tools like Claude Desktop and VS Code Copilot straight to Testiny over the MCP (Model Context Protocol) server, and let them read and write your test data through the same API everything else uses.
Discovery
listProjects listTestCaseFolders listTestCases listTestRuns Test cases & folders
createFolder editFolder moveFolder createTestCase editTestCase moveTestCases Test execution
createTestRun setTestResult setTestResultBatch getTestStatus addTestResultComment "Create a Sprint 24 regression test run in the Mobile App project and execute test case TC-123"
"Generate API tests for the new subscription feature based on our existing billing test cases."
AI assistants can read and create test cases, create and organize folders, move test cases and folders, create test runs, update results, and generate automation code for frameworks like Selenium and Cypress — a standardized interface to your test management data, so the work happens through natural language instead of a browser tab.
# one line in Claude Code
claude mcp add --transport http testiny \
https://app.testiny.io/api/v1/mcp-server{
"mcpServers": {
"testiny": {
"type": "http",
"url": "https://app.testiny.io/api/v1/mcp-server",
"headers": {
"Authorization": "Bearer <your-api-key>"
}
}
}
}HTTP transport, MCP protocol version 2025-06-18. Authenticate with OAuth or an API key. An API key inherits the permissions of the user who created it, so create a scoped key rather than handing an assistant your own. The MCP server needs a paid or trial plan — Starter and up, not Free.
BDD test cases are read-only over MCP. listTestCases returns the Gherkin scenario in steps, createTestCase always uses the steps template, and editTestCase rejects
a BDD case with status cannot_edit_bdd_test_case.
Explore further
Discover more test management features
Plan and execute testing
Structure manual test cases, test plans, and automated runs in a single workflow.
Connect your stack
Bring Testiny into the tools your team already uses, and migrate existing test data without the risk.
Scale with confidence
Add governance, on-premises deployment, and milestone tracking as testing scales across teams.
How each deep integration actually works
What each of the deep connectors actually buys you, in more detail.
Jira integration
The deep bi-directional integration with Jira lets you link test cases directly with Jira issues, create bugs automatically, and keep test run status in sync in real time. Link work items in bulk — connect multiple requirements or defects to multiple test cases at once. Teams keep their familiar Jira workflows and get Testiny's test management on top of them.
Supports both Jira Cloud and Jira Data Center with a license-free setup. Jira Cloud authenticates with OAuth 2.0 (3LO) and can create issues under a shared integration account, as the actual user, or both. Learn more about Jira test management integration.
The Jira Marketplace app now runs on Atlassian's Forge platform from version 2.0.0, ahead of Atlassian deprecating Connect apps in Q4 2026 — so the app you install today is the one that keeps working.
GitHub integration
Use the GitHub integration to link issues with tests and create GitHub issues from failed results. Collect automation test results from your GitHub Actions pipelines and see them next to the manual runs. This is particularly valuable for open-source projects and for teams using GitHub as their central development platform.
Seamless workflow integration for GitHub-based development teams. Explore GitHub test management features.
Azure DevOps integration
Integrate with Azure DevOps for test management inside your Microsoft ecosystem. Link work items, track test results, and feed Azure Pipelines runs back into Testiny so a pipeline result and a manual result sit in the same report.
A good fit for teams already standardized on Microsoft development tools. Discover Azure DevOps test management.
Issue trackers, CI/CD and test automation
The bidirectional integration with leading issue trackers changes how teams handle bugs and feature requests. Testiny keeps test results and issue links in sync, and you can raise a new ticket for a discovered defect at the moment you find it.
That buys three things. First, a unified view of all testing activity in one place. Second, automated test failures land next to the test management data instead of in a pipeline log. Third, central management of all test data makes reporting and metrics analysis possible at all.
Testiny's automation features connect to CI/CD pipelines and test automation frameworks through the Testiny CLI, which imports automated results directly. The platform supports a wide range of frameworks and tools including Selenium, Cypress, Jest, JUnit, TestNG, Playwright and many others, so teams keep the tools they picked and still get one place to manage what those tools produced.
Frequently asked questions
About connecting Testiny to the rest of your stack.
Can I connect more than one Jira instance?
Yes. Testiny supports multiple integrations of the same type, each with its own configuration and project mapping. A Jira Cloud site and a Jira Data Center instance can be connected at the same time, and different Testiny projects can point at different ones.
We authenticate Jira with an API token. Do we have to start over?
No. API-token authentication is legacy for Jira Cloud, but an existing token-based integration can be upgraded to OAuth 2.0 in place. The project mapping and all existing issue links are preserved.
My tool is not in the list. Can I still link to it?
Yes. The custom integration links any tool with an addressable issue URL, using URL templates you define, and the REST API covers whatever that does not. Beyond the vendors listed here the docs also cover Notion, Shortcut and Pivotal Tracker.
Which plan do I need for SSO?
SSO requires the Business plan or higher. Free plans sign in with email and password. Once SSO is configured you can require it per user; the organization owner is deliberately exempt so an account can always get back in.
Does Testiny run my automated tests?
No. Your CI pipeline runs them. Testiny imports the results through the Testiny CLI, then manages, links and analyses them alongside your manual runs. Automation sources are created on first use and scoped per project.
What can an AI assistant actually do through the MCP server?
Fifteen tools across discovery, test cases and folders, and test execution — listing projects and cases, creating and moving folders and test cases, creating test runs, and setting results. BDD test cases are read-only. The server needs a paid or trial plan, and an API key inherits the permissions of whoever created it, so scope it.
Put Testiny in the middle of the tools you already use.
Start free for 21 days. No credit card required — cancel anytime.