[5] Use testlink for Test Management "reprint 』

Testlink is used to manage the test process. By using the functions provided by testlink, you can manage the test process from test requirements, test design, to test execution, it also provides statistics and analysis of a variety of test results, so that we can start the test work and analyze the test results.

Testlink is open to SourceForgeSource codeProject. As a Web-based test management system, testlink provides the following functions:

• Test Requirement Management
• Test Case Management
• Test Case coverage management for test requirements
• Test plan preparation
• Test Case execution
• Measure and measure large amounts of test data.

The latest version of testlink is 1.6.2. In the subsequent sections of this article, the author will introduce in detail the complete process of using testlink1.6.0 for test management.

1. Install and start

1. Before installing testlink1.6.0, you must complete the following environments required for installation and running: Webserver, PhP4, and MySQL. The recommended installation environment is as follows:

• Apache HTTP Server 2.0.59
• PHP 4.4.1
• MySQL 4.1.21

2. Save the testlink installation package to the server, decompress it to the htdocs directory of apache2, and rename it testlink.

3. automatically install testlink

• Enter the access address http: // yoursite/testlink/install/index. php In the browser, for example, http: // localhost: 80/testlink/install/index. php.
• Select New install. On the displayed page, enter the username and password for logging on to MySQL, such as root. Prompt installation successful, detailed installation instructions please refer to http://blog.csdn.net/judyxm/archive/2006/01/12/577148.aspx

4. log on to the homepage of testlink. The system creates a default Administrator account for testlink. the username and password are admin and Admin. You can use this account to access testlink. Log on to http: // 127.0.0.1: 80/testlink/index. php. If you see the following page, it indicates that the installation is successful.

Ii. Initial Configuration (set users and products)

1. user settings

In the testlink system, each user can maintain his/her own private information. Admin can create users, but cannot view passwords of other users. In the user information, you need to set an email address. If the user forgets the password, the system can get it through mail.

The testlink system provides six roles: Admin, Leader, Senior tester, tester, guest, and testdesigner. The corresponding functional permissions are as follows: (see figure)

• Guest: only has read permission. It is suitable for users who want to view test cases, test requirements, and project analysis.
• Testdesigner: All work that can be performed on test cases and test requirements.
• Tester: only test cases can be executed.
• Senior Tester: allows you to view and maintain test cases and execute test cases. However, you cannot manage test plans or assign test tasks.
• LEADER: You can perform all the work of testing specifications and requirements, manage test plans, and assign test tasks.
• Admin: maintenance product, user.

At the same time, it supports the needs of users in different regions for different languages and supports different languages based on users' preferences.

2. Product settings

Testlink can manage multiple products. After admin configures the product, testers can manage test requirements, test cases, and test plans. Testlink allows you to set different background colors for each product for easy management.

Iii. Test Requirement Management

Test requirements are the basis for testing. First, we need to break down and sort out product testing requirements. One product can contain multiple test requirement specifications, and one test requirement specification can contain multiple test requirements;

• Create Test Requirement Specification
  The description of the test requirement specification is simple, including the name and scope.
• Create test requirement
  Test requirements include: requirement ID, name, range, requirement status, and case that covers the requirement. Testlink provides two States to manage requirements: Correct (valid) and untestable (not testable ).

• Import test requests from files
  Testlink provides the ability to import test requests from files. The Supported file types are CSV and CSV (door.

Iv. Test Case Management

The management of test cases supported by testlink includes three layers: component, category, and test case. We map component to the functional modules of the project, and category to the functions of each module. Test Case is written in these category. We can use the test case search function to find the required test cases from different projects and hundreds of thousands of test cases, or even directly copy the test cases written in other projects, this solves the problem of managing and reusing test cases.

However, there is another problem that cannot be solved, that is, the problem corresponding to the test requirement. In the test management, we are very concerned about the coverage rate of test requirements. After the test requirements are extracted from the requirement specification, testlink provides the ability to manage the correspondence between test requirements and test cases.

• Create component
  The component content includes: name, description, scope, related content, and constraints.
• Create a category
  The content of category includes: name, test scope and target, configuration information, test data, and test tool.
• Create test case
  Test cases include: Test Case name, brief description, steps, expected results, and keywords.

  The created test case tree is as follows:

• Establish the coverage relationship between test cases and test requirements.
  Select the test case in the left-side case tree, and then select the test requirement on the right side to perform assign.

V. Test Plan Formulation

In the testlink system, a complete test plan includes:

• Name of the test phase (such as the integration test phase and system test phase)
• Milestone (specify the start time and end time of each test phase, and the ratio of completion priorities A, B, and C)
• Build version (defines the build version to be tested in this test plan, generally named after the product name + time .)
• Schedule testers (select the participants of this test plan from the user list .)

• Test Case set
  • Set priority rules. The priority is divided into three levels: A, B, and C. The system determines the priority based on the combination of user-defined importance levels and risk levels. The importance levels include low, medium, and high. Risk Levels include Level 3: 1, 2, and 3.
  • Select the test case set for this test plan from the test case
  • Set the importance level and risk level of each test case category
  • Set the responsibility for each test case category. Select the owner of each category from the tester list of this test plan to perform and complete the test case execution.

Vi. test execution

Run the test case and record the test results based on the execution of each build version. The test results can be selected in four cases:

Not run: not executed

Pass: The execution passes

Failed: execution failed

Blocked: the use case cannot be executed and is blocked due to failure of other use cases.

VII. Test Result Analysis

Based on the data recorded during the test, testlink provides a wide range of measurement statistics functions to intuitively obtain the data that needs to be analyzed and summarized during the test management process:

• Test Case coverage of test requirements: requirements that have passed the test, those that have not passed the test, those that are in the blocking status, and those that have not yet started the test.

• Test Case execution for each version:
  1) ratio of testing case execution with various priorities
  2) test case execution ratio of each module
  3) test case execution rate of each Tester

• Execution status of each version

• What is the execution status of all test cases in different build versions? Is not executed.

• Blocked test case list

• List of failed test cases

• Number of bugs in each test case
  If it is connected to the bug tracking system, the following table shows the number of bugs in each test case.

8. Integration with the Bug Tracking System

Testlink provides interface configurations associated with multiple bug tracking systems. Currently, the supported bug systems include Jira, Bugzilla, And mantis. For more information about the configuration method, see help.

9. Other usability Functions

Testlink also provides many easy-to-use functions, such:

• Generate Test Cases Directly from test requirements
• Document import and export functions
• Test Report can be exported as Excel
• Supports keyword setting.

Summary

Testlink is used to manage the test process. By using the functions provided by testlink, we can manage the test process from test requirements, test design, to test execution, it also provides statistics and analysis of a variety of test results, so that we can start the test work and analyze the test results.

In this article, the author demonstrates in detail how to use testlink for test management based on his own experience, and briefly introduces how to use testlink. We hope to help you learn how to use the basic functions of testlink. At the same time, you can refer to this process and the help documentation of testlink to manage the test process.