Testlink study Four: TestLink1.9.13 Instructions for use

Objective

　　Test management tool refers to the process of using tools to manage the entire test input, execution and test results of the software. It can improve the efficiency of regression testing, greatly improve the test time, test quality, use case reuse, demand coverage and so on.

Testlink is used for the management of the test process, and by using the functionality provided by Testlink, the test process can be completely managed from test requirements, test design to test execution, and it also provides statistics and analysis of a variety of test results. Allows us to simply start the test work and analyze the test results. Furthermore, Testlink can correlate multiple bug tracking systems, such as Bugzilla, Mantis and Jira, and README.

Testlink is one of SourceForge's open source projects and is a PHP-based, web-enabled test management system that can be divided into two parts-management and plan execution.

Management section, including product management, user management, test requirements management and test case management;

Plan the execution part, including the test plan and execute the test plan, and finally show the relevant test result analysis and test report.

The main features of Testlink include :

• Test Requirements Management
• Test Case Management
• Test case coverage management for test requirements
• Development of Test plans
• Execution of test Cases
• Measurement and statistical functions of a large number of test data

Key features of Testlink include :

• Support multi-product or multi-project managers to manage test requirements, plans, use cases and executions by product and project, and maintain independence between projects;
• Test cases, not only can create modules or test suites, but also can be multi-level classification, the formation of tree-like management structure;
• Can be customized fields and keywords, greatly improve the adaptability of the system, to meet the needs of different users;
• The same project can be developed different test plans, the same test cases can be assigned to different test plans, support a variety of keywords conditional filtering test cases;
• Can be easily implemented and up to 8 popular defect management systems (such as Mantis, Bugzilla, Jira, readme, etc.) integration;
• Different roles such as Test Manager, Test lead, Test designer, veteran tester, and general tester can be set, and roles with specific permissions can be customized.
• Test results can be exported in several formats, such as HTML, Ms Excel, MS Word, and email.
• You can search for test cases based on keywords, test cases can also be generic copy generation, and so on.

In the next section of this article, the complete process of using TestLink1.9.13 for test management is described in detail.

First, Login

Visit http://localhost/testlink/login.php and log in to Testlink first page based on your account and password. As shown in the following:

First Login: can register, can use the default Admin/admin

Test management process

Ii. initial setup (set user, product) 2.1 set User

In the Testlink system, each user can maintain their own private information. Admin can create users, but cannot see other users ' passwords. In the user information, you need to set up an email address, if the user forgets the password, the system can be obtained through mail.

The Testlink system provides six roles, namely tester, Guest, tester, Test Designer, Senior tester, leader, admin. The corresponding function permissions are as follows:

6 User levels:

Guest: Can browse test specifications, keywords, test results and edit personal information;
Tester: You can browse test specifications, keywords, test results, and edit test execution results;
Test Designer: Edit testing specifications, keywords and requirements specification;
Senior Tester: Allows editing of test specifications, keywords, requirements, and test execution and creation of releases;
Leader: Allows editing of test specifications, keywords, requirements, test execution, test plans (including priorities, milestones and allocation plans), and releases;
Admin: All rights, including user management;

At the same time, support different geographical users to different language needs, can be based on user preferences to provide users with different language support. 2.1.1 Admin Create new user Create User: 2.1.2 User self-registration

Note: The default role for registered successful users is guest.

2.2 Product Management 2.2.1 Test Project management

Testlink can manage multiple projects, and individual test projects are independent and cannot share data, but only admin-level users can set the project . After the admin has set up the project, the tester will be able to perform the relevant management tasks such as test requirements, test cases, test plans, etc.

1) After the initial login to the system, the page is added to the project page, such as:

If you select the Enable Product requirements feature , the home page for the test project will display the product requirements area. Not selected by default.

If enable test automation (API keys)is selected, the test mode drop-down selection box appears when you create a test case, including two options for manual and automatic, and if not, the drop-down selection box does not appear , all of the test cases are manual execution types.

Active : Whether the test project is active. Non-admin users can only see the active item in the test item drop-down selection box in the top right corner of the home page. For inactive test projects, the administrator sees an * number in front of them in the test item drop-down box in the top right corner of the home page.

Enter the project name, prefix, tick "Enable product Requirements", click Create, Create Project success.

2) If it is not the initial login system, the Admin user can click on "Product Management"-"Test Project Management" and click the "Create" button on the new interface to create a new project.

