CN112445490A - File sequence processing method and device, terminal equipment and storage medium - Google Patents
File sequence processing method and device, terminal equipment and storage medium Download PDFInfo
- Publication number
- CN112445490A CN112445490A CN202011300137.0A CN202011300137A CN112445490A CN 112445490 A CN112445490 A CN 112445490A CN 202011300137 A CN202011300137 A CN 202011300137A CN 112445490 A CN112445490 A CN 112445490A
- Authority
- CN
- China
- Prior art keywords
- action
- sequence
- execution
- information
- source file
- 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.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 26
- 230000009471 action Effects 0.000 claims abstract description 374
- 230000006870 function Effects 0.000 claims abstract description 149
- 238000012360 testing method Methods 0.000 claims abstract description 134
- 238000000034 method Methods 0.000 claims abstract description 48
- 238000012545 processing Methods 0.000 claims abstract description 18
- 230000008569 process Effects 0.000 claims description 25
- 238000004590 computer program Methods 0.000 claims description 20
- 238000002405 diagnostic procedure Methods 0.000 description 11
- 101150064138 MAP1 gene Proteins 0.000 description 5
- 238000004458 analytical method Methods 0.000 description 4
- 230000006854 communication Effects 0.000 description 4
- 238000003745 diagnosis Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 230000010354 integration Effects 0.000 description 4
- 230000004044 response Effects 0.000 description 4
- 101100456045 Schizosaccharomyces pombe (strain 972 / ATCC 24843) map3 gene Proteins 0.000 description 3
- 238000004891 communication Methods 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 101100400452 Caenorhabditis elegans map-2 gene Proteins 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
-
- 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/362—Software debugging
- G06F11/3644—Software debugging by instrumenting at runtime
-
- 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/362—Software debugging
- G06F11/366—Software debugging using diagnostics
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Software Systems (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application is applicable to the technical field of computers, and provides a file sequence processing method, a file sequence processing device, terminal equipment and a storage medium, wherein the file sequence processing method comprises the following steps: obtaining a source file to be processed; determining each action node label and the sequence of each action node label contained in the source file to be processed to obtain action execution sequence information; the action node label is a node label used for describing a test action; according to the action execution sequence information, calling execution functions corresponding to the action node labels from a preset dynamic link library in sequence, and executing a test sequence described by a source file; the execution function is a computer function which is correspondingly established for various action node labels in advance and is used for realizing the test action described by the action node labels; the preset dynamic link library is obtained by compiling a program file containing each execution function in advance. The method and the device for testing the file can enable the testing sequence formally described in the source file to be actually run.
Description
Technical Field
The present application belongs to the field of computer technologies, and in particular, to a file sequence processing method and apparatus, a terminal device, and a storage medium.
Background
Currently, there are often some source files for formally describing Test sequences, such as Open Test sequence eXchange (OTX) source files. The OTX source file is a file in which a standardized test sequence of the vehicle automatic diagnosis process is formally described by Extensible Markup Language (XML) based on the ISO13209 standard, so that the data format of the diagnosis communication process is convenient to be uniform.
However, the existing parsing tools, such as the XML parsing tool, can only perform simple data reading on data in the source file, so that the test sequence in the source file cannot be actually run.
Disclosure of Invention
In view of this, embodiments of the present application provide a file sequence processing method, an apparatus, a terminal device, and a storage medium, so as to solve a problem in the prior art how to enable a test sequence formally described in a source file to be actually run.
A first aspect of an embodiment of the present application provides a file sequence processing method, including:
obtaining a source file to be processed;
determining each action node label and the sequence of each action node label contained in the source file to be processed to obtain action execution sequence information; the action node label is a node label used for describing a test action;
according to the action execution sequence information, calling execution functions corresponding to the action node labels from a preset dynamic link library in sequence, and executing a test sequence described by the source file to be processed; the execution function is a computer function which is correspondingly established for various action node labels in advance and is used for realizing the test action described by the action node labels; the preset dynamic link library is obtained by compiling a program file containing each execution function in advance.
Optionally, the determining each action node tag and the sequence of each action node tag included in the source file to be processed to obtain action execution sequence information includes:
recording the unique identification information of each action node label in the source file to be processed in sequence;
according to the unique identification information of each action node label recorded in sequence, sequentially determining the name of an execution function corresponding to each action node label to obtain action execution sequence information; the action execution sequence information comprises names of execution functions recorded in sequence;
correspondingly, the step of calling the execution function corresponding to each action node tag in sequence from a preset dynamic link library according to the action execution sequence information, and executing the test sequence described by the source file to be processed includes:
and calling the execution functions corresponding to the names of the execution functions in sequence from the preset dynamic link library according to the action execution sequence information, and executing the test sequence described by the source file.
Optionally, the determining each action node tag and the sequence of each action node tag included in the source file to be processed to obtain action execution sequence information includes:
recording the unique identification information of each action node label in the source file to be processed in sequence to obtain action execution information; the action execution information comprises unique identification information of action node labels recorded in sequence;
correspondingly, the step of calling the execution function corresponding to each action node tag in sequence from a preset dynamic link library according to the action execution sequence information, and executing the test sequence described by the source file to be processed includes:
and calling an execution function corresponding to the unique identification information of each action node label from the preset dynamic link library in sequence according to the action execution sequence information, and executing the test sequence described by the source file.
Optionally, the determining each action node tag and the sequence of each action node tag included in the source file to be processed to obtain action execution sequence information includes:
recording each action node label and the sequence of each action node label contained in each flow node label in the source file to be processed through a first interface to obtain first recording information;
recording the sequence of each flow node label in the source file to be processed through a second interface to obtain second recording information;
and obtaining the action execution sequence information according to the first record information and the second record information.
Optionally, the action execution sequence information further includes parameter information corresponding to each action node tag recorded in sequence, and correspondingly, according to the action execution sequence information, sequentially calls, from a preset dynamic link library, an execution function corresponding to each action node tag, and executes a test sequence described by the source file to be processed, where the test sequence includes:
according to the action execution sequence information, when the execution function corresponding to each action node label is called from a preset dynamic link library in sequence, the corresponding parameter information is transmitted to the execution function, and the test sequence described by the source file is executed according to the parameter information.
Optionally, before the obtaining the source file to be processed, the method further includes:
acquiring a preset number of source files;
sequentially analyzing each source file, and sequentially creating corresponding execution functions for each action node label contained in the source file to obtain a program file containing each execution function;
and compiling the program file, generating a preset dynamic link library and storing the preset dynamic link library.
Optionally, the file sequence processing method further includes:
recording the log information of the test sequence execution process;
and adjusting the preset dynamic link library according to the log information.
A second aspect of the embodiments of the present application provides a file sequence processing apparatus, including:
the device comprises a first acquisition unit, a second acquisition unit and a processing unit, wherein the first acquisition unit is used for acquiring an OTX source file to be processed;
an action execution sequence information determining unit, configured to determine each action node tag and a sequence of each action node tag included in the source file to be processed, to obtain action execution sequence information; the action node label is a node label used for describing a test action;
the execution unit is used for calling the execution functions corresponding to the action node labels from a preset dynamic link library in sequence according to the action execution sequence information and executing the test sequence described by the source file to be processed; the execution function is a computer function which is correspondingly established for various action node labels in advance and is used for realizing the test action described by the action node labels; the preset dynamic link library is obtained by compiling a program file containing each execution function in advance.
Optionally, the action execution sequence information determining unit is specifically configured to record unique identification information of each action node tag in the source file to be processed in sequence; according to the unique identification information of each action node label recorded in sequence, sequentially determining the name of an execution function corresponding to each action node label to obtain action execution sequence information; the action execution sequence information comprises names of execution functions recorded in sequence;
correspondingly, the execution unit is specifically configured to call the execution functions corresponding to the names of the execution functions in sequence from the preset dynamic link library according to the action execution sequence information, and execute the test sequence described in the source file.
Optionally, the action execution sequence information determining unit is specifically configured to record unique identification information of each action node tag in the source file to be processed in sequence, so as to obtain action execution information; the action execution information comprises unique identification information of action node labels recorded in sequence;
correspondingly, the execution unit is specifically configured to call, according to the action execution sequence information, an execution function corresponding to the unique identification information of each action node tag from the preset dynamic link library in sequence, and execute the test sequence described by the source file.
Optionally, the action execution sequence information determining unit includes a first recording module, a second recording module, and a sequence integration module:
the first recording module is used for recording each action node label contained in each flow node label in the source file to be processed and the sequence of each action node label through a first interface to obtain first recording information;
the second recording module is used for recording the sequence of each flow node label in the source file to be processed through a second interface to obtain second recording information;
and the sequence integration module is used for obtaining the action execution sequence information according to the first record information and the second record information.
Optionally, the action execution sequence information further includes parameter information corresponding to each action node tag recorded in sequence, and correspondingly, the execution unit is specifically configured to, according to the action execution sequence information, transfer an execution function corresponding to each action node tag from a preset dynamic link library in sequence, while transferring the corresponding parameter information to the execution function, and execute a test sequence described in the source file according to the parameter information.
Optionally, the file processing apparatus further includes:
the second acquisition unit is used for acquiring a preset number of source files;
a program file obtaining unit, configured to sequentially parse each source file, and sequentially create corresponding execution functions for each action node tag included in the source file, so as to obtain a program file including each execution function;
and the compiling unit is used for compiling the program file, generating a preset dynamic link library and storing the preset dynamic link library.
Optionally, the file sequence processing apparatus further includes:
the log information recording unit is used for recording the log information of the test sequence execution process;
and the adjusting unit is used for recording the log information of the test sequence execution process.
A third aspect of the embodiments of the present application provides a terminal device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, the terminal device is enabled to implement the steps of the file sequence processing method.
A fourth aspect of embodiments of the present application provides a computer-readable storage medium, which stores a computer program that, when executed by a processor, causes a terminal device to implement the steps of the file sequence processing method as described above.
A fifth aspect of the embodiments of the present application provides a computer program product, which, when running on a terminal device, causes the terminal device to execute the steps of the file sequence processing method according to any one of the above first aspects.
Compared with the prior art, the embodiment of the application has the advantages that: in the embodiment of the application, because the preset dynamic link library is set in advance, the preset dynamic link library is a dynamic link library obtained by compiling a program file containing each execution function in advance, each execution function is a computer function which is created in advance and is respectively used for realizing the test action described by each action node label, after the source file to be processed is obtained, the action execution sequence information can be obtained by only determining each action node label and the sequence of each action node label contained in the source file to be processed, the execution functions corresponding to the action node labels in the preset dynamic link library can be directly called in sequence according to the action execution sequence information, the test actions are executed in sequence, and finally the execution of the test sequence of the source file can be completely and accurately finished, so that the test sequence formally described in the source file can be actually run.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present application, and those skilled in the art can also obtain other drawings according to the drawings without creative efforts.
Fig. 1 is a schematic view of an application scenario corresponding to a file sequence processing method provided in an embodiment of the present application;
fig. 2 is a schematic flow chart of an implementation of a file sequence processing method provided in an embodiment of the present application;
FIG. 3 is a schematic diagram of a document sequence processing apparatus provided in an embodiment of the present application;
fig. 4 is a schematic diagram of a terminal device provided in an embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, 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.
In order to explain the technical solution described in the present application, the following description will be given by way of specific examples.
It will 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 present application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the specification of the present application 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.
It should be further understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to a determination" or "in response to a detection". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".
In addition, in the description of the present application, the terms "first," "second," "third," and the like are used solely to distinguish one from another and are not to be construed as indicating or implying relative importance.
Fig. 1 shows a schematic view of an application scenario corresponding to a file sequence processing method according to an embodiment of the present application, which includes a vehicle diagnostic test platform 11, a diagnostic test apparatus 12, and a vehicle 13. The vehicle diagnostic test platform 11 establishes a communication connection with the diagnostic test device 12, and the diagnostic test device 12 is connected with an On Board Diagnostics (OBD) interface 131 of the vehicle 13. The vehicle diagnosis test platform 11 may obtain a source file to be processed by the file sequence processing method according to the embodiment of the present application, and determine each action node tag included in the source file to be processed and the sequence of each action node tag to obtain action execution sequence information; and calling the execution functions corresponding to the action node labels in sequence from a preset dynamic link library according to the action execution sequence information, executing the test sequence described by the source file, and controlling the diagnostic test device 12 to complete the diagnostic test of the vehicle 13.
The first embodiment is as follows:
fig. 2 shows a schematic flowchart of a file sequence processing method provided in an embodiment of the present application, which is detailed as follows:
in S201, a source file to be processed is acquired.
In an embodiment of the present application, the source file is a file formally describing (e.g., described in XML language) a test sequence consisting of individual test actions required to perform certain test tasks (e.g., vehicle diagnostic tests). The source file can only describe the test sequence formally, and can not be directly used for the application program to call and execute the corresponding test action. Wherein the source file to be processed is a specified source file describing a test sequence to be currently executed.
The terminal device may acquire the source file to be processed from its own storage unit, or may download the source file to be processed from another device or a network. For example, when the source file to be processed is an OTX source file, the source file to be processed may be obtained by reading a readable storage medium provided by a manufacturer of the vehicle to be processed and storing each source file of the vehicle to be tested, or the source file corresponding to the vehicle to be tested may be downloaded from a website according to the vehicle type information by obtaining the vehicle type information of the vehicle to be tested, so as to obtain the source file to be processed.
In S202, determining each action node label and the sequence of each action node label included in the source file to be processed to obtain action execution sequence information; the action node label is a node label used for describing the test action in the node labels.
In this embodiment of the present application, the source file may be in an XML format, and data related to each test described in the source file is encapsulated and stored by node tags of each level. Specifically, the node tag of the source file at least includes a node tag for describing the test action, i.e. action node tag < action >. The action node label encapsulates the detailed parameters of the single test action, such as start execution time, conditions, units to be executed, end time and conditions, etc. In the source file, the execution sequence of each test action is described by arranging each action node label in sequence, so that the test sequence is completely described. Optionally, the source file is an OTX source file, the test sequence described in the source file is specifically a vehicle diagnostic test sequence, and the detailed parameter in the action node tag may include name information of an Electronic Control Unit (ECU) to be executed.
In the embodiment of the application, after the source file to be processed is obtained, the source file to be processed may be processed by calling a preset dynamic link library (for convenience of description, referred to as an analysis dynamic link library) for analyzing the source file, the source file to be processed may be analyzed, and the action node tags included in the source file and the execution sequence of each action node tag are recorded in the analysis process, so as to obtain the action execution sequence information of the source file to be processed.
In S203, sequentially calling an execution function corresponding to each action node tag from a preset dynamic link library according to the action execution sequence information, and executing a test sequence described by the source file to be processed; the execution function is a computer function which is correspondingly established for various action node labels in advance and is used for realizing the test action described by the action node labels; the preset dynamic link library is obtained by compiling a program file containing each execution function in advance.
In the embodiment of the application, the preset dynamic link library is a dynamic link library obtained by compiling a preset program file in advance, the preset program file includes execution functions, and the execution functions are computer functions which are correspondingly created for various action node labels in advance and are used for realizing the test actions described by the action node labels. Illustratively, the computer function may be a function in the form of C + + code. The preset dynamic link library is stored in the storage unit in advance so as to call compiled execution functions in the preset dynamic functions in sequence after the source file to be processed is obtained.
Specifically, after the action execution sequence information of the current source file to be processed is determined, the execution functions corresponding to the action node labels included in the source file to be processed may be sequentially called from the preset dynamic link library according to the recorded execution sequence of the action node labels, and the test actions included in the test sequence are executed one by one through the execution functions, thereby implementing the sequential execution of the test sequence.
In the embodiment of the application, because the preset dynamic link library is set in advance, the preset dynamic link library is a dynamic link library obtained by compiling a program file containing each execution function in advance, each execution function is a computer function which is created in advance and is respectively used for realizing the test action described by each action node label, after the source file to be processed is obtained, the action execution sequence information can be obtained by only determining each action node label and the sequence of each action node label contained in the source file to be processed, the execution functions corresponding to the action node labels in the preset dynamic link library can be directly called in sequence according to the action execution sequence information, the test actions are executed in sequence, and finally the execution of the test sequence of the source file can be completely and accurately finished, so that the test sequence formally described in the source file can be actually run.
Optionally, the step S202 includes:
a1: recording the unique identification information of each action node label in the source file to be processed in sequence;
a2: according to the unique identification information of each action node label recorded in sequence, sequentially determining the name of an execution function corresponding to each action node label to obtain action execution sequence information; the action execution sequence information comprises names of execution functions recorded in sequence;
correspondingly, the step S203 includes:
a3: and calling the execution functions corresponding to the names of the execution functions in sequence from the preset dynamic link library according to the action execution sequence information, and executing the test sequence described by the source file.
In this embodiment, the analyzing dynamic link library may be specifically invoked to execute steps a1 to a2, to obtain names of execution functions recorded in sequence as the action execution sequence information, and then, according to the action execution sequence information, the execution functions corresponding to the names of the execution functions are sequentially invoked from the preset dynamic link library, so as to sequentially implement the execution of each test action, thereby completing the execution of a whole test sequence.
Specifically, in step a1, when the parsing dynamic link library parses the source file, the action node tags and their sequence may be recorded by recording the unique identification information of each parsed action node tag in sequence. Specifically, the unique identification information may be a unique identification number ID of the action node tag. Alternatively, the action execution order information may be recorded by associating a container map. The associated container map implements mapped storage of two data by storing respective key-value pairs similar to < key, value >. For the sake of distinction, the association container herein is referred to as a first association container map 1. When one action node label is analyzed, the current sequence number is used as a key value, and the unique identification information of the current action node label is used as a value and is correspondingly stored in the map 1. For example, when the first node label is resolved, the sequence number is 1, when the second node label is resolved, the sequence number is incremented by 2, when the third node label is resolved, the sequence number is incremented by 3, and so on.
In the embodiment of the present application, the analysis dynamic link library further prestores a correspondence between the unique identification information of the action node tag and the name of the execution function, and specifically, the unique identification information of the action node tag may be used as a key value, and the name of the corresponding execution function may be used as a value for mapping and storing through the second association container map 2. In step a2, the name of the execution function recorded in sequence may be obtained as the action execution sequence information according to the unique identification information (which may be the first associated container map1) of each action node tag recorded in sequence and the correspondence stored in the second associated container map 2. Specifically, the action execution sequence information may be stored by the third association container map3, where the current sequence number is used as a key value, and the name of the execution function corresponding to the sequence number currently determined in combination with the maps 1 and 2 is used as a value, so as to realize the in-sequence recording of the names of the respective execution functions.
In the embodiment of the present application, the compiled execution function stored in the preset dynamic link library may be specifically called according to the name of the execution function. Specifically, in step a3, according to the names of the execution functions recorded in sequence in the action execution sequence information, the corresponding compiled execution functions in the preset dynamic link library are sequentially called, so as to sequentially implement each test action, and finally, complete accurate execution of the test sequence.
Optionally, the step S202 includes:
b1: recording the unique identification information of each action node label in the source file to be processed in sequence to obtain action execution information; the action execution information comprises unique identification information of action node labels recorded in sequence;
correspondingly, the step S203 includes:
b2: and sequentially calling an execution function corresponding to the unique identification information of each action node label from the preset dynamic link library according to the action execution sequence information, and executing the test sequence described by the source file.
In the embodiment of the application, the preset dynamic link library stores the corresponding relation between the unique identification information and the execution function. After the step B1 of executing the analysis dynamic link library is called to obtain the unique identification information of each action node label recorded in sequence as the action execution sequence information, according to the action execution sequence information and the corresponding relationship between the unique identification information and the execution function stored in the preset dynamic link library, the execution function corresponding to the unique identification information of each action node label is called from the preset dynamic link library in sequence, and the execution of each test action is sequentially realized, thereby completing the execution of a whole test sequence.
Specifically, in step B1, similar to step a1, the action node tags and their sequence may be recorded by the parsing dynamic link library sequentially recording the unique identification information of each parsed action node tag when parsing the source file. Then, the unique identification information of the action node label recorded in order is used as the action execution order information, and for example, the information stored in the first associated container map is used as the action execution order information.
In step B2, after the action execution sequence information is determined, a preset dynamic link library is called, the action execution sequence information is transmitted to the preset dynamic link library, and each execution function is called in sequence according to the corresponding relationship between the unique identification information and the execution function stored in the preset dynamic link library, so as to sequentially implement each test action, and finally complete accurate execution of the test sequence. Optionally, the preset dynamic link library may specifically store a fourth associated container map4, where in the map4, the key value is unique identification information of the action node tag, and the value is a name of the corresponding execution function. After the preset dynamic link library acquires the action execution sequence information containing the unique identification information of the action node labels recorded in sequence, the names of the corresponding execution functions are sequentially determined by combining the map4, and the corresponding compiled execution functions are called through the names of the execution functions, so that each test action in the test sequence is sequentially realized.
In the embodiment of the application, the recording of the dynamic node tags and the sequence thereof contained in the source file to be processed is specifically realized in a manner of sequentially recording the unique identification information of each dynamic node tag in the source file to be processed, and because the unique identification information can uniquely identify one dynamic node tag and the data form thereof is usually simpler (usually a character string type with a small data size), the accuracy of the recorded action execution sequence information can be ensured, and meanwhile, the storage space is saved.
Optionally, the step S201 includes:
recording each action node label and the sequence of each action node label contained in each flow node label in the source file to be processed through a first interface to obtain first recording information;
recording the sequence of each flow node label in the source file to be processed through a second interface to obtain second recording information;
and obtaining the action execution sequence information according to the first record information and the second record information.
In the embodiment of the present application, a complete test sequence may be specifically divided into each test sub-flow, and each test sub-flow includes each specific test action combined in sequence. Correspondingly, in the source file to be processed, information of one test sub-process (i.e. each action node tag < action >) is specifically encapsulated through a process node tag (e.g. < procedure > tag in the OTX source file), and then each specific test action information is respectively described through each action node tag < action > contained in the process node tag.
In the embodiment of the application, the first record information can be obtained by respectively recording each action node label included in each process node label and the sequence of each action node label through the first interface. The first record information describes each test action contained in the single sub-flow sequence. And simultaneously, recording the sequence among the flow node labels through a second interface to obtain second recording information. The second record information describes the sequential execution order among the test sub-processes.
Then, through the first record information and the second record information, all the action node labels included in each process node label can be sequentially combined to obtain action execution sequence information including the complete execution sequence of all the action node labels.
For example, the key self-learning diagnostic process of the vehicle includes a test sub-process 1 and a test sub-process 2, wherein the test sub-process 1 includes a test action a1, a test action a2 and a test action a3, and the test sub-process 2 includes a test action b1, a test action b2 and a test action b 3. If the OTX source file corresponding to the key self-learning diagnosis process is a current source file to be processed, the OTX source file includes two process node tags, which may be called a procedure1 and a procedure2, wherein action node tags encapsulated in the procedure1 may sequentially include an action node tag action _ a1 for describing a test action a1, an action node tag action _ a2 for describing a test action a2, and an action node tag action _ a3 for describing a test action a 3; the procedure2 encapsulated action node tags may in turn include action node tag action _ b1 for describing test action b1, action node tag action _ b2 for describing test action b2, action node tag action _ b3 for describing test action b 3. The first recording information can be recorded in sequence through the first interface: procedure1 includes, in order, action _ a1, action _ a2, action _ a 3; the procedure2 contains action _ b1, action _ b2, and action _ b3, in order. The execution sequence of the procedure1 and the procedure2 may be recorded as follows through the second interface: procedure1 → procedure 2. Then, according to the first record information and the second record information, complete action execution sequence information can be obtained: action _ a1 → action _ a2 → action _ a3 → action _ b1 → action _ b2 → action _ b 3.
In the embodiment of the application, considering that the source file is usually packaged with the flow node tags, the execution sequence of the action node tags included in each flow node tag is recorded by setting the first interface, the execution sequence between each flow node tag is recorded by the second interface, and the action execution sequence information of the source file to be processed can be efficiently and accurately obtained by combining the two pieces of recorded information.
Optionally, the action execution sequence information further includes parameter information included in each action node tag recorded in sequence, and correspondingly, step S203 includes:
according to the action execution sequence information, when the execution function corresponding to each action node label is called from a preset dynamic link library in sequence, the corresponding parameter information is transmitted to the execution function, and the test sequence described by the source file is executed according to the parameter information.
In the embodiment of the application, the action node labels and the sequence thereof are recorded, and the parameter information corresponding to the action node labels is also recorded, so that the action execution sequence information in which the action node labels are recorded in sequence and the parameter information corresponding to the action node labels are also recorded is generated. For example, in step a1 or step B1, each time an action node tag is resolved, both unique identification information of the action node tag and parameter information encapsulated in the resolved action node tag may be stored in the value of map 1. Correspondingly, in step a2, the key value of map3 is an order number, and the value contains both the name of the executed function and the corresponding parameter information. Therefore, the action execution sequence information includes parameter information corresponding to the action node labels in sequence, regardless of whether the first associated container map1 is used as the action execution sequence information or the third associated container map3 is used as the action execution sequence information.
Then, in step S203, according to the action execution sequence information, while the execution function corresponding to the action node tag is called from the preset dynamic link library, the corresponding parameter information can be accurately transmitted to the execution function, so that the execution function can accurately implement the corresponding test action according to the parameter information, thereby accurately completing the execution of the test sequence.
In the embodiment of the application, because each compiled execution function in the preset dynamic link library is usually a flexibly-set execution function requiring parameter information to be transmitted, the sequence of each action node label is recorded, and meanwhile, the parameter information required to be transmitted is recorded, so that corresponding parameter information can be accurately transmitted when the execution function corresponding to the action node label is called later, and thus, a test sequence described by a source file to be processed is accurately and flexibly executed.
Optionally, before step S201, the method further includes:
s2001: acquiring a preset number of source files;
s2002: sequentially analyzing each source file, and sequentially creating corresponding execution functions for each action node label contained in the source file to obtain a program file containing each execution function;
s2003: and compiling the program file, generating a preset dynamic link library and storing the preset dynamic link library.
In the embodiment of the present application, before a source file to be processed is obtained, advance compiling and storing of a preset dynamic link library is realized in advance through steps S2001 to S2003.
In step S2001, a preset number of source files containing various action node tags that may occur are provided in advance from a storage medium provided by a vehicle manufacturer or from a website. For example, if the file sequence processing method in the embodiment of the present application is specifically applied to processing an OTX source file, the source files in the preset number specifically include various OTX source files corresponding to different ECUs and different diagnostic process functions that may be used.
In step S2002, each source file is sequentially parsed, and a corresponding execution function is sequentially created for an action node tag included in each source file, where the execution function is a specific implementation code segment (for example, C + + code) of the test action described by the action node tag. Specifically, the created code information of each execution function is written into the same program file, and a program file including each execution function is obtained.
In step S2003, the program file including each execution function is compiled, the obtained dynamic link library is a preset dynamic link library, and the preset dynamic link library is stored for calling in subsequent steps.
In the embodiment of the application, the steps S2001 to S2003 are performed in advance to create and store the preset dynamic link library in advance, so that after the source file to be processed is acquired, each test action can be directly implemented by calling the execution function in the preset dynamic link library, and the execution of the test sequence is completed.
Optionally, before step S203, the method further includes:
loading other preset modules;
correspondingly, in step S203, the method includes:
and calling the execution functions corresponding to the action node labels in sequence from a preset dynamic link library according to the action execution sequence information, and finishing the execution of the test sequence described by the source file to be processed by combining with other preset modules.
Specifically, the other preset modules may specifically include a diagnostic software module, a display program module, a Data Link Protocol Data Unit (D-PDU) module, and the like, where the modules are specifically in the form of a Dynamic Link Library (DLL) or an executable file (EXE), and the preset Dynamic Link Library is matched with the preset modules to implement complete execution of the test sequence.
Optionally, the file sequence processing method according to the embodiment of the present application further includes:
recording the log information of the test sequence execution process;
and adjusting the preset dynamic link library according to the log information.
In this embodiment of the application, in step S203, the log information of the test sequence execution process may be recorded while the test sequence is executed.
And then, when the test is automatically interrupted or the test is completely finished, judging whether the execution process of the current test sequence is normal or not according to the recorded log information. If the abnormal condition exists, the execution function of abnormal information in the preset dynamic link library is inquired through the log information, and the adjustment of the preset dynamic link library is realized by modifying and perfecting the code segment of the execution function, so that the preset dynamic link library can be called smoothly afterwards, and the success rate of smoothly executing the subsequent test sequence is improved.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
Example two:
fig. 3 is a schematic structural diagram of a file sequence processing apparatus provided in an embodiment of the present application, and for convenience of description, only parts related to the embodiment of the present application are shown:
the file sequence processing apparatus includes: a first acquisition unit 31, an action execution sequence information determination unit 32, and an execution unit 33. Wherein:
a first obtaining unit 31, configured to obtain a source file to be processed.
An action execution sequence information determining unit 32, configured to determine each action node tag and a sequence of each action node tag included in the source file to be processed, so as to obtain action execution sequence information; the action node label is a node label used for describing the test action.
The execution unit 33 is configured to sequentially call, according to the action execution sequence information, execution functions corresponding to the action node tags from a preset dynamic link library, and execute a test sequence described by the source file to be processed; the execution function is a computer function which is correspondingly established for various action node labels in advance and is used for realizing the test action described by the action node labels; the preset dynamic link library is obtained by compiling a program file containing each execution function in advance.
Optionally, the action execution sequence information determining unit 32 is specifically configured to record unique identification information of each action node tag in the source file to be processed in sequence; according to the unique identification information of each action node label recorded in sequence, sequentially determining the name of an execution function corresponding to each action node label to obtain action execution sequence information; the action execution sequence information comprises names of execution functions recorded in sequence;
correspondingly, the executing unit 33 is specifically configured to call the executing functions corresponding to the names of the executing functions in sequence from the preset dynamic link library according to the action executing sequence information, and execute the test sequence described in the source file.
Optionally, the action execution sequence information determining unit 32 is specifically configured to record unique identification information of each action node tag in the source file to be processed in sequence, so as to obtain action execution information; the action execution information comprises unique identification information of action node labels recorded in sequence;
correspondingly, the executing unit 33 is specifically configured to sequentially call, according to the action execution sequence information, an executing function corresponding to the unique identification information of each action node tag from the preset dynamic link library, and execute the test sequence described by the source file.
Optionally, the action execution sequence information determining unit 32 includes a first recording module, a second recording module, and a sequence integration module:
the first recording module is used for recording each action node label contained in each flow node label in the source file to be processed and the sequence of each action node label through a first interface to obtain first recording information;
the second recording module is used for recording the sequence of each flow node label in the source file to be processed through a second interface to obtain second recording information;
and the sequence integration module is used for obtaining the action execution sequence information according to the first record information and the second record information.
Optionally, the action execution sequence information further includes parameter information corresponding to each action node tag recorded in sequence, and correspondingly, the execution unit 33 is specifically configured to, according to the action execution sequence information, while calling an execution function corresponding to each action node tag in sequence from a preset dynamic link library, transmit corresponding parameter information to the execution function, and execute a test sequence described in the source file according to the parameter information.
Optionally, the file sequence processing apparatus further includes:
the second acquisition unit is used for acquiring a preset number of source files;
a program file obtaining unit, configured to sequentially parse each source file, and sequentially create corresponding execution functions for each action node tag included in the source file, so as to obtain a program file including each execution function;
and the compiling unit is used for compiling the program file, generating a preset dynamic link library and storing the preset dynamic link library.
Optionally, the file sequence processing apparatus further includes:
the log information recording unit is used for recording the log information of the test sequence execution process;
and the adjusting unit is used for recording the log information of the test sequence execution process.
It should be noted that, for the information interaction, execution process, and other contents between the above-mentioned devices/units, the specific functions and technical effects thereof are based on the same concept as those of the embodiment of the method of the present application, and specific reference may be made to the part of the embodiment of the method, which is not described herein again.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
Example three:
fig. 4 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in fig. 4, the terminal device 4 of this embodiment includes: a processor 40, a memory 41 and a computer program 42, such as a file sequence handling program, stored in said memory 41 and executable on said processor 40. The processor 40 implements the steps in the above-described respective file sequence processing method embodiments, such as the steps S201 to S203 shown in fig. 2, when executing the computer program 42. Alternatively, the processor 40, when executing the computer program 42, implements the functions of the modules/units in the above-mentioned device embodiments, such as the functions of the units 31 to 33 shown in fig. 3.
Illustratively, the computer program 42 may be partitioned into one or more modules/units that are stored in the memory 41 and executed by the processor 40 to accomplish the present application. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution process of the computer program 42 in the terminal device 4. For example, the computer program 42 may be divided into a first acquiring unit, an action sequence execution information determining unit, and an executing unit, and the specific functions of each unit are as follows:
the device comprises a first acquisition unit, a second acquisition unit and a processing unit, wherein the first acquisition unit is used for acquiring a source file to be processed;
an action execution sequence information determining unit, configured to determine each action node tag and a sequence of each action node tag included in the source file to be processed, to obtain action execution sequence information; the action node label is a node label used for describing a test action;
the execution unit is used for calling the execution functions corresponding to the action node labels from a preset dynamic link library in sequence according to the action execution sequence information and executing the test sequence described by the source file to be processed; the execution function is a computer function which is correspondingly established for various action node labels in advance and is used for realizing the test action described by the action node labels; the preset dynamic link library is obtained by compiling a program file containing each execution function in advance.
The terminal device 4 may be a desktop computer, a notebook, a palm computer, a cloud server, or other computing devices. The terminal device may include, but is not limited to, a processor 40, a memory 41. Those skilled in the art will appreciate that fig. 4 is merely an example of a terminal device 4 and does not constitute a limitation of terminal device 4 and may include more or fewer components than shown, or some components may be combined, or different components, e.g., the terminal device may also include input-output devices, network access devices, buses, etc.
The Processor 40 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 41 may be an internal storage unit of the terminal device 4, such as a hard disk or a memory of the terminal device 4. The memory 41 may also be an external storage device of the terminal device 4, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, which are provided on the terminal device 4. Further, the memory 41 may also include both an internal storage unit and an external storage device of the terminal device 4. The memory 41 is used for storing the computer program and other programs and data required by the terminal device. The memory 41 may also be used to temporarily store data that has been output or is to be output.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus/terminal device and method may be implemented in other ways. For example, the above-described embodiments of the apparatus/terminal device are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow in the method of the embodiments described above can be realized by a computer program, which can be stored in a computer-readable storage medium and can realize the steps of the embodiments of the methods described above when the computer program is executed by a processor. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.
Claims (10)
1. A file sequence processing method is characterized by comprising the following steps:
obtaining a source file to be processed;
determining each action node label and the sequence of each action node label contained in the source file to be processed to obtain action execution sequence information; the action node label is a node label used for describing a test action;
according to the action execution sequence information, calling execution functions corresponding to the action node labels from a preset dynamic link library in sequence, and executing a test sequence described by the source file to be processed; the execution function is a computer function which is correspondingly established for various action node labels in advance and is used for realizing the test action described by the action node labels; the preset dynamic link library is obtained by compiling a program file containing each execution function in advance.
2. The file sequence processing method according to claim 1, wherein the determining the order of each action node tag and each action node tag included in the source file to be processed to obtain action execution order information includes:
recording the unique identification information of each action node label in the source file to be processed in sequence;
according to the unique identification information of each action node label recorded in sequence, sequentially determining the name of an execution function corresponding to each action node label to obtain action execution sequence information; the action execution sequence information comprises names of execution functions recorded in sequence;
correspondingly, the step of calling the execution function corresponding to each action node tag in sequence from a preset dynamic link library according to the action execution sequence information, and executing the test sequence described by the source file to be processed includes:
and calling the execution functions corresponding to the names of the execution functions in sequence from the preset dynamic link library according to the action execution sequence information, and executing the test sequence described by the source file.
3. The file sequence processing method according to claim 1, wherein the determining the order of each action node tag and each action node tag included in the source file to be processed to obtain action execution order information includes:
recording the unique identification information of each action node label in the source file to be processed in sequence to obtain action execution information; the action execution information comprises unique identification information of action node labels recorded in sequence;
correspondingly, the step of calling the execution function corresponding to each action node tag in sequence from a preset dynamic link library according to the action execution sequence information, and executing the test sequence described by the source file to be processed includes:
and calling an execution function corresponding to the unique identification information of each action node label from the preset dynamic link library in sequence according to the action execution sequence information, and executing the test sequence described by the source file.
4. The file sequence processing method according to claim 1, wherein the determining the order of each action node tag and each action node tag included in the source file to be processed to obtain action execution order information includes:
recording each action node label and the sequence of each action node label contained in each flow node label in the source file to be processed through a first interface to obtain first recording information;
recording the sequence of each flow node label in the source file to be processed through a second interface to obtain second recording information;
and obtaining the action execution sequence information according to the first record information and the second record information.
5. The file sequence processing method according to claim 1, wherein the action execution sequence information further includes parameter information corresponding to each action node tag recorded in sequence, and correspondingly, according to the action execution sequence information, the method calls an execution function corresponding to each action node tag from a preset dynamic link library in sequence to execute a test sequence described by the source file to be processed, including:
according to the action execution sequence information, when the execution function corresponding to each action node label is called from a preset dynamic link library in sequence, the corresponding parameter information is transmitted to the execution function, and the test sequence described by the source file is executed according to the parameter information.
6. The file sequence processing method according to claim 1, further comprising, before said obtaining a source file to be processed:
acquiring a preset number of source files;
sequentially analyzing each source file, and sequentially creating corresponding execution functions for each action node label contained in the source file to obtain a program file containing each execution function;
and compiling the program file, generating a preset dynamic link library and storing the preset dynamic link library.
7. The file sequence processing method according to any one of claims 1 to 6, characterized by further comprising:
recording the log information of the test sequence execution process;
and adjusting the preset dynamic link library according to the log information.
8. A file sequence processing apparatus characterized by comprising:
the device comprises a first acquisition unit, a second acquisition unit and a processing unit, wherein the first acquisition unit is used for acquiring a source file to be processed;
an action execution sequence information determining unit, configured to determine each action node tag and a sequence of each action node tag included in the source file to be processed, to obtain action execution sequence information; the action node label is a node label used for describing a test action;
the execution unit is used for calling the execution functions corresponding to the action node labels from a preset dynamic link library in sequence according to the action execution sequence information and executing the test sequence described by the source file to be processed; the execution function is a computer function which is correspondingly established for various action node labels in advance and is used for realizing the test action described by the action node labels; the preset dynamic link library is obtained by compiling a program file containing each execution function in advance.
9. A terminal device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the computer program, when executed by the processor, causes the terminal device to carry out the steps of the method according to any one of claims 1 to 7.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, causes a terminal device to carry out the steps of the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011300137.0A CN112445490A (en) | 2020-11-19 | 2020-11-19 | File sequence processing method and device, terminal equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011300137.0A CN112445490A (en) | 2020-11-19 | 2020-11-19 | File sequence processing method and device, terminal equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112445490A true CN112445490A (en) | 2021-03-05 |
Family
ID=74737560
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011300137.0A Pending CN112445490A (en) | 2020-11-19 | 2020-11-19 | File sequence processing method and device, terminal equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112445490A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113268464A (en) * | 2021-06-07 | 2021-08-17 | 平安科技（深圳）有限公司 | Log display method and device, electronic equipment and storage medium |
| CN115080509A (en) * | 2022-06-10 | 2022-09-20 | 北京达佳互联信息技术有限公司 | Data processing method and device, electronic equipment and storage medium |
| CN117407048A (en) * | 2023-12-14 | 2024-01-16 | 江西飞尚科技有限公司 | Flow configuration method and system of plug-in data processing software |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105468811A (en) * | 2015-10-10 | 2016-04-06 | 陕西千山航空电子有限责任公司 | Fight parameter system automation testing method |
| CN108334365A (en) * | 2017-08-23 | 2018-07-27 | 中国电子科技集团公司第四十研究所 | A kind of realization ATS software Instrumental parameter interface Dynamic Configuration |
| CN111552267A (en) * | 2020-04-22 | 2020-08-18 | 深圳市元征科技股份有限公司 | Vehicle diagnosis method and device and vehicle diagnosis equipment |
-
2020
- 2020-11-19 CN CN202011300137.0A patent/CN112445490A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105468811A (en) * | 2015-10-10 | 2016-04-06 | 陕西千山航空电子有限责任公司 | Fight parameter system automation testing method |
| CN108334365A (en) * | 2017-08-23 | 2018-07-27 | 中国电子科技集团公司第四十研究所 | A kind of realization ATS software Instrumental parameter interface Dynamic Configuration |
| CN111552267A (en) * | 2020-04-22 | 2020-08-18 | 深圳市元征科技股份有限公司 | Vehicle diagnosis method and device and vehicle diagnosis equipment |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113268464A (en) * | 2021-06-07 | 2021-08-17 | 平安科技（深圳）有限公司 | Log display method and device, electronic equipment and storage medium |
| CN113268464B (en) * | 2021-06-07 | 2023-06-23 | 平安科技（深圳）有限公司 | Log display method and device, electronic equipment and storage medium |
| CN115080509A (en) * | 2022-06-10 | 2022-09-20 | 北京达佳互联信息技术有限公司 | Data processing method and device, electronic equipment and storage medium |
| CN117407048A (en) * | 2023-12-14 | 2024-01-16 | 江西飞尚科技有限公司 | Flow configuration method and system of plug-in data processing software |
| CN117407048B (en) * | 2023-12-14 | 2024-03-12 | 江西飞尚科技有限公司 | Flow configuration method and system of plug-in data processing software |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112445490A (en) | File sequence processing method and device, terminal equipment and storage medium | |
| CN108459962B (en) | Code normalization detection method and device, terminal equipment and storage medium | |
| CN113127338A (en) | Firmware testing method, server and computer readable storage medium | |
| CN107766236B (en) | Test task automatic management method, device, equipment and storage medium | |
| CN108459850B (en) | Method, device and system for generating test script | |
| US20220391306A1 (en) | Software environment for control engine debug, test, calibration and tuning | |
| CN112948233A (en) | Interface testing method, device, terminal equipment and medium | |
| CN114895935A (en) | Method and device for flashing vehicle ECU, electronic equipment and storage medium | |
| CN112729868A (en) | Vehicle diagnosis method, device, equipment and medium | |
| CN111693294A (en) | Vehicle detection method and device, terminal equipment and storage medium | |
| CN113505895B (en) | Machine learning engine service system, model training method and configuration method | |
| CN112346981A (en) | Joint debugging test coverage rate detection method and system | |
| CN112306041A (en) | Vehicle configuration information writing method and device and electronic equipment | |
| CN111610965A (en) | Standard SDK (software development kit) making method and device of access control platform | |
| CN114896161A (en) | File construction method and device based on artificial intelligence, computer equipment and medium | |
| CN113886302A (en) | Serial port number obtaining method and device of application equipment, terminal equipment and storage medium | |
| CN113934198A (en) | Vehicle diagnosis method, vehicle diagnosis device, electronic device, and storage medium | |
| CN114330278A (en) | Method and equipment for judging consistency of returned data | |
| CN113806231A (en) | Code coverage rate analysis method, device, equipment and medium | |
| CN112949258A (en) | Data processing method and device, electronic equipment and storage medium | |
| CN107977315B (en) | Embedded software object code unit testing method based on Bootloader mode | |
| CN111338956A (en) | Automatic pressure measurement method, device, equipment and storage medium | |
| CN112445491A (en) | File sequence processing method and device, terminal equipment and storage medium | |
| CN114756440B (en) | Data writing method, device and equipment of smart card and storage medium | |
| CN111597101A (en) | SDK access state detection method, computer device and computer readable storage medium |
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 |