TestLink

Visit Website

Introduction

TestLink is a long-standing open-source, web-based test management system written in PHP. The project site lists TestLink Stable 1.9.20 (“Raijin”) as the current release, available from SourceForge or as a Bitnami virtual appliance, with the source on GitHub under the GPL-2.0 licence.

TestLink covers the classic test management workflow: test specifications organised into test suites and test cases, test plans tied to builds, assignment of test execution to testers, and reports on progress and results. It can link test cases to requirements and integrates with bug trackers such as Jira, Bugzilla, Mantis and Redmine so that failed executions can be linked to defects. An XML-RPC API lets automation frameworks report results.

Activity is low but not zero. The GitHub repository’s most recent commit was in December 2025 on the testlink_1_9_20_fixed branch, which carries nightly fixes to 1.9.20, while the website’s copyright notice still reads 2013/2018. That makes TestLink a reasonable choice for teams that want a free, self-hosted tool and accept an older interface, but a risky one for teams that need active feature development.

How it compares: commercial SaaS tools such as TestRail, Qase, Testiny and Testmo offer modern interfaces, automation integrations and support, often with free tiers for small teams. Among open-source options, TestLink is the best-known, but its age shows in UI and setup.

In the quality loop TestLink sits at the release and CI gate stage as the record of what was tested on which build.

Features

1. Test specification: Hierarchical test suites and test cases with steps and expected results.
2. Test plans and builds: Plan executions per build and assign them to testers.
3. Requirements coverage: Link test cases to requirements and report coverage.
4. Bug tracker integration: Connect to Jira, Bugzilla, Mantis, Redmine and others.
5. XML-RPC API: Report automated test results programmatically.
6. Reports: Progress, results and metrics reports per plan and build.
7. Self-hosted: Runs on a PHP web stack with MySQL/MariaDB or PostgreSQL.

Pros

1. Free and open source: GPL-2.0, with no licence fees.
2. Self-hosted control: Data stays on your servers.
3. Proven: Used for many years, so its workflow and limits are well understood.

Cons

1. Dated interface: The UI feels old next to modern SaaS tools.
2. Slow development: The stable release is 1.9.20, with fixes on a maintenance branch rather than new features.
3. Admin effort: You install, back up, secure and upgrade the PHP stack yourself.

Usage and Links (Example)

Install TestLink on a PHP and database server (or use the Bitnami appliance), create a project, write test suites and cases, then create a test plan and a build. Assign executions to testers, record results, and link failures to your bug tracker. Automation can report results through the XML-RPC API, for example from a CI job after a test run.

Keep the server patched and restricted to internal networks, since it is a self-hosted PHP application.

A useful evaluation checklist for any test management tool: import a realistic slice of your existing tests, push one real CI result file through the API, link a requirement and a defect in your tracker, and build the report your release manager asks for. Measure how long each step takes, check permission and audit features against your compliance needs, and confirm how you would export everything if you later switch tools.

Useful links:

• TestLink site
• Source on GitHub

Pricing

Free and open source under GPL-2.0. Hosting and maintenance costs are yours.

Recommended for?

• Teams that need a free, self-hosted test case manager
• Organisations with strict data residency that cannot use SaaS
• Teams already familiar with TestLink who need a stable, unchanging tool

Conclusion

TestLink is still a workable, free test management system with a familiar workflow and integrations, but development has slowed to maintenance fixes. It suits teams that value self-hosting and zero licence cost over a modern experience.

If you need active feature development, automation-first workflows or a polished UI, look at the commercial alternatives listed here, several of which have free tiers.