testlink用户手册

User Manual

TestLink 1.6

Copyright . 2004,2005 TestLink Development Team

Permission is granted to copy, distribute and/or modify this document under the terms

of the GNU Free Documentation License, Version 1.2 or any later version published

by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts,

and no Back-Cover Texts. The license is available in "GNU Free Documentation

License" homepage.

See an example of TestLink work flow:

1.Administrator create a product “Fast Foo” and a user Adam with rights “leader” and

Bela with rights “Senior tester”.

2.Adam imports Software Requirements and for part of these requirements generates

empty Test cases.

3.Bela describe test sneario of these Test cases that are organized according to

Components and Categories.

4.Adam creates Keyword: “Regression” and assign es this keyword to ten of these test

cases.

5.Adam creates a Test Plan “Fish & Chips”, Build “Fish 0.1” and add Test Cases with

account himself on the login page. Manager do it. He has “Guest” rights and could see

results and Test cases. He can see that everything passed in overal report ;-) and

problems in build “Fish 0.1” in a report for particular Build. But he can change

nothing.

2 Overall structure

There are three cornerstones: Product, Test Plan and User. All other data are relations

or attributes for this base. First, definition of a couple of terms that are used

throughout the documentation.

2.1 Products and Test Plans

Product: A product is something that will exist forever in TestLink. Products will

Case Suite and Test Results.

2.2 Test Case Categorization

TestLink breaks down the test case structure into three levels components, categories,

and test cases. These levels are persisted throughout the application.

Component: Components are the parents of categories. Each component can have

Category: Categories are the parents of test cases. Each category can have many test

Test Case: Test cases are the fundamental piece of TestLink.

Test Specification: All components, categories and test cases within Product.

3 Test Specification

3.1 Creating Test Cases

create component(s) for your product. You can fill description which can be printed

then. Component includes categories. Category has the similar meaning but is second

level of Test Specification and includes just Test Cases.

User can also copy or move Test Cases.

Title: could include either short description or abbreviation (e.g. TL-

 Expected results: describe checkpoints and expected behaviour a

tested product or system.

3.2 Deleting Test Cases

Test cases, categories, and components may be deleted from a test plan by users with

lead permissions from the "delete test cases" screen. Deleting data may be useful

when first creating a test plan since there are no results. However, Deleting test cases

recommended when using this functionality.

Test cases could be related with software/system requirements as n to n. The

functionality must be enabled for a product. User can assign Test Cases and

Requirements via link Assign Requirements in the main screen.

4 Keywords

Keywords were created to give users another level of depth when categorizing test

Reviewed Test cases