Program testing system and method

Abstract

The invention provides a program testing system and method for improving program testing efficiency. The method includes: configuring the configuration items required for the function under test of the program under test to complete a diversion; identifying the calling function and the called function, controlling the current call of the calling function to turn to a test-specific function; and controlling the submodule according to the turning The current call turns to control and calls the corresponding test-specific function for testing. The present invention also supports a test evaluation method based on function calls and customizable standards. The invention is helpful for software research and development, especially for C language project research and development, greatly improving the commissioning work efficiency, improving the usability of test operation, and contributing to the improvement of test quality.

Description

Technical field [0001] The present invention relates to the field of software debugging and testing, in particular to a program testing system and method capable of implementing white box testing by describing the debugging process in a form. Background technique [0002] In IT product R&D, software debugging and testing take up a lot of working time. Improving the work efficiency of both will directly speed up the progress of product development. Improving the quality of both will also directly improve product quality and reduce R&D risks. A formal description of software debugging and testing operations is a necessary condition for improving efficiency. However, current mainstream white box testing tools generally only implement formal descriptions of test operations, and rarely describe debugging operations as scripts and automatically convert them into test cases for repeated execution. [0003] At present, the main white-box testing tools in this field, such as CodeTest for ...

AI Technical Summary

Problems solved by technology

After the system under test is running, use cases cannot be written and run online, nor can its running results be viewed online to improve test design, which ultimately makes it difficult to convert debugging records into practical test cases

[0008] 2. The debugging operation is very random, and it is difficult to convert it into an effective test case

[0009] Even if there was a technique to record all debug operations as scripts, recording all debug records would be too cumbersome and difficult to maintain use cases

If only local operations are taken, it is easy to lose the correlation before and after the operation

At the same time, debugging is aimed at the code line, because the source code is volatile, which also makes it difficult to maintain the use case

[0010] Moreover, the debugging operation is very casual. If the direct conversion also makes the test script very casual, it will make it difficult to evaluate the work effect.

Images