Third, test demand management

The requirement specification is the basis for us to carry out the test. First of all, we can decompose and collate the requirements specification of the product, split it into multiple requirements, a product can contain multiple requirements, and a requirement can contain multiple test requirements.

• Create Test requirement Specifications
• Create test requirements

3.1 Creating Test requirements Specifications

Click on the "Product Requirements"-"Product Requirements Specification" menu above the home page to create a new product requirement specification. The description of the product requirements specification is simple and contains the title, scope, and type of the content. As shown in the following:

Title: Title of the requirement specification
scope : scope of the requirement

3.2 Creating test requirements

Select the requirement specification you want to edit, and click on the "Create new test Requirement" button on this page to start creating our test requirements. As shown in the following:

Test requirements include: Document identification, name, scope, status of requirements, type of requirement, and number of test cases required.

Testlink provides a variety of states to manage requirements: Drafts, audits, corrections, completion, implementation, effective (Valid), non-testable (not testable), and expiration.

Number of test cases required: The total number of test requirements that the requirement contains. When the results are counted, there is a way to count requirements coverage , and when not all the requirements are added to the Testlink, use the total demand to assess the demand coverage. The total number of requirements is the number entered here.

Other than that:
1) Testlink provides the ability to import test requirements from a file, supported by CSV and CSV (door), XML,DocBook , and four types of files. Testlink also provides the ability to export requirements, supported file types are XML .
2) Testlink also provides the ability to upload files, which can be attached to the requirements when creating test requirements.

Iv.. Test Plan Management

In the Testlink system, a complete test plan includes: Create a test plan, version management.

4.1 Creating a test case set

Click the test Plan Management menu under the test Plan management module of the home page.

On the page that appears, click the "Create" button to enter the test plan creation page as shown:

The content of the test plan includes the plan name, the plan description, and whether it was created from an existing test plan, and if it is selected to be created from an existing test plan, the newly created test plan contains all the associated information for the selected test plan, such as a test case for which the test plan has been assigned.

Create a test plan called "Flash purchase V6.3 system test".

4.2 Version Management

Click the Version Management menu under the test Plan management module of the home page to create a new beta version. The content of the beta version includes: the identification of the input version, the description of the version, the activity, and, if the build of the activity, the build is available, otherwise the build is unavailable.

4.3 Edit/delete milestone (temporarily no effect)

Create a new test milestone by clicking the Edit/Delete milestone menu under the test Plan management module of the home page. The content of the test milestone includes: Name, date, priority.

4.4 Assigning a test plan role

Click the Assign test Plan role menu under the Home User Management module to assign users to the test plan.

When you assign a test Plan role page, you can select a test plan, select a test role that needs to assign permissions, and then click the Better button to better test the plan.
After you select a test plan, you can assign the test plan to different users in different roles, and through the role list, you can select the user's action role for the test plan.
Once selected, click the Update button to save the results.

V. Test Case Management

The management of the test cases supported by Testlink consists of two layers: a new set of test cases, a test Suites, and a testing Cases. Test case sets can be mapped to the project's functional modules, and the test cases correspond to specific functions.
We can use the test Case search feature to find the test cases we need from different projects, hundreds of test cases, and also provide the ability to move and copy test cases, move or copy a test case to another project, tick the Automatic Update tree option, add, When you delete or edit a test case, the update tree is automatically updated.

5.1 Creating a test case set

Write test cases by tapping the test cases-Edit test Cases menu on the home page. Such as:

Click "Create test Case Set" to create the component. The contents of the component include: component name, details, keywords. Such as:

After filling in the relevant content, you can click the "Save" button.

5.2 Creating test Cases

Select the set of test cases that you created, and click the Create Test Case button on the right side of the page to create a new test case. The elements of a test case include: Test case title, summary, steps, expected results, keywords.

Summary: Includes test intent and preconditions.

recommendation : Each data type to be subdivided when writing test cases. When writing test cases, some of the steps of the test cases are the same, and the data types that may change are the same, and we can implement them in a copy-based way. If the following test case operations are the same for multiple classifications, except for partial data types or field names, you can reduce the workload of the test case by moving the test case. It is also possible to list different test data in the summary of the creation of the test case, and then perform the same action in the test step, depending on the test data.

To do so, let's look at the created test Case tree (below):

5.3 Establishing coverage relationships for test cases and test requirements

Click the "Assign Product Requirements" menu under the home "Product Requirements" module, go to the Requirements Assignment page, select the test case in the left-hand case tree, and select the corresponding test requirement on the right, and assign it.

To do this, let's look at the test cases that have been assigned.

To do this, let's look at a product requirements overview, such as:

VI. test Case Set Management

After the test case is ready, you can perform related actions on the set of test cases.

6.1 Adding/Removing test cases to a test plan

On the home page through the test Plan drop-down list, first select a test plan, click the "Add/Remove test cases to test Plan" button under "test Case set" and go to add test cases to the test plan. As shown in the following:

You can assign a test case that you have already created to the test plan. By clicking on a set of test cases, you can see all the test cases under the set of test cases, as shown in:

1) Increase the selection of test cases :

You can select the test case to be executed in the test plan, or you can select the version of the test case that needs to be performed under the test plan based on the version drop-down list. When you have selected, click the Add Selected test Case button to assign the selected test case to the test plan.

2) Delete the selected test case to the test plan

You can select the test case to be executed in the test plan, or you can select the version of the test case that needs to be performed under the test plan based on the version drop-down list. When you have selected, click the Delete selected test Case button to remove the test plan from the selected test case.

6.2 Show the latest test case versions

Click the "show the latest version of test Cases" menu under the home "test Case set" module and go to the latest version of the display page that connects to the test case, where you can see the latest version of the test case connected to the test plan.

6.3 Assigning execution test cases (assigning tasks to testers)

Click the Set test Case owner menu under the home Test case set module and go to the Assign Test Cases page to specify a specific performer for each use case contained in the current test plan.

On the Assign Test Case page, select a test case set or test case in the left case tree, the right page will appear with a drop-down list to let you select the user. Select the appropriate user thickness, tick the test case, click the button at the bottom of the right page to complete the assignment of the use case.

Of course, this can also be done in bulk designation-the top of the right page, there is a drop-down list can select the user, the following list of test cases to select the use case to assign to the user, and then click on the "Execute" button to complete the assignment of multiple use cases to a person's action. As shown in the following examples:

1) Select the test plan on the left, the version to be assigned

2) on the right side of the page, select the tester you want to assign to

Vii. test Execution/reporting of bugs

Putting them together is because reporting bugs is done synchronously in the process of execution--when a bug is found in the process of executing the use case we need to report it to our bug management system Bugzilla immediately.

Before performing a test, you need to create a build version for each test plan, and a test plan can create multiple builds--we can do this by identifying the version number of each release, indicating which version of the test plan we are executing, and which can correspond to bugzilla. Of course, you can also use other meanings, such as the focus of the test execution.

Once the build is created, the test case is also assigned to the current test plan and then we can execute the test.

On the "Execute Test" menu in the horizontal navigation bar, click on the Go to execution page. This page, also in Split, the left is a use case tree, the right page content is the main content.

One thing to note here is that while execution is ostensibly for a test plan, it actually corresponds to the execution of the test case in the test plan.

In the left-hand case tree, you can select a test case based on specific conditions, select a test case set, a test plan, a build description, a description of the test set, and so on at the top of the right page, and a button to batch set the status of the test cases contained in the test set, you can set all the test cases to pass, Failure, locking, in the following is the details of each test case, while the last part of each test case, there is a "description/description" input box, you can enter some of the instructions for execution, as well as "test results", these two inputs are required after we completed the test case ourselves to fill out.

There are four types of test results:

Pass: The test case passed ( Green background )
Failure: The test case did not succeed, this time it may be necessary to submit a bug to Bugzilla ( red background )
Lock: This use case cannot be executed and is blocked because of other use case failures. ( Grey background )
Not yet executed: if one of the test cases is not executed, it is marked as "not executed" in the final measure ( no background )

Note: The test case execution result is non-pass status, all need to fill in the instructions .
When this section is completed, the results are recorded at the beginning of the use case. If Testlink and Bugzilla are integrated, there will be a bug tag behind this record, and after clicking on this bug tag, an input box will appear that records the number of bugs, and if the test case fails, You can enter the ID of the bug found in the bugzilla in this place, and then a link to the ID appears below the record, and after clicking on the ID, you can link directly to the Bug's page in Bugzilla.

7.1 Performing Tests

The test Execution page looks like this:

7.2 Reporting Bugs

