CN111090578A - Project development joint debugging method and device, computer equipment and storage medium - Google Patents
Project development joint debugging method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN111090578A CN111090578A CN201910969973.9A CN201910969973A CN111090578A CN 111090578 A CN111090578 A CN 111090578A CN 201910969973 A CN201910969973 A CN 201910969973A CN 111090578 A CN111090578 A CN 111090578A
- Authority
- CN
- China
- Prior art keywords
- data
- target
- target background
- joint debugging
- address
- 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.)
- Granted
Links
- 238000011161 development Methods 0.000 title claims abstract description 52
- 238000000034 method Methods 0.000 title claims abstract description 51
- 238000005538 encapsulation Methods 0.000 claims abstract description 48
- 238000004458 analytical method Methods 0.000 claims abstract description 35
- 230000002452 interceptive effect Effects 0.000 claims abstract description 22
- 238000004806 packaging method and process Methods 0.000 claims abstract description 13
- 238000004590 computer program Methods 0.000 claims description 15
- 238000012790 confirmation Methods 0.000 claims description 7
- 238000007405 data analysis Methods 0.000 claims description 4
- 230000004044 response Effects 0.000 description 14
- 238000010586 diagram Methods 0.000 description 10
- 230000008569 process Effects 0.000 description 8
- 238000012545 processing Methods 0.000 description 8
- 238000004891 communication Methods 0.000 description 5
- 230000003993 interaction Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000006243 chemical reaction Methods 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000000605 extraction 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
- 238000000926 separation method Methods 0.000 description 1
- 238000000547 structure data Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
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/362—Software debugging
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a project development joint debugging method, a project development joint debugging device, computer equipment and a storage medium. The method comprises the steps that a target background connected with a ark framework platform is connected with a corresponding target background according to a target address of the target background; the target address comprises an IP address and a port number of a target background; receiving request data sent by the target background according to a front-end request, and inserting the request data into a pre-stored data encapsulation template for encapsulation to obtain encapsulation data; analyzing the packaging data to obtain corresponding analyzed data; and sending the analysis data to a display area of a debugging interactive interface for front-end display. The method realizes that the target address of the target background is directly connected with the target background for direct connection, and the target background can be accurately accessed for joint debugging after the target background is appointed, so that the joint debugging efficiency is improved.
Description
Technical Field
The invention relates to the technical field of function testing, in particular to a project development joint debugging method and device, computer equipment and a storage medium.
Background
In the existing ARK ARK architecture, when joint debugging of front and background projects is carried out in a development stage (joint debugging refers to interface debugging between a front-end page and background services), services are deployed in an ARK architecture platform when the background projects are started. The problem of random access can exist when the front-end page accesses the background service through the canoe architecture platform, namely the front-end page accesses the same interface for multiple times to obtain different background service feedback results instead of accessing the corresponding background service after the interface is appointed, and the joint debugging efficiency is reduced. Specifically, generally, a background engineer has multiple front-end engineers participating in developing different modules, and when multiple backgrounds are started to debug at the same time, a foreground accesses a service randomly and may not access the service to be accessed, which brings great difficulty to joint debugging.
Disclosure of Invention
The embodiment of the invention provides an engineering development joint debugging method, an engineering development joint debugging device, computer equipment and a storage medium, and aims to solve the problem that in the prior art, random access exists when a front-end page accesses background services through a ARK frame platform in an ARK frame, namely, the front-end page accesses the same interface for multiple times to obtain different background service feedback results, and the joint debugging efficiency is reduced.
In a first aspect, an embodiment of the present invention provides an engineering development joint debugging method, including:
connecting with a corresponding target background according to a target address of the target background connected with the ark framework platform; the target address comprises an IP address and a port number of a target background;
receiving request data sent by the target background according to a front-end request, and inserting the request data into a pre-stored data encapsulation template for encapsulation to obtain encapsulation data;
analyzing the packaging data to obtain corresponding analyzed data; and
and sending the analysis data to a display area of a debugging interactive interface for front-end display.
In a second aspect, an embodiment of the present invention provides an engineering development joint debugging apparatus, including:
the background direct connection unit is used for connecting the corresponding target background according to the target address of the target background connected with the ark framework platform; the target address comprises an IP address and a port number of a target background;
the data encapsulation unit is used for receiving request data sent by the target background according to the front-end request, inserting the request data into a pre-stored data encapsulation template and encapsulating to obtain encapsulated data;
the data analysis unit is used for analyzing the packaging data to obtain corresponding analysis data; and
and the data display unit is used for sending the analysis data to a display area of the debugging interactive interface for front-end display.
In a third aspect, an embodiment of the present invention further provides a computer device, which includes a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor, when executing the computer program, implements the joint debugging method for engineering development according to the first aspect.
In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program, and the computer program, when executed by a processor, causes the processor to execute the project development joint debugging method according to the first aspect.
The embodiment of the invention provides a project development joint debugging method, a project development joint debugging device, computer equipment and a storage medium, which realize that a target address of a target background is directly connected with the target background for direct connection, and the target background can be accurately accessed for joint debugging after the target background is appointed, so that the joint debugging 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 schematic view of an application scenario of an engineering development joint debugging method according to an embodiment of the present invention;
fig. 2 is a schematic flow chart of an engineering development joint debugging method according to an embodiment of the present invention;
fig. 3 is another schematic flow chart of the engineering development joint debugging method according to the embodiment of the present invention;
fig. 4 is another schematic flow chart of the project development joint debugging method according to the embodiment of the present invention;
fig. 5 is another schematic flow chart of the project development joint debugging method according to the embodiment of the present invention;
fig. 6 is a sub-flow diagram of the project development joint debugging method according to the embodiment of the present invention;
fig. 7 is a schematic block diagram of an engineering development joint debugging apparatus provided in an embodiment of the present invention;
FIG. 8 is another schematic block diagram of an engineering development joint debugging apparatus provided in an embodiment of the present invention;
fig. 9 is another schematic block diagram of an engineering development joint debugging apparatus provided in an embodiment of the present invention;
fig. 10 is another schematic block diagram of an engineering development joint debugging apparatus provided in an embodiment of the present invention;
fig. 11 is a schematic block diagram of a subunit of an engineering development joint debugging apparatus provided in an embodiment of the present invention;
FIG. 12 is a schematic block diagram of a computer device provided by 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.
Referring to fig. 1 and fig. 2, fig. 1 is a schematic view of an application scenario of an engineering development joint debugging method according to an embodiment of the present invention; fig. 2 is a schematic flowchart of an engineering development joint debugging method according to an embodiment of the present invention, where the engineering development joint debugging method is applied to a server and is executed by application software installed in the server.
As shown in fig. 2, the method includes steps S110 to S140.
S110, connecting the target background with the corresponding target background according to the target address of the target background connected with the ark framework platform; and the target address comprises an IP address and a port number of a target background.
In this embodiment, in order to more clearly understand the technical solution of the present application, the following describes the related terminal. The technical scheme is described in the angle of the front end.
The ARK canoe framework platform is abbreviated as a canoe framework platform and used for project of a front-end and rear-end separation framework, and the canoe framework is a set of micro-service framework similar to springclosed.
And the other is the front end of the ARK ARK frame platform, which is used by the front-end developer of the project to develop the project.
And thirdly, a background of the ARK ARK architecture platform is used by background developers of projects to develop the projects.
Generally, a background project in an ARK frame platform has multiple engineers participating in developing different modules, each module may have versions (e.g., V1.0 and V2.0 versions) in different periods, and when different versions of the same module are distributed on different backgrounds, when the multiple backgrounds are started to debug at the same time, a foreground will randomly access a certain background service corresponding to the module when accessing the service of the module, and may not access the service desired to be accessed, which brings great difficulty to joint debugging. For example, the front-end input access module a may receive feedback from one of background a1, background a2, and background A3, which results in inefficient joint debugging. At this time, in order to implement direct connection between the front end and the designated background, address information of the target background needs to be obtained, and after the obtained address information of the target background is analyzed, direct connection between the front end and the corresponding target background is implemented.
In an embodiment, as shown in fig. 3, step S110 further includes:
s101, acquiring an initial configuration file connected with a ark framework platform;
s102, receiving a target address of a target background, and replacing address information in the initial configuration file with the target address to obtain a current configuration file.
In one embodiment, step S110 includes:
and connecting with a corresponding target background according to the current configuration file.
In this embodiment, for example, the initial configuration file for the front end to connect to the ark frame platform is:
proxyTable:{
’/admin’:{
target:’https://aaaa.bbbb.com.cn’
pathRewrite:{
’^/admin’:’/’
},
},
}
and the address behind the target indicates that a background is randomly allocated by the ARK ARK frame platform after the front end is connected with the ARK ARK frame platform corresponding to the aaaa, bbbb, com and cn address.
When the target address information of the target background is obtained from the target background, the address after the target in the initial configuration file may be replaced with the target address information, for example, the target address information is 10.110.110.11:6000, and then aaaa, bbbb, com, cn is replaced with 10.110.110.11:6000, so that the current configuration file is obtained, where 10.110.110.11 in the target address information represents the IP address of the target background, and 6000 represents the port number of the target background. When the initial configuration file is modified into the current configuration file, the front end can be directly connected with the target background in an appointed mode.
However, since the communication between the front background and the front end is based on the data format of the ARK frame platform, if the front end directly sends a data request to the background directly connected with the front end, the data fed back by the background cannot be analyzed at the front end, and at this time, subsequent packaging processing of the data is required.
And S120, receiving request data sent back by the target background according to the front-end request, and inserting the request data into a pre-stored data encapsulation template for encapsulation to obtain encapsulated data.
In this embodiment, the front end generally stores a data encapsulation template for format conversion of request data returned and sent by the target background according to the front end request in advance, so that the front end can identify the corresponding request data. The data encapsulation template stored in the front end has at least two acquisition modes, wherein one mode is to extract from local historical request data of the front end, and the other mode is to acquire from interactive data in the canoe architecture platform.
In an embodiment, as shown in fig. 4, as a first embodiment of obtaining the data encapsulation template, step S110 further includes:
s103, obtaining local historical request data, and positioning a first data structure body which is the same as a preset keyword in the historical request data;
and S104, deleting the data in the first data structure body to obtain a data packaging template.
In this embodiment, the history request data is history data stored at the front end when the front end interacts with the rear end through the ARK frame platform, for example, the history data has a keyword of response.
In an embodiment, as shown in fig. 6, as a second embodiment of obtaining the data encapsulation template, step S110 further includes:
s105, acquiring interactive data in the ark framework platform, and positioning a second data structure body which is the same as a preset keyword in the interactive data;
and S106, deleting the data in the second data structure body to obtain a data packaging template.
In this embodiment, when the front end interacts with the background through the canoe architecture platform, interaction data is cached or permanently stored in the canoe architecture platform, and one of the interaction data stored in the canoe architecture platform is obtained as an analysis sample. For example, the interactive data has a keyword of response.data, and data content in the data structure body after the response.data is obtained, the specific data of the data structure body is generally in { }, for example, the response.data { } is the obtained data encapsulation template.
Through the two embodiments of obtaining the data encapsulation template, the data encapsulation template can be effectively extracted to encapsulate the request data, so that the front end can effectively identify the request data.
S130, analyzing the packaged data to obtain corresponding analyzed data.
In this embodiment, the encapsulated data is analyzed, that is, the data content in the data structure body of the encapsulated data is analyzed, so as to obtain the data fed back by the background. The reason why the request data is encapsulated through the encapsulation template is that the request data cannot be identified by the front end without the processing (because the front end can only identify the data fed back by the ARK ARK frame platform originally, the request data is subjected to the encapsulation processing of the ARK ARK frame platform before being fed back to the front end by the background, and the encapsulation process is preposed to the local part of the front end at this time), and the request data can be read and analyzed by the front end normal knowledge after being encapsulated through the encapsulation template in a local specified area of the front end to obtain the encapsulation data.
In one embodiment, as shown in fig. 6, step S130 includes:
s131, positioning and acquiring a data structure body of the packaging data;
and S132, acquiring data in the data structure body to obtain analysis data.
In this embodiment, the encapsulated data is parsed, that is, the encapsulation process is the reverse process. For example, the encapsulated data contains a keyword of response.data, and data content in a data structure body after the response.data is obtained, specific data of the data structure body is generally in { }, for example, data in parentheses in the response.data { } is obtained analysis data. The analysis data corresponding to the front-end request can be obtained by analyzing the encapsulated data, so that joint debugging can be performed at the front end.
And S140, sending the analysis data to a display area of the debugging interactive interface for front-end display.
In this embodiment, after the front end receives the analysis data (e.g., code data of the V2.0 version of the module a), in order to facilitate the front-end operation user to perform debugging, the analysis data needs to be sent to a display area of a debugging interactive interface for front-end display. The front end is provided with a debugging platform similar to the back end, and the analysis data is displayed in a display area of a debugging interactive interface of the debugging platform, so that developers at the front end can check or edit the analysis data conveniently.
In an embodiment, step S140 is followed by:
and if the editing confirmation instruction is detected, sending the editing information of the analyzed data to a target background.
In this embodiment, after the operation user at the front end views the analysis data, the analysis data can be modified and edited, an editing confirmation instruction is started after the editing is completed and the storage is clicked, and at this time, once the front end detects the editing confirmation instruction, the front end sends the editing information (i.e., the updated analysis data) of the analysis data to the target background, so as to realize joint debugging of the front end and the background.
The method realizes that the target address of the target background is directly connected with the target background for direct connection, and the target background can be accurately accessed for joint debugging after the target background is appointed, so that the joint debugging efficiency is improved.
The embodiment of the invention also provides an engineering development joint debugging device, which is used for executing any embodiment of the engineering development joint debugging method. Specifically, referring to fig. 7, fig. 7 is a schematic block diagram of an engineering development joint debugging apparatus according to an embodiment of the present invention. The project development joint debugging device 100 may be configured in a server.
As shown in fig. 7, the engineering development joint debugging apparatus 100 includes a background direct connection unit 110, a data encapsulation unit 120, a data analysis unit 130, and a data display unit 140.
The background direct-connection unit 110 is used for connecting a corresponding target background according to a target address of the target background connected with the ark framework platform; and the target address comprises an IP address and a port number of a target background.
In this embodiment, a background project in an ordinary ARK frame platform may have multiple engineers participating in developing different modules, each module may have versions (e.g., V1.0, V2.0 versions) in different periods, and if different versions of the same module are distributed on different backgrounds, when the multiple backgrounds are started simultaneously for debugging, a foreground will randomly access a certain background service corresponding to the module when accessing the service of the module, and may not access a service that is desired to be accessed, which brings great difficulty to joint debugging. For example, the front-end input access module a may receive feedback from one of background a1, background a2, and background A3, which results in inefficient joint debugging. At this time, in order to implement direct connection between the front end and the designated background, address information of the target background needs to be obtained, and after the obtained address information of the target background is analyzed, direct connection between the front end and the corresponding target background is implemented.
In an embodiment, as shown in fig. 8, the engineering development joint debugging apparatus 100 further includes:
an initial configuration file obtaining unit 101, configured to obtain an initial configuration file connected to the ark frame platform;
and the address replacing unit 102 is configured to receive a target address of a target background, and replace the address information in the initial configuration file with the target address to obtain a current configuration file.
In an embodiment, the background direct-connection unit S110 is further configured to:
and connecting with a corresponding target background according to the current configuration file.
In this embodiment, for example, the initial configuration file for the front end to connect to the ark frame platform is:
proxyTable:{
’/admin’:{
target:’https://aaaa.bbbb.com.cn’
pathRewrite:{
’^/admin’:’/’
},
},
}
and the address behind the target indicates that a background is randomly allocated by the ARK ARK frame platform after the front end is connected with the ARK ARK frame platform corresponding to the aaaa, bbbb, com and cn address.
When the target address information of the target background is obtained from the target background, the address after the target in the initial configuration file may be replaced with the target address information, for example, the target address information is 10.110.110.11:6000, and then aaaa, bbbb, com, cn is replaced with 10.110.110.11:6000, so that the current configuration file is obtained, where 10.110.110.11 in the target address information represents the IP address of the target background, and 6000 represents the port number of the target background. When the initial configuration file is modified into the current configuration file, the front end can be directly connected with the target background in an appointed mode.
However, since the communication between the front background and the front end is based on the data format of the ARK frame platform, if the front end directly sends a data request to the background directly connected with the front end, the data fed back by the background cannot be analyzed at the front end, and at this time, subsequent packaging processing of the data is required.
And the data encapsulation unit 120 is configured to receive request data sent back by the target background according to the front-end request, and insert the request data into a pre-stored data encapsulation template for encapsulation to obtain encapsulated data.
In this embodiment, the front end generally stores a data encapsulation template for format conversion of request data returned and sent by the target background according to the front end request in advance, so that the front end can identify the corresponding request data. The data encapsulation template stored in the front end has at least two acquisition modes, wherein one mode is to extract from local historical request data of the front end, and the other mode is to acquire from interactive data in the canoe architecture platform.
In an embodiment, as shown in fig. 9, as a first embodiment of obtaining a data encapsulation template, the engineering development joint debugging apparatus 100 further includes:
a first data structure acquiring unit 103, configured to acquire local history request data, and locate a first data structure in the history request data that is the same as a preset keyword;
and a first data deleting unit 104, configured to delete the data in the first data structure to obtain a data encapsulation template.
In this embodiment, the history request data is history data stored at the front end when the front end interacts with the rear end through the ARK frame platform, for example, the history data has a keyword of response.
In an embodiment, as shown in fig. 10, as a second embodiment of obtaining a data encapsulation template, the engineering development joint debugging apparatus 100 further includes:
a second data structure obtaining unit 105, configured to obtain interactive data in the ark frame platform, and locate a second data structure in the interactive data that is the same as a preset keyword;
and a second data deleting unit 106, configured to delete the data in the second data structure, so as to obtain a data encapsulation template.
In this embodiment, when the front end interacts with the background through the canoe architecture platform, interaction data is cached or permanently stored in the canoe architecture platform, and one of the interaction data stored in the canoe architecture platform is obtained as an analysis sample. For example, the interactive data has a keyword of response.data, and data content in the data structure body after the response.data is obtained, the specific data of the data structure body is generally in { }, for example, the response.data { } is the obtained data encapsulation template.
Through the two embodiments of obtaining the data encapsulation template, the data encapsulation template can be effectively extracted to encapsulate the request data, so that the front end can effectively identify the request data.
And a data analysis unit 130, configured to analyze the encapsulation data to obtain corresponding analysis data.
In this embodiment, the encapsulated data is analyzed, that is, the data content in the data structure body of the encapsulated data is analyzed, so as to obtain the data fed back by the background. The reason why the request data is encapsulated through the encapsulation template is that the request data cannot be identified by the front end without the processing (because the front end can only identify the data fed back by the ARK ARK frame platform originally, the request data is subjected to the encapsulation processing of the ARK ARK frame platform before being fed back to the front end by the background, and the encapsulation process is preposed to the local part of the front end at this time), and the request data can be read and analyzed by the front end normal knowledge after being encapsulated through the encapsulation template in a local specified area of the front end to obtain the encapsulation data.
In one embodiment, as shown in fig. 11, the data parsing unit 130 includes:
a structure positioning unit 131 configured to position a data structure for acquiring the package data;
and a structure data extraction unit 132, configured to acquire data in the data structure to obtain analytic data.
In this embodiment, the encapsulated data is parsed, that is, the encapsulation process is the reverse process. For example, the encapsulated data contains a keyword of response.data, and data content in a data structure body after the response.data is obtained, specific data of the data structure body is generally in { }, for example, data in parentheses in the response.data { } is obtained analysis data. The analysis data corresponding to the front-end request can be obtained by analyzing the encapsulated data, so that joint debugging can be performed at the front end.
And the data display unit 140 is configured to send the analysis data to a display area of the debugging interactive interface for front-end display.
In this embodiment, after the front end receives the analysis data (e.g., code data of the V2.0 version of the module a), in order to facilitate the front-end operation user to perform debugging, the analysis data needs to be sent to a display area of a debugging interactive interface for front-end display. The front end is provided with a debugging platform similar to the back end, and the analysis data is displayed in a display area of a debugging interactive interface of the debugging platform, so that developers at the front end can check or edit the analysis data conveniently.
In an embodiment, the engineering development joint debugging apparatus 100 further includes:
and the edit data sending unit is used for sending the edit information of the analysis data to the target background if the edit confirmation instruction is detected.
In this embodiment, after the operation user at the front end views the analysis data, the analysis data can be modified and edited, an editing confirmation instruction is started after the editing is completed and the storage is clicked, and at this time, once the front end detects the editing confirmation instruction, the front end sends the editing information (i.e., the updated analysis data) of the analysis data to the target background, so as to realize joint debugging of the front end and the background.
The device realizes direct connection by directly connecting the target address of the target background with the target background, and can accurately access the target background after the target background is appointed to perform joint debugging, thereby improving the joint debugging efficiency.
The above engineering development joint debugging means may be implemented in the form of a computer program that can be run on a computer device as shown in fig. 12.
Referring to fig. 12, fig. 12 is a schematic block diagram of a computer device according to an embodiment of the present invention. The computer device 500 is a server, and the server may be an independent server or a server cluster composed of a plurality of servers.
Referring to fig. 12, 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 program 5032, when executed, causes the processor 502 to perform the joint debugging method for engineering development.
The processor 502 is used to provide computing and control capabilities that 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 enabled to execute the joint debugging method for engineering development.
The network interface 505 is used for network communication, such as providing transmission of data information. Those skilled in the art will appreciate that the configuration shown in fig. 12 is a block diagram of only a portion of the configuration associated with aspects of the present invention and is not intended to limit the computing device 500 to which aspects of the present invention 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.
The processor 502 is configured to run the computer program 5032 stored in the memory to implement the joint debugging method for engineering development disclosed in the embodiment of the present invention.
Those skilled in the art will appreciate that the embodiment of a computer device illustrated in fig. 12 does not constitute a limitation on the specific construction of the computer device, and that in other embodiments a computer device may include more or fewer components than those illustrated, or some components may be combined, or a different arrangement of components. For example, in some embodiments, the computer device may only include a memory and a processor, and in such embodiments, the structures and functions of the memory and the processor are consistent with those of the embodiment shown in fig. 12, and are not described herein again.
It should be understood that, in the embodiment of the present invention, 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.
In another embodiment of the invention, a computer-readable storage medium is provided. The computer readable storage medium may be a non-volatile computer readable storage medium. The computer readable storage medium stores a computer program, wherein the computer program, when executed by a processor, implements the project development joint debugging method disclosed by the embodiments of the present invention.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described apparatuses, devices and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again. 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 by the present invention, it should be understood that the disclosed apparatus, device and method can be implemented in other ways. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only a logical division, and there may be other divisions when the actual implementation is performed, or units having the same function may be grouped into one unit, for example, a plurality of units or components may be combined or may be 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 also be an electric, mechanical or other form of connection.
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 of the present invention.
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 can be realized in a form of hardware, and can also be realized in a form of a software functional 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 stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: various 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.
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. A project development joint debugging method is characterized by comprising the following steps:
connecting with a corresponding target background according to a target address of the target background connected with the ark framework platform; the target address comprises an IP address and a port number of a target background;
receiving request data sent by the target background according to a front-end request, and inserting the request data into a pre-stored data encapsulation template for encapsulation to obtain encapsulation data;
analyzing the packaging data to obtain corresponding analyzed data; and
and sending the analysis data to a display area of a debugging interactive interface for front-end display.
2. The project development joint debugging method of claim 1, wherein before connecting with a corresponding target background according to a target address of the target background connected with the ark framework platform, the method further comprises:
acquiring an initial configuration file connected with a ark framework platform;
receiving a target address of a target background, and replacing address information in the initial configuration file with the target address to obtain a current configuration file;
the target address of the target background connected with the ark framework platform is connected with the corresponding target background, and the method comprises the following steps:
and connecting with a corresponding target background according to the current configuration file.
3. The project development joint debugging method of claim 1, wherein before connecting with a corresponding target background according to a target address of the target background connected with the ark framework platform, the method further comprises:
obtaining local historical request data, and positioning a first data structure body which is the same as a preset keyword in the historical request data;
and deleting the data in the first data structure body to obtain a data packaging template.
4. The project development joint debugging method of claim 1, wherein before connecting with a corresponding target background according to a target address of the target background connected with the ark framework platform, the method further comprises:
acquiring interactive data in a ark framework platform, and positioning a second data structure body which is the same as a preset keyword in the interactive data;
and deleting the data in the second data structure to obtain a data packaging template.
5. The project development joint debugging method according to claim 1, wherein the analyzing the encapsulated data to obtain corresponding analyzed data comprises:
positioning and obtaining a data structure body of the packaging data;
and acquiring data in the data structure body to obtain analytic data.
6. The project development joint debugging method of claim 1, wherein after sending the analysis data to a display area of a debugging interactive interface for front-end display, the method further comprises:
and if the editing confirmation instruction is detected, sending the editing information of the analyzed data to a target background.
7. An engineering development joint debugging device, characterized by comprising:
the background direct connection unit is used for connecting the corresponding target background according to the target address of the target background connected with the ark framework platform; the target address comprises an IP address and a port number of a target background;
the data encapsulation unit is used for receiving request data sent by the target background according to the front-end request, inserting the request data into a pre-stored data encapsulation template and encapsulating to obtain encapsulated data;
the data analysis unit is used for analyzing the packaging data to obtain corresponding analysis data; and
and the data display unit is used for sending the analysis data to a display area of the debugging interactive interface for front-end display.
8. The project development joint debugging device of claim 7, further comprising:
the system comprises an initial configuration file acquisition unit, a parameter acquisition unit and a parameter setting unit, wherein the initial configuration file acquisition unit is used for acquiring an initial configuration file connected with a ark framework platform;
the address replacing unit is used for receiving a target address of a target background and replacing the address information in the initial configuration file with the target address to obtain a current configuration file;
the background direct connection unit is further configured to:
and connecting with a corresponding target background according to the current configuration file.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the project development joint debugging method according to any one of claims 1 to 6 when executing the computer program.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program which, when executed by a processor, causes the processor to carry out the project development joint debugging method according to any one of claims 1 to 6.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910969973.9A CN111090578B (en) | 2019-10-12 | 2019-10-12 | Joint debugging method and device for engineering development, computer equipment and storage medium |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910969973.9A CN111090578B (en) | 2019-10-12 | 2019-10-12 | Joint debugging method and device for engineering development, computer equipment and storage medium |
Publications (2)
Publication Number | Publication Date |
---|---|
CN111090578A true CN111090578A (en) | 2020-05-01 |
CN111090578B CN111090578B (en) | 2024-05-10 |
Family
ID=70392969
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201910969973.9A Active CN111090578B (en) | 2019-10-12 | 2019-10-12 | Joint debugging method and device for engineering development, computer equipment and storage medium |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN111090578B (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112363935A (en) * | 2020-11-11 | 2021-02-12 | 平安普惠企业管理有限公司 | Data joint debugging method and device, electronic equipment and storage medium |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120084757A1 (en) * | 2010-10-01 | 2012-04-05 | Fujitsu Limited | Computer-readable, non-transitory medium saving debugging support program, debugging support device, and debugging support method |
US9471466B1 (en) * | 2015-05-28 | 2016-10-18 | Sap Se | End-to-end in-browser web-application debugging |
CN206773462U (en) * | 2017-04-28 | 2017-12-19 | 广州市机房宝信息科技有限公司 | A kind of plug and play monitoring system |
CN109491905A (en) * | 2018-11-02 | 2019-03-19 | 北京金山云网络技术有限公司 | Head end test method, apparatus and electronic equipment |
CN110138833A (en) * | 2019-04-12 | 2019-08-16 | 中国平安人寿保险股份有限公司 | Method for rapidly debugging, device, medium and the equipment of React Native module in APP |
-
2019
- 2019-10-12 CN CN201910969973.9A patent/CN111090578B/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120084757A1 (en) * | 2010-10-01 | 2012-04-05 | Fujitsu Limited | Computer-readable, non-transitory medium saving debugging support program, debugging support device, and debugging support method |
US9471466B1 (en) * | 2015-05-28 | 2016-10-18 | Sap Se | End-to-end in-browser web-application debugging |
CN206773462U (en) * | 2017-04-28 | 2017-12-19 | 广州市机房宝信息科技有限公司 | A kind of plug and play monitoring system |
CN109491905A (en) * | 2018-11-02 | 2019-03-19 | 北京金山云网络技术有限公司 | Head end test method, apparatus and electronic equipment |
CN110138833A (en) * | 2019-04-12 | 2019-08-16 | 中国平安人寿保险股份有限公司 | Method for rapidly debugging, device, medium and the equipment of React Native module in APP |
Non-Patent Citations (1)
Title |
---|
段勇涛: "卫星地面任务联调系统的设计与实现", 《中国优秀硕士学位论文全文数据库 (工程科技Ⅱ辑)》, no. 11, 15 November 2009 (2009-11-15), pages 031 - 113 * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112363935A (en) * | 2020-11-11 | 2021-02-12 | 平安普惠企业管理有限公司 | Data joint debugging method and device, electronic equipment and storage medium |
Also Published As
Publication number | Publication date |
---|---|
CN111090578B (en) | 2024-05-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN108459962B (en) | Code normalization detection method and device, terminal equipment and storage medium | |
CN111488166B (en) | Method and device for upgrading software of management unit of double-core intelligent ammeter and storage medium | |
CN111538659B (en) | Interface testing method, system, electronic equipment and storage medium of business scene | |
CN110377462B (en) | Interface testing method and device and terminal equipment | |
CN114546738B (en) | Universal test method, system, terminal and storage medium for server | |
CN111061643A (en) | SDK cluster compatibility detection method and device, electronic equipment and storage medium | |
CN103595774A (en) | System application uninstalling method and device with terminal based on server side | |
CN111858296B (en) | Interface testing method, device, equipment and storage medium | |
CN112181522B (en) | Data processing method and device and electronic equipment | |
CN113094255A (en) | Simulation test method, device and system for data interface | |
US9262142B2 (en) | Web application development tool | |
CN112729868A (en) | Vehicle diagnosis method, device, equipment and medium | |
CN109992511B (en) | Device and method for obtaining code test coverage rate | |
CN111046245A (en) | Multi-source heterogeneous data source fusion calculation method, system, equipment and storage medium | |
CN111090578B (en) | Joint debugging method and device for engineering development, computer equipment and storage medium | |
CN114895935A (en) | Method and device for flashing vehicle ECU, electronic equipment and storage medium | |
CN114579194A (en) | Spring remote call-based exception handling method and system | |
CN110609666B (en) | Printer configuration method and device, electronic equipment and readable storage medium | |
CN116775114A (en) | Version library compatibility determining method and device, computer equipment and storage medium | |
CN117743145A (en) | Test script generation method and device based on coding template and processing equipment | |
CN109408063B (en) | Instruction pile inserting method and device based on virtual machine | |
KR102324259B1 (en) | Method and apparatus for providing platform-integrated sdk capable of developing multiple platforms with a single source code | |
CN115755867A (en) | Vehicle diagnosis method and related device | |
CN112073505B (en) | Method for unloading on cloud server, control device and storage medium | |
CN105138342B (en) | A kind of service development method and apparatus |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |