TestLink is a web-based

test management Test management most commonly refers to the activity of managing a testing process. A test management tool is software used to manage tests (automated or manual) that have been previously specified by a test procedure. It is often associated with ...

system that facilitates

software quality assurance Software quality assurance (SQA) is a means and practice of monitoring all software engineering processes, methods, and work products to ensure compliance against defined standards. It may include ensuring conformance to standards or models, suc ...

. It is developed and maintained by Teamtest. The platform offers support for test cases, test suites, test plans, test projects and user management, as well as various reports and statistics.

Requirements

Because TestLink is web-based software, an administrator needs access to a web server and a database in order to install and run it. TestLink has support for the

MySQL MySQL () is an Open-source software, open-source relational database management system (RDBMS). Its name is a combination of "My", the name of co-founder Michael Widenius's daughter My, and "SQL", the acronym for Structured Query Language. A rel ...

MariaDB MariaDB is a community-developed, commercially supported Fork (software development), fork of the MySQL relational database management system (RDBMS), intended to remain free and open-source software under the GNU General Public License. Developm ...

and

PostgreSQL PostgreSQL ( ) also known as Postgres, is a free and open-source software, free and open-source relational database management system (RDBMS) emphasizing extensibility and SQL compliance. PostgreSQL features transaction processing, transactions ...

databases. In order to use TestLink, a user only requires a

web browser A web browser, often shortened to browser, is an application for accessing websites. When a user requests a web page from a particular website, the browser retrieves its files from a web server and then displays the page on the user's scr ...

Usage

The basic units used by TestLink are: Test Case, Test Suite, Test Plan, Test Project and User.

Test Plan

Test Plans are the basic unit for executing a set of tests on an application. Test Plans include Builds, Milestones, User assignment and Test Results. A Test Plan contains name, description, collection of chosen Test Cases, Builds, Test Results, milestones, tester assignment and priority definition. Each Test Plan is related to the current Test Project. Test Plans may be created from the "Test Plan management" page by users with lead privileges for the current Test Project. Press "Create" button and enter data. Test Plan definition consists of title, description (html format) and status "Active" check-box. Description should include the next information with respect to company processes: * Summary/Scope * Features to be tested * Features to not be tested * Test criteria (to pass tested product) * Test environment, Infrastructure * Test tools * Risks * References (Product plan or Change request, Quality document(s), etc.) Test Plans are made up of Test Cases imported from a Test Specification at a specific point of time. Test Plans may be created from other Test Plans. This allows users to create Test Plans from Test Cases that exist at a desired point in time. This may be necessary when creating a Test Plan for a patch. In order for a user to see a Test Plan they must have the proper rights. Rights may be assigned (by leads) in the define User/Project Rights section. This is an important thing to remember when users tell you they can't see the project they are working on. Test Plans may be deleted by users with lead privileges.

Test Case

A Test Case describes a simple task in the workflow of an application. A test case is a fundamental part of TestLink. After a tester runs a test case it can either pass, fail or block it. Test cases are organized in test suites. Test Cases have the following parts: * Identifier of a Test Case is assigned automatically by TestLink, and cannot be changed by users. This ID composes from Test Project prefix and a counter related to the Test Project in which the Test Case is created. * Title: could include either short description or abbreviation (e.g. TL-USER-LOGIN) * Summary: should be really short; just for overview, introduction and references. * Steps: describe test scenario (input actions); can also include precondition and clean-up information here. * Expected results: describe checkpoints and expected behaviour of a tested product or system. * Attachments: could be added if configuration allows it. * Importance: Test designer could set importance of the test IGH, MEDIUM and LOW * Execution type: Test designer could set automation support of the test ANUAL/AUTOMATED* Custom fields: Administrator could define own parameters to enhance Test Case description or categorization. Large custom fields (more than 250 characters) are not possible. But information could be added into parent Test Suite and referred via custom fields. For example, you can describe Configuration 'standard', 'performance', 'standard_2' and refer via CF to this labels.

User

Each TestLink user has an assigned Role that defines the features available. The default types are: Guest, Test Designer, Senior tester, Tester, Leader and Administrator but custom roles can also be created.

Test Projects

Test Projects are the basic organisational unit of TestLink. Test Projects could be products or solutions of your company that may change their features and functionality over time but for the most part remains the same. Test Project includes requirements documentation, Test Specification, Test Plans and specific user rights. Test Projects are independent and do not share data.

Test Specifications

TestLink breaks down the Test Specification structure into Test Suites and Test Cases. These levels are persisted throughout the application. One Test Project has just one Test Specification.

Features

* User roles and management * Grouping of test cases in test specifications * Test plans * Platforms * Requirements with versioning and revisioning * Support for testing different builds of the software * Reports, charts and monitors * Customization of the user interface using Smarty templates * Integration with

LDAP The Lightweight Directory Access Protocol (LDAP ) is an open, vendor-neutral, industry standard application protocol for accessing and maintaining distributed Directory service, directory information services over an Internet Protocol (IP) networ ...

* Integration with other software using a provided API * Bug tracking system integration (

Mantis Mantises are an order (Mantodea) of insects that contains over 2,400 species in about 460 genera in 33 families. The largest family is the Mantidae ("mantids"). Mantises are distributed worldwide in temperate a ...

, JIRA,

Bugzilla Bugzilla is a web-based general-purpose bug tracking system and testing tool originally developed and used by the Mozilla project, and licensed under the Mozilla Public License. Released as open-source software by Netscape Communications in 19 ...

FogBugz FogBugz is an integrated web-based project management system featuring bug and issue tracking, discussion forums, wikis, customer relationship management Customer relationship management (CRM) is a strategic process that organizations u ...

Redmine Redmine is a free and open source, web-based project management and issue tracking tool. It allows users to manage multiple projects and associated subprojects. It features per project wikis and forums, time tracking, and flexible, role-based ac ...

, and others)

References

External links

TestLink Project page

TestLink sourceforge page
{{DEFAULTSORT:TestLink Software testing tools