How to Manage Requirements, Execute Test Cases and Generate Reports Using TestLink – Tutorial #2

Warmly welcome to the second part of our “Navigating the TestLink Test Management Tool” Tutorial series. If you’ve skipped Part-1, it can be found here:Getting Started with the TestLink Test Management Tool

In our last tutorial, we discussed TestLink’s installation process, creating a Test Plan, and crafting Test Cases.

Today, we will delve into essential features provided by TestLink, including handling requirements, executing test cases, and producing test reports.

So, let’s begin!

Establishing Users and Allocating Roles in TestLink

TestLink sets various access norms based on user roles. The following are the pre-set roles defined in TestLink:

• Guest: This role is only permitted to view test cases and metrics without any editing rights.
• Tester: Testers are eligible to implement test cases and survey test metrics.
• Senior Tester: Senior Testers have the capability to view, alter, create, and erase test cases. They can additionally execute test cases and examine metrics. Nonetheless, they lack the privilege to formulate a Test Plan.
• Leader & Admin: Both Test Leaders and Admins have identical rights, including the capacity to view/alter/create/delete Test Plans and Builds, execute test cases, delete a project, and designate user roles and permissions. Moreover, Admin users are given the rights to modify the product by creating, deleting, and updating projects.

You can also establish tailor-made roles with distinct permissions, as illustrated in the image below:

In this next section, we provide detailed instructions on creating users and allocating user roles: Follow these guidelines to create a user and assign different roles:

Step #1) Click on the Users/Roles link situated in the TestLink navigation bar to make your way to the Users/Roles page.

Step #2) Once you are on the Users/Roles page, click on the “Create” icon.

Step #3) Fill in the username, user’s particulars, and role in the displayed form, then hit the “Save” icon.

Step #4) To allocate a Test project role to a user, navigate to the “Assign Test Project Roles” tab.

Step #5) Select the Project name and Role for the User from the drop-down lists, as demonstrated in the figure.

You can also navigate to the “Assign Test Plan Roles” tab and attribute roles to users for particular Test Plans.

Penning Requirements

A requirement is a prerequisite or obligation the software must meet or performance.

Here are the steps to pen requirements in TestLink:

Step #1) Click on the Requirements link in the navigational panel to redirect you to the Requirements page.

Step #2) Once on the Requirements page, click the “Create” icon.

Step #3) Fill in the Document ID, Title, and Description for the requirement, as shown in the figure, and tap on the “Save” icon.

Step #4) The requirement specification will be created and presented in the left-side panel.

Step #5) Click on the “Create” icon below Requirements Operations.

Step #6) Fill in all the details as shown in the figure, and hit the “Save” icon.

Attaching Requirements to Test Cases

In TestLink, one can append requirements to test cases, a vital function for keeping track of test coverage based on stipulations. Test reports can aid in detecting requirements that are yet to be covered and enable you to incorporate them into test suites for optimal test coverage.

Follow these step-by-step procedures to append a requirement to a test case:

Step #1) Open the relevant test case from the Test specification division.

Step #2) Click on the “Requirements” icon on the test case, as shown in the illustration, to open the requirements dialogue.

Step #3) From the drop-down box, choose the requirements specification and tick the requirement checkbox as seen in the image.

Step #4) Tap the “Assign” button to add the chosen requirement to the assigned requirements section.

The requirement has been successfully attached to the test case.

Implementing Test Cases

Within TestLink, you have the ability to implement test cases and alter their execution status. A test case status can be denoted as “passed,” “failed,” or “blocked.” Initially, the status is set to “not run,” however, once updated, it cannot be reverted back to “not run” status.

Follow these directions to implement a test case:

Step #1) Hit the “Test Execution” link in the navigation bar to proceed to the Test Execution panel.

Step #2) Opt for the desired test case from the