Nitpicky

Test management that keeps the record straight.

Nitpicky is self-hosted test management for any software team. Write and review test cases, run them on every configuration, follow how far a release has come, and trace it all to your requirements — on your own servers, built to the rules of regulated industries.

See what it does Get in touch

Nitpicky is in development: it is not available yet.

A test run in Nitpicky: its details beside the progress of its tests, each status with its tests, then the tests by section.

Everything a test team does, in one place

A test repository with a memory

Suites and sections, test cases with steps, shared steps and parameters. Every change is a new version with its author and note; branches and baselines follow your releases. Import from CSV, Excel, Xray or Zephyr Scale, export to CSV, Excel, PDF and XML.

Runs and plans that say how far they are

Runs of a suite on each configuration, plans of many runs, devices and matrices. Testers find their tests in To do, record results step by step from the keyboard, and every list shows the progress of its tests.

Requirements, traced

Requirements come from Jira with their Fix Versions. See which ones a release covers, which tests verify them, and which cases to look at again when a requirement changes.

Reports that answer the question

Progress by run, configuration, tester or priority; release readiness against exit criteria; trends, workload and defects. Dashboards across projects, and reports mailed as PDF on a schedule.

Reviews and approvals

Drafts go through your workflow to a reviewer, who approves them — with an electronic signature where the project asks for one. Runs execute the approved versions only.

Exploratory sessions

Charters, notes and findings in sessions of their own, each finding followed up by a defect or a new test case; a closed session is read-only, and signed where the project signs.

Results, one click per step

Each step takes its status in one click, the worst proposes the result's, and the steps left pass in one more. A result is never changed: a correction is a new result, and both stay in the history.

Adding a result: each step with a button for each status, the result proposed by the worst step, the build and the defects.

Ready for an audit, whatever you build

Nitpicky is for any software team. Where your work is regulated — medical devices, automotive, finance — a project can switch on the rules of regulated industries: it is designed to 21 CFR Part 11, ISO 13485 and IEC 62304.

  • Electronic signatures that ask for the password again, bound to one version and its content hash, never carried over to the next.
  • Nothing is deleted. Records are archived, results and the audit trail only grow, and every change is recorded with who made it, when and why.
  • An audit trail you can check: each event hashed and chained, exported for the auditor as CSV or PDF.
  • Validation evidence with every release: the requirements, the tests that verify them and their results, and a check of your own installation.

From requirement to result

The requirements of a release, each with the test cases that verify it and how their latest tests went. The traceability matrix and the coverage report are one click away, and so is a new test case for a requirement nobody covers yet.

The requirements of a release, imported from Jira, each with the test cases that verify it and the status of their latest results.

How far the release has come

Every test of a milestone's runs by the status of its latest result, then run by run, by configuration, by tester or by priority. The readiness report weighs a release against its exit criteria, and any report can be saved, exported or mailed on a schedule.

The progress report of a release: 55,168 tests by the status of their latest result, then each run with its own progress.

Works with the tools you have

Jira

Data Center and Cloud: requirements with their Fix Versions, defects filed from a result, and links back on each issue.

Automated tests

Reporters for Playwright, Vitest, Jest, Cypress and pytest, JUnit XML files, and the nit command line: automated results land in the same runs as manual ones.

Trackers and chats

Defects in GitHub, GitLab or Azure DevOps too; notifications in Slack and Microsoft Teams, and by email when each person wants them.

Coming from TestRail

A migration that brings projects, cases, runs and results across, and an API compatible with TestRail's, so existing scripts keep working.

Nitpicky in Jira

The Nitpicky app for Jira Data Center 9.12, 10.3 and 11.3 shows, on each issue and in the details of the boards, the test cases that name it and how their tests went, read with the reader's own Nitpicky session, and writes a new test case for the issue in one click. Jira's administrators install it on their Jira.

On your servers, your way

Install

Docker Compose with HTTPS built in, or a Helm chart for Kubernetes and OpenShift; PostgreSQL 18. Servers without internet are covered too.

Sign in

Your directory decides who is in: LDAP and Active Directory, single sign-on with OIDC or SAML, two-step sign-in with TOTP, and external users who see only their own tests.

Keep it safe

Nightly backups with tested restores, upgrades that roll back on their own, files on disk or S3 with Object Lock, and a review against OWASP ASVS level 2.

Projects move between installations as .nitpick archives, history, signatures and audit trail included; their format is described by its JSON Schema.

Get in touch

Questions, ideas, or want to hear when Nitpicky is available? Write to hello@nitpicky.dev.