Testlink test Case management tool general use process

(a) preview

1. Create Project

2. Create requirements (skip)

3. Create plan,

4. Create a use case,

5. Version management (build),

6. Assigning Use cases to requirements (possibly more than one, skipping)

7. Add a use case to a plan

8. Assigning performers to use cases

9. Execution plan/Report bug

10. View analysis Results (generate test Report) (ii) Details 1. Create Project: Test Project management--> Create new test project

The list bar on the left side of the home page has a "test project management" menu with "Create new test Project" in the submenu, which allows you to create new test projects.

At the same time, other submenus in the menu can be used to edit, delete, and set existing user permissions for a test project.

By default, only members of the Admin group have the right to operate on test project.

2. Create demand (Skip): Requirements--Requirement specification

The "Requirements" menu in the list bar on the left side of the home page has "requirement Specification" in the submenu to add the editorial requirements specification.

In the meantime, another item in the menu can specify a test case for the requirement (there will be a way to count the requirements coverage when the results are counted).

A point to note: Each requirement must have a corresponding number of req--in fact, we analyze the requirements and then divide it into one, and the test cases correspond to these req.

By default, only members of the admin group have the power to operate on the requirements.

3. Develop test plan Management--------Test plan Management---Create

L list on the right of the homepage, there is a special "test plan Management" menu, select its submenu "Testplanmanagement", enter the page will appear "Create" button, click to create a new test plan.

4. Create a use case (*): Test Specification--Create test suite--> test Cases Operations-->create

L first need to explain the hierarchy of the Testlink use case tree:

L Test project--test suite--test case

L So before you create a test case, you need to ensure that the test project and test suite that the use case belongs to already exist.

I've already told you how to create a test project, and then you'll explain how to create a test suite.

When the test project has been created, select "Specification" in the horizontal navigation bar, the page appears or the left and right parts of it--the use case tree.

The root node of the L-tree is the test project we created (the top-right corner of the page can toggle the test project, like Mantis).

Click on the test project and the "New test Suite" button on the right side of the page, click to create test suite (testing set – a functional module that can be understood as a test project).

When the test suite is created, refresh the use case tree (left page content, Updatetree), and you can see that the set of tests we just created has appeared in the use case tree.

Click on the test set and the "Create test case (s)" button appears in the right page content, click to create new test cases.

After the test case is created, refresh the use case tree, and you'll see that the testcase we just created appears in the next level of test suite in the use case tree.

Note: Use cases can be specified in versions-because as demand changes, or some other factor, use cases are constantly changing and need to be

L version number to differentiate this change.

L PS: Choose different level, the right side of the page will appear the different kinds of buttons-each button corresponding to the operation and its literal meaning is

l correspond to, for example

A) in the use case tree we have selected a TestProject, and the following button appears on the right page:

New test suite--Creating a testing set

Reorder children--to reorder Children (test suite) for this testing project

Import test suite--Importing testing set

Export all test suites--exports all testing sets

b) We have selected a testsuite in the use case tree, and the following button appears on the right page:

edit--Editing Test Sets

delete--Deleting a test set

move/copy--moving or copying a test set

Reorder children--to reorder the children of the test set

Export Test suite--The set of tests

New Test suite--newly created set

Import test suite--Importing testing set

Create test case (s)--creating the testing cases

Import test Case (s)--Importing testing cases

Export test Case (s)--exporting testing cases

c) We have selected a test case in the use cases tree, and the following button appears on the right page:

edit--editing the current use case

delete--Delete the current use case

move/copy--Move/Copy the current use case

Deactivate This version--sets the current use case version to an invalid state

Create a new version--creates a newer version for the current use case

export--Export Use Cases

5. Version management: builds/releases---Create

6. Assigning Use cases to requirements (skip): Requirements--Assign Requirements

L the list bar on the left side of the home page, with the option "Assign Requirements" in the submenu of "Requirements".

L will go to "specification" similar interface after selecting.

L Select a test case in the left-hand case tree and a list of requirements appears on the right page content.

As we have said earlier, the test case corresponds to one of the req of the requirement.

L TICK the check box in front of the appropriate req and click on the "Assign" button below to complete the assignment of the requirement.

Of course, you can also undo the need to associate with a use case-the page will have a "unassign" button at the same time.

7. Add a use case to the plan (automatically linked to the latest version): Add/remove test cases--> Select Test Cases--Add selected

The menu for "test plan Contents" in the list on the right of the home page has a submenu with "ADD test case (s)" in its submenu.

Click this to enter a page similar to "specification"--but only to the test suite level on the left-hand use case tree.

Select a test suite, and the right page lists all of the test cases that the test set contains, in the case you need to add to the plan.

Check the box in front and click on the "Add selected" button below to add the test case to the test plan you selected.

L Of course, you can also remove the use cases that are added to the plan.

L added to the plan of the test with the yellow bottom, the check box appears after the Remove, tick, click on the "add/removeselected" below to complete the removal operation.

8. Specify the performer for use cases: Assign test Case execution--and Select test Cases--Assign to selected username--Save

The next thing to do is to specify a specific performer for each use case included in the test plan.

l Home, right list, "Test Plan Contents", its submenu has "Assign Test case Execution", select this we can go to the next page, to specify the actual performer for the test cases.

On this page, select test suite or test case in the left-hand tree, the right-hand page will have a drop-down list for you to select the user, select the appropriate person, then check the box in front of the test case and click the button below the right-hand page to complete the assignment.

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

9. Execution plan/Report bug: "Test execution" on the top or "execute Tests" onthe left--> Execute Tests-->submmit Bug if found

We put them together because reporting bugs is done synchronously during execution-that is, we need to report them to our bug management system as soon as we find bugs in the process of executing the use cases.

Before you execute a test plan, you need to create a build version of the test plan--we can do that by date, indicating the date when we executed the test plan, or, of course, other meanings, such as the focus of this test execution.

L list on the right, the "test plan Management" menu, which has a "build Management" in its submenu, select the "Create" button for the page to enter, which is the action to create a new build for the test plan.

L PS: On the top of the page, there is a drop-down list on the right, which is used to select the test plan that is currently being manipulated.

L then we can execute the test plan.

L The "Execute" menu in the horizontal navigation bar, click to go to the execution page.

L This page, the same in Split, the left is a use case tree, the right page content is the main content.

Here's a little bit to illustrate that while execution is ostensibly for a test plan, it actually corresponds to the execution of the test case in the test plan.

L on the left-hand use case tree, select a test suite, the right side of the page will appear in the testing plan, build description, test set description and so on, there is a batch set of the test set contained in the state of the testing case button, namely "Bulk TC status Management". The next step is the details of all the test cases contained in the test set.

The last part of each test case, "notes/description", "result" is required for us to complete the test case after the completion of our own.

When this section is completed, the results are recorded at the beginning of the use case.

L at the same time, the bug management system in the execution of the test case found when the bug ID is recorded here-testlink and Mantis after integration, you can click the mouse into the mantis to see the specific situation of the bug, very convenient.

10. View analysis Results: Test Reports-Check the all kinds of test result and Reports

L Home, results menu in the horizontal navigation bar, click to enter the result viewing interface.

On this page, you can view the results of the execution from a variety of angles-for example, from the angle of requirement coverage, use case state perspective, and so on.

Of course, Testlink also has some other ancillary features, such as "custom field," which you can use to customize a field to work with your use case-for example, we can customize a "priority" field to assign priorities to each use case.

http://www.ibm.com/developerworks/cn/opensource/os-testlink/