Once a bug is found in the process of executing the test case, we need to report it to our bug management system immediately. Testlink provides the interface configuration associated with a variety of bug tracking systems, and the currently supported bug systems are Jira, Bugzilla, Mantis. The relevant methods of configuration management refer to help.
If Testlink and Jira are integrated, then after the test, the test results will be more than a bug-managed item, it is a small bug mark, click on the bug mark, there will be a record the error number of the input box.
If the test case is unsuccessful, you can enter the ID of the bug found in the Jira in this place, and then a link to the ID will appear below the record, and after clicking on the ID, you can link directly to the Bug's page in Jira.

Entries

VIII. Analysis of test results

Testlink based on the data recorded during the testing process, it provides a wealth of statistical functions, which can be used to analyze and summarize the data in the process of test management. You can go to the test Results Report page by clicking on the "Test results" menu in the home landscape navigation bar, as shown in:

The left column lists the metrics you can choose, all of which are queries based on build, with three types of report formats for all measures.
Normal: report format appears on the right side of the page
MS Excel: After you select the type, the report appears in Excel
Html_email: When this type is selected, the report is sent to the mailbox as email if Testlink is configured with mail features

8.1 Overall Test Plan Progress

Review the overall test situation, which can be viewed based on the test component, the test case owner, and the keyword.

8.2 Based on the report of each version of the tester

8.3 Failed test Cases

Count all test cases where the current test result is failed

8.4 Blocked Test Cases

Count all test cases with current test results as blocked

8.5 test cases that have not been executed

Count all test cases that have not yet been executed

8.6 Charts

By clicking on the chart, you can see the reports generated by Testlink in the form of graphs, which are very intuitive.

8.7 Product demand-based reporting

With this report, you can see the requirements coverage, with the following metrics:
Requirements Overview: Requirements-related information
The need to pass: the need to test through
The wrong requirements:
Lock-In requirements:
Requirements not yet implemented:

Ix. features of ease of Use 9.1 keyword management 9.1.1 creating keywords

Click the Keyword Management menu under the Home Product Management module to create a new keyword. Keywords include: the name of the keyword, the description of the keyword.

9.1.2 Assigning keywords

After you've established your keywords, you can associate keywords with test cases, create keywords, assign the keyword to test cases, click the Assign to test Case button on the Create Keyword page, or click the Assign Keyword menu under the test Cases module on the home page to select the test case in the left-hand case tree. Then select the right side of the corresponding keywords, to be assigned.

Move the keywords in the list of useful keywords to the Assigned keyword list and click the Assign button to complete the Assign keyword action.

9.1.3 assigning good keywords, search for test cases by keyword

Click "Search Test Case" under the home "test Case" module to search by keyword, the right is to search out all the test cases assigned to the keyword, directly click on the front of the "edit", "delete", "Move/Copy" button to perform the actions we need.

9.1.4 Search for required test cases by keyword when performing tests

We create a "15_070916" (can be understood as the build number) keyword, by keyword search for this version of the required test cases, to perform the test.

9.1.5 Edit Delete Test Cases

Go to a Keyword Management page and click the Delete button after a keyword message to delete it.

9.2 Generating test cases directly from test requirements

9.3 Document import, export function 9.4 Report can be exported as Excel

9.5 Customizing 9.5.1 custom Field Management

Click the custom Field Management menu under the home page customization scope, go to the Custom field Management page, click the Create button, and you can create a field as shown in

You can fill in names, callouts, types (including many), and some display conditions. Finally, choose where to use the field, where it can be used, test cases, test plans, and test classifications.

9.5.2 Assigning a custom field

After filling out the good one custom field, you must assign the custom field to use, click the Assign custom field menu under the Home page customization scope, and enter the custom field Assignment page as shown in:

Select the box in front of the custom field and click the Assign button to complete the assignment.

Summary :

Testlink is used for the management of the test process, and by using the functionality provided by Testlink, we can manage the test process from test requirements, test design, to test execution, and it also provides a lot of statistical and analysis of test results. Allows us to start testing work and analyze test results simply.
In this paper, according to their own use and learning, the detailed demonstration of how to use Testlink to carry out the whole process of testing management, a simple introduction of the use of Testlink method. We hope to help you learn the basic functions of testlink, and you can refer to this process and Testlink's help documentation to manage the test process.

Testlink study Four: TestLink1.9.13 Instructions for use