CN112631905A - Execution process data management method and device, computer equipment and storage medium - Google Patents
Execution process data management method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN112631905A CN112631905A CN202011503864.7A CN202011503864A CN112631905A CN 112631905 A CN112631905 A CN 112631905A CN 202011503864 A CN202011503864 A CN 202011503864A CN 112631905 A CN112631905 A CN 112631905A
- Authority
- CN
- China
- Prior art keywords
- process data
- execution process
- test data
- data
- program
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Abstract
The embodiment of the invention discloses a method and a device for managing execution process data, computer equipment and a storage medium, and relates to the technical field of block chains. The method comprises the following steps: acquiring tracking IDs of the test data, wherein the tracking IDs of different test data are different; inputting the test data into a program to be tested, and recording execution process data of the test data in the program to be tested; storing the corresponding relation between the execution process data and the tracking ID of the test data into a preset database; and if an inquiry request is received, acquiring execution process data from the database according to the tracking ID contained in the inquiry request, and displaying the execution process data. According to the technical scheme of the embodiment of the invention, the execution process data of the test data in the program can be recorded in detail, and not only the result is recorded, so that a user can quickly and clearly locate the specific problem of the program, the problem troubleshooting efficiency of the user is improved, and the software development efficiency is improved.
Description
Technical Field
The invention relates to the technical field of software development and testing, in particular to a method and a device for managing execution process data, computer equipment and a storage medium.
Background
Testing is an essential link in software development. The general steps of the current test are: a tester finds a BUG, and then records the BUG in a BUG system in a mode of adding pictures to characters, describes which function module the content comprises, clicks what button or operates what step to report errors, and also describes which interface reports errors in detail, and the current interface parameters describe which function point has problems when being stolen. After receiving the bug, the developer generally checks whether the error is reported or not in the log system, and the log can be played again if the error is not found, so that the tester can play the operation again, then check whether the log has problems or not, and possibly repeat the previous steps if the log has no problems. The problem that the bug is solved for a long time and has low efficiency and can not be found out if the bug can not be solved for a certain time, thereby causing potential hidden danger.
The most common way of tracking problem records at present is to use a log system, and a log platform uses test data keywords to query log details, so that where a program is executed can be judged, and partial error information can be checked. The above methods have disadvantages including: only the program execution result can be seen, and the program execution process cannot be inquired.
Disclosure of Invention
The embodiment of the invention provides a method and a device for managing execution process data, computer equipment and a storage medium, and aims to solve the problem that the execution process of a program cannot be inquired because only the execution result of the program can be seen through a log, so that the problem of slow program inspection is caused.
In a first aspect, an embodiment of the present invention provides an execution process data management method, which includes:
acquiring tracking IDs of the test data, wherein the tracking IDs of different test data are different;
inputting the test data into a program to be tested, and recording execution process data of the test data in the program to be tested;
storing the corresponding relation between the execution process data and the tracking ID of the test data into a preset database;
and if an inquiry request is received, acquiring execution process data from the database according to the tracking ID contained in the inquiry request, and displaying the execution process data.
In a second aspect, an embodiment of the present invention further provides an execution process data management apparatus, including:
the generating unit is used for acquiring the tracking ID of the test data, and the tracking IDs of different test data are different;
the recording unit is used for inputting the test data into a program to be tested and recording the execution process data of the test data in the program to be tested;
the storage unit is used for storing the corresponding relation between the execution process data and the tracking ID of the test data into a preset database;
and the query unit is used for acquiring the execution process data from the database according to the tracking ID contained in the query request and displaying the execution process data if the query request is received.
In a third aspect, an embodiment of the present invention further provides a computer device, which includes a memory and a processor, where the memory stores a computer program, and the processor implements the above method when executing the computer program.
In a fourth aspect, the present invention also provides a computer-readable storage medium, which stores a computer program, and the computer program can implement the above method when being executed by a processor.
The embodiment of the invention provides a method and a device for managing execution process data, computer equipment and a storage medium. Wherein the method comprises the following steps: acquiring tracking IDs of the test data, wherein the tracking IDs of different test data are different; inputting the test data into a program to be tested, and recording execution process data of the test data in the program to be tested; storing the corresponding relation between the execution process data and the tracking ID of the test data into a preset database; and if an inquiry request is received, acquiring execution process data from the database according to the tracking ID contained in the inquiry request, and displaying the execution process data. According to the technical scheme of the embodiment of the invention, the execution process data of the test data in the program can be recorded in detail, and not only the result is recorded, so that a user can quickly and clearly locate the specific problem of the program, the problem troubleshooting efficiency of the user is improved, and the software development efficiency is improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 is a flowchart illustrating a process data management method according to an embodiment of the present invention;
FIG. 2 is a sub-flow diagram of a process data management method according to an embodiment of the present invention;
FIG. 3 is a sub-flow diagram of a process data management method according to an embodiment of the present invention;
FIG. 4 is a sub-flow diagram of a process data management method according to an embodiment of the present invention;
FIG. 5 is a sub-flow diagram of a process data management method according to an embodiment of the present invention;
FIG. 6 is a flowchart illustrating a method for process data management according to another embodiment of the present invention;
FIG. 7 is a schematic block diagram of a process data management apparatus provided in an embodiment of the present invention;
FIG. 8 is a schematic block diagram of a process data management apparatus according to another embodiment of the present invention;
fig. 9 is a schematic block diagram of a computer device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
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 invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the specification of the present invention 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 ]".
Referring to fig. 1, fig. 1 is a flowchart illustrating a method for executing process data management according to an embodiment of the present invention. The invention can be applied to intelligent government affairs/intelligent city management/intelligent community/intelligent security/intelligent logistics/intelligent medical treatment/intelligent education/intelligent environmental protection/intelligent traffic scenes, thereby promoting the construction of intelligent cities. As shown, the method includes the following steps S1-S4.
And S1, acquiring the trace ID of the test data, wherein the trace ID of different test data is different.
In a specific implementation, the trace ID is an identifier of the test data, and is used to search the execution process data of the test data. Meanwhile, in order to avoid confusion, the trace ID of each test data is different.
In an embodiment, the obtaining of the trace ID of the test data in the above steps includes the following steps:
and acquiring the hash value of the test data, and taking the hash value of the test data as the tracking ID of the test data.
Hash value, (Hash Function) is a method of creating a small digital "fingerprint" from any kind of data. The hash value of the data is unique and the hash value of different data is different.
The hash value of the test data is used as the trace ID of the test data, so that the trace ID of the test data is unique, and trace ID repetition is effectively avoided.
And S2, inputting the test data into a program to be tested, and recording the execution process data of the test data in the program to be tested.
In specific implementation, the test data is input into a program to be tested so as to test the program to be tested.
And in the test process, synchronously recording the execution process data of the test data in the program to be tested. Such as the method by which the test data passes, the content of the variables. The most detailed execution process can be recorded to each line of code.
By recording the execution process data of the test data in the program to be tested, a program developer can conveniently and accurately know the execution process of the test data in the program to be tested, so that the efficiency of troubleshooting and fault repairing is improved.
Referring to fig. 2, in an embodiment, the program to be tested includes a plurality of code segments, and the above steps record execution process data of the test data in the program to be tested, and specifically include the following steps:
s21, obtaining the execution parameters and the execution results of each code segment.
In specific implementation, the code segment refers to a code capable of independently completing a certain complete function in the program to be tested. Such as code segments that independently perform interface call functions.
The execution parameters of a code segment include its variable parameters, and if the code segment is for calling an interface, also the interface parameters of the interface it calls. The execution result refers to an output result of the code segment. The execution process of the code segment can be clearly shown through the execution parameters and the execution result of the code segment, and the analysis by a user is facilitated.
It is understood that the execution parameters of the code segment are set by the tester according to the actual situation, and the invention is not limited in particular.
S22, recording the code segments, the execution parameters of the code segments, and the execution results into a predetermined recording file.
In a specific implementation, the record file is used for correspondingly recording the execution parameters and the execution results of each code segment and each code segment.
The record file may be embodied as an EXCEL file, or other type of file, and the present invention is not particularly limited thereto.
Specifically, in an embodiment, the following table 1 records the execution parameters and the execution results of each code segment and each code segment.
| Serial number | Code segment | Execution | Execution results | |
| 1 | ||||
| 2 |
Table 1 executive data record table
And S3, storing the corresponding relation between the execution process data and the tracking ID of the test data into a preset database.
In specific implementation, a database is pre-constructed, and the execution process data of the test data and the tracking ID of the test data are correspondingly stored in the database, so that a user can conveniently query the execution process data of the test data according to the tracking ID of the test data.
In one embodiment, the trace ID of the execution process data and the trace ID of the test data are further stored into a blockchain, so as to ensure that the execution process data is not tampered, thereby improving reliability and security thereof.
Referring to fig. 3, in an embodiment, the step of storing the corresponding relationship between the execution process data and the trace ID of the test data in a preset database includes the following steps:
s31, compressing the record file into a compressed file.
In this embodiment, the execution process data is stored in the log file. In order to reduce the memory occupation, the recording file is compressed into a compressed file. The algorithm used in the compression process may specifically select a dictionary algorithm, a fixed bit length algorithm, and the like, and the present invention is not particularly limited.
And S32, correspondingly storing the compressed file and the trace ID of the test data into a database.
In a specific implementation, the database is a pre-established database, for example, MYSQL database may be selected. In the database, the compressed file corresponding to the test data and the trace ID of the test data are correspondingly stored, that is, a mapping relation is established between the compressed file corresponding to the test data and the trace ID of the test data. Thus, the corresponding compressed file can be queried by tracking the ID.
And S4, if an inquiry request is received, acquiring the execution process data from the database according to the tracking ID contained in the inquiry request, and displaying the execution process data.
In specific implementation, according to the tracking ID included in the query request, corresponding execution process data is searched in the database, and the execution process data is displayed on a display page of the terminal.
Referring to fig. 4, in an embodiment, the above steps obtain execution process data from the database according to the tracking ID included in the query request, and specifically include the following steps:
and S41, searching the compressed file in the database by taking the tracking ID contained in the query request as a retrieval condition.
And S42, decompressing the compressed file to obtain a record file, and calling the execution process data of the test data from the record file.
Referring to fig. 5, in an embodiment, the above steps show the execution process data, and specifically include the following steps:
and S51, displaying a code display frame, a parameter display frame and a result display frame.
In specific implementation, a code display frame, a parameter display frame and a result display frame are displayed on a display page of the terminal.
It is understood that the number of the code exhibition boxes, the parameter exhibition boxes, and the result exhibition boxes is consistent with the number of the code segments. Namely, for each code segment, a group of code display frames, parameter display frames and result display frames are displayed correspondingly.
S52, filling the code segment of the program to be tested, the execution parameters of the code segment, and the execution result of the code segment into the code display frame, the parameter display frame, and the result display frame, respectively.
In the specific implementation, the code segment of the program to be tested, the execution parameter of the code segment and the execution result of the code segment are respectively filled into the code display frame, the parameter display frame and the result display frame, so that a user can conveniently compare and check the program to be tested, problems can be found as soon as possible, and the checking speed is improved.
It can be understood that, if the code segment has multiple segments, each code segment, its execution parameters and execution results are filled into the corresponding code display frame, parameter display frame and result display frame, respectively.
By applying the technical scheme of the invention, the tracking ID of the test data is obtained, and the tracking IDs of different test data are different; inputting the test data into a program to be tested, and recording execution process data of the test data in the program to be tested; storing the corresponding relation between the execution process data and the tracking ID of the test data into a preset database; and if an inquiry request is received, acquiring execution process data from the database according to the tracking ID contained in the inquiry request, and displaying the execution process data. According to the technical scheme of the embodiment of the invention, the execution process data of the test data in the program can be recorded in detail, and not only the result is recorded, so that a user can quickly and clearly locate the specific problem of the program, the problem troubleshooting efficiency of the user is improved, and the software development efficiency is improved.
FIG. 6 is a flowchart illustrating a method for performing process data management according to another embodiment of the invention. As shown in fig. 6, the execution procedure data management method of the present embodiment includes steps S210 to S270.
S61, receiving the test data, and judging whether the test data contains debug parameters.
In a specific implementation, the test data refers to data for testing a program to be tested, and the test data is pre-selected by a person skilled in the art according to a test requirement of the program to be tested, which is not limited in this invention. The technical scheme of the invention aims to record the execution process data of the test data in the program to be tested. However, due to the limitation of storage resources, not all test data need to record its execution process data. In the invention, only the test data containing debug parameters can record the execution process data.
Therefore, when test data is received, it is first determined whether the test data includes debug parameters. If yes, the execution process data of the test data needs to be recorded. Otherwise, the execution process data of the test data does not need to be recorded.
And S62, if the test data contain debug parameters, acquiring the trace IDs of the test data, wherein the trace IDs of different test data are different.
In a specific implementation, the trace ID is an identifier of the test data, and is used to search the execution process data of the test data. Meanwhile, in order to avoid confusion, the trace ID of each test data is different.
In an embodiment, the obtaining of the trace ID of the test data in the above steps includes the following steps:
and acquiring the hash value of the test data, and taking the hash value of the test data as the tracking ID of the test data.
Hash value, (Hash Function) is a method of creating a small digital "fingerprint" from any kind of data. The hash value of the data is unique and the hash value of different data is different.
The hash value of the test data is used as the trace ID of the test data, so that the trace ID of the test data is unique, and trace ID repetition is effectively avoided.
And S63, inputting the test data into a program to be tested, and recording the execution process data of the test data in the program to be tested.
In specific implementation, the test data is input into a program to be tested so as to test the program to be tested.
And in the test process, synchronously recording the execution process data of the test data in the program to be tested. Such as the method by which the test data passes, the content of the variables. The most detailed execution process can be recorded to each line of code.
By recording the execution process data of the test data in the program to be tested, a program developer can conveniently and accurately know the execution process of the test data in the program to be tested, so that the efficiency of troubleshooting and fault repairing is improved.
And S64, storing the corresponding relation between the execution process data and the trace ID of the test data into a preset database.
In specific implementation, a database is pre-constructed, and the execution process data of the test data and the tracking ID of the test data are correspondingly stored in the database, so that a user can conveniently query the execution process data of the test data according to the tracking ID of the test data.
In one embodiment, the trace ID of the execution process data and the trace ID of the test data are further stored into a blockchain, so as to ensure that the execution process data is not tampered, thereby improving reliability and security thereof.
And S65, if receiving the query request, acquiring the execution process data from the database according to the tracking ID contained in the query request, and displaying the execution process data.
In specific implementation, according to the tracking ID included in the query request, corresponding execution process data is searched in the database, and the execution process data is displayed on a display page of the terminal.
And S66, setting the time for clearing the execution process data.
In a specific implementation, step S66 is performed after step S64. Specifically, after the execution process data and the trace ID of the test data are correspondingly stored in a preset database, the time for clearing the execution process data is set.
For example, in one embodiment, if the time of the expired cleaning of the execution process data is set to be zero after 3 days, the execution process data is deleted at the zero after 3 days.
And S67, if the time of the execution process data being out of date is reached, deleting the execution process data from the database.
In specific implementation, when the time for cleaning the execution process data is expired, the execution process data is deleted from the database, so that the storage space can be released, and the storage load of a server is reduced.
Referring to fig. 7, fig. 7 is a schematic block diagram of an implementation process data management device 70 according to an embodiment of the present invention. The present invention also provides an execution process data management apparatus 70 corresponding to the above execution process data management method. The execution process data management device 70 includes a unit for executing the execution process data management method, and the execution process data management device 70 may be configured in a desktop computer, a tablet computer, a portable computer, or the like. Specifically, the execution process data management device 70 includes a generation unit 71, a recording unit 72, a storage unit 73, and a query unit 74.
A generating unit 71, configured to obtain trace IDs of the test data, where the trace IDs of different test data are different;
the recording unit 72 is configured to input the test data into a program to be tested, and record execution process data of the test data in the program to be tested;
a storage unit 73, configured to store the corresponding relationship between the execution process data and the trace ID of the test data in a preset database;
and the query unit 74 is configured to, if a query request is received, obtain execution process data from the database according to the tracking ID included in the query request, and display the execution process data.
In an embodiment, the program under test includes a plurality of code segments, and the recording of the execution process data of the test data in the program under test includes:
acquiring execution parameters and execution results of the code segments;
and correspondingly recording the execution parameters and the execution results of the code segments and the code segments into a preset recording file.
In an embodiment, the storing the correspondence between the trace ID of the execution process data and the trace ID of the test data into a preset database includes:
compressing the record file into a compressed file;
and correspondingly storing the compressed file and the trace ID of the test data into a database.
In an embodiment, the obtaining execution process data from the database according to the tracking ID included in the query request includes:
searching a compressed file in the database by taking the tracking ID contained in the query request as a retrieval condition;
and decompressing the compressed file to obtain a record file, and calling the execution process data of the test data from the record file.
In one embodiment, said presenting said execution process data comprises:
displaying a code display frame, a parameter display frame and a result display frame;
and filling the code segment of the program to be tested, the execution parameter of the code segment and the execution result of the code segment into the code display frame, the parameter display frame and the result display frame respectively.
Fig. 8 is a schematic block diagram of an execution process data management apparatus 70 according to another embodiment of the present invention. As shown in fig. 8, the execution procedure data management apparatus 70 of the present embodiment is the above-described embodiment, and is added with a judgment unit 75, a setting unit 76, and a deletion unit 77.
The determining unit 75 is configured to receive the test data, and determine whether the test data includes debug parameters.
A setting unit 76 for setting the time of the expired cleaning of the execution process data.
A deleting unit 77, configured to delete the execution process data from the database if the time for clearing the execution process data expires.
It should be noted that, as can be clearly understood by those skilled in the art, the specific implementation processes of the above-mentioned execution process data management apparatus 70 and each unit may refer to the corresponding descriptions in the foregoing method embodiments, and for convenience and brevity of description, no further description is provided herein.
The execution process data management means 70 may be implemented in the form of a computer program that can be run on a computer device as shown in fig. 9.
Referring to fig. 9, fig. 9 is a schematic block diagram of a computer device according to an embodiment of the present application. The computer device 500 may be a terminal. The terminal can be an electronic device with a communication function, such as a smart phone, a tablet computer, a notebook computer, a desktop computer, a personal digital assistant and a wearable device.
The computer device 500 includes a processor 502, memory, and a network interface 505 connected by a system bus 501, where the memory may include a non-volatile storage medium 503 and an internal memory 504.
The non-volatile storage medium 503 may store an operating system 5031 and a computer program 5032. The computer programs 5032, when executed, cause the processor 502 to perform a method of performing process data management.
The processor 502 is used to provide computing and control capabilities to support the operation of the overall computer device 500.
The internal memory 504 provides an environment for the operation of the computer program 5032 in the non-volatile storage medium 503, and when the computer program 5032 is executed by the processor 502, the processor 502 can be caused to execute a method for performing process data management.
The network interface 505 is used for network communication with other devices. Those skilled in the art will appreciate that the above-described architecture, which is merely a block diagram of portions of architecture associated with aspects of the present application, is not intended to limit the computing device 500 to which aspects of the present application may be applied, and that a particular computing device 500 may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
Wherein the processor 502 is configured to run the computer program 5032 stored in the memory to implement the following steps:
acquiring tracking IDs of the test data, wherein the tracking IDs of different test data are different;
inputting the test data into a program to be tested, and recording execution process data of the test data in the program to be tested;
storing the corresponding relation between the execution process data and the tracking ID of the test data into a preset database;
and if an inquiry request is received, acquiring execution process data from the database according to the tracking ID contained in the inquiry request, and displaying the execution process data.
The processor 502 further implements the following steps before implementing the trace ID for the acquired test data:
receiving test data, and judging whether the test data contains debug parameters;
and if the test data contains debug parameters, executing the step of obtaining the trace ID of the test data.
In an embodiment, after the step of storing the correspondence between the trace IDs of the execution process data and the test data in the preset database, the processor 502 further performs the following steps:
setting an overdue cleaning time of the execution process data;
and if the time for clearing the expiration of the execution process data is reached, deleting the execution process data from the database.
In an embodiment, the program under test includes a plurality of code segments, and the recording of the execution process data of the test data in the program under test includes:
acquiring execution parameters and execution results of the code segments;
and correspondingly recording the execution parameters and the execution results of the code segments and the code segments into a preset recording file.
In an embodiment, the storing the correspondence between the trace ID of the execution process data and the trace ID of the test data into a preset database includes:
compressing the record file into a compressed file;
and correspondingly storing the compressed file and the trace ID of the test data into a database.
In an embodiment, the obtaining execution process data from the database according to the tracking ID included in the query request includes:
searching a compressed file in the database by taking the tracking ID contained in the query request as a retrieval condition;
and decompressing the compressed file to obtain a record file, and calling the execution process data of the test data from the record file.
In one embodiment, said presenting said execution process data comprises:
displaying a code display frame, a parameter display frame and a result display frame;
and filling the code segment of the program to be tested, the execution parameter of the code segment and the execution result of the code segment into the code display frame, the parameter display frame and the result display frame respectively.
It should be understood that in the embodiment of the present Application, the Processor 502 may be a Central Processing Unit (CPU), and the Processor 502 may also be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, and the like. Wherein a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
It will be understood by those skilled in the art that all or part of the flow of the method implementing the above embodiments may be implemented by a computer program instructing associated hardware. The computer program may be stored in a storage medium, which is a computer-readable storage medium. The computer program is executed by at least one processor in the computer system to implement the flow steps of the embodiments of the method described above.
Accordingly, the present invention also provides a storage medium. The storage medium may be a computer-readable storage medium. The storage medium stores a computer program. The computer program, when executed by a processor, causes the processor to perform the steps of:
acquiring tracking IDs of the test data, wherein the tracking IDs of different test data are different;
inputting the test data into a program to be tested, and recording execution process data of the test data in the program to be tested;
storing the corresponding relation between the execution process data and the tracking ID of the test data into a preset database;
and if an inquiry request is received, acquiring execution process data from the database according to the tracking ID contained in the inquiry request, and displaying the execution process data.
In one embodiment, before executing the computer program to implement the obtaining of the trace ID of the test data, the processor further implements the following steps:
receiving test data, and judging whether the test data contains debug parameters;
and if the test data contains debug parameters, executing the step of obtaining the trace ID of the test data.
In an embodiment, after the step of storing the correspondence between the trace IDs of the execution process data and the test data in a preset database is implemented by the processor by executing the computer program, the following steps are further implemented:
setting an overdue cleaning time of the execution process data;
and if the time for clearing the expiration of the execution process data is reached, deleting the execution process data from the database.
In an embodiment, the program under test includes a plurality of code segments, and the recording of the execution process data of the test data in the program under test includes:
acquiring execution parameters and execution results of the code segments;
and correspondingly recording the execution parameters and the execution results of the code segments and the code segments into a preset recording file.
In an embodiment, the storing the correspondence between the trace ID of the execution process data and the trace ID of the test data into a preset database includes:
compressing the record file into a compressed file;
and correspondingly storing the compressed file and the trace ID of the test data into a database.
In an embodiment, the obtaining execution process data from the database according to the tracking ID included in the query request includes:
searching a compressed file in the database by taking the tracking ID contained in the query request as a retrieval condition;
and decompressing the compressed file to obtain a record file, and calling the execution process data of the test data from the record file.
In one embodiment, said presenting said execution process data comprises:
displaying a code display frame, a parameter display frame and a result display frame;
and filling the code segment of the program to be tested, the execution parameter of the code segment and the execution result of the code segment into the code display frame, the parameter display frame and the result display frame respectively.
The storage medium is an entity and non-transitory storage medium, and may be various entity storage media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a magnetic disk, or an optical disk. The computer readable storage medium may be non-volatile or volatile.
Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be embodied in electronic hardware, computer software, or combinations of both, and that the components and steps of the examples have been described in a functional general in the foregoing description for the purpose of illustrating clearly the interchangeability of hardware and software. 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 invention.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative. For example, the division of each unit is only one logic function division, and there may be another division manner in actual implementation. For example, various elements or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented.
The steps in the method of the embodiment of the invention can be sequentially adjusted, combined and deleted according to actual needs. The units in the device of the embodiment of the invention can be merged, divided and deleted according to actual needs. In addition, functional units in the embodiments of the present invention 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, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a storage medium. Based on such understanding, the technical solution of the present invention essentially or partially contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a terminal, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, while the invention has been described with respect to the above-described embodiments, it will be understood that the invention is not limited thereto but may be embodied with various modifications and changes.
While the invention has been described with reference to specific embodiments, the invention is not limited thereto, and various equivalent modifications and substitutions can be easily made by those skilled in the art within the technical scope of the invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (10)
1. An executive process data management method, comprising:
acquiring tracking IDs of the test data, wherein the tracking IDs of different test data are different;
inputting the test data into a program to be tested, and recording execution process data of the test data in the program to be tested;
storing the corresponding relation between the execution process data and the tracking ID of the test data into a preset database;
and if an inquiry request is received, acquiring execution process data from the database according to the tracking ID contained in the inquiry request, and displaying the execution process data.
2. The method of claim 1, wherein prior to obtaining the trace ID for the test data, the method further comprises:
receiving test data, and judging whether the test data contains debug parameters;
and if the test data contains debug parameters, executing the step of obtaining the trace ID of the test data.
3. The execution process data management method according to claim 1, wherein after storing the correspondence between the execution process data and the trace ID of the test data in a preset database, the method further comprises:
setting an overdue cleaning time of the execution process data;
and if the time for clearing the expiration of the execution process data is reached, deleting the execution process data from the database.
4. The execution process data management method according to claim 1, wherein the program under test includes a plurality of code segments, and the recording of the execution process data of the test data in the program under test includes:
acquiring execution parameters and execution results of the code segments;
and correspondingly recording the execution parameters and the execution results of the code segments and the code segments into a preset recording file.
5. The execution process data management method according to claim 4, wherein the storing the correspondence between the trace IDs of the execution process data and the test data in a preset database includes:
compressing the record file into a compressed file;
and correspondingly storing the compressed file and the trace ID of the test data into a database.
6. The execution process data management method according to claim 5, wherein the acquiring execution process data from the database according to the tracking ID included in the query request includes:
searching a compressed file in the database by taking the tracking ID contained in the query request as a retrieval condition;
and decompressing the compressed file to obtain a record file, and calling the execution process data of the test data from the record file.
7. The executive process data management method of claim 5, wherein the presenting the executive process data comprises:
displaying a code display frame, a parameter display frame and a result display frame;
and filling the code segment of the program to be tested, the execution parameter of the code segment and the execution result of the code segment into the code display frame, the parameter display frame and the result display frame respectively.
8. An executive process data management device, comprising:
the generating unit is used for acquiring the tracking ID of the test data, and the tracking IDs of different test data are different;
the recording unit is used for inputting the test data into a program to be tested and recording the execution process data of the test data in the program to be tested;
the storage unit is used for storing the corresponding relation between the execution process data and the tracking ID of the test data into a preset database;
and the query unit is used for acquiring the execution process data from the database according to the tracking ID contained in the query request and displaying the execution process data if the query request is received.
9. A computer arrangement, characterized in that the computer arrangement comprises a memory having stored thereon a computer program and a processor implementing the method according to any of claims 1-7 when executing the computer program.
10. A computer-readable storage medium, characterized in that the storage medium stores a computer program which, when executed by a processor, implements the method according to any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011503864.7A CN112631905A (en) | 2020-12-18 | 2020-12-18 | Execution process data management method and device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011503864.7A CN112631905A (en) | 2020-12-18 | 2020-12-18 | Execution process data management method and device, computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112631905A true CN112631905A (en) | 2021-04-09 |
Family
ID=75316981
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011503864.7A Pending CN112631905A (en) | 2020-12-18 | 2020-12-18 | Execution process data management method and device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112631905A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115061940A (en) * | 2022-07-28 | 2022-09-16 | 德萱(天津)科技发展有限公司 | Data processing method and system based on software research and development process |
-
2020
- 2020-12-18 CN CN202011503864.7A patent/CN112631905A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115061940A (en) * | 2022-07-28 | 2022-09-16 | 德萱(天津)科技发展有限公司 | Data processing method and system based on software research and development process |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107729227B (en) | Application program test range determining method, system, server and storage medium | |
| CN107045477B (en) | Quality assessment platform capable of carrying out multi-dimensional detection | |
| CN109871368B (en) | Database detection method, database detection device, computer device and storage medium | |
| CN110990274A (en) | Data processing method, device and system for generating test case | |
| CN112328499A (en) | Test data generation method, device, equipment and medium | |
| CN114116505A (en) | Code testing method and device | |
| CN108399125B (en) | Automatic testing method and device, computer equipment and storage medium | |
| CN112631905A (en) | Execution process data management method and device, computer equipment and storage medium | |
| CN105912467B (en) | Performance test method and device | |
| CN112835779A (en) | Test case determination method and device and computer equipment | |
| CN112231232A (en) | Method, device and equipment for determining test data model and generating test data | |
| CN112363944A (en) | Method and equipment for comparing return values of multiple environment interfaces | |
| CN111767222A (en) | Data model verification method and device, electronic equipment and storage medium | |
| CN111190986A (en) | Map data comparison method and device | |
| CN114818645B (en) | Automatic report generation method, device, equipment and medium based on data body | |
| CN116795723B (en) | Chain unit test processing method and device and computer equipment | |
| CN113987010B (en) | Method and device for realizing insight of multi-dimensional data set | |
| CN112099838B (en) | Method, device and storage medium for determining version difference | |
| CN116467208A (en) | Interface automatic test method and device and computer equipment | |
| CN116909876A (en) | Debugging method, debugging device, computer device, storage medium, and program product | |
| CN117195855A (en) | Work order duplicate checking method and device and related equipment | |
| CN114416565A (en) | Data processing method, device, server and storage medium | |
| CN117370154A (en) | Method and device for identifying failure use cases, electronic equipment and storage medium | |
| CN113656318A (en) | Software version testing method and device and computer equipment | |
| CN114116519A (en) | Interface test method and device, electronic equipment and 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 |