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.