Experiment-11

Aim: Study of any Open source testing tool (Test Link)

Test link is an open source test management tool. It enables creation and organization of test
cases and helps manage into test plan. Allows execution of test cases from test link itself. One can
easily track test results dynamically, generate reports, generate test metrics, prioritize test cases
and assign unfinished tasks. It’s a web based tool with GUI, which provides an ease to develop
test cases, organize test cases into test plans, execute these test cases and generate reports. Test
link exposes API, written in PHP, can help generate quality assurance dashboards. The functions
like add test case to Test Plan, Assign Requirements, Create Test Case etc. helps create and
organize test cases per test plan. Functions like Get Test Cases for Test Plan, Get last execution
Result allows one to create quality assurance dashboard.

Test Link enables easily to create and manage Test cases as well as organize them into Test plans. These
Test plans allow team members to execute Test cases and track test results dynamically, generate reports,
trace software requirements, prioritize and assign tasks. Read more about implemented features and try
demo pages.

Overall structure

There are three cornerstones: Product, or attributes for this base. First, definition of documentation.

Products and Test Plans

Test Planand User. All other data are relations a couple of terms that are used throughout the

Product: A Product is something that will exist forever in Test Link. Products will undergo many
different versions throughout their lifetimes. Product includes Test Specification with Test Cases
and should be sorted via Keywords.

Test Plan: Test Plans are created when you’d like to execute test cases. Test plans can be made
up of the test cases of one or many Products. Test Plan includes Builds, Test Case Suite and Test
Results.

User : An User has a Role, that defines available Test Link features.

Test Case Categorization

Test Link 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 many
Categories.

Name: AKASH CAHURASIYA Roll no:2104220130005

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

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

Test Specification: All Components, Categories and test cases within Product.
Test Case Suite: All Components, Categories and test cases within Test Plan.
Test Specification

Creating Test Cases

Tester must follow this structure: Component, Category and test case. At first you create
Component(s) for your Product. 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.
Test Cases has following parts:
•Title: could include either short description or abbreviation (e.g. TL-USER-LOGIN)
Summary: should be really short; just for overview.
•Steps: describe test scenario (input actions); can also include precondition and
cleanup information here.
• Expected results: describe checkpoints and expected behaviour a tested Product or system.

Deleting Test Cases

Test cases, Categories, and Components may be deleted from a test plan by users with lead
permissions from the delete test casesscreen. Deleting data may be useful when first creating a
test plan since there are no results. However, Deleting test cases will cause the loss of all results
associated with them. Therefore, extreme caution is recommended when using this functionality.

Requirements relation
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.

Test Plans
Test plan contains name, description, collection a chosen test cases, builds, test results,
milestones, tester assignment and priority definition.

Creating a new Test Plan

Test Plans may be deleted from the Create test planpage (link Create Test Plan) by users with
lead privileges. Test plans are the basis for test case execution. Test plans are made up of test
cases imported from Products at a specific point of time. Test plans can only be created by users
with lead privileges. Test plans may be created from other test plans. This allows users to create
test plans from test cases that at a desired point in time. This may be necessary when creating a

Name: AKASH CAHURASIYA Roll no:2104220130005

 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 Execution

Test execution is available when:

1.A Test Specification is written.

2.A Test Plan is created.

3.Test Case Suite (for the Test Plan) is defined.

4.A Build is created.

5.The Test plan is assigned to testers (otherwise they cannot navigate to this Test Plan).

Select a required Test Plan in main page and navigate to the Execute tests’ link. Left pane
serves for navigation in Test Case Suite via tree menu, filtering and define a tested build.

Test Status

Execution is the process of assigning a result (pass, fail, blocked) to a test case for a specific
build. Blocked’ test case is not possible to test for some reason (e.g. a problem in configuration
disallows to run a tested functionality).

Insert Test results

Test Results screen is shown via click on an appropriate Component, Category or test case in
navigation pane. The title shows the current build and owner. The colored bar indicate status of
the test case. Yellow box includes test scenario of the test case.

Updated Test Cases:

If users have the proper rights they can go to the Update modified test casepage through the link
on main page. It is not necessary for users to update test cases if there has been a change (newer
version or deleted).
Advantages:

Easy in tracking test cases (search with keyword, test case id, version etc.)
1.We can add our custom fields to test cases.
Allocating the work either test case creation/execution any kind of documents is easy

Name: AKASH CAHURASIYA Roll no:2104220130005

 2.when a test cases is updated the previous version also can be tracked
3.We can generate results build wise
4.Test plans are created for builds and work allocations can be done.
Report, is one of the awesome functionality present in the Test link, it generates reports in
desired format like HTML/ CSV /Excel and we can create graphs too.
5.And the above all is done on the privileges based which is an art of the test link and i liked this
feature much

Example of Test Link workflow:

1.Administrator create a Product Fast Foodand a user Adam with rights leaderand Bela with
rights Senior teste.

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

3.Bela describe test scenario of these Test cases that are organized according to Components and
Categories.

4.Adam creates Keyword: Regressionand assigns this keyword to ten of these test cases.

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

6.Adam and Bela execute and record the testing with result: 5 passed, 1 failed and 4 are blocked.

7.Developers make a new build Fish 0.2and Bela tests the failed and blocked test cases only.
Exceptionaly all these five Test cases passed.

8.Manager would like to see results. Administrator explains him that he can create account
himself on the login page. Manager does it. He has Guestrights and could see results and Test
cases. He can see that everything passed in overall report and problems in build Fish 0.1in a
report for particular Build. But he can change nothing.

Name: AKASH CAHURASIYA Roll no:2104220130005