What it does
Kiwi TCMS brings manual and automated testing work into a shared web dashboard. Teams can describe test plans and cases, create runs for a particular product build, record execution outcomes, and connect failures with issue trackers. Plugins collect results from external test frameworks, so Kiwi TCMS is the record and coordination layer rather than the test runner itself.
Organize a release around plans and runs
A useful first task is to prepare a regression plan for one feature area. Add or create test cases, then, when a build is ready, create a Test Run for the build and choose the confirmed cases that should execute. Assign the run to a tester and use a separate run for each build or environment combination. Testers record each execution's status and notes; issue-tracker integrations can connect a failure to a bug.
Kiwi TCMS also accepts automation results through plugins for popular testing frameworks. That lets a QA team see manual and automated outcomes together, but the test suite still runs in its own runner. The product has an external JSON-RPC and XML-RPC API for connecting other tools.
Decide who operates it
The upstream community edition can be self-hosted, while the project also offers subscription options for support, private tenants, and managed hosting. Current subscription rates and included service limits were not established from the pages accessed, so no exact price is stated.
The upstream kiwitcms/kiwi repository uses GPL-2.0+; the features matrix lists a separate AGPL-3.0+ license for the enterprise build. Check which delivery edition you intend to deploy before reviewing its license or hosting terms.
Strengths
- Keeps test plans, cases, build-specific runs, and execution histories in one QA workflow.
- Collects automated results through plugins and links test failures to supported issue trackers.
- Provides JSON-RPC and XML-RPC interfaces for external tooling.
Watch out for
- Kiwi TCMS records and coordinates tests; teams still need manual testers or separate automation runners to produce results.
- Self-hosting means the team must operate its own instance unless it chooses a hosted subscription.
Best for
- Planning manual regression runs across product builds and environments.
- Collecting automation results alongside manual QA execution records.
- Teams that need a searchable history of test cases, runs, assignments, and linked bugs.
Sources
- Kiwi TCMS - test management system (Oct 26, 2026)
- Kiwi TCMS - Features matrix (Oct 26, 2026)
- Introduction - Kiwi TCMS documentation (Oct 26, 2026)
- Test Runs - Kiwi TCMS documentation (Oct 26, 2026)
- Kiwi TCMS - Self Support Subscription Explained (Oct 26, 2026)
- Kiwi TCMS upstream LICENSE - GNU General Public License version 2 (Oct 26, 2026)