Integrations
Connect your tests, CI and trackers
Results from any CI land next to manual tests, bugs stay in step with your tracker, and every page shows the exact command or setting.
Playwright test reporting with a results dashboard and a release verdict
Send Playwright test results to TestPlum with the built-in JUnit reporter and one curl step. Get run history, flaky tests and a release verdict.
Read moreA JUnit XML test results dashboard: upload JUnit XML from any CI
Upload JUnit XML from Jest, Vitest, pytest, Playwright or any tool with one curl command. Get run history, failure groups and a Ready or Not ready answer.
Read moreA CTRF report viewer and dashboard that keeps every retry
Upload a CTRF JSON report to TestPlum with one curl command. See every retry as its own attempt, flaky tests, failure groups and a release verdict.
Read moreGitHub Actions test results, with the release answer in every run
Send GitHub Actions test results to TestPlum with one workflow step. See the release answer in the job summary and stop the build when it is Not ready.
Read moreGitLab CI test results, with a release answer that can stop the pipeline
Send GitLab CI test results to TestPlum from after_script, print the release answer in the log and stop the pipeline in a .post job when Not ready.
Read moreJira test management integration with two-way bug sync
Connect Jira to TestPlum: send bugs to Jira and keep their state in sync both ways, and import Jira stories as requirements with live test coverage.
Read moreA test management MCP server for your coding assistant
TestPlum's test management MCP server lets Claude Code, Cursor and other MCP clients read requirements, write tests, triage failures and check readiness.
Read moreOne step from any CI
Every CI integration works the same way: your test tool writes its own report (JUnit XML, CTRF or Allure), and one curl step sends it to TestPlum with a key that only works for that project. The results land next to manual results, count toward the release you are working on, and the build can print the answer, Ready or Not ready with the reasons, or stop until it is ready.
Trackers stay in step both ways: bugs found in a run go to Jira or GitHub and their status comes back. For coding assistants, the MCP server lets an agent read tests, record results and ask whether a release is ready. More on the API and webhooks for developers.
Find out whether your next release is ready
Create a workspace, import your tests or write a few, and record a run. Everything on this site is in the product today.