TestLink

test management
system

HOW TO WORK WITH TESTLINK

1.
2.
3.
4.
5.
6.
7.
8.

Create a Project
Create Test Cases (Test Suites) for this Project
Create Test Plan
Specify Build of the Project you are going to test
Add Test Cases to the Test Plan
Assign Test Cases to Test Engineers
Execute Test Cases (Test Engineers)
See Reports and Charts

HOW TO WORK WITH TESTLINK

Additional facilities:
Assigning Keywords (we may form a group of
Test Cases for Regression tests)
Specifying Requirements (we may bind them
with Test Cases in the many-to-many relation
and see if our Test Cases cover our requirements)
Events log (you can see here the history of all the
changes)

STEP 1. CREATE A PROJECT

To create a project go to the Test Project

Management section:

STEP 1. CREATE A PROJECT

STEP 1. CREATE A PROJECT.

IMPORTANT FIELDS
Name
ID (used for forming a unique Test Cases ID)
E.g. ET-03 means that the Test Case is created for
Easy Test project and it has ID=3
Project Description (what is the aim of the
Project, what is the target group, what is the
business logic, what is the Test Environment)

STEP 1. CREATE A PROJECT.

IMPORTANT FIELDS
Enhanced features:
Requirements feature we may specify
requirements and see if they are well-covered by
Test Cases
Testing priority we may assign priority to
Test Cases (high, medium, low)
Test Automation we may specify whether the
test should be performed manually or
automatically
Inventory to tell the truth, I didnt understand
what it means

STEP 1. CREATE A PROJECT.

IMPORTANT FIELDS

You can now set this project here, like in Mantis,

in the top right corner

STEP 2. CREATE TEST CASES

STEP 2. CREATE TEST CASES.

CREATING TEST SUITE

STEP 2. CREATE TEST CASES.

CREATING TEST SUITE

STEP 2. CREATE TEST CASES

STEP 2. CREATE TEST CASES

Test Case Title
Summary
Preconditions
Execution type
(manual or automated)
Test importance
(High, Medium or Low)

STEP 2. CREATE TEST CASES

STEP 2. CREATE TEST CASES

STEP 2. CREATE TEST CASES

We may also import & export Test Suites & Test
Cases (in the .XML format):
We import them from one project

And export the file in other

Unfortunately, now its the only way to transfer

them from one project to another

STEP 3.SPECIFY TEST PLAN

TestLink wont allow you to execute Test Suites if
you dont create a Test Plan and specify Test
Build.
How to do that? Elementary my dear Watson!
Lets begin from the Plan

STEP 3.SPECIFY TEST PLAN

STEP 3. SPECIFY TEST PLAN

Current Test Plan will appear in the top right

corner

STEP 4. SPECIFY BUILD

After youve added a Test Plan menu for adding

Test Build appears:

Add a new build there

STEP 4. SPECIFY BUILD

STEP 5. ADD TEST CASES TO THE

PLAN

Unfortunately, only Test Cases, not Test Suites or

the whole Test Specification can be added to a
Test plan. So, until you dont select one separate
TC the button Add to Test Plans will not
appear.

STEP 5. ADD TEST CASES TO THE

PLAN

Then you can choose what Test Plans you want to

add the selected TC to.

STEP 6. ASSIGN TEST CASE

EXECUTION TO TESTERS

Before assigning TC to testers you should create

a DB of users with appropriate roles here:

Or here:

STEP 6. ASSIGN TEST CASE

EXECUTION TO TESTERS

Add the users you need filling in the form:

STEP 6. ASSIGN TEST CASE

EXECUTION TO TESTERS

Then you can assign TC execution here:

STEP 6. ASSIGN TEST CASE

EXECUTION TO TESTERS

You can assign test cases to testers and send

them email notifiactions:

STEP 7. EXECUTE TESTS

To start executing tests Test Engineer should go

to test Execution section:

Then choose a TC and you will face:

STEP 7. EXECUTE TESTS

We may also connect TestLink with our bugtracking system Mantis, then during execution
you will see:

STEP 7. EXECUTE TESTS

After click on

Create new bug,

creating the bug
using Mantis
user interface
and reorganinzing
the windows.

STEP 7. EXECUTE TESTS

Test engineer writes the issue ID on Testlink:

