Popular test design tools

As we know, the testing process starts from making a test plan. This document includes all the necessary information: how, when, by who and how often the testing is performed; what methods are used; and what tools are involved.

Why is it so important to choose the tools in advance?

It will optimize the whole process and organize the work properly, all that undoubtedly affects the quality. The same applies to the implementation of test design, that is, the description of test cases.

A test case is a set of actions that describes checking a test product one step at a time with the expected result attached to every step. 

In order to assess the adequacy of their design, there is a concept of test coverage. It displays how thoroughly and well-covered with tests the basic requirements are. 

Positive test cases describe scenarios of product operation according to the way they are indicated in the specifications — for example, the user authorization checking with valid data.

Negative test cases enable checking the adequacy of the product work in case of inputting the wrong information or the failure of one of the components as the authorization with an invalid password.

As a rule, there are more negative test cases than positive ones. 

A combination of test scenarios to check one functional, module, or program component is called a test suite. The process of performing test cases with the indication of test results (passed or failed) is called a test run. It is possible to start any number of test runs from one test suite. 

You can write test cases and combine them into the test sets in any text editor in the form of a table or file folder. However, it is more convenient and rational to use special programs and applications.

The good tool for creating test scenarios allows to:

• describe cases step by step with indicating expected results;
• add attachments;
• combine test cases into test sets;
• start test runs;
• indicate test results;
• receive the final report on test runs.

The functionality of such programs is much broader. However, even the listed minimum helps significantly to organize the testing process.

TestLink and TestRail should be highlighted among all test case-creating tools that win users over with their simplicity in use, broad functionality and availability.

Let's talk about each of them separately and find out why they are so loved on real projects.

Testlink

Testlink is a popular tool for creating, structuring, storing, performing test cases and generating testing reports. One of the main advantages of this test management system is that it is free.

This application does not boast a bright design as TestRail has; it is minimalistic, but still user-friendly.

It is possible to set several access levels for different users. 

Depending on the role, the user can only review test case results, start test runs, add and change test cases, make a test plan or, as in the administrator case, manage the system at all levels.

Testlink allows creating product requirements and attaching test cases to the particular one of them.

It is convenient and helps streamline the project. Furthermore, reading the documentation on the requirements page during a specific test scenario is always possible.

One more benefit of the work in Testlink is infinite capacity. The user can create any number of folders and subfolders with test cases. This advantage helps to structure the project and set it according to the user's preferences.

Work with the program starts with creating the project, setting it and distributing the roles. Then the structure is formed.

After finishing this part of the work, we can proceed to test scenarios writing.

Test case attributes are basic:

• identifier (ID);
• name;
• test description;
• preconditions;
• steps to reproduce;
• expected results;
• severity;
• run method (manual, automated);
• status.

Additionally, the program enables indicating keywords for every test case. It makes navigation through the test plan easier when there are a large number of test cases. Test cases can also contain attachments: images (layouts), text documents (test data, specifications), etc.

Testlink provides the possibility to specify the platform where the testing will be performed. (For example, desktop, mobile devices)

It is clear that some scenarios will be the same for all platforms. In order to avoid test cases duplication, the program allows adding one scenario in several test cases. All the information, such as which scenarios are included in which cases, is displayed on the page.  

When you write test cases, you should consider that in comparison with TestRail, in Testlink, every step and expected results are added separately. It slightly complicates the process of creating test cases, although it significantly improves its readability and facilitates its use.

The reports extraction is of separate notice. This function is necessary to analyze the results of test runs and the test case coverage of requirements. We can make a report on the product version on the testing platforms and every specific user. The report can be as narrowly focused (only failed tests description) as, in contrast, extensive (description of all performing test plan indicators in all product versions.)

TestRail

TestRail is one of the most powerful tools, which opens many possibilities to keep the documentation, organizing, and testing process' implementation. In addition, it is famous for its user-friendliness and broad functionality. 

You can see all advantages of working in TestRail still on the creating a new project stage. There is an extensive settings panel. The user can save all test cases in one repository or divide them into sub-folders, set all access levels for all users, and add roles.

The highly useful function is the possibility of flexible field settings.

We can regulate every field name, type, and place to prepare the system for convenient use in particular project conditions. That is to remove all unnecessary things and add only those that are used in work.

Integrating with the bug-tracking system provides more opportunities for TestRail. 

In that way, we can bind required test cases and their factual results to the tickets in Jira. 

During the test run, in case of detecting defects, TestRail allows creating bug reports without leaving the test case results page. This optimization saves considerable time. 

In order to start the testing process, we create a test run. 

One more benefit to this tool is that it is unnecessary to add all test cases from the set into a run. TestRail is quite flexible and permits to include into the run only those scenarios that are required to be tested. 

You can see all advantages of working in TestRail still on the creating a new project stage. There is an extensive settings panel. The user can save all test cases in one repository or divide them into sub-folders, set all access levels for all users, and add roles.

The highly useful function is the possibility of flexible field settings.

We can regulate every field name, type, and place to prepare the system for convenient use in particular project conditions. That is to remove all unnecessary things and add only those that are used in work.

Integrating with the bug-tracking system provides more opportunities for TestRail. 

In that way, we can bind required test cases and their factual results to the tickets in Jira. 

During the test run, in case of detecting defects, TestRail allows creating bug reports without leaving the test case results page. This optimization saves considerable time. 

In order to start the testing process, we create a test run. 

One more benefit to this tool is that it is unnecessary to add all test cases from the set into a run. TestRail is quite flexible and permits to include into the run only those scenarios that are required to be tested. 

Separately worth noting is the result panel of test runs.

Here everything is simple, demonstrative, intuitive, and transparent. For example, results are displayed in a circular chart where it is clear to see the percent of successful test cases and the failed ones.

Also, the complete list of test cases is displayed with the results for a particular scenario and every section. This demonstrativeness allows quickly analyzing information, providing the process insights, and contributing to the effective management of the project.

Another consideration is reporting. This function is also implemented and widely used in TestRail. A report for a chosen period is generated and sent to an email. In addition, templates can be kept for the following use, which is also very helpful.

TestRail is a paid tool. However, there is a free trial version through which we can assess whether it is suitable for the particular project or it is better to try something else.  

The tools for test case creation can significantly increase the quality of testing. When everything is streamlined, located in one place, and results of passing test cases are demonstrative and well visualized, the possibility of finding defects is higher. The variety of the programs and applications is quite great now, but the reviewed services in this article are indisputable leaders on projects. That is why the ability to use Testlink and TestRail is one of the required skills of the tester.