A dynamic testing method for embedded software based on source code piling

Abstract

The invention discloses a dynamic testing method of embedded software based on piling of source code. On the basis of the source code of the original embedded software, a test agent module is added, and the test agent is distributed in the underlying data sending and receiving interface of the original embedded software source code. The stub function provides a data collection and control mechanism, and provides a serial port communication mechanism with the computer test server software to realize the computer test server software to control the embedded software to carry out automatic test functions, which can solve the above-mentioned problems of large differences between the tested software and the actual operating environment. Simulate user behavior to realize automated dynamic testing of embedded software.

Description

technical field [0001] The invention relates to an embedded software dynamic testing method based on source code piling. Background technique [0002] With the development of embedded software and hardware technology, a variety of consumer electronics products such as smart phones, tablets, etc. use this technology to achieve various complex functions. The scale of embedded software codes is becoming larger and larger, and the functions are becoming more and more complex. In order to improve the stability and reliability of embedded software, a lot of testing work needs to be done during the software development and testing phase to find potential software problems. Testing will take up a lot of time during the development of embedded devices. In order to improve the efficiency of testing and reduce simple and repetitive manual testing operations, embedded automatic testing tools are introduced, and the embedded software for testing. [0003] The working principle of the c...

AI Technical Summary

Problems solved by technology

[0007] 1) Pure software automated testing tools increase the amount of source code of the system under test in terms of instrumentation and preprocessing, and run in an embedded system with relatively insufficient IO, memory, and CPU resources. These additional codes increase The burden of the system may even cause link failure or operation failure. The environment where the user program runs is different from the actual environment. Performance analysis of a certain function cannot be done, and only module or unit coverage tests can be done.

The lexical / grammatical analysis of the compiler generates a lot of stub information, which leads to an increase in the size of the final generated embedded program and a decrease in system performance, which makes the tested software and the actual operating environment quite different;

Images