And it looks like here after saving:

STEP 7. EXECUTE TESTS

Execution history is being saved:

STEP 8. SEE REPORTS AND

CHARTS

After test case execution is finished you may see the

results of it using Test Reports section

Or here:

STEP 8. SEE REPORTS AND CHARTS

Youll face the following page:

STEP 8. SEE REPORTS AND

CHARTS

Test Plan Rerport - the document has options

to define a content and a document structure.
You may choose the info you wanna get
and you will surely get it!

STEP 8. SEE REPORTS AND

CHARTS

Test Plan report (part of it)

STEP 8. SEE REPORTS AND

CHARTS

The document 'Test Report' has options to

define a content and document structure. It
includes Test cases together with test results.

STEP 8. SEE REPORTS AND

CHARTS

Test result matrix

STEP 8. SEE REPORTS AND

CHARTS

Charts

STEP 8. SEE REPORTS AND

CHARTS

Charts results by tester (there are only

unassigned test cases in the diagram):

STEP 8. SEE REPORTS AND

CHARTS
Charts Results for top level suites:
1. Log in the application
2. News module

STEP 8. SEE REPORTS AND CHARTS

Blocked, Failed, and Not Run Test Case
Reports
These reports show all of the currently blocked,
failing, or not run test cases.
E.g.

STEP 8. SEE REPORTS AND

CHARTS

General Test Plan Metrics

This page shows you only the most current status
of a Test plan by test suite, owner, and keyword.

STEP 8. SEE REPORTS AND

CHARTS

Query metrics work like filters in Mantis

STEP 8. SEE REPORTS AND CHARTS

Requirements based report
If we have some requirements specified and have
connected them with TC we can see the following
report:

ADDITIONAL FACILITIES.
ASSIGNING KEYWORDS
1.

Go to the Assign Keywords section

2.

Select some Test Suite and then youll be able o

go to Keywords Management

ADDITIONAL FACILITIES.
ASSIGNING KEYWORDS
Add keywords if there are no KW at all or if there
are no KW you need:

ADDITIONAL FACILITIES.
ASSIGNING KEYWORDS

Now you can add Keywords both to Test Suites

& Test Cases, either all the Keywords (>>) or
only one KW (>)

ADDITIONAL FACILITIES.
ASSIGNING KEYWORDS

Then youll be able to see such a useful chart

demonstrating the Results by KW:

ADDITIONAL FACILITIES.
SPECIFYING REQUIREMENTS

You can open the section in this way:

Or in this:

ADDITIONAL FACILITIES.
SPECIFYING REQUIREMENTS

Requirements Specification adding

ADDITIONAL FACILITIES.
SPECIFYING REQUIREMENTS

Then we create Requirements:

ADDITIONAL FACILITIES.
SPECIFYING REQUIREMENTS
Then we create
Requirements:

ADDITIONAL FACILITIES.
SPECIFYING REQUIREMENTS
Pay attention that there are different types of the
Requirements:

ADDITIONAL FACILITIES.
SPECIFYING REQUIREMENTS
Then assign requirements to Test Cases:

ADDITIONAL FACILITIES.
SPECIFYING REQUIREMENTS
Select Test Suite or Test Case and assign it to 1 or
more requirements (R. can be assign to TC in the
relation man-to-many)

ADDITIONAL FACILITIES. EVENTS

LOG

WHAT BENEFITS DO WE HAVE?

We have all the documentation structured and
organized.
2. We solve the problem of version control.
3. We can control the testing process (Events log +
different kinds of Reports)
4. We can see if all the requirements are covered
with Test Cases
5. We can select Test Cases for Regression Testing
6. We can see the results of testing in a very clear
and easy-to-use form.
etc.
1.

SOURCES

http://blog.testlink.org/

http://testlink.org/demo/

http://lib.custis.ru/TestLink#.D0.9D.D0.B0.D
0.B7.D0.BD.D0.B0.D1.87.D0.B5.D0.BD.D0.B8.D0.
B5_.D1.82.D0.B5.D1.81.D1.82.D0.BE.D0.B2_.D0.
B4.D0.BB.D1.8F_.D0.BF.D1.80.D0.BE.D0.B3.D0.B
E.D0.BD.D0.B0

THANK YOU
FOR YOUR
ATTENTION!