TestLink: The Complete Guide to Free Open-Source Test Management
TestLink is the most widely deployed open-source test management tool. It's been around since 2003, has over 10 million downloads, and provides the core test management workflow — test cases, test plans, execution, and reporting — at zero license cost. For budget-constrained teams that need structured test management, TestLink remains a viable option.
What TestLink Provides
TestLink covers the essential test management workflow:
- Test specification: Create and organize test cases in a hierarchical structure
- Test plans: Group test cases for a specific release or sprint
- Test execution: Record results (pass/fail/blocked) against a test plan
- Requirements management: Link test cases to requirements, track coverage
- Reporting: Coverage reports, execution results, defect summaries
- Bugtracker integration: Link to Jira, Mantis, Bugzilla, GitHub Issues
What TestLink doesn't provide: native automation execution, CI/CD integration beyond basic API calls, or modern UI. It's a manual test management tool with API hooks for automation results.
Installation
TestLink requires PHP + MySQL (or PostgreSQL). Docker simplifies setup:
# docker-compose.yml
version: '3'
services:
testlink:
image: bitnami/testlink:latest
ports:
- "8080:8080"
environment:
TESTLINK_DATABASE_HOST: mariadb
TESTLINK_DATABASE_NAME: testlink
TESTLINK_DATABASE_USER: testlink
TESTLINK_DATABASE_PASSWORD: testlinkpass
TESTLINK_USERNAME: admin
TESTLINK_PASSWORD: adminpassword
TESTLINK_EMAIL: admin@example.com
depends_on:
- mariadb
mariadb:
image: bitnami/mariadb:latest
environment:
MARIADB_DATABASE: testlink
MARIADB_USER: testlink
MARIADB_PASSWORD: testlinkpass
MARIADB_ROOT_PASSWORD: rootpassword
volumes:
- mariadb-data:/bitnami/mariadb
volumes:
mariadb-data:docker-compose up -d
# Access at http://localhost:8080For production, add a reverse proxy (nginx) and enable HTTPS.
Setting Up Your First Project
After login:
- Go to Test Project Management > Create
- Name:
My Application - Prefix:
APP(used for test case IDs like APP-001) - Enable: Requirements, Custom Fields, Active status
- Click Create
Each project has isolated test cases, plans, and results.
Creating Test Suites and Test Cases
Create test suites (folder structure):
- Go to Test Specification
Create suite hierarchy matching your application:
My Application
├── Authentication
│ ├── Login
│ └── Registration
├── User Profile
└── BillingCreate a test case:
- Navigate to the suite: Authentication > Login
- Click the + icon > Add Test Case
- Fill in:
- Title: User can login with valid credentials
- Summary: Verify the login flow with correct email and password
- Preconditions: User account exists with email test@example.com
- Set: Priority (High), Status (Final)
Add test steps:
| Step | Action | Expected Result |
|---|---|---|
| 1 | Navigate to https://app.example.com/login | Login page displays |
| 2 | Enter test@example.com in email field | Email field accepts input |
| 3 | Enter TestPass123! in password field | Password field accepts input, masked |
| 4 | Click Sign In button | Form submits |
| 5 | Verify current URL | URL contains /dashboard |
| 6 | Verify user name in header | User's name visible in top navigation |
The test case is assigned ID APP-001 automatically.
Linking Requirements
If requirements are tracked outside TestLink, you can add them manually:
- Go to Requirements > Create Requirement Specification
- Add requirements:
- REQ-001: Users must be able to log in with email and password
- Go to your test case > Requirements tab
- Search for REQ-001 > Link it
TestLink tracks coverage: which requirements have at least one test case covering them, and whether those tests are passing.
Creating a Test Plan
A test plan groups test cases for a specific testing effort:
- Go to Test Plan Management > Create
- Name:
v2.0.0 Release Regression - Active: Yes
- Click Create
Add test cases to the plan:
- Open the test plan
- Go to Add/Remove Test Cases
- Select test suites or individual test cases to add
- Assign build:
v2.0.0(versions the test execution) - Assign testers to test cases
Executing Tests
- Open the test plan
- Go to Execute Tests
- Filter by: Assigned to me, Status: Not Run
- For each test case:
- Read the test steps
- Execute against the application
- Record result: Passed / Failed / Blocked
- Add notes (actual behavior if failed)
- If failed: attach screenshot, log defect in linked bugtracker
The test plan dashboard shows progress in real-time.
Importing Test Cases From Excel
TestLink supports bulk import via XML or CSV. For Excel import, use the TestLink Excel importer (community tool) or format your data as TestLink XML:
<?xml version="1.0" encoding="UTF-8"?>
<testcases>
<testcase name="User can login with valid credentials">
<summary><![CDATA[Verify login with correct email and password]]></summary>
<preconditions><![CDATA[User account exists]]></preconditions>
<steps>
<step>
<step_number>1</step_number>
<actions><![CDATA[Navigate to /login]]></actions>
<expectedresults><![CDATA[Login form visible]]></expectedresults>
<execution_type>1</execution_type>
</step>
</steps>
<importance>2</importance>
<execution_type>1</execution_type>
<status>1</status>
</testcase>
</testcases>Import via Test Specification > Import Test Cases.
Automation Integration
TestLink has a REST-like XML-RPC API for pushing automation results. After automated tests run, push results to TestLink:
# Push results to TestLink via API
import testlink
tls = testlink.TestlinkAPIClient(
'http://testlink.example.com/lib/api/xmlrpc/v1/xmlrpc.php',
devKey='your-api-key'
)
# Report a test result
tls.reportTCResult(
testcaseid=123, # TestLink test case ID
testplanid=456, # Test plan ID
buildname='v2.0.0',
status='p', # p=pass, f=fail, b=blocked
notes='Automated run via pytest - 2026-05-25'
)Install the Python client: pip install TestLink-API-Python-client
For Robot Framework, use the robotframework-testlink library which pushes results automatically.
TestLink Reporting
Built-in reports:
- Test Plan Report: Complete pass/fail status for all tests in a plan
- General Test Plan Metrics: Progress dashboard with completion percentage
- Requirements Coverage: Which requirements have test coverage
- Test Results by Tester: Who ran what, results per person
- Export to Excel: For stakeholder reporting
TestLink Limitations
UI is dated: The interface has barely changed since 2010. It's functional but not modern.
No built-in dashboards: Results display as tables and simple charts, not the visual dashboards teams expect from modern tools.
Limited agile support: No native sprint/board concepts. Test plans can model sprints but it's not intuitive.
Performance: Large installations (50,000+ test cases) have slow UI.
Mobile-unfriendly: Not responsive — can't run tests from a mobile device.
Setup and maintenance burden: Self-hosted means you manage backups, upgrades, and server issues.
TestLink vs. Paid Alternatives
| Factor | TestLink | TestRail | Zephyr Scale |
|---|---|---|---|
| Cost | Free (hosting costs) | $36/user/month | $10+/user/month |
| UI quality | Dated | Modern | Modern |
| Jira integration | Plugin | Native | Native (Jira app) |
| Automation API | XML-RPC | REST | REST |
| Cloud hosting | Self-hosted only | Cloud available | Cloud available |
| Mobile | No | Yes | Limited |
| Support | Community | Commercial | Commercial |
TestLink wins only on cost. If licensing budget is unavailable, TestLink is better than no test management. If budget allows, TestRail's UX and support quality justify the cost for most teams.
Migration Path
If you outgrow TestLink, export your test cases as XML and import to TestRail, Zephyr, or another tool. TestLink XML exports are fairly standard and most tools have importers. The migration effort depends on test case count and how much metadata (custom fields, requirements links) you need to preserve.
Summary
TestLink is a viable free test management tool for teams that need basic structure — test case library, test plans, execution tracking — without budget for commercial tools. The trade-offs are real: dated UI, self-hosting overhead, no modern CI/CD integration beyond an XML-RPC API. Use it as a stepping stone if budget is the blocker, with a plan to migrate to TestRail or Zephyr when the team grows and the ROI on better tooling becomes clear.