Shulou(Shulou.com)06/01 Report--

The first part is use case writing.

The content of the use case is obtained from the test case design, and then implemented in the document according to the use case writing specification, which is the relationship between form and content. A good test case must contain

There is enough content to divide the content into eight elements, and as long as the eight elements are written completely and accurately, this use case will be better written (it feels like a three-paragraph filling duck in a primary school composition).

Eight elements of a general use case: test project, use case number, test title, importance level, preset condition, test input, operation procedure, expected output.

Description:

1) on the level of importance:

The importance levels of use cases are generally divided into three levels: high, medium, and low, which will be divided according to the actual situation. In general, the high level corresponds to the use cases that ensure the basic functions, core business, important features, and high frequency of actual use of the system; the middle level corresponds to the test cases with high and low importance; the low level corresponds to the test cases of modules or functions that are not used frequently and have little impact on the business functions of the system. The importance level of the RPA robot use case is related to the importance level of the corresponding requirements. The importance levels of requirements are generally divided into high, medium and low. Dividing the importance levels of requirements is conducive to iterative development, and different requirements are realized successively. The importance level of the use case is also related to the test purpose of the use case, and the test case for the normal situation is more important than the use case for the exception.

2) expected output:

The expected output is a very important part of the test case. If you want to judge whether the tested object is working properly, you need to judge by the expected output. Once the expected output is inaccurate or incomplete, the role of the entire test case will be greatly reduced.

3) doubt: a. Does each test case have to be written in detail?

The purpose of writing test cases is twofold: one is to help the use case designer consider the use case more comprehensively; the other is to provide it to the people who execute the test case. Therefore, the extent to which the test case is written, whether it is detailed or simple, has a lot to do with who executes the test case. If the use case is executed by the use case designer, it can be written simply, such as the test number, test title, and importance level. If the use case is cross-executed for testers in your own group, then the test case should be written in a little more detail. If the use case is for others to execute, such as outsourcing the execution of the test case, then the test case needs to be written in great detail.

You can consider the following three aspects when writing the expected output:

1. Interface display: after the execution of the operation steps, you can see what is displayed on the interface, such as the test of the registration function, enter the registration information, click to register, and you will see the message of successful registration on the interface.

two。 Database changes: after the completion of the operation steps, the records in the database will change accordingly, such as the test of the delete function. After clicking to delete, the record in the database will be deleted.

3. Changes in related information: that is, after the execution of the operation steps, some information related to the tested object will change, such as the test of the logout function. After clicking the logout, the previously accessible pages will no longer be accessible.

Part II defect management

1. Concept

The basic concept of defect: defect, fault, failure.

Defect: a deviation that exists in the software that can be activated and exists inside the software in a static form, equivalent to bug

Fault: the state that occurs during the operation of the software, which can cause unexpected conditions. If left unhandled, it can cause failure, which is a dynamic behavior.

Failure: the result of external abnormal behavior produced when the software is running, the performance is inconsistent with the needs of the user, the function is terminated, and the user is unable to complete the desired application.

The concept of defect report form

Defect report is the beginning of any defect modification. After the tester finds a defect during the test execution, the tester records the relevant information about the defect in the defect report. Then, notify the developer for confirmation and repair.

Defect report form can be used as the data basis for later defect measurement, but also for the assessment of the whole product.

two。 Defect management process

The defect management process of software testing tools is consistent with the life cycle of defects. Of course, there are some zombie defects, that is, defects that will never die (it is a legacy state in the defect management tool, and it has been left behind because of system history, and no one cares about every version upgrade).

3. The goal of defect management

1) defect tracking

2) defect analysis

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.