CN108132876B - Embedded software object code unit testing method based on injection mode - Google Patents
Embedded software object code unit testing method based on injection mode Download PDFInfo
- Publication number
- CN108132876B CN108132876B CN201711285257.6A CN201711285257A CN108132876B CN 108132876 B CN108132876 B CN 108132876B CN 201711285257 A CN201711285257 A CN 201711285257A CN 108132876 B CN108132876 B CN 108132876B
- Authority
- CN
- China
- Prior art keywords
- test
- address
- function
- tested
- bintest
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention provides an embedded software object code unit testing method based on an injection mode; firstly, injecting a unit test program BINTEST into an unused program Flash storage space of the target code, modifying a timed interrupt service program inlet of the target code, and replacing the original timed interrupt service inlet with the inlet of the unit test program BINTEST. The unit test program BINTEST realizes the interaction between a test state machine and an upper computer. Automatic test software for installing automatic unit test on the upper computer has the functions of: acquiring information of a tested function, input setting and output expectation in a test script; automatic interaction with the unit test program BITTEST: after response information of the unit test program BINTEST is obtained according to the variable value reading interaction request, the measured output of the unit test is obtained through analysis, and then the measured output is compared with the output expectation in the script. The method has the characteristics that the difference between the delivery state of the test object and the delivery state of the target code is small, and the method accords with the environment in real use.
Description
Technical Field
The invention relates to a test and verification technology of an embedded software unit, in particular to an embedded software object code unit test method based on an injection mode.
Background
Software unit testing is an important means for ensuring software quality safety, and strict unit testing verification is particularly required for high-safety embedded software. The current common software unit test is mainly based on source code: and assembling and compiling the source code and the test module, and testing in a simulation environment or a target environment. However, the environment for software delivery is different from the environment for unit test, such as the unit test using Cantata, which usually uses the CPU operation of the desktop computer instead of the target computer; the Cantata can also perform unit testing in a target environment, and the allocation space and the allocation time (due to instrumentation) of the actual target code are inconsistent with those in actual use by compiling the function source code and the testing module in a combined manner and downloading the function source code and the testing module into the target machine for operation.
Disclosure of Invention
In order to be consistent with the real use environment as much as possible, the invention provides an embedded software target code unit testing method based on an injection mode, and the unit testing method is realized under the condition that the use environments of the target code are consistent as much as possible. The technical scheme adopted by the invention is as follows:
an embedded software object code unit testing method based on an injection mode comprises the following steps:
step S1, injecting the unit test program BINTEST to the unused Flash memory space of the target code, hijacking the timed interrupt service program entrance of the target code, and replacing the original timed interrupt service entrance of the target code with the entrance of the unit test program BINTEST to achieve the purpose of actually executing the unit test program BINTEST by the timed interrupt service.
The object code is a software program to be tested and is written in a program Flash of the object machine in a binary representation. And after the embedded system is powered on, automatically executing the object code.
And step S2, automatically and sequentially inquiring the test script under the appointed project directory by the upper computer automation unit test software AutoTest, and acquiring the information of the tested function, the input setting and the output expectation in the test script.
Step S3, automatically interacting the upper computer automatic unit test software AutoTest and the unit test program BINTEST: packing and sending an interactive request data packet of 'set variable value' according to address data in 'input setting' information; packing and sending an interactive request data packet for calling the tested function according to the address data in the information of the tested function; packing and sending an interactive request data packet of 'reading variable values' according to address data in 'output expectation' information; and receiving response information corresponding to the unit test program BINTEST.
Step S4, after the upper computer automation unit test software AutoTest obtains the response information of the unit test program BINTEST according to the variable value reading interaction request, the actual measurement output of the unit test is obtained through analysis, then the actual measurement output is compared with the output expectation in the script, the conclusion whether the unit test passes or not is obtained, the test script file is displayed and written back, and the step S2 is carried out until all test cases in the test script are executed; the next test script is then queried until all test scripts have been processed.
Further, in step S1, the unit test program BINTEST implements interaction between a test state machine and an upper computer, and the functions include: setting variable values, calling a function to be tested and reading the variable values.
Further, in step S2, the upper computer automation unit test software AutoTest reads the test script, and if only the variable information in the test script does not have the address information, reads the map mapping file corresponding to the test object code, finds the address information, and if no address information exists, pops up an error prompt.
Further, the unit test program BITTEST interacts with the upper computer in a communication mode, and the protocol of the communication data packet comprises: protocol header, length, command word, address, value, and checksum.
Further, the method for setting the variable value comprises the following steps:
and the unit test program BINTEST judges that a complete data packet is received according to the protocol header and the length, and checks and verifies the data packet. After the data packet passes verification, if the command word is a command word for setting variable values, analyzing the two subsequent data as a setting address and a setting value, and setting the test state machine to be a setting variable value state; setting address in RAM space range, writing the RAM memory unit of the address into the set value by unit test program BINTEST; finally, interactive response is carried out: and packaging and communicating the set variable value return command word, the set address and the read address value to the upper computer.
Further, the method for calling the tested function comprises the following steps:
and the unit test program BINTEST judges that a complete data packet is received according to the protocol header and the length, and checks and verifies the data packet. After the data packet is verified, if the command word is a command word for calling the function to be tested, analyzing 1 piece of data behind the command word as a function address, and setting a test state machine to be in a state for calling the function to be tested; the function address is in the program Flash space range and is consistent with the actual physical address of the tested function. The unit test program BINTEST transfers the address to a function pointer, and then the function pointer is used for realizing the calling execution of the tested function; finally, interactive response is carried out: and packaging, communicating and sending the command word for calling the tested function and the function address to an upper computer.
Furthermore, when the test state machine is in the state of calling the function to be tested, the protocol packet of calling the function to be tested can be continuously received, and the next function to be tested is continuously called.
Thus, some component tests can be carried out, such as continuous processing of a signal, and the design can support continuous operation and test final results after the acquisition function, the diagnosis function, the fault confirmation function and the filtering function are carried out.
Further, the method for reading the variable value comprises the following steps:
and the unit test program BINTEST judges that a complete data packet is received according to the protocol header and the length, and checks and verifies the data packet. After the data packet is verified, if the command word is a read variable value command word, analyzing 1 piece of data behind the command word as a read address, and setting a test state machine to be a read variable value state; the 'reading address' is in the RAM space range, and the unit test program BINTEST realizes reading the RAM memory unit of the address; finally, interactive response is carried out: and (3) returning the read variable value to the command word, the read address and the read address, packaging, communicating and sending to the upper computer.
The response refers to the return of the unit test program BINTEST to the automatic unit test software AutoTest of the upper computer.
Further, in step S3, an interactive request of "set variable value" is performed to obtain an interactive response, and it needs to be determined whether the command word in the response packet is a "set variable value return command word"; if yes, further judging whether the 'set address' and the 'read value of the address' accord with the information in the interactive request, if yes, automatically carrying out the interactive request of the next 'set variable value', until all 'input set' information in the test script is processed, and carrying out the interactive request of 'calling the tested function'. If the two judgments are not, the execution failure is marked in the test result.
Further, in step S3, an interactive request for "calling the function to be tested" is performed to obtain an interactive response, and it needs to be determined whether the command word in the response packet is "call the function to be tested and return the command word"; if yes, further judging whether the function address accords with the information in the interactive request, if yes, automatically carrying out the next interactive request for calling the tested function until the information processing of all the tested functions in the test script is finished, and carrying out the interactive request for reading the variable value; if the two judgments are not, the execution failure is marked in the test result.
Further, in step S3, an interactive request of "read variable value" is performed to obtain an interactive response, and it needs to be determined whether the command word in the response packet is a "read variable value return command word"; if so, further judging whether the read address conforms to the information in the interactive request, if so, taking the value of the read address as actual measurement output to be used in step S4, automatically carrying out the next interactive request for reading the variable value until the information processing of all the read variable values in the test script is finished, and carrying out step S4; if the two judgments are not, the execution failure is marked in the test result.
The invention has the advantages that: although the method adds new codes in the tested target code software and hijacks an interrupt service interface, the method has no influence on unit test, the tested function is not modified, the tested function is changed to be in accordance with the environment in real use, including the position of a target CPU in Flash and periodic calling, and the defects in the actual use of the software can be further discovered.
Drawings
FIG. 1 is a flow chart of a unit testing method of the present invention.
FIG. 2 is a schematic diagram of a test script with address information according to the present invention.
Detailed Description
The invention is further illustrated by the following specific figures and examples.
Software unit testing is generally mainly based on source code: and assembling and compiling the source code and the test module, and performing unit test in a simulation environment or a target environment. The invention carries out unit test based on the object code, does not need to compile the source code, but injects a section of unit test program BINTEST into the object code, hijacks a timed interrupt service entrance, and interacts with an upper computer to complete the test.
The working process of the embedded software object code unit testing method based on the injection mode is shown in figure 1, and the implementation process of the method is divided into four steps:
Step 1.1: firstly, judging whether a packet of complete data is received or not, judging according to a protocol header, a length and a checksum, and if the checksum passes, receiving the packet of complete data.
Step 1.2: entering different states for processing according to the command word:
a) the command word is a 'set variable command word', and is processed as follows:
first, the next 2 data are resolved into "set address" and "set value";
then, judging whether the 'set address' is in the RAM space range, if the condition is false, performing interactive response: communication sending fault information data packet: setting an address out of RAM range command word; otherwise, writing the RAM memory unit of the address into a set value.
Finally, interactive response is carried out: and packaging and communicating the set variable value return command word, the set address and the read address value to the upper computer.
b) The command word is 'call to the tested function command word', and is processed as follows:
firstly, resolving 1 data as 'function address';
then, judging whether the function address is in the space range of the program Flash, and if the address long word value is not 0xFFFFFFFF in the program Flash, performing interactive response: communication sending fault information data packet: the function sets an error command word; otherwise, the address is transferred to a function pointer, and then the call execution of the tested function is realized through the function pointer.
Finally, interactive response is carried out: and packaging, communicating and sending the command word for calling the tested function and the function address to an upper computer.
Function type default types are: the parameter is null and returns null. And various function types can be designed and different command words are distributed. For functions with parameters or return values, the transfer is performed by using global variables not used by the software under test.
Such as:
Case FuncType_R_INT16_I_INT16_INT16:
pFunc_R_Int16_I_Int16_Int16 = addressFunc;
INT16_40008000 =
pFunc_R_Int16_I_Int16_Int16(INT16_40006000, INT16_40006002)；
when the state is in the 'calling tested function state', receiving a 'calling tested function' protocol packet, and continuously calling the next tested function; this allows for component testing, such as testing the results of a signal processed through a number of functions, such as inputting, converting, diagnosing, selecting, and filtering.
c) The command word is a 'read variable value command word', and is processed as follows:
firstly, 1 piece of resolved data is a read address;
then, judging whether the 'read address' is in the RAM space range, if the condition is false, performing interactive response: communication sending fault information data packet: reading a command word with an address exceeding the RAM range; otherwise, reading the RAM memory unit of the address.
Finally, interactive response is carried out: and (3) returning the read variable value to the command word, the read address and the read address, packaging, communicating and sending to the upper computer.
Step 2, testing software AutoTest of an upper computer automation unit to obtain information such as a tested function, an input sequence, an output expectation and the like in a test script; if the test script has no address information but only variable information, reading a map file (mapping file) corresponding to the test target, searching the address information, and forming an intermediate file: "test script with address information", see fig. 2, if there is no address information, an error prompt is popped up.
And 3, automatically interacting the upper computer automatic unit test software Autotest and the unit test program BINTEST:
a) sending a 'set variable' communication data packet according to a sequence in the script, judging whether the setting is successful or not after obtaining a return data packet, and if the setting is failed, marking that the test is not successfully executed, and carrying out the next case; otherwise, sending the next communication data packet of the set variable in sequence until all the set variables are finished.
b) Sending a communication data packet of 'calling a tested function' according to a sequence in the script, judging whether the setting is successful or not after obtaining a return data packet, and if the setting is failed, marking that the test is not successfully executed, and carrying out the next use case; otherwise, sending the next communication data packet of calling the tested function in sequence until all the communication data packets of calling the tested function are finished.
c) And sending the 'read variable' communication data packet according to the sequence in the script to obtain a return data packet, and then sending the next 'read variable' communication data packet according to the sequence until all 'read variables' are finished.
And 4, comparing the value of the unit test output variable obtained by the automatic unit test software with the output expectation in the test script to obtain the conclusion whether the unit test passes, and displaying and writing back the test script file. Then, carrying out the next test case until all the test cases in the test script are executed; the next test script is then queried until all test scripts have been processed.
The method has the characteristics that the difference between the delivery states of the test object and the target code is small, the method accords with the environment in real use, and the defects in actual use of software can be found by the target CPU, the position in Flash and the periodic calling.
Claims (11)
1. An embedded software object code unit testing method based on an injection mode is characterized by comprising the following steps:
step S1, injecting the unit test program BINTEST to the unused Flash memory space of the target code, hijacking the timed interrupt service program entrance of the target code, and replacing the original timed interrupt service entrance of the target code with the entrance of the unit test program BINTEST to achieve the purpose of actually executing the unit test program BINTEST by the timed interrupt service;
step S2, automatically and sequentially inquiring a test script under a specified project directory by the upper computer automation unit test software AutoTest, and acquiring information of a tested function, input setting and output expectation in the test script;
step S3, automatically interacting the upper computer automatic unit test software AutoTest and the unit test program BINTEST: packing and sending an interactive request data packet of 'set variable value' according to address data in 'input setting' information; packing and sending an interactive request data packet for calling the tested function according to the address data in the information of the tested function; packing and sending an interactive request data packet of 'reading variable values' according to address data in 'output expectation' information; receiving response information corresponding to a unit test program BINTEST;
step S4, after the upper computer automation unit test software AutoTest obtains the response information of the unit test program BINTEST according to the variable value reading interaction request, the actual measurement output of the unit test is obtained through analysis, then the actual measurement output is compared with the output expectation in the script, the conclusion whether the unit test passes or not is obtained, the test script file is displayed and written back, and the step S2 is carried out until all test cases in the test script are executed; the next test script is then queried until all test scripts have been processed.
2. The injection based embedded software object code unit testing method of claim 1,
in step S1, the unit test program BINTEST implements interaction between a test state machine and an upper computer, and the functions include: setting variable values, calling a function to be tested and reading the variable values.
3. The injection based embedded software object code unit testing method of claim 1,
in step S2, the upper computer automation unit test software AutoTest reads the test script, reads the map mapping file corresponding to the test target code if only the variable information in the test script has no address information, finds the address information, and pops up an error prompt if no address information exists.
4. The injection based embedded software object code unit testing method of claim 2,
through communication mode interaction, the protocol of the communication data packet comprises: protocol header, length, command word, address, value, and checksum.
5. The injection based embedded software object code unit testing method of claim 2,
the variable value setting method comprises the following steps:
the unit test program BINTEST judges that a complete data packet is received according to the protocol header and the length, and checks and verifies the data packet; after the data packet passes verification, if the command word is a command word for setting variable values, analyzing the two subsequent data as a setting address and a setting value, and setting the test state machine to be a setting variable value state; setting address in RAM space range, writing the RAM memory unit of the address into the set value by unit test program BINTEST; finally, interactive response is carried out: and packaging and communicating the set variable value return command word, the set address and the read address value to the upper computer.
6. The injection based embedded software object code unit testing method of claim 2,
the method for calling the tested function comprises the following steps:
the unit test program BINTEST judges that a complete data packet is received according to the protocol header and the length, and checks and verifies the data packet; after the data packet is verified, if the command word is a command word for calling the function to be tested, analyzing 1 piece of data behind the command word as a function address, and setting a test state machine to be in a state for calling the function to be tested; the 'function address' is in the program Flash space range and is consistent with the actual physical address of the tested function; the unit test program BINTEST transfers the address to a function pointer, and then the function pointer is used for realizing the calling execution of the tested function; finally, interactive response is carried out: and packaging, communicating and sending the command word for calling the tested function and the function address to an upper computer.
7. The injection based embedded software object code unit testing method of claim 2,
when the test state machine is in the state of calling the function to be tested, the protocol packet of calling the function to be tested can be continuously received, and the next function to be tested is continuously called.
8. The injection based embedded software object code unit testing method of claim 2,
the method for reading the variable value comprises the following steps:
the unit test program BINTEST judges that a complete data packet is received according to the protocol header and the length, and checks and verifies the data packet; after the data packet is verified, if the command word is a read variable value command word, analyzing 1 piece of data behind the command word as a read address, and setting a test state machine to be a read variable value state; the 'reading address' is in the RAM space range, and the unit test program BINTEST realizes reading the RAM memory unit of the address; finally, interactive response is carried out: and (3) returning the read variable value to the command word, the read address and the read address, packaging, communicating and sending to the upper computer.
9. The injection based embedded software object code unit testing method of claim 1,
in step S3, an interactive request of "set variable value" is performed to obtain an interactive response, and it is necessary to determine whether the command word in the response packet is a "set variable value return command word"; if yes, further judging whether the set address and the value of the read address conform to the information in the interactive request, if yes, automatically carrying out the interactive request of the next set variable value until all the input set information in the test script is processed, and carrying out the interactive request of calling the tested function; if the two judgments are not, the execution failure is marked in the test result.
10. The injection based embedded software object code unit testing method of claim 1,
in step S3, an interactive request "call the function to be tested" is performed to obtain an interactive response, and it is necessary to determine whether the command word in the response packet is "call the function to be tested and return the command word"; if yes, further judging whether the function address accords with the information in the interactive request, if yes, automatically carrying out the next interactive request for calling the tested function until the information processing of all the tested functions in the test script is finished, and carrying out the interactive request for reading the variable value; if the two judgments are not, the execution failure is marked in the test result.
11. The injection based embedded software object code unit testing method of claim 1,
in step S3, an interactive request of "read variable value" is performed to obtain an interactive response, and it is necessary to determine whether the command word in the response packet is a "read variable value return command word"; if so, further judging whether the read address conforms to the information in the interactive request, if so, taking the value of the read address as actual measurement output to be used in step S4, automatically carrying out the next interactive request for reading the variable value until the information processing of all the read variable values in the test script is finished, and carrying out step S4; if the two judgments are not, the execution failure is marked in the test result.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711285257.6A CN108132876B (en) | 2017-12-07 | 2017-12-07 | Embedded software object code unit testing method based on injection mode |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711285257.6A CN108132876B (en) | 2017-12-07 | 2017-12-07 | Embedded software object code unit testing method based on injection mode |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108132876A CN108132876A (en) | 2018-06-08 |
| CN108132876B true CN108132876B (en) | 2021-03-19 |
Family
ID=62389196
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711285257.6A Active CN108132876B (en) | 2017-12-07 | 2017-12-07 | Embedded software object code unit testing method based on injection mode |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108132876B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110850788A (en) * | 2019-12-06 | 2020-02-28 | 中国航发控制系统研究所 | Multi-electric distributed control system architecture for aircraft engine |
| CN112597007B (en) * | 2020-12-14 | 2023-10-03 | 中国航发控制系统研究所 | Integrated test integrity analysis method for embedded software |
| CN113296653B (en) * | 2021-07-27 | 2021-10-22 | 阿里云计算有限公司 | Simulation interaction model construction method, interaction method and related equipment |
| CN114816558B (en) * | 2022-03-07 | 2023-06-30 | 深圳市九州安域科技有限公司 | Script injection method, equipment and computer readable storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103279415A (en) * | 2013-05-27 | 2013-09-04 | 哈尔滨工业大学 | Embedded software test method based on combinatorial test |
| CN106055469A (en) * | 2016-05-19 | 2016-10-26 | 中国科学院软件研究所 | System and method for mobile terminal application testing based on code injection |
| CN106445803A (en) * | 2016-08-17 | 2017-02-22 | 中国航空工业集团公司西安飞行自动控制研究所 | Security-critical embedded software target code coverage analysis method |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10078574B2 (en) * | 2006-09-25 | 2018-09-18 | Typemock Ltd. | Methods and systems for isolating software components |
| WO2012124841A1 (en) * | 2011-03-15 | 2012-09-20 | 현대자동차 주식회사 | Communication test device and method thereof |
-
2017
- 2017-12-07 CN CN201711285257.6A patent/CN108132876B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103279415A (en) * | 2013-05-27 | 2013-09-04 | 哈尔滨工业大学 | Embedded software test method based on combinatorial test |
| CN106055469A (en) * | 2016-05-19 | 2016-10-26 | 中国科学院软件研究所 | System and method for mobile terminal application testing based on code injection |
| CN106445803A (en) * | 2016-08-17 | 2017-02-22 | 中国航空工业集团公司西安飞行自动控制研究所 | Security-critical embedded software target code coverage analysis method |
Non-Patent Citations (3)
| Title |
|---|
| Development and Structural Analysis of Injection Moulding-Hydraulics Clamping Unit Testing System;Mohd Hilmi Othman等;《Applied Mechanics and Materials》;20130410;第315卷;第1-4页 * |
| Testing with the appropriate injection;Tarin Gamberini;《https://www.taringamberini.com/en/blog/java/testing-with-the-appropriate-injection/》;20170530;第156-160页 * |
| 依赖注入和单元测试;HarlanC;《https://www.cnblogs.com/harlanc/p/6876462.html》;20170519;第1-7页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108132876A (en) | 2018-06-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108132876B (en) | Embedded software object code unit testing method based on injection mode | |
| US7275184B2 (en) | Software verification method for control units and verification system | |
| CN106021101B (en) | The method and device that mobile terminal is tested | |
| CN110209520B (en) | Method and device for improving SSD (solid State disk) testing efficiency, computer equipment and storage medium | |
| CN103399814A (en) | Automated testing method and automated testing device | |
| CN111563032A (en) | APP debugging method and device, computer equipment and storage medium | |
| CN112395202A (en) | Interface automation test method and device, computer equipment and storage medium | |
| US7149943B2 (en) | System for flexible embedded Boundary Scan testing | |
| CN106292647B (en) | A kind of test method and device of electric machine controller operating condition | |
| CN107977315B (en) | Embedded software object code unit testing method based on Bootloader mode | |
| CN107273745B (en) | Dynamic analysis method for malicious code in dynamic link library form | |
| CN113742215A (en) | Method and system for automatically configuring and calling test tool to perform test analysis | |
| CN111258915B (en) | Method for carrying out automatic unit test on PLC program | |
| CN107203373B (en) | Interface control acquiring method, interface control testing method, interface control acquiring device and interface control testing device | |
| CN112445490A (en) | File sequence processing method and device, terminal equipment and storage medium | |
| CN116431522A (en) | Automatic test method and system for low-code object storage gateway | |
| CN114780326B (en) | Cross-platform calibration test method, device and equipment | |
| US11899561B2 (en) | Method for operating a control unit when testing software of the control unit, and method for operating a test computer when testing software of a control unit | |
| CN117597669A (en) | Test method, system and device | |
| CN114661615A (en) | FPGA software testing method and device | |
| CN114297088A (en) | Method, device, equipment and medium for testing front end vue frame assembly | |
| CN111813665A (en) | Big data platform interface data testing method and system based on python | |
| CN111752823A (en) | Method, device and equipment for testing vehicle-mounted power supply application software | |
| Mouzakitis et al. | Advanced automated onboard vehicle diagnostics testing | |
| US6026344A (en) | Diagnosis method for vehicle systems |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |