Open Source Test Case Management: The Free Tier Trap

A QA lead who has just been told to cut tooling spend spends a Tuesday afternoon reading forum threads about open source test case management. By Thursday she has picked one, migrated forty test cases as a trial, and hit a wall she did not see coming. A feature she needs sits behind a paid tier. Or the container will not even start on her teammate's laptop. This happens often enough that it deserves a name. The free tier looked complete from the outside and was not. This post keeps the same argument we made before about why that happens. This time every claim carries a name, a date, and a page you can check yourself in about ten minutes.

The four ways open source, therefore free, breaks down

Teams usually run into one of four situations when they go looking for a no cost test case manager. Naming them precisely matters more than describing the general feeling of disappointment.

• The project is genuinely abandoned. No releases, no responses to issues, nothing shipping.
• The project is alive but has aged past what a new team will accept in its interface or its stack.
• The project is healthy and shipping, but the free tier has quietly had the useful parts removed.
• The project never had a free tier worth using in the first place, and the marketing just implied one.

The second and third cases get confused constantly. That confusion is what costs teams the most time, because the fix for each is completely different. A team that thinks it has an abandonment problem will spend a sprint evaluating replacements when the real fix was a training afternoon. A team that thinks it has an aging interface problem will invest in workarounds for a free tier ceiling that was never going to move no matter how much training happens.

Aging is not abandonment: the honest read on TestLink

TestLink is the case most often cited as a dead project, and that citation is wrong. Checked on 25 August 2026, TestLink is still maintained. Version 1.9.20 is the final release of the 1.9.x family. A 2.x line is actively in development. The maintainer posted a progress update on 6 December 2025. That is not the profile of an abandoned tool.

What TestLink actually has is a different, more common problem. The interface and the underlying stack have aged past what a team hiring junior QA engineers in 2026 will tolerate without complaint. That is a real cost. It is worth naming honestly rather than dressing it up as neglect.

A team leaving TestLink is not fleeing a corpse. It is outgrowing a tool the way you outgrow a spreadsheet. Gradually, then all at once. The people who still remember how the reporting screens work have moved to other jobs. The person who inherits the install has to relearn a decade old interface from scratch, usually during the same week a release is already running late.

That relearning cost is easy to underestimate until someone has to live it. A new QA hire spends her first two weeks on the job just figuring out where existing test suites are filed, because the navigation predates conventions her previous three jobs all used.

Free, but with the useful parts removed: the Kiwi TCMS example

Kiwi TCMS is where the second failure mode has real, checkable evidence. It deserves to be stated fairly before anything critical is said about it. Kiwi TCMS is actively maintained. Version 16.3 shipped on 24 August 2026, the day before this piece was checked.

It is licensed under GPL-2.0. It has roughly 1.2 thousand stars on GitHub. Its container images have been pulled over 500,000 times. This is not a stalled hobby project. It is a working, popular, healthy piece of open source software, and any post that calls it dead or dying is simply wrong.

Here is what the free Community Edition actually gives you, and what it does not. Each fact is sourced to the page it came from.

• The Community Edition container displays EthicalAds inside your own self-hosted instance. Ad-free images require the Self Support subscription at $25 a month (kiwitcms.org, "Self Support Subscription Explained," 20 August 2025).
• The free images are built for x86_64 only. There is no aarch64 build, so an Apple Silicon Mac or an AWS Graviton instance cannot run it without extra work.
• Releases are rolling only. There are no version tagged images, so a free user cannot pin the exact version they are running or roll back to a known one.
• Multi-tenancy, meaning separate isolated projects for separate teams or clients under one install, is an Enterprise feature priced at $600 a month (kiwitcms.org features page and "Community Edition Explained," 18 February 2026).

None of this is dishonest. Kiwi TCMS states every one of these limits openly on its own site. It is written in plain language, for anyone who reads past the download button. The problem was never that Kiwi TCMS hides anything.

The problem is that the phrase open source told the reader none of it. Free and open source are not the same promise. The gap between them is exactly where a Tuesday afternoon research session turns into a Thursday migration headache.

Consider a six person QA team evaluating Kiwi TCMS this quarter. Two of them run Apple Silicon laptops issued last year. The free container image will not start on either machine without extra containerization work nobody budgeted for. That is not a hypothetical edge case. It is what x86_64 only means the first week a new hire opens their laptop.

Or consider the team that has been running the same free instance for fourteen months. An auditor asks which version was live when a specific defect shipped in March. Because there is no version tagged image, nobody can answer with certainty. The team can describe roughly when they last restarted the container, and that is the best answer available.

Two licenses, one real difference worth knowing

Kiwi TCMS is GPL-2.0. Tesbo is Apache 2.0. Both are genuinely open source licenses, and neither is more honest than the other. The practical difference shows up if you ever modify the code and redistribute it.

GPL-2.0 requires that your modified version also be released under GPL-2.0, so the openness carries forward to whatever you build on top. Apache 2.0 lets you modify and redistribute under different terms, including closed ones, as long as you keep the required notices. Neither choice tells you anything about a project's free tier feature set. That is a separate business decision the maintainer makes, and it is exactly the decision this whole post has been examining.

Why an unproven abandonment claim is worse than no example

It would be easy to name a third tool here as the abandoned case and move on. We are not going to do that, because an unproven claim of abandonment is worse than leaving the category as a description. Calling a maintained project dead damages trust in everything else on the page. It undermines even the parts that are carefully sourced and dated.

If you are checking a tool yourself and want to know whether it fits the abandoned pattern, look at the same signals used above for TestLink and Kiwi TCMS. Check the date of the last release. Check whether issues get responses. Check whether the maintainer has said anything public in the last six months. A project with no answer on any of those three checks is the one worth calling dormant, and only with a dated citation of your own attached to the claim.

How to check any tool yourself before you commit an afternoon

You do not need to trust any blog post, including this one. Before adopting a free tier for anything, three checks take about ten minutes and tell you most of what matters.

• Which CPU architectures does the project actually build for. If your team has even one Apple Silicon or ARM machine, check this first.
• Does the project ship version tagged images, or is it rolling release only. Rolling only means you cannot pin what you run, which matters the day an auditor asks what was live in March.
• Does the running container display anything you did not put there yourself, such as ads or third party branding, and is that disclosed anywhere on the project's own site.

If a tool passes all three checks and the remaining limits still fit your team, that free tier is a genuinely good deal. If it fails one, at least you know that going in. That is a much better time to find out than during a migration weekend, with three engineers pulled off feature work to make a Friday deadline.

For teams already past this point, two related pieces cover the next steps. One works through what actually breaks during a move away from TestLink or Kiwi TCMS, case by case. The other is a separate guide to what self-hosting a test case manager should actually mean, beyond just running a container on your own server.