Features · v1.2.0

Everything in the box.

Nothing here is gated behind a higher tier. The software is free; paid plans only cover hosting it for you.

Test cases

A repository, not a spreadsheet.

Folders, templates, custom fields, shared steps, and saved views — with AI to draft cases from text, issues, or screenshots of your app.

  • Rich text with tables, code, and images
  • Shared steps, with expected results beside each step
  • Auto-save, draft recovery, and private staged cases
  • AI generation, auto-tagging, and duplicate detection
Repository · test cases

Requirements & traceability

Coverage you can defend.

Author requirements or mirror them from your tracker, link cases from either side, and watch coverage roll up from real results.

  • Synced from Jira, Azure DevOps, GitLab, GitHub, Gitea, Redmine, MantisBT, ClickUp
  • Suspect flags when a requirement changes after its case last ran
  • Traceability snapshots for release sign-off
  • Coverage Gaps and Coverage Changes reports
Docs
Requirements · coverage rollups

Impact Analysis

Test only what changed.

Pick two commits or a pull request and get the affected tests from the git diff alone — no coverage agent, no instrumentation.

  • GitHub, GitLab, Bitbucket, Azure DevOps, Gitea
  • Code Pins tie a case to a file, symbol, or glob
  • Every selection explains itself, with a score
  • Webhook rules compose the run on push or pull request — and execute it
Docs
Impact · affected tests

Automated execution

Execute automation from the test run.

Execute a run's automated cases in your own CI while testers take the manual ones. Both land in one checklist.

  • GitHub Actions, GitLab CI, or a signed webhook for any CI
  • Your own parameters per target — browser, environment, build
  • No agent, no framework lock-in
  • Track, cancel, and retry from the run
Docs
Test run · execute automated cases

CLI & reporters

Results from any pipeline.

A standalone binary for Linux, macOS, and Windows — no Node.js — plus official Playwright and WebdriverIO reporters that stream results live.

  • JUnit, TestNG, xUnit, NUnit, MSTest, Mocha, Cucumber
  • Format auto-detected
  • Screenshots, videos, and traces uploaded with the result
  • Link results to cases by id in the test name
Docs
any CI · push results with the CLIbash
# one binary, no Node.js$ testplanit config set --url https://qa.example.com --token tpi_…# format is auto-detected$ testplanit import "./test-results/*.xml" -p 1 -n "CI Build 123"# link to existing cases by id in the test name, e.g. "[123] login"$ testplanit import results.xml -p 1 -n "Build 123" --case-matcher name

QuickScript

Manual case in, automation code out.

Select cases, pick a framework, export ready-to-run scripts. Three levels: template, AI-enhanced, or generated against your own repository.

  • Playwright, Cypress, Selenium, pytest, Jest, and more
  • 40+ templates across E2E, unit, and API testing
  • Repository mode uses your page objects and helpers
QuickScript · export preview

Test runs

Manual, automated, or both in one run.

Live results, configurable statuses, forecasting from history, and Magic Select to build the run with AI.

  • Hybrid runs: manual and automated results share one status
  • Risk scores put the cases that most deserve a run first
  • Dependencies hold a case until its prerequisites pass
  • Completed runs are locked to preserve history
Test runs · results

Failure Patterns

Two hundred red rows, a handful of problems.

Automated failures are grouped by what actually went wrong, so a red run reads as a short list of patterns instead of a wall of rows.

  • AI suggests a root cause from a catalogue you control
  • Link an issue and the pattern becomes a known issue
  • Quarantine keeps known failures out of your pass rate
  • Flaky candidates flagged from pass/fail history
Docs
Failure Patterns · grouped by cause

Alerts

Hear about it before you go looking.

Pick a metric, set a threshold, and choose who is told when it is crossed — a pass rate under your bar, a stalled run, a case that has started to flake.

  • Thirty metrics across cases, runs, milestones, and projects
  • In-app, email, daily digest, or a webhook to Slack
  • Follow only the alerts that matter to you
  • System alerts for AI budgets and background jobs
Docs
Notifications & Alerts · alert rules

Data-driven testing

One case, many rows.

Define parameters once and run every data row as its own tracked iteration — with datasets shared across a project and pinned by version.

  • Per-iteration status, assignee, and notes
  • Row reservation so parallel CI jobs never collide
  • Iteration Matrix report
Test case · parameters and datasets

Reports

Fourteen reports and a builder.

Test Case Health, Flaky Tests, Failure Rate Trend, Automation Candidates, Requirement Traceability, and more — saved, frozen, and shared by link.

  • Report Builder for anything not pre-built
  • Saved reports with relative date ranges
  • Frozen reports keep the numbers you signed off on
  • Public, authenticated, or password-protected links
Reports · Test Case Health

Exploratory testing

Sessions, first-class.

Charter-driven sessions with a timer, notes as you go, and issues captured in place — tracked next to your structured runs.

  • Work distribution and completion trends
  • Session reports and version tracking
Sessions · summary

Integrations & AI

Your tracker. Your model.

Issues, milestones, and requirements sync from the tools you already use. AI runs on the provider you choose — including models you host yourself.

  • Jira (native Forge app), GitHub, GitLab, Azure DevOps, Gitea, Redmine, MantisBT, ClickUp
  • OpenAI, Claude, Gemini, DeepSeek, Ollama, Azure OpenAI, any OpenAI-compatible endpoint
  • MCP server for your AI assistant
  • REST API and documented webhooks
Issues · synced from Jira

Review & governance

Quality gates the server enforces.

Request review on cases, runs, and sessions, and decide exactly how results may be recorded — per project.

  • Approve, request changes, or reject, with a reviewer inbox
  • Required fields and edit windows on results
  • Justification when a result flips
  • Composition lock when execution starts
Project settings · governance

Security

Enterprise identity, audited.

SAML 2.0 and SCIM 2.0 with several identity providers on one instance, two-factor enforcement, custom roles, and audit logs with before/after diffs.

  • Okta, Microsoft Entra, OneLogin; Google, Microsoft, Apple, magic link
  • Project access view: who can open it, and which grant decided
  • API tokens with expiration
Admin · security

And the rest

The small print, in full.

For anything not listed, the docs are the source of truth.

Import
CSV with saved column mappings · Markdown with AI parsing · Testmo migration · issues linked by ticket key
Export
CSV · PDF for runs and milestones · NDJSON data-lake endpoints
Collaboration
Custom roles · @mentions and comments · in-app, email, and digest notifications with a switch per type · link previews in Slack and Teams
Search
Full-text search on Elasticsearch · saved views · record keys like PROJ-TC-123
Recovery
Trash with self-service restore · audit logs with a retention window
Languages
17 languages, including right-to-left
Accessibility
Dark mode · WCAG AA · keyboard shortcuts
Deploy
Docker Compose · Helm chart · hosted in US-Chicago or EU-Frankfurt
Source
AGPL-3.0 on GitHub · every feature on every plan

Get started

See it with your own tests.