Software testing with test cases as the core

At present, there are few methods to compile software test cases in detail in the software test books published in China, and most of the methods are very theoretical descriptions. In addition, the biggest problem is that the method for determining input data of test cases is described as the design method of test cases.

For example, for the test case design method, the most common statements are: equivalence class, boundary value, and causal coefficient. In fact, these are just how to determine the test input data in the software test case design, which is valid for the data control input values in the dialog box. If you describe the method for determining the input data as a test case, the test example designed in this way has limitations.

In fact, writing test cases involves two aspects: Writing Test Case input data, and writing test case entities (including test objectives, test steps, and test expected results ).

Therefore, it is necessary to break down the work of writing test cases into two stages: the first stage is called "Test Case Design", and the second stage is called "test case implementation ". The first phase of the task is how to determine the organizational structure of the test case (modular, phased). modular means that the tested software is divided into various modules, and each module is organized into a test case group. A phased process is to compile software test cases according to different stages of software development, such as unit test cases, system test cases, and acceptance test cases.

The process of writing software test cases.