Lesson Notes: A summary summary of software testing knowledge points

Unit Test Content:

In the unit test, the tester needs to understand the module's I/O condition and the logical structure of the module according to the detailed design specification and the source program list, mainly using the test case of white box test, supplemented by the test case of black box test, so that it can identify and respond to any reasonable input and unreasonable input.

(1) Module interface test: At the beginning of the unit test, the data stream of the module to be tested should be measured. The test project includes: whether the input parameters of the module are called correctly, whether the parameters entered to the submodule are correct when the module calls the Submodule, and whether the definition of global quantities is consistent in each module. Consider whether the file attributes are correct, whether the open and close statements are correct, whether the buffer capacity matches the record length, whether the file was opened before the read and write operation, whether the file was closed when the file was processed, the text/input error, whether the I/O error was checked and handled. (2) Local data structure test. Test items include: Incorrect or inconsistent data type descriptions, use of variables that have not been assigned or initialized, default values for errors or errors, incorrect spelling or writing of variable names, inconsistent data types, and global data impact on modules. (3) Path test. The test project includes selecting the appropriate test case, testing the important execution path in the module, and designing the test case to find errors due to incorrect calculations, incorrect comparisons, or abnormal flow of control, and testing the basic execution paths and loops to find a large number of path errors. (4) Error handling test. Includes: Whether the description of the error is difficult to understand, whether the description of the error locates the error, whether the error displayed matches the actual error, the correctness of the error condition, or whether the error condition has caused systematic intervention before the error is processed. (5) Boundary test. Include: note the likelihood of an error in the data flow, the control flow that is exactly equal to, greater than, or less than the determined comparison value. Carefully select test cases for these places and test them carefully. If there is a requirement for the operating time of the module, a critical path test is also required to determine the factors that affect the runtime of the module in the worst-case and mean-time sense. Steps for unit testing:module is not a separate program, when considering the test module, at the same time to consider its contact with the outside world, with some auxiliary modules to simulate the module connected with the other modules. Includes: Driver module, stub module. If a module to complete a variety of functions, you can consider this module is composed of several small programs. Each of these small programs must first do the unit test to do the work, the key modules also do performance testing. For procedures that support some standard procedures, the interconnection test should be initiated. This is specifically referred to as module testing to differentiate unit tests.

Lesson Notes: A summary summary of software testing knowledge points