
Kiwi TCMS
the leading open source test management system

Contribute
Become a financial contributor.
Top financial contributors
Individuals
€400 EUR since Dec 2018
€220 EUR since Sep 2019
€200 EUR since Oct 2019
€100 EUR since Jan 2020
€38 EUR since Sep 2019
€20 EUR since May 2019
€10 EUR since Aug 2019
€5 EUR since Jun 2019
€5 EUR since Oct 2019
€5 EUR since Sep 2020
€5 EUR since Oct 2020
€5 EUR since Jan 2021
€5 EUR since Jan 2021
€1 EUR since Aug 2020
€1 EUR since Sep 2020
Organizations
€10k EUR since Mar 2020
€118 EUR since Jun 2019
Kiwi TCMS is all of us
Our contributors 23
Everyone who has supported Kiwi TCMS. Individuals and organizations that believe in –and take ownership of– our purpose.
Open Source S...
Total contributions
€10,000 EUR
Congratulations on your Open Source Speed Dating award!
Unotech Softw...
Total contributions
€10 EUR
sponsor

Connect
Let’s get the ball rolling!
What's new with Kiwi TCMS
Stay up to dates with our latest activities and progress.
Kiwi TCMS v8.8 has been released
200K downloads on Docker Hub
Progress update on open source hardware for black-box testing

Budget
Transparent and open finances.
Bug bounty KiwiTCMS, 1 issue and 1 closing PR
by Bryan Mutai •
Financial contribution to Kiwi TCMS
from Andrii Kogut •
Financial contribution to Kiwi TCMS
from Borisker •
Today’s balance
€5,833.11 EUR
~ €20,276.54 EUR

About
Kiwi TCMS is the leading open source test case management system. It is used during software testing and quality assurance to collect information about what and when has been tested, which versions of the product have been tested and in what environment. This information is helpful when making a go/no-go decision before a release, monitoring and planning the workload of the QA team and various reports.
When doing manual testing each engineer on the team can easily find the tasks assigned to them and all instructions necessary to execute the tests and report the results.
In automation testing scenarios TCMS systems are useful to collect test execution information and later analyze it. This is especially important when you don’t execute all of the tests all of the time!