CN116881174B - ECU application software closed-loop test method, device, equipment and storage medium - Google Patents
ECU application software closed-loop test method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN116881174B CN116881174B CN202311152313.4A CN202311152313A CN116881174B CN 116881174 B CN116881174 B CN 116881174B CN 202311152313 A CN202311152313 A CN 202311152313A CN 116881174 B CN116881174 B CN 116881174B
- Authority
- CN
- China
- Prior art keywords
- tested
- execution file
- file
- information
- error position
- 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
- 238000010998 test method Methods 0.000 title description 7
- 238000011161 development Methods 0.000 claims abstract description 35
- 238000000034 method Methods 0.000 claims abstract description 29
- 238000012360 testing method Methods 0.000 claims abstract description 25
- 241001362551 Samba Species 0.000 claims description 20
- 238000012544 monitoring process Methods 0.000 claims description 10
- 230000009471 action Effects 0.000 claims description 3
- 238000004590 computer program Methods 0.000 claims description 3
- 238000012827 research and development Methods 0.000 abstract description 4
- 238000012986 modification Methods 0.000 description 6
- 230000004048 modification Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 3
- 238000013522 software testing Methods 0.000 description 3
- 230000001360 synchronised effect Effects 0.000 description 3
- 230000004075 alteration Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000007639 printing Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000006378 damage Effects 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000011835 investigation Methods 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 238000007493 shaping process Methods 0.000 description 1
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
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
A method, a device, equipment and a storage medium for testing closed loop of ECU application software relate to the technical field of automobile electric control research and development, and the method comprises the following steps: acquiring an execution file to be tested; mounting the execution file to be tested on a target server of a cloud end; based on a cross-platform operation simulator, operating the to-be-tested execution file in a target container of the target server, collecting an operation real-time log of the to-be-tested execution file, and synchronously transmitting the operation real-time log to a local end; identifying an error position in the running real-time log, and outputting the error position information through an integrated development module; obtaining a repaired execution file to be tested, and repeating the steps; according to the method, a cloud computing and local end is adopted to construct a cloud integrated system, automatic and rapid iteration test and problem positioning are achieved, and the electric control research and development efficiency of the automobile is greatly improved.
Description
Technical Field
The application relates to the technical field of automobile electric control research and development.
Background
In the current vehicle-mounted ECU application software testing process, because of the problem of cross-CPU instruction set architecture, compiled execution software generally needs to be burnt into a development board for testing, and the specific method is as follows: the problem cause is determined by connecting the development board observation logs. The test mode is required to be burnt into the development board for testing, so that time is greatly wasted, hardware resources are relied on, and the test efficiency is extremely low. And the test is long in time consumption, so that the development efficiency of the automobile electric control is difficult to improve.
Therefore, how to provide a CU application software testing method that can quickly locate a problem and can perform an iterative test is a technical problem to be solved in the art.
Disclosure of Invention
In order to solve the technical problems, the application provides a closed loop test method, a device, equipment and a storage medium for ECU application software.
Based on the same inventive concept, the application has two independent technical schemes:
1. a testing method of ECU application software comprises the following steps:
s1, acquiring an execution file to be tested;
s2, mounting the execution file to be tested on a target server of a cloud;
s3, based on a cross-platform operation simulator, operating the to-be-tested execution file in a target container of the target server, collecting an operation real-time log of the to-be-tested execution file, and synchronously transmitting the operation real-time log to a local end;
s4, identifying an error position in the running real-time log, and outputting information of the error position through an integrated development module;
s5, acquiring the repaired execution file to be tested, and repeating the steps S2-S4.
Further, the to-be-tested execution file is mounted on a target server of a cloud, and the method specifically comprises the following steps:
mounting the execution file to be tested on the Samba component of the local end;
acquiring the network position of the target server through the Samba component;
and based on the network position, the to-be-tested execution file is mounted on a corresponding target server through the Samba component, and is synchronously mounted to a designated directory of a network file system NFS in the target server.
Further, based on a cross-platform running simulator, running the to-be-tested execution file in a target container of the target server, and specifically comprising the following steps:
the execution file to be tested is synchronously transmitted to a target container under the action of the network file system NFS;
based on the support of the cross-platform running simulator QEMU, the to-be-tested execution file runs in the target container, and a running real-time log is generated.
Further, the execution file to be tested is an ARM architecture execution file, and the target container in the target server is an X86 architecture.
Further, the real-time log of the execution file operation to be detected is collected and synchronously transmitted to a local end, and the method specifically comprises the following steps:
based on a side-car acquisition mode, acquiring an operation real-time log of the to-be-detected execution file by adopting a promtail component, and storing the operation real-time log into a loki database in real time;
and configuring the loki database based on a data monitoring system Grafana, and synchronously transmitting the running real-time log in the loki database to a local end.
Further, the information of the error position is output through an integrated development module, and the method is realized through the following steps:
acquiring a bat script file;
and modifying the local end instruction registry based on the bat script file, enabling the local end to support calling the integrated development module through a network based on the error position, and outputting the information of the error position.
Further, the bat script file includes the following instructions:
closing a command prompt window for back display;
acquiring information of the error position as an incoming parameter, and storing the incoming parameter in a variable IDE;
outputting information contained in the variable IDE, transmitting the information to a search string findstr command, matching the information contained in the variable IDE with preset integrated development module information, and ignoring the information contained in the variable IDE and the case of characters in the preset integrated development module information when matching;
and after the matching is successful, opening a file path and a code line number position appointed by the integrated development module through the information of the error position, and realizing the information output of the error position.
2. An ECU application software testing device comprising:
the file acquisition module is used for acquiring an execution file to be detected;
the mounting module is used for mounting the execution file to be tested on a target server of the cloud;
the test module is used for running the execution file to be tested in a target container of the target server based on a cross-platform running simulator, collecting a running real-time log of the execution file to be tested and synchronously transmitting the running real-time log to a local end;
the problem positioning module is used for identifying the error position in the running real-time log and outputting the information of the error position through the integrated development module;
and the iteration module is used for acquiring the repaired execution file to be tested and sequentially and repeatedly executing the mounting module, the testing module and the problem positioning module.
3. An electronic device comprises a processor and a storage device, wherein a plurality of instructions are stored in the storage device, and the processor is used for reading the plurality of instructions in the storage device and executing the method.
4. A computer readable storage medium storing a computer program which when executed by a processor implements the method described above.
The ECU application software closed-loop testing method, the device, the equipment and the storage medium provided by the application at least comprise the following beneficial effects:
(1) A cloud computing and local end are adopted to construct a cloud integrated system, the environment configuration is disposable, repeated configuration is not needed, online continuous test can be realized only by reporting error logs each time, and recompilation operation is performed after problems are analyzed, so that automatic and rapid iterative test and problem positioning are realized, and compared with the traditional burning test mode, the problem investigation time is greatly reduced, and the electric control research and development efficiency of an automobile is greatly improved;
(2) Because the cloud computing technology is adopted, the working efficiency can be greatly improved without depending on hardware resources, meanwhile, a plurality of components with partial functions are integrated together, the used components are only one part of the components in the traditional use, and the system realizes the communication of the components, so that the complete closed-loop debugging is realized.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments or the description of the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings can be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of one embodiment of a closed loop test method for ECU application software provided by the application;
FIG. 2 is a workflow diagram of the closed loop test method of the ECU application software provided by the application under an application scene;
fig. 3 is a display diagram of a log packaged in a table form in the ECU application software closed-loop test method provided by the application.
Detailed Description
In order to better understand the above technical solutions, the following detailed description will be given with reference to the accompanying drawings and specific embodiments.
In the following description, for purposes of explanation and not limitation, specific details are set forth such as the particular system architecture, techniques, etc., in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
It should be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present application, but the present application may be practiced in other ways other than those described herein, and persons skilled in the art will readily appreciate that the present application is not limited to the specific embodiments disclosed below.
For convenience of description, the following will describe some terms or terminology involved in the embodiments of the present application:
and (3) ECU: an electronic control unit (Electronic Control Unit), also called a "car running computer", "car carrying computer", etc. The microcomputer controller is a microcomputer controller special for the automobile in terms of application, and is also called a singlechip special for the automobile. It is composed of microprocessor (CPU), memory (ROM, RAM), input/output interface (I/O), A/D converter (A/D) and shaping and driving large-scale integrated circuits.
Samba component: is an open source software suite, and the Samba component provides a way to share files between different operating systems.
NFS: is a network file system (Network File System), NFS is a protocol for sharing a file system over a network.
Target container: the container is a virtualization technology, and can run application software independent of the environment, software developed by a software development engineer runs here, and the target container is a container in a target server.
QEMU: the system is a cross-platform running simulator (Quick simulator) which can run embedded programs on a cloud or a local PC.
PC: is a computer (Personal Computer), which is a local computer corresponding to the cloud.
promtail component: and an open source system for log acquisition.
loki: log storage and query systems.
Grafana is a data monitoring system used in the present application to monitor the log of the application software.
Grafana-web: grafana may be browser (web) based access, grafana-web refers to the process of accessing Grafana based on a browser.
side-car acquisition mode: refers to running a secondary container alongside a primary application (similar to the side car of a conventional car) for collecting, processing and forwarding logs generated by the application.
Embodiment one:
referring to fig. 1, in some embodiments, there is provided a closed loop test method for ECU application software, comprising the steps of:
s1, acquiring an execution file to be tested;
s2, mounting the execution file to be tested on a target server of a cloud;
s3, running the execution file to be tested in a target container of the target server based on a cross-platform running simulator, collecting a real-time running log of the execution file to be tested, and synchronously transmitting the real-time running log to a local end;
s4, identifying an error position in the running real-time log, and outputting information of the error position through an integrated development module;
s5, acquiring the repaired execution file to be tested, and repeating the steps S2-S4.
Specifically, step S1 is performed at the local side.
In step S2, the to-be-tested execution file is mounted on a target server in the cloud, and specifically includes the following steps:
s21, mounting the execution file to be tested on the Samba component of the local end;
s22, acquiring the network position of the target server through the Samba component;
s23, based on the network position, the to-be-tested execution file is mounted on a corresponding target server through the Samba component, and is synchronously mounted to a designated directory of a network file system NFS in the target server.
In step S3, based on the cross-platform running simulator, the to-be-tested execution file is run in the target container of the target server, which specifically includes the following steps:
s311, synchronously transmitting the execution file to be tested to a target container under the action of the network file system NFS;
s312, based on the support of the cross-platform operation simulator QEMU, the to-be-tested execution file operates in the target container to generate an operation real-time log.
The execution file to be tested is an ARM architecture execution file, and a target container in the target server is an X86 architecture.
As a preferred implementation manner, the method for collecting the real-time log of the execution file operation to be tested and synchronously transmitting the log to the local end specifically includes the following steps:
s321, acquiring an operation real-time log of the to-be-tested execution file by adopting a promtail component based on a side-car acquisition mode, and storing the operation real-time log into a loki database in real time;
s322, configuring the loki database based on a data monitoring system Grafana, and synchronously transmitting the running real-time log in the loki database to a local end.
Wherein the promtail component needs to configure the following parameters:
the promtail monitoring port is used for outputting the running condition of the promtail component and the running real-time log acquisition condition;
the data synchronization position and the data synchronization period are used for recording the position of last data synchronization and the time interval of re-synchronization data after the promtail component collects the running real-time log;
and the storage address is used for pushing the collected log to the target address for storage.
And the label is used for filtering data through the label when inquiring the log.
In step S4, the information of the error position is output through the integrated development module, which is specifically implemented through the following steps:
s41, acquiring a bat script file;
s42, modifying the local end instruction registry based on the bat script file, enabling the local end to support calling the integrated development module through a network based on the error position, and outputting information of the error position.
In step S41, the bat script file includes the following instructions:
closing a command prompt window for back display, wherein the back display (Echo) is used for displaying the batch command being executed, the executing result and the like;
acquiring error position information as an input parameter, and storing the input parameter in a variable IDE, wherein the variable IDE is a preset variable in a local PC;
outputting the value of the variable IDE, transmitting the value to a search string findstr command, matching the variable value contained in the variable IDE with a vscodeweb or an idea, and ignoring case when matching;
after the matching is successful, the file path and the code line number position appointed by the vscode or the IDEA are opened through the input parameters.
The code is specifically as follows, supporting idea and vscode initiation:
@echo off
set IDE=%1
echo %IDE% | findstr "vscodeweb"
if /i %errorlevel% equ 0 (
code -g %2:%3:1
)
echo %IDE% | findstr "idea"
if /i %errorlevel% equ 0 (
idea64 --line %3 %2
)
as shown in fig. 2, a specific application scenario of the method provided in this embodiment is further described with reference to fig. 2. Before starting, several physical servers/virtual machines are prepared, and qemu\docker\k8s\Samba\NFS base environments are deployed. Fig. 2 is a schematic diagram of the closed loop debugging system of the ECU application software provided in this embodiment, mainly involving 12 steps indicated in the above diagram, where the light-color part module represents a developer development environment, and the dark-color part module represents the system integration scheme. The method comprises the steps of installing a Samba component, modifying a local PC registry by a bat script file, and performing Grafana-web synchronous monitoring on a local side, wherein the operations of installing the Samba component, the bat script file, the Grafana-web synchronous monitoring are carried out on the cloud side, and installing the target container, the QEMU support, the probail component, the loki database and the Grafana component.
Step (1) and step (2) are developer processing parts, the execution file obtained in step (2) is input into a system, and the system directly obtains the execution file to be processed, and the method specifically comprises the following steps:
step (1): the system provides a development log library for the ECU developer to quote, and the library is used for printing logs at the places where the logs are required to be output;
step (2): developing functional codes by developers, and compiling the functional codes into ARM architecture execution files; the ECU application software closed-loop debugging system acquires an ARM architecture execution file to be tested;
step (3), (4): based on the "network location" function of the local PC, a network location is added in the local PC by using Samba component, and the folders can be distinguished according to the items in the target location. Automatically mounting an execution file to be tested to a target server by utilizing a Samba component, and simultaneously installing an NFS file system by the target server, and automatically synchronizing the file to an NFS specified directory; creating a pod for running a target program in k8s, designating an output log of the program to a specific directory, and simultaneously mounting the directory to the NFS, wherein the target is contained in the directory in the Samba assembly, so that real-time synchronization of an execution file to be tested of a local side PC to a target container is realized;
the integrated development module IDE tool (such as a vscore) introduces a dependency log library, codes are written, and the output path of the execution file to be tested after the codes are compiled is the network position.
Step (5) and (6): because of the mounted NFS, the latest execution file can be automatically synchronized into a container based on the ECU running environment built by the K8S, and meanwhile, based on the QEMU simulator, an ARM architecture execution file can be run under an X86 architecture, so that program running and log printing are realized;
step (7): based on a side-car acquisition mode, a promtail component is adopted to realize log monitoring acquisition of an operating program in a container;
step (8), (9), p: log data acquired by the probail are stored in a loki database in real time, and a loki data source is configured based on a grafana component to realize data synchronization;
configuring a monitoring panel based on the grafana component, collecting loki information, and packaging and displaying the log in a form of a table; the log library encapsulates log output formats, specifically: time, level, code file, number of lines, method, log.
Examples:
time:"2023-07-2411:01:27,949";level:"WARN";codeLine:"com/alibaba/nacos/common/http/HttpClientBeanHolder.java,114";function:"shutdown";log:"[vtv-project][HttpClientBeanHolder]Destruction of the end"。
specifically, as shown in fig. 3, a display diagram of a log packaged in a table form is shown, wherein a column of code is clickable, after clicking, an integrated development module IDE is started through a web browser, a bat script file is used for modifying a PC registry, and after modification, two starting instructions are added in the registry of a computer, so that a development tool is called.
Step ⑪: modifying a local end PC instruction registry by utilizing a bat script file to enable the local end PC instruction registry to support the starting of an integrated development module IDE tool based on WEB call;
step ⑫: specific log information output by an application program, such as error logs, can be displayed on a grafana monitoring interface, specific files and line numbers of the code output logs can be positioned, meanwhile, based on configuration of a registry, an integrated development module IDE can be started by clicking, and error reporting codes can be automatically jumped to for bug repair.
Based on the steps, the closed-loop debugging system with local compiling, cloud operation and real-time jump modification bug is realized.
Embodiment two:
in some embodiments, there is provided an ECU application software closed loop test device comprising:
the file acquisition module is used for acquiring an execution file to be detected;
the mounting module is used for mounting the execution file to be tested on a target server of the cloud;
the test module is used for running the execution file to be tested in a target container of the target server based on a cross-platform running simulator, collecting a running real-time log of the execution file to be tested and synchronously transmitting the running real-time log to a local end;
the problem positioning module is used for identifying the error position in the running real-time log and outputting the information of the error position through the integrated development module;
and the iteration module is used for acquiring the repaired execution file to be tested and sequentially and repeatedly executing the mounting module, the testing module and the problem positioning module.
Embodiment III:
in some embodiments, an electronic device is provided that includes a processor and a storage device having a plurality of instructions stored therein, the processor configured to read the plurality of instructions in the storage device and perform the method described above.
Embodiment four:
in some embodiments, a computer readable storage medium is provided, which stores a computer program which, when executed by a processor, implements the above method.
While preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following claims be interpreted as including the preferred embodiments and all such alterations and modifications as fall within the scope of the application. It will be apparent to those skilled in the art that various modifications and variations can be made to the present application without departing from the spirit or scope of the application. Thus, it is intended that the present application also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.
Claims (7)
1. The ECU application software closed-loop testing method is characterized by comprising the following steps of:
s1, acquiring an execution file to be tested;
s2, mounting the execution file to be tested on a target server of a cloud;
s3, based on a cross-platform running simulator QEMU, running the to-be-tested execution file in a target container of the target server, collecting a running real-time log of the to-be-tested execution file, and synchronously transmitting the running real-time log to a local end;
s4, identifying the error position in the running real-time log, and outputting information of the error position through an integrated development module IDE;
s5, acquiring the repaired execution file to be tested, and repeating the steps S2-S4;
the method for mounting the execution file to be tested on the target server of the cloud comprises the following steps:
mounting the execution file to be tested on the Samba component of the local end;
acquiring the network position of the target server through the Samba component;
based on the network position, the to-be-tested execution file is mounted on a corresponding target server through the Samba component, and is synchronously mounted to a designated directory of a network file system NFS in the target server;
the information of the error position is output through an integrated development module, and the method is realized through the following steps:
acquiring a bat script file;
modifying the local end instruction registry based on the bat script file, enabling the local end to support calling the integrated development module through a network based on the error position, and outputting information of the error position;
the bat script file includes the following instructions:
closing a command prompt window for back display;
acquiring information of the error position as an incoming parameter, and storing the incoming parameter in a variable IDE;
outputting information contained in the variable IDE, transmitting the information to a search string findstr command, matching the information contained in the variable IDE with preset integrated development module information, and ignoring the information contained in the variable IDE and the case of characters in the preset integrated development module information when matching;
and after the matching is successful, opening a file path and a code line number position appointed by the integrated development module through the information of the error position, and realizing the information output of the error position.
2. The ECU application software closed loop testing method according to claim 1, wherein running the execution file to be tested in a target container of the target server based on a cross-platform running simulator comprises the steps of:
the execution file to be tested is synchronously transmitted to a target container under the action of the network file system NFS;
based on the support of the cross-platform running simulator QEMU, the to-be-tested execution file runs in the target container, and a running real-time log is generated.
3. The method for testing the closed loop of the application software of the ECU according to claim 2, wherein the execution file to be tested is an ARM architecture execution file, and the target container in the target server is an X86 architecture.
4. The method for closed loop testing of ECU application software according to claim 1, wherein collecting the real-time log of the execution file operation to be tested and synchronously transmitting the log to a local terminal comprises the following steps:
based on a side-car acquisition mode, acquiring an operation real-time log of the to-be-detected execution file by adopting a promtail component, and storing the operation real-time log into a loki database in real time;
and configuring the loki database based on a data monitoring system Grafana, and synchronously transmitting the running real-time log in the loki database to a local end.
5. An ECU application software closed loop testing device, comprising:
the file acquisition module is used for acquiring an execution file to be detected;
the mounting module is used for mounting the execution file to be tested on a target server of the cloud;
the test module is used for running the execution file to be tested in a target container of the target server based on a cross-platform running simulator, collecting a running real-time log of the execution file to be tested and synchronously transmitting the running real-time log to a local end;
the problem positioning module is used for identifying the error position in the running real-time log and outputting the information of the error position through the integrated development module;
the iteration module is used for acquiring the repaired execution file to be tested and sequentially and repeatedly executing the mounting module, the testing module and the problem positioning module;
the method for mounting the execution file to be tested on the target server of the cloud comprises the following steps:
mounting the execution file to be tested on the Samba component of the local end;
acquiring the network position of the target server through the Samba component;
based on the network position, the to-be-tested execution file is mounted on a corresponding target server through the Samba component, and is synchronously mounted to a designated directory of a network file system NFS in the target server;
the information of the error position is output through an integrated development module, and the method is realized through the following steps:
acquiring a bat script file;
modifying the local end instruction registry based on the bat script file, enabling the local end to support calling the integrated development module through a network based on the error position, and outputting information of the error position;
the bat script file includes the following instructions:
closing a command prompt window for back display;
acquiring information of the error position as an incoming parameter, and storing the incoming parameter in a variable IDE;
outputting information contained in the variable IDE, transmitting the information to a search string findstr command, matching the information contained in the variable IDE with preset integrated development module information, and ignoring the information contained in the variable IDE and the case of characters in the preset integrated development module information when matching;
and after the matching is successful, opening a file path and a code line number position appointed by the integrated development module through the information of the error position, and realizing the information output of the error position.
6. An electronic device comprising a processor and a memory means, wherein a plurality of instructions are stored in the memory means, the processor being arranged to read the plurality of instructions in the memory means and to perform the method of any of claims 1-4.
7. A computer readable storage medium storing a computer program, which when executed by a processor performs the method according to any one of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311152313.4A CN116881174B (en) | 2023-09-08 | 2023-09-08 | ECU application software closed-loop test method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311152313.4A CN116881174B (en) | 2023-09-08 | 2023-09-08 | ECU application software closed-loop test method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116881174A CN116881174A (en) | 2023-10-13 |
| CN116881174B true CN116881174B (en) | 2023-11-14 |
Family
ID=88257219
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311152313.4A Active CN116881174B (en) | 2023-09-08 | 2023-09-08 | ECU application software closed-loop test method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116881174B (en) |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104978263A (en) * | 2014-04-09 | 2015-10-14 | 腾讯科技（深圳）有限公司 | Mobile terminal application program test method and mobile terminal application program test system |
| KR20200007133A (en) * | 2018-07-12 | 2020-01-22 | 현대자동차주식회사 | Method and apparatus for dinamically injecting fault for vehicle ecu software test |
| CN113468111A (en) * | 2021-07-27 | 2021-10-01 | 中国银行股份有限公司 | Log monitoring management system and method for container cloud |
| CN114625664A (en) * | 2022-03-24 | 2022-06-14 | 上海英恒电子有限公司 | Automatic testing method, device, equipment and storage medium |
| CN115809076A (en) * | 2022-12-06 | 2023-03-17 | 合众新能源汽车股份有限公司 | ECU software automation integration method and system |
| CN115935631A (en) * | 2022-11-28 | 2023-04-07 | 蔚来软件科技(上海)有限公司 | Test system and method for vehicle equipment and storage medium |
| CN116069648A (en) * | 2023-01-29 | 2023-05-05 | 浙江极氪智能科技有限公司 | Software testing method, system, equipment and storage medium |
| CN116126710A (en) * | 2023-02-06 | 2023-05-16 | 重庆长安汽车股份有限公司 | Vehicle-mounted software simulation method, device, equipment and medium |
| WO2023103712A1 (en) * | 2021-12-06 | 2023-06-15 | 比亚迪股份有限公司 | Ecu upgrade method and device, and readable storage medium |
| CN116561088A (en) * | 2023-07-04 | 2023-08-08 | 合众新能源汽车股份有限公司 | Log management method and device for vehicle-mounted system and computer readable storage medium |
| CN116701096A (en) * | 2022-02-28 | 2023-09-05 | 亿咖通(湖北)技术有限公司 | Cloud server testing method, virtual machine, vehicle machine system and storage medium |
-
2023
- 2023-09-08 CN CN202311152313.4A patent/CN116881174B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104978263A (en) * | 2014-04-09 | 2015-10-14 | 腾讯科技（深圳）有限公司 | Mobile terminal application program test method and mobile terminal application program test system |
| KR20200007133A (en) * | 2018-07-12 | 2020-01-22 | 현대자동차주식회사 | Method and apparatus for dinamically injecting fault for vehicle ecu software test |
| CN113468111A (en) * | 2021-07-27 | 2021-10-01 | 中国银行股份有限公司 | Log monitoring management system and method for container cloud |
| WO2023103712A1 (en) * | 2021-12-06 | 2023-06-15 | 比亚迪股份有限公司 | Ecu upgrade method and device, and readable storage medium |
| CN116701096A (en) * | 2022-02-28 | 2023-09-05 | 亿咖通(湖北)技术有限公司 | Cloud server testing method, virtual machine, vehicle machine system and storage medium |
| CN114625664A (en) * | 2022-03-24 | 2022-06-14 | 上海英恒电子有限公司 | Automatic testing method, device, equipment and storage medium |
| CN115935631A (en) * | 2022-11-28 | 2023-04-07 | 蔚来软件科技(上海)有限公司 | Test system and method for vehicle equipment and storage medium |
| CN115809076A (en) * | 2022-12-06 | 2023-03-17 | 合众新能源汽车股份有限公司 | ECU software automation integration method and system |
| CN116069648A (en) * | 2023-01-29 | 2023-05-05 | 浙江极氪智能科技有限公司 | Software testing method, system, equipment and storage medium |
| CN116126710A (en) * | 2023-02-06 | 2023-05-16 | 重庆长安汽车股份有限公司 | Vehicle-mounted software simulation method, device, equipment and medium |
| CN116561088A (en) * | 2023-07-04 | 2023-08-08 | 合众新能源汽车股份有限公司 | Log management method and device for vehicle-mounted system and computer readable storage medium |
Non-Patent Citations (3)
| Title |
|---|
| An automotive test-bed for ECU testing, validation and verification;Drolia, U等;Proceedings 2011 10th International Conference on Information Processing in Sensor Networks (IPSN 2010);全文 * |
| CI平台下的Web自动化测试的研究与实现;朱怡嘉;中国优秀硕士学位论文全文数据库信息科技辑;全文 * |
| 基于DEBA-SVM算法的发动机远程故障预判诊断研究;贾奎;中国优秀硕士学位论文全文数据库 工程科技Ⅱ辑;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116881174A (en) | 2023-10-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9727436B2 (en) | Adding a profiling agent to a virtual machine to permit performance and memory consumption analysis within unit tests | |
| Bringmann et al. | Model-based testing of automotive systems | |
| Muccini et al. | Using software architecture for code testing | |
| US7178135B2 (en) | Scope-based breakpoint selection and operation | |
| CN101295280B (en) | Automatic software debugging method and system | |
| US20070079288A1 (en) | System and method for capturing filtered execution history of executable program code | |
| CN1645339A (en) | Debugging method for applied programm in simulator of embedded system | |
| US20060253842A1 (en) | Modelling of programmable devices | |
| CN112270149A (en) | Verification platform automation integration method and system, electronic equipment and storage medium | |
| CN104915297B (en) | A kind of automated testing method of the APP power consumption of android equipment | |
| CN108614767A (en) | A kind of remote debugging method and device | |
| CN102722438B (en) | Kernel debugging method and equipment | |
| Iyenghar et al. | Towards model-based test automation for embedded systems using UML and UTP | |
| US7243059B2 (en) | Simulation of hardware based on smart buffer objects | |
| CN116881174B (en) | ECU application software closed-loop test method, device, equipment and storage medium | |
| Cunha et al. | An experiment in tool integration: the DDBG parallel and distributed debugger | |
| CN103176903B (en) | The test method and equipment of MapReduce distributed system program | |
| CN114840410A (en) | Test analysis method and device, computer equipment and storage medium | |
| CN113760397A (en) | Interface call processing method, device, equipment and storage medium | |
| US20030188225A1 (en) | Extended "run to" function | |
| JPH08314760A (en) | Program development supporting device | |
| CN113360397A (en) | Regression testing method, device, equipment and storage medium of system function | |
| CN1312587C (en) | An embedded real time operating system fault analysis positioning system and method | |
| CN113608996B (en) | Mirror image compiling test method, system, device and readable storage medium | |
| CN111611161B (en) | Implementation method of lightweight debugging tool applied to avionic software |
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 |