Method and system for testing drive software

Abstract

The disclosed testing method for drive software comprises: generating the test case on background to describe the testing process; generating test script on background to describe the case including the extended command script to send to the single board; using the latter to analyze the script to obtain and execute corresponding extended function. Wherein, the said extended function includes an interface packaging function.

Description

technical field [0001] The invention relates to a testing technology of driving software, in particular to a testing method and a testing system of driving software. Background technique [0002] As we all know, the driver software provides the driving function of the physical device, and shields the implementation details of the device driver from the upper layer. At present, the upward operation interface of the driver software has not yet formed a unified interface among various products. For example, MD 5500 products and ESR products use similar FLASH chips and basically use the same functions, but the interfaces of the driver software are very different, and the number of parameters and parameter positions of the interfaces are different. [0003] When implementing the test design of the driver software, because the functions completed by the object to be tested are basically fixed (such as sending data, receiving data, configuration, verification, loopback, etc.), it ...

AI Technical Summary

Problems solved by technology

[0007] At present, when testers conduct test design and implementation, they basically discuss the matter as it stands without considering the reuse of test work. The completed deliverables, including test projects, test cases, test scripts, and test codes, can only be used in a certain driver of the product. It is basically not reusable on the driver modules of other products that perform the same functions; resulting in most of the achievements not being inherited by related products and related modules; or even if they can be partially reused, more work needs to be invested for adaptability Revise

[0008] Since the problem of test design reuse is rarely considered, testers only test a certain module of a certain product, and do not have experience in reusing related products and related modules

Moreover, limited by the tester's test level and test technology accumulation, the completeness of the test design is poor and the consideration is not comprehensive, and test points are often missed

[0009] In addition, when testers design and implement tests, they are very random and the process is difficult to constrain

[0010] To sum up, the existing testing work has the defects of low reusability of driving software test design, poor test completeness, incompleteness, and poor process standardization.

[0011] In the prior art, for the test of the driver software, it basically adopts the mode of test command to complete, and the TCL (Tool Command Language, Terminal Control Language) interpreter is not embedded in the application program. The shortcoming of this mode is that the test The process is solidified in the execution of the command, it is not easy to expand, and the degree of support for automated testing is not enough

Images