# TestPlum

> TestPlum is a test management platform for QA teams. It connects requirements, test cases, test runs and defects, and turns recorded results into release readiness, risk and flaky-test reports.

TestPlum is web-based test management software for QA teams that test manual and automated software before release. Key facts:

- Test cases have structured steps with an expected result per step, versions with diffs, templates, custom fields and CSV import/export.
- Test runs snapshot case versions; results are append-only; testers record results with keyboard shortcuts (1–9).
- A live requirements traceability matrix derives each requirement's status (passing, failing, partial, untested, not covered) from recorded results and flags orphans.
- Release readiness is a verdict from six checks with user-set thresholds: runs in scope, execution completion, pass rate, critical cases failing or blocked, open critical issues and requirements verified.
- Risk-based selection scores each case from priority, last result, edits since execution, no history, failing requirements and flakiness; flaky score = flips ÷ (decisive results − 1).
- CI uploads JUnit XML with idempotency keys; a versioned REST API is described in OpenAPI 3.1; webhooks are HMAC-SHA256 signed; issues can be sent to GitHub or Jira.
- Organization and per-project roles (14 permissions), tenant isolation, Argon2id passwords, revocable sessions, audit log. AI assistance is optional.

## Product
- [Test case management](https://testplum.com/features/test-case-management/): Structured steps, versions with diffs, templates, custom fields, saved views and CSV import/export.
- [Test runs and execution](https://testplum.com/features/test-runs/): Run snapshots, assignment, step results with keyboard shortcuts, append-only history, burndown and retests.
- [Requirements and traceability](https://testplum.com/features/requirements-traceability/): Requirement coverage, derived status, orphan detection and an exportable traceability matrix.
- [Reports and release readiness](https://testplum.com/features/release-readiness/): Readiness verdicts, explainable risk scores, flaky-test detection, workload and a configurable report builder.
- [Defect tracking](https://testplum.com/features/defect-tracking/): Issues from failures, duplicate suggestions, workflow and history, comments and mentions, GitHub and Jira push.
- [CI, API and webhooks](https://testplum.com/features/ci-automation/): JUnit XML ingestion with idempotency keys, OpenAPI 3.1 REST API, scoped API keys and signed webhooks.

## Guides
- [What is test management?](https://testplum.com/learn/what-is-test-management/): Test management is the practice of planning, writing, executing and reporting on software tests so a team knows what was tested, what passed and whether a release is ready. A test management tool stores test cases, organises them into runs, records every result and links tests to requirements and defects.
- [Requirements traceability matrix: what it is and how to build one](https://testplum.com/learn/requirements-traceability-matrix/): A requirements traceability matrix (RTM) is a table that maps every requirement to the test cases that verify it, the latest result of each test and any open defects. It answers two questions before a release: is every requirement tested, and is every tested requirement passing?
- [Release readiness: six checks that tell you if a build can ship](https://testplum.com/learn/release-readiness-checklist/): A build is ready to release when explicit, agreed checks all pass: the right test runs are in scope, enough of them are executed, the pass rate meets your bar, no critical tests are failing or blocked, open critical defects are within your limit and enough requirements are verified with none failing.
- [Flaky tests: how to detect, measure and fix them](https://testplum.com/learn/flaky-tests/): A flaky test is one that passes and fails on the same code without a relevant change. Measure flakiness from history: count how often a test's outcome flips between pass and fail across its recent decisive results, divide by the number of decisive results minus one, and investigate tests that score above about 0.3.
- [Risk-based testing: prioritise the tests that matter most](https://testplum.com/learn/risk-based-testing/): Risk-based testing means running the tests most likely to find important problems first. A practical score adds points for business priority, a recent failure, changes since the last run, never having been run, a failing linked requirement and flakiness; you then run cases from the highest score down until time runs out.

## Reference
- [Security overview](https://testplum.com/security/): controls in place today; no certifications are claimed.
- [FAQ](https://testplum.com/faq/): direct answers about the product.
- [Glossary](https://testplum.com/glossary/): definitions of software testing terms.
- [Full text for language models](https://testplum.com/llms-full.txt)

## Optional
- [Create a workspace](https://app.testplum.com/signup)