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

For testers with some testing experience, they all summarize or master some minority testing skills. Rapid testing is a group of risk-based testing methods, which aims at some common software defects. Generally, it does not need a lot of testing time, and a batch of errors can be found in a short time only by knowing the basic situation of the product.

The following are some of the rapid testing methods summarized by test expert James Bachd in rapid software testing, which are supplemented and adjusted here, and synchronously updated to our test knowledge sharing library, which can be added, deleted, changed and checked when used.

The method name aims at the risk testing method Happy path software fails in a typical user scenario to check whether its performance meets the expectations of the user and the product team, without causing users to feel confused or uncomfortable to interrupt and properly handle all interruptions is a difficult development task, many software will be interrupted by interruptions usually by clicking the "cancel" button, closing the dialog box, and so on. Corner-digging software can not correctly handle some abnormal situations to start a software operation, and then destroy the resources that the operation depends on, such as deleting the files it will access, shutting down the network services it will access, starting another program to lock the database tables it wants to modify, and so on. The software should handle these exceptions reasonably so as not to cause serious faults. The software cannot correctly handle the changes of the data. Configure the parameters of the software with some values, and modify these parameter values during the operation of the software to check whether the software can accept changes in the data. When certain operations are performed repeatedly, the software may make mistakes and repeat a set of operations many times. Using concurrent processes and nested structures to test the continuous use of software there may be resource leaks, error accumulation and other defects that can be exposed for a long time to test a software for a long time, do not close it. In this process, the resources used by some tools, including CPU, memory, OS handle, database connection, etc., are used to find the defects in the use of resources in the software. In addition, it is important to pay attention to whether the functionality of the software becomes incorrect or unstable with the extension of testing time. Function interaction different functions may be written by different programmers, their logic may be inconsistent to call each other or share a set of functions of data, and then oppress them with exaggerated data or operations to expose problems in the interaction click help software can not correctly display the functions of context-sensitive help roaming software, such as the current function provides context-sensitive help, the tester calls up the help The content displayed in the check does describe the current function, and can help users complete the current operation input constraint tool programmers may make mistakes when writing input check code, and some wrong input data will pass the check, thus endangering software testers to find the software's input variables and try various means to make illegal data pass the check code.

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.