CN111190596A - Joint debugging method and device, computer equipment and readable storage medium - Google Patents
Joint debugging method and device, computer equipment and readable storage medium Download PDFInfo
- Publication number
- CN111190596A CN111190596A CN201911348173.1A CN201911348173A CN111190596A CN 111190596 A CN111190596 A CN 111190596A CN 201911348173 A CN201911348173 A CN 201911348173A CN 111190596 A CN111190596 A CN 111190596A
- Authority
- CN
- China
- Prior art keywords
- interface
- end interface
- module
- joint debugging
- information
- 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
- 238000000034 method Methods 0.000 title claims abstract description 37
- 230000004044 response Effects 0.000 claims abstract description 43
- 238000012423 maintenance Methods 0.000 claims abstract description 39
- 238000012545 processing Methods 0.000 claims abstract description 12
- 238000012795 verification Methods 0.000 claims abstract description 9
- 230000006870 function Effects 0.000 claims description 32
- 238000004590 computer program Methods 0.000 claims description 17
- 238000007726 management method Methods 0.000 description 20
- 230000000007 visual effect Effects 0.000 description 16
- 238000011161 development Methods 0.000 description 13
- 230000005540 biological transmission Effects 0.000 description 7
- 238000012360 testing method Methods 0.000 description 7
- 230000002776 aggregation Effects 0.000 description 4
- 238000004220 aggregation Methods 0.000 description 4
- 230000008859 change Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 230000003203 everyday effect Effects 0.000 description 4
- 238000012552 review Methods 0.000 description 3
- 210000004258 portal system Anatomy 0.000 description 2
- 238000012827 research and development Methods 0.000 description 2
- 238000010200 validation analysis Methods 0.000 description 2
- 230000001413 cellular effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000000391 smoking effect Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
Abstract
The invention provides a joint debugging method and a joint debugging device, which are applied to joint debugging of the front end and the rear end of an interface, and the method comprises the following steps: determining a front-end interface to be processed and corresponding front-end interface information according to a received user instruction; determining a rear-end interface and rear-end interface information corresponding to the front-end interface; performing formatting verification on a data field preset by the maintenance content to judge whether the front-end interface information is consistent with the rear-end interface information; if the data is consistent with the message content, analyzing the data sent through the front-end interface by using the back end to obtain the corresponding message content; and carrying out corresponding response processing according to the message content to obtain a response result, and sending the response result to the front-end interface. The method can improve the automation degree of joint debugging, reduce manual operation and improve the joint debugging efficiency.
Description
Technical Field
The invention relates to the field of research and development management, in particular to a visual joint debugging device and method for assisting software development and a readable storage medium.
Background
This section is intended to provide a background or context to the embodiments of the invention that are recited in the claims and the detailed description. The description herein is not admitted to be prior art by inclusion in this section.
In the process of software development, the following procedures are generally included: the method comprises the steps of providing requirements, making a UI (User Interface) design drawing, making a front-back end appointed Interface/parameters/data, developing front-back end in parallel, integrating front-back end, modifying page style at front end, integrating successfully, and performing CI (Continuous Integration) joint debugging. The existing software development has the following problems: one function point at the front end or the rear end may be developed by several software developers, and since each developer is responsible for each function, the problem is more when the CI is jointly adjusted, the joint adjustment difficulty is high, and the normal promotion of the research and development progress is not facilitated.
Disclosure of Invention
In view of the above, it is desirable to provide a visual joint debugging method, a visual joint debugging apparatus and a readable storage medium, which are used to improve joint debugging efficiency.
In a first aspect, an embodiment of the present invention provides a joint debugging method, which is applied to joint debugging of front and back ends of an interface, and includes the following steps:
determining a front-end interface to be processed and corresponding front-end interface information according to a received user instruction;
determining a rear-end interface and rear-end interface information corresponding to the front-end interface;
performing formatting verification on a data field preset by the maintenance content to judge whether the front-end interface information is consistent with the rear-end interface information;
if the data is consistent with the message content, analyzing the data sent through the front-end interface by using the back end to obtain the corresponding message content;
and carrying out corresponding response processing according to the message content to obtain a response result, and sending the response result to the front-end interface.
Further, whether the front-end interface information is consistent with the back-end interface information is judged by performing formatting verification on a data field preset by the maintenance content, and the method comprises the following steps:
determining an ID code corresponding to the maintenance content;
acquiring a data format of a corresponding data field from a local database according to the ID code, wherein the data format is used for indicating the storage length occupied when the data field is stored;
and checking whether the data format is consistent with the data format stored in the local database.
Further, the data field includes an interface name, a field type, a field description, and an interface request mode.
Further, the ID coding adopts a tag, length and value triple; the label represents the type of the message, the length represents the length of the message, and the value represents the content of the message.
And further, when the front-end interface information is inconsistent with the rear-end interface information, sending an error-reporting prompt and displaying the error-reporting prompt on a user interface.
Further, when the front-end interface information is inconsistent with the back-end interface information, respectively corresponding byte code streams of the inconsistent front-end interface information and the inconsistent back-end interface information are obtained and sent to a preset address.
Further, performing corresponding response processing according to the message content to obtain a response result, and sending the response result to the front-end interface further includes:
and when the response result is that the interface joint debugging is successful, running a preset automatic script to execute the continuous integrated joint debugging.
In a second aspect, an embodiment of the present invention provides a joint debugging apparatus, which is applied to joint debugging of front and rear ends of an interface, and includes:
the project management module is used for providing a project management interface for a user to input projects and sub-project information of the same project; the project management module is also used for managing an interface corresponding to each sub project;
the interface maintenance module is used for determining a front-end interface to be processed and corresponding front-end interface information according to the received user instruction; the system comprises a front end interface, a back end interface and a control module, wherein the front end interface is used for receiving front end interface information and back end interface information;
the automatic joint debugging module is used for automatically executing joint debugging according to a preset rule;
the control module is connected with the project management module, the interface maintenance module and the automatic joint debugging module so as to control the project management module, the interface maintenance module and the automatic joint debugging module to execute corresponding functions; the control module comprises a judging module, an analyzing module and a response module;
the judging module is used for judging whether the front-end interface information is consistent with the rear-end interface information or not by carrying out formatting verification on a data field preset by the maintenance content;
the analysis module is used for analyzing the data sent by the front-end interface by using the back end to obtain the corresponding message content when the judgment module judges that the data are consistent;
and the response module is used for carrying out corresponding response processing according to the message content to obtain a response result and sending the response result to the front-end interface.
In a third aspect, the present invention also provides a computer device comprising a memory for storing a computer program and a processor for executing the computer program to make the computer device execute the steps of the method of the first aspect.
In a fourth aspect, the present invention also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the method of the first aspect described above.
The visual joint debugging method and the visual joint debugging device provided by the invention can be used for a user to input project information, front-end and rear-end interface information and the like, so that the user can conveniently and uniformly manage the project and the interface information, and can execute maintenance and joint debugging of the front-end and rear-end interfaces, so that the formats of the front-end and rear-end interfaces are kept consistent, and the software development efficiency and the interface joint debugging efficiency are improved; in addition, after one function point of multi-party development is completed, all sub-modules corresponding to the function point are subjected to internal joint debugging, then automatic joint debugging is executed regularly according to preset rules, the difficulty of final unified joint debugging can be reduced by performing internal joint debugging in advance, joint debugging efficiency is improved, the automation degree of joint debugging can be improved by automatically executing joint debugging regularly, manual operation is reduced, and joint debugging efficiency is further improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the description of the embodiments are some examples of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on the drawings without creative efforts.
Fig. 1 is a flowchart of a visual joint debugging method according to an embodiment of the present invention;
fig. 2 is a block diagram of a visual joint debugging apparatus according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a computer device according to an embodiment of the present invention.
Detailed Description
So that the manner in which the above recited objects, features and advantages of the present invention can be understood in detail, a more particular description of the invention, briefly summarized above, may be had by reference to the embodiments thereof which are illustrated in the appended drawings. In addition, the embodiments and features of the embodiments of the present application may be combined with each other without conflict.
In the following description, numerous specific details are set forth to provide a thorough understanding of the present invention, and the described embodiments are merely a subset of the embodiments of the present invention, rather than a complete embodiment. All other embodiments, which can be obtained by a person skilled in the art without any inventive step based on the embodiments of the present invention, are within the scope of the present invention.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. The terminology used herein in the description of the invention is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention.
Example one
Fig. 1 is a flowchart of a visual joint debugging method according to a first embodiment of the present invention, which is applied to joint debugging at the front and back ends of an interface, and includes:
s101, determining a front-end interface to be processed and corresponding front-end interface information according to a received user instruction.
The user instructions comprise that the user adds and modifies the project or sub-project information through the visual project management interface. The project management interface is used for a user to input projects and sub-project information of the same project; the specific content of the project or the sub-project is a team name, a project name and project personnel, and is mainly used for maintaining a team, a team project and a corresponding interface. On the project management setting interface, the project information can be input to record and manage the project. In a general development task, a plurality of projects can be included, each project can include a plurality of sub-projects, and all project or sub-project information can be input in advance on a project management interface so as to complete a corresponding software development task according to the projects.
And determining the corresponding front-end interface and the corresponding front-end interface information according to the project or sub-project information needing to be managed and maintained. Each item or sub-item corresponds to 1 or more preset front-end interfaces. And obtaining corresponding preset front-end interface information according to the front-end interface.
The front-end interface is used for sending information to the back-end interface and receiving response information returned by the back-end interface.
S102, determining a rear-end interface corresponding to the front-end interface and rear-end interface information.
After the front-end interface and the front-end interface information are determined, the back-end interface and the back-end interface information corresponding to the front-end interface and the front-end interface information need to be determined.
Interface documents of a front end and a rear end are required to be customized in advance before project development, and the interface documents comprise a preset interface format so as to enable the interface formats of the front end and the rear end to be uniform; if the interface document needs to change in the subsequent version alternation, notification information needs to be sent to a preset address to inform relevant developers to synchronously modify the front-end interface information and the back-end interface information. For example, if the interface document changes or modifies, it is automatically mailed to the mailboxes of previously entered project members. The formats of the front-end interface and the back-end interface need to be unified, so that the back end can normally analyze the information sent by the front end.
S103, performing formatting verification on a data field preset by the maintenance content, and judging whether the front-end interface information is consistent with the back-end interface information.
The step of performing formatting verification on a data field preset by the maintenance content to judge whether the front-end interface information is consistent with the back-end interface information specifically comprises the following steps:
an ID code corresponding to the maintenance content is determined.
The ID coding adopts a tag, length and value triple; the label represents the type of the message, the length represents the length of the message, and the value represents the content of the message.
The tag, length and value triplets have good expandability and simple structure. The subsequent expansion of the functional field is facilitated. The triplets of tags, lengths and values require both communicating parties to obtain a description document in advance, i.e. they do not have the characteristics of structuring and self-interpretation. The front and back ends are required to specify the corresponding interface documents for engagement.
And acquiring a data format of the corresponding data field from a local database according to the ID code, wherein the data format is used for indicating the storage length occupied when the data field is stored.
The data field comprises an interface name, a field type, a field description and an interface request mode.
And checking whether the data format is consistent with the data format stored in the local database.
When the front-end interface and the back-end interface are jointly adjusted, whether the interface developed by the front end meets the requirement of the back end or not is judged (the length of each data bit field set by the front-end interface and the back-end interface is consistent and meets the requirement), and if the length of each data bit field set by the front-end interface and the back-end interface is inconsistent, prompt information is output. And when the front-end interface information is inconsistent with the rear-end interface information, sending an error reporting prompt and displaying the error reporting prompt on a user interface.
And when the front-end interface information is inconsistent with the rear-end interface information, respectively corresponding byte code streams of the inconsistent front-end interface information and the rear-end interface information can be acquired and sent to a preset address. And related developers receive related error reporting information through the preset address, and maintain and modify the front and rear ports in time, so that the problem of inconsistency of the front and rear ports in the next software version is solved.
In the interface joint debugging, each maintenance content has a unique ID code. The maintenance content of each specific ID code has a preset data field. When the front-end interface and the back-end interface are connected, the back end carries out formatting validation on the data message which is received and sent by the front end and has maintenance content, firstly, the ID coding information is extracted from the preset position, the data format corresponding to the ID coding information is extracted from the local database according to the ID coding information, and whether the format of the received data is consistent with the format stored in the local database or not is verified. The data format check mainly checks the storage length occupied when each data field is stored, and does not check the specific stored information. And checking the storage length to ensure that the data bits can be aligned, and reading the data without reading information errors caused by bit taking deviation. And when the back end detects that the data format of the front end is inconsistent, sending an error report prompt and displaying the error report prompt on a user interface. And when the back end checks that the data formats of the front end are consistent, analyzing the related data, performing corresponding response processing according to the content of the message after analysis, and returning a response result to the front end. For example: the name of the interface, the field name, the field type, the field description and the interface request mode in the data with the ID code of 1 are respectively 4 bytes, 256 bytes, 4 bytes, 256 bytes and 4 bytes. In the data with ID code 2, the name of the interface, the field name, the field type, the field description, and the interface request mode are 4 bytes, 128 bytes, 4 bytes, 256 bytes, and 8 bytes, respectively.
The interface joint debugging module comprises: the interface name, the request type, the request URL, the request parameters and the request result of the front end are visual, the interface is directly called to return data, the data are dynamically generated according to the written rule, so that the front end does not need to wait for a developer at the rear end to develop the interface and then call the interface, and can be synchronously developed with the background, and the efficiency can be improved.
After the interface information is set on the interface maintenance interface, the interface corresponding to the interface joint debugging module can be automatically entered, and the joint debugging result information is displayed on the interface corresponding to the interface joint debugging module.
And S104, if the data are consistent, analyzing the data sent through the front-end interface by using the back end to obtain the corresponding message content.
And the back end analyzes the data sent by the front end interface to obtain the corresponding message content. And judging whether the message content conforms to the preset content.
And S105, carrying out corresponding response processing according to the message content to obtain a response result, and sending the response result to the front-end interface.
And when the message content is judged not to accord with the preset content, the response result is joint debugging failure. And when the message content is judged to accord with the preset content, the response result is that the joint debugging is successful.
And when the response result is that the interface joint debugging is successful, running a preset automatic script to execute the continuous integrated joint debugging. The joint debugging is automatically executed according to a preset rule; specifically, the method comprises the following steps: after one function point of multi-party development is completed, all sub-modules corresponding to the function point are subjected to internal joint debugging; and executing automatic joint debugging at a preset frequency at a preset time point. For example, a written interface joint call case is maintained well, a certain rule is set, and if 3 am every day is assumed, automatic joint call execution is performed, so that whether the updated code influences the call of the original interface every day is known. And after the execution of the interface joint debugging related operation is finished, executing the continuous integrated joint debugging.
The data transmission mode agreed by the front end and the back end of the interface comprises CGI- > APS- > SS, CGI- > SS and CGI- > APS, the 3 modes are specifically defined in advance, after the definition is finished, the required document of each system needs to be updated, and when the front end and the back end transmit data, the data can be transmitted according to the set mode.
CGI (Common gateway interface) is a specification of an external program when the Web server operates, and a program written according to CGI can extend the functions of the server. The CGI application program can interact with the browser and can also communicate with an external data source such as a database server through a database API (application programming interface) to acquire data from the database server. Formatted as an HTML document, and sent to the browser, or the data obtained from the browser may be placed in a database.
ASP (active server Page) is a WEB-based programming technique, which may be one of CGI. It can perform all functions of the previous CGI program, such as counter, message book, bulletin board, chat room, etc. The ASP can easily implement dynamic control of the page content, displaying different page contents according to different viewers.
The SS English full name is Supesuite, which is a community portal system with independent content management function and strong aggregation function. The SueStite can realize content aggregation of forums and personal spatial information in the station.
By the joint debugging method, a user can input project information, front-end and rear-end interface information and the like, the project and interface information can be conveniently and uniformly managed by the user, the maintenance and joint debugging of the front-end and rear-end interfaces can be executed, the formats of the front-end and rear-end interfaces are kept consistent, and the software development efficiency and the interface joint debugging efficiency are improved; in addition, after one function point of multi-party development is completed, all sub-modules corresponding to the function point are subjected to internal joint debugging, then automatic joint debugging is executed regularly according to preset rules, the difficulty of final unified joint debugging can be reduced by performing internal joint debugging in advance, joint debugging efficiency is improved, the automation degree of joint debugging can be improved by automatically executing joint debugging regularly, manual operation is reduced, and joint debugging efficiency is further improved.
Example two
Referring to fig. 2, a second embodiment of the present invention further provides a composition diagram of a visual joint debugging device, which is applied to joint debugging at the front end and the rear end of an interface, and the device includes a project management module, an interface maintenance module, an interface joint debugging module, an automatic joint debugging module, a data transmission mode setting module, a control module, and the like.
The control module is in signal connection with the project management module, the interface maintenance module, the interface joint debugging module, the automatic joint debugging module and the data transmission mode setting module and is used for controlling the modules to execute corresponding functions or operations. The control module comprises a judging module, an analyzing module and a response module.
The project management module is used for providing a project management interface for a user to input projects and sub-project information of the same project; the project management module is also used for managing the corresponding interface of each sub project. The specific content of the project or the sub-project is a team name, a project name and project personnel, and the module is mainly used for maintaining the team, the team project and a corresponding interface. The project information can be input on a setting interface corresponding to the project management module, and the project is recorded and managed. In a general development task, a plurality of projects can be included, each project can include a plurality of sub-projects, and all project or sub-project information can be input in advance on a project management interface so as to complete a corresponding software development task according to the projects.
The interface maintenance module is used for determining a front-end interface to be processed and corresponding front-end interface information according to the received user instruction; and the information of the back-end interface and the back-end interface corresponding to the front-end interface is determined.
The interface maintenance module is used for maintaining all front-end and back-end interfaces and determining a front-end interface to be processed and corresponding front-end interface information according to the received user instruction; the system comprises a front end interface, a back end interface and a control module, wherein the front end interface is used for receiving front end interface information and back end interface information; so that the interfaces of the front end and the rear end conform to a preset interface format; the maintenance content comprises the name of the interface, the field name, the field type, the field description, the interface request mode, whether to fill in or not and the like. Through the function, developers can inquire the request mode and request rule of the interface to be called, so that the development is convenient, and the unification of the interface rules of the front end and the back end is facilitated. After the project information is set, the relevant interface of the interface maintenance module can be automatically entered, the corresponding information of all the interfaces at the front end and the rear end can be input in the interface maintenance interface, and the interface information is set, modified and the like, so that the interface information can be managed and maintained conveniently.
The interface maintenance module is also used for formulating an interface document, and the interface document comprises a preset interface format so as to unify the front-end interface format and the back-end interface format; the interface maintenance module is also used for sending a notification message to a preset address after the interface document changes, for example, if the interface document changes or is modified, an email is automatically sent to a mailbox of a project member input in advance.
And the interface joint debugging module is used for judging whether the interface developed by the front end meets the requirement of the rear end (the length of each data bit field set by the front-end interface and the rear-end interface is consistent and meets the requirement), and if the formats of the front-end interface and the rear-end interface are inconsistent, outputting prompt information.
In the interface joint debugging module, each maintenance content has a unique ID code. The ID coding adopts a tag, length and value triple; the label represents the type of the message, the length represents the length of the message, and the value represents the content of the message. The tag, length and value triplets have good expandability and simple structure. The subsequent expansion of the functional field is facilitated. The triplets of tags, lengths and values require both communicating parties to obtain a description document in advance, i.e. they do not have the characteristics of structuring and self-interpretation. The front and back ends are required to specify the corresponding interface documents for engagement.
The maintenance content of each specific ID code has a preset data field. When the front-end interface and the back-end interface are connected, the back end carries out formatting validation on the data message which is received and sent by the front end and has maintenance content, firstly, the ID coding information is extracted from the preset position, the data format corresponding to the ID coding information is extracted from the local database according to the ID coding information, and whether the format of the received data is consistent with the format stored in the local database or not is verified. The data format check mainly checks the storage length occupied when each data field is stored, and does not check the specific stored information. And checking the storage length to ensure that the data bits can be aligned, and reading the data without reading information errors caused by bit taking deviation. And when the back end detects that the data format of the front end is inconsistent, sending an error report prompt and displaying the error report prompt on a user interface. And when the back end checks that the data formats of the front end are consistent, analyzing the related data, performing corresponding response processing according to the content of the message after analysis, and returning a response result to the front end. For example: the name of the interface, the field name, the field type, the field description and the interface request mode in the data with the ID code of 1 are respectively 4 bytes, 256 bytes, 4 bytes, 256 bytes and 4 bytes. In the data with ID code 2, the name of the interface, the field name, the field type, the field description, and the interface request mode are 4 bytes, 128 bytes, 4 bytes, 256 bytes, and 8 bytes, respectively.
The interface joint debugging module comprises: the interface name, the request type, the request URL, the request parameters and the request result of the front end are visual, the interface is directly called to return data, the data are dynamically generated according to the written rule, so that the front end does not need to wait for a developer at the rear end to develop the interface and then call the interface, and can be synchronously developed with the background, and the efficiency can be improved.
After the interface information is set on the interface maintenance interface, the interface corresponding to the interface joint debugging module can be automatically entered, and the joint debugging result information is displayed on the interface corresponding to the interface joint debugging module.
The automatic joint debugging module is used for automatically executing joint debugging according to a preset rule; specifically, the method comprises the following steps: after one function point of multi-party development is completed, all sub-modules corresponding to the function point are subjected to internal joint debugging; and executing automatic joint debugging at a preset frequency at a preset time point. For example, a written interface joint call case is maintained well, a certain rule is set, and if 3 am every day is assumed, automatic joint call execution is performed, so that whether the updated code influences the call of the original interface every day is known. And after the execution of the interface joint debugging related operation is finished, executing the CI joint debugging.
The judging module is used for judging whether the front-end interface information is consistent with the rear-end interface information or not by carrying out formatting verification on a data field preset by the maintenance content. And the analysis module is used for analyzing the data sent by the front-end interface by using the back end to obtain the corresponding message content when the judgment module judges that the data are consistent. And the response module is used for carrying out corresponding response processing according to the message content to obtain a response result and sending the response result to the front-end interface.
When the front-end interface and the back-end interface are jointly adjusted, whether the interface developed by the front end meets the requirement of the back end or not is judged (the length of each data bit field set by the front-end interface and the back-end interface is consistent and meets the requirement), and if the length of each data bit field set by the front-end interface and the back-end interface is inconsistent, prompt information is output. And when the front-end interface information is inconsistent with the rear-end interface information, sending an error reporting prompt and displaying the error reporting prompt on a user interface.
And when the front-end interface information is inconsistent with the rear-end interface information, respectively corresponding byte code streams of the inconsistent front-end interface information and the rear-end interface information can be acquired and sent to a preset address. And related developers receive related error reporting information through the preset address, and maintain and modify the front and rear ports in time, so that the problem of inconsistency of the front and rear ports in the next software version is solved.
And the data transmission mode setting module is used for setting a front-end and back-end data transmission mode. For example, the data transmission mode is CGI- > APS- > SS, CGI- > APS, which of the 3 modes is specifically defined in advance, and after the specification is defined, the document is also required to be updated according to the requirements of each system, and when the front end and the back end transmit data, the data is transmitted according to the set mode.
CGI (Common gateway interface) is a specification of an external program when the Web server operates, and a program written according to CGI can extend the functions of the server. The CGI application program can interact with the browser and can also communicate with an external data source such as a database server through a database API (application programming interface) to acquire data from the database server. Formatted as an HTML document, and sent to the browser, or the data obtained from the browser may be placed in a database.
ASP (active server Page) is a WEB-based programming technique, which may be one of CGI. It can perform all functions of the previous CGI program, such as counter, message book, bulletin board, chat room, etc. The ASP can easily implement dynamic control of the page content, displaying different page contents according to different viewers.
The SS English full name is Supesuite, which is a community portal system with independent content management function and strong aggregation function. The SueStite can realize content aggregation of forums and personal spatial information in the station.
Through the visual joint debugging device, a user can input project information, front-end and rear-end interface information and the like, the project and interface information can be conveniently and uniformly managed by the user, the maintenance and joint debugging of the front-end and rear-end interfaces can be executed, the formats of the front-end and rear-end interfaces are kept consistent, and the software development efficiency and the interface joint debugging efficiency are improved; in addition, after one function point of multi-party development is completed, all sub-modules corresponding to the function point are subjected to internal joint debugging, then automatic joint debugging is executed regularly according to preset rules, the difficulty of final unified joint debugging can be reduced by performing internal joint debugging in advance, joint debugging efficiency is improved, the automation degree of joint debugging can be improved by automatically executing joint debugging regularly, manual operation is reduced, and joint debugging efficiency is further improved.
EXAMPLE III
On the basis of the first embodiment, a visual joint debugging method provided by the third embodiment of the invention further comprises the following steps: 1. during the requirement analysis and review, all the development of the front and back ends must be participated, rather than only the system responsible person, so that the specific developer is unclear about the rule agreed by the front and back ends. 2. The interface document needs to be made, all front-end and back-end personnel participate in the review, and after the review is finished, if the interface document changes, all developers need to be notified by mails, but the interface document is not updated in the WIKI by the developers. 3. The data transmission modes agreed at the front end and the back end, such as CGI- > APS- > SS, or CGI- > APS, are specifically defined in advance, and after the definition is good, the document required by each system needs to be updated. 4. Aiming at a small function point, for example, several continuous pages without breakpoints, the multi-person development is realized, and after the development is finished, the internal joint debugging is completed firstly. 5. The front end and the back end adopt a contract testing method: the front end and the back end determine the specific format of the interface, the set of formats is equivalent to a set of contracts, and the front end and the back end develop respective functions according to the contracts. Meanwhile, as a consumer, the back end is assumed to add a set of automated tests to the interface, so as to ensure that the functions of the module a conform to the contract. Each time the code of module a changes, this set of tests is triggered, the passing of the test means that the producer provides the correct functionality for the consumer, and vice versa. Thus, the change of the module A does not affect the module B, even if the change of the module A has an effect, the change can be reflected 6 in the first time through testing, the front-end and rear-end joint debugging of each service line can be automatically tested through a tool, a visual interface management tool RAP can be used for performing the front-end and rear-end joint debugging, and then the CI joint debugging is performed. This can improve the quality of development, joint debugging efficiency, delivery quality, smoking test, and system test.
Example four
Fig. 3 is an exemplary structural diagram of a computer device according to an embodiment of the present invention. The computer apparatus 1 (or the terminal 1, hereinafter collectively referred to as the computer apparatus 1) provided in the present embodiment includes: a processor 10, a memory 20, and a computer program, such as a communication control program, stored in the memory 20 and operable on the processor 10. When the processor 10 executes the computer program, the steps of the visual joint debugging method in the second embodiment of the method are implemented. Alternatively, the processor 10, when executing the computer program, implements the functions of the modules in the first embodiment of the apparatus.
The Processor 10 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. The general purpose processor may be a microprocessor or the processor may be any conventional processor or the like, and the processor 10 is the control center of the computer apparatus, and various interfaces and lines are used to connect the various parts of the whole terminal.
The memory 20 can be used for storing the computer programs and/or modules, and the processor 10 can implement various functions of the computer device 1 by running or executing the computer programs and/or modules stored in the memory 20 and calling the data stored in the memory 20. The memory 20 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. In addition, the memory 20 may include high speed random access memory, and may also include non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), at least one magnetic disk storage device, a Flash memory device, or other volatile solid state storage device.
The modules integrated in the computer device 1 according to the present invention may be stored in a computer-readable storage medium if they are implemented in the form of software functional units and sold or used as independent products. Based on such understanding, all or part of the flow of the method according to the embodiments of the present invention may also be implemented by a computer program, which may be stored in a computer-readable storage medium, and when the computer program is executed by a processor, the steps of the method embodiments may be implemented. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.
It will be evident to those skilled in the art that the invention is not limited to the details of the foregoing illustrative embodiments, and that the present invention may be embodied in other specific forms without departing from the spirit or essential attributes thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the invention being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned. Furthermore, it is obvious that the word "comprising" does not exclude other elements or steps, and the singular does not exclude the plural. A plurality of units, modules or devices recited in the system, device or terminal device claims may also be implemented by the same unit, module or device through software or hardware. The terms first, second, etc. are used to denote names, but not any particular order.
Although the present invention has been described in detail with reference to the preferred embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted without departing from the spirit and scope of the invention.
Claims (10)
1. A joint debugging method is applied to joint debugging of the front end and the rear end of an interface, and is characterized by comprising the following steps:
determining a front-end interface to be processed and corresponding front-end interface information according to a received user instruction;
determining a rear-end interface and rear-end interface information corresponding to the front-end interface;
performing formatting verification on a data field preset by the maintenance content to judge whether the front-end interface information is consistent with the rear-end interface information;
if the data is consistent with the message content, analyzing the data sent through the front-end interface by using the back end to obtain the corresponding message content;
and carrying out corresponding response processing according to the message content to obtain a response result, and sending the response result to the front-end interface.
2. The method of claim 1, wherein determining whether the front-end interface information is consistent with the back-end interface information is performed by performing a formatting check on a data field that is preset by a maintenance content, the method comprising:
determining an ID code corresponding to the maintenance content;
acquiring a data format of a corresponding data field from a local database according to the ID code, wherein the data format is used for indicating the storage length occupied when the data field is stored;
and checking whether the data format is consistent with the data format stored in the local database.
3. The method of claim 2, wherein the data fields include an interface name, a field type, a field description, an interface request mode.
4. The method of claim 2, wherein the ID encoding employs a tag, length, value triplet; the label represents the type of the message, the length represents the length of the message, and the value represents the content of the message.
5. The method of claim 1, wherein when the front-end interface information is inconsistent with the back-end interface information, an error prompt is issued and displayed on a user interface.
6. The method of claim 1, wherein when the front-end interface information is inconsistent with the back-end interface information, respectively corresponding byte code streams of the inconsistent front-end interface information and the back-end interface information are obtained and sent to a preset address.
7. The method of claim 1, wherein performing corresponding response processing according to the message content to obtain a response result, and sending the response result to the front-end interface further comprises:
and when the response result is that the interface joint debugging is successful, running a preset automatic script to execute the continuous integrated joint debugging.
8. The utility model provides a ally oneself with accent device, is applied to the antithetical couplet of interface front and back end and transfers, its characterized in that includes:
the project management module is used for providing a project management interface for a user to input projects and sub-project information of the same project; the project management module is also used for managing an interface corresponding to each sub project;
the interface maintenance module is used for determining a front-end interface to be processed and corresponding front-end interface information according to the received user instruction; the system comprises a front end interface, a back end interface and a control module, wherein the front end interface is used for receiving front end interface information and back end interface information;
the automatic joint debugging module is used for automatically executing joint debugging according to a preset rule;
the control module is connected with the project management module, the interface maintenance module and the automatic joint debugging module so as to control the project management module, the interface maintenance module and the automatic joint debugging module to execute corresponding functions; the control module comprises a judging module, an analyzing module and a response module;
the judging module is used for judging whether the front-end interface information is consistent with the rear-end interface information or not by carrying out formatting verification on a data field preset by the maintenance content;
the analysis module is used for analyzing the data sent by the front-end interface by using the back end to obtain the corresponding message content when the judgment module judges that the data are consistent;
and the response module is used for carrying out corresponding response processing according to the message content to obtain a response result and sending the response result to the front-end interface.
9. A computer device, comprising a memory for storing a computer program and a processor for executing the computer program to cause the computer device to perform the method according to any one of claims 1-7.
10. A computer-readable storage medium having stored thereon a computer program, characterized in that: the computer program realizing the steps of the method according to any one of claims 1-7 when executed by a processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911348173.1A CN111190596A (en) | 2019-12-24 | 2019-12-24 | Joint debugging method and device, computer equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911348173.1A CN111190596A (en) | 2019-12-24 | 2019-12-24 | Joint debugging method and device, computer equipment and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111190596A true CN111190596A (en) | 2020-05-22 |
Family
ID=70707521
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911348173.1A Pending CN111190596A (en) | 2019-12-24 | 2019-12-24 | Joint debugging method and device, computer equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111190596A (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112612451A (en) * | 2020-12-18 | 2021-04-06 | 平安普惠企业管理有限公司 | Interface generation method, device, equipment and computer readable storage medium |
| CN112671574A (en) * | 2020-12-18 | 2021-04-16 | 深圳赛安特技术服务有限公司 | Front-end and back-end joint debugging method and device, proxy equipment and storage medium |
| CN112882844A (en) * | 2021-02-07 | 2021-06-01 | 成都新希望金融信息有限公司 | Network front-end and back-end based joint debugging method and device and storage medium |
| CN112905455A (en) * | 2021-02-05 | 2021-06-04 | 北京有竹居网络技术有限公司 | Interface information checking method, device, equipment and storage medium |
| CN113490256A (en) * | 2021-07-01 | 2021-10-08 | 建信金融科技有限责任公司 | Front-end and back-end joint debugging method, device, medium and equipment |
| CN113641589A (en) * | 2021-09-01 | 2021-11-12 | 中国银行股份有限公司 | Data processing method and device |
| CN113687965A (en) * | 2021-10-25 | 2021-11-23 | 深圳市工易付电子科技有限公司 | Data interaction method, device, equipment and storage medium |
| CN115086436A (en) * | 2022-06-16 | 2022-09-20 | 平安银行股份有限公司 | Method and device for parameter verification between Application Program Interfaces (APIs), computer equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109522218A (en) * | 2018-10-19 | 2019-03-26 | 平安科技（深圳）有限公司 | Interface test method, device, computer equipment and storage medium |
| CN109857391A (en) * | 2019-01-18 | 2019-06-07 | 山石网科通信技术股份有限公司 | Processing method and processing device, storage medium and the electronic device of data |
| CN110222282A (en) * | 2019-04-17 | 2019-09-10 | 深圳壹账通智能科技有限公司 | Data processing method, device, server and storage medium |
| CN110347380A (en) * | 2019-07-18 | 2019-10-18 | 中国联合网络通信集团有限公司 | Front and back end development approach and equipment |
| CN110362313A (en) * | 2019-07-02 | 2019-10-22 | 威富通科技有限公司 | A kind of form validation method, client and server |
-
2019
- 2019-12-24 CN CN201911348173.1A patent/CN111190596A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109522218A (en) * | 2018-10-19 | 2019-03-26 | 平安科技（深圳）有限公司 | Interface test method, device, computer equipment and storage medium |
| CN109857391A (en) * | 2019-01-18 | 2019-06-07 | 山石网科通信技术股份有限公司 | Processing method and processing device, storage medium and the electronic device of data |
| CN110222282A (en) * | 2019-04-17 | 2019-09-10 | 深圳壹账通智能科技有限公司 | Data processing method, device, server and storage medium |
| CN110362313A (en) * | 2019-07-02 | 2019-10-22 | 威富通科技有限公司 | A kind of form validation method, client and server |
| CN110347380A (en) * | 2019-07-18 | 2019-10-18 | 中国联合网络通信集团有限公司 | Front and back end development approach and equipment |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112612451A (en) * | 2020-12-18 | 2021-04-06 | 平安普惠企业管理有限公司 | Interface generation method, device, equipment and computer readable storage medium |
| CN112671574A (en) * | 2020-12-18 | 2021-04-16 | 深圳赛安特技术服务有限公司 | Front-end and back-end joint debugging method and device, proxy equipment and storage medium |
| CN112612451B (en) * | 2020-12-18 | 2024-04-12 | 北京金海品读科技有限公司 | Interface generation method, device, equipment and computer readable storage medium |
| CN112671574B (en) * | 2020-12-18 | 2024-04-16 | 深圳赛安特技术服务有限公司 | Front-end and back-end joint debugging method and device, proxy equipment and storage medium |
| CN112905455A (en) * | 2021-02-05 | 2021-06-04 | 北京有竹居网络技术有限公司 | Interface information checking method, device, equipment and storage medium |
| CN112882844A (en) * | 2021-02-07 | 2021-06-01 | 成都新希望金融信息有限公司 | Network front-end and back-end based joint debugging method and device and storage medium |
| CN112882844B (en) * | 2021-02-07 | 2024-01-26 | 成都新希望金融信息有限公司 | Joint debugging method, device and storage medium based on network front end and network back end |
| CN113490256A (en) * | 2021-07-01 | 2021-10-08 | 建信金融科技有限责任公司 | Front-end and back-end joint debugging method, device, medium and equipment |
| CN113641589A (en) * | 2021-09-01 | 2021-11-12 | 中国银行股份有限公司 | Data processing method and device |
| CN113687965A (en) * | 2021-10-25 | 2021-11-23 | 深圳市工易付电子科技有限公司 | Data interaction method, device, equipment and storage medium |
| CN115086436A (en) * | 2022-06-16 | 2022-09-20 | 平安银行股份有限公司 | Method and device for parameter verification between Application Program Interfaces (APIs), computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111190596A (en) | Joint debugging method and device, computer equipment and readable storage medium | |
| CN102244594B (en) | At the networks simulation technology manually and in automatic testing instrument | |
| CN109344170B (en) | Stream data processing method, system, electronic device and readable storage medium | |
| CN109032923A (en) | Method for testing software, device based on call chain, terminal | |
| US10452522B1 (en) | Synthetic data generation from a service description language model | |
| CN108628748B (en) | Automatic test management method and automatic test management system | |
| CN110727580A (en) | Response data generation method, full-flow interface data processing method and related equipment | |
| CN107451112B (en) | Form tool data checking method, device, terminal equipment and storage medium | |
| CN111897738B (en) | Automatic testing method and device based on atomic service | |
| CN112905460A (en) | Device and method for simulating three-party receipt by automatic interface test | |
| CN111078529B (en) | Client writing module testing method and device and electronic equipment | |
| CN112506771A (en) | Message comparison method and device | |
| CN108170557B (en) | Method and apparatus for outputting information | |
| CN113141366B (en) | Message submitting method and device, storage medium and electronic equipment | |
| CN114205276B (en) | Performance test method and device for product management system and electronic equipment | |
| CN113722226B (en) | Bank presenting and disc returning testing method and device, computer equipment and storage medium | |
| CN116126723A (en) | Interface automatic test construction method based on workflow platform | |
| CN115729832A (en) | Method and device for maintaining system ledger and verifying indexes | |
| CN115601180A (en) | Fund service data exchange simulation test method and system | |
| CN116069660A (en) | Automatic testing method and device for Internet of things platform, computer equipment and storage medium | |
| CN116881169A (en) | Contract file maintenance method and device, computer equipment and storage medium | |
| CN117472372A (en) | Responsive form construction method and system | |
| CN114860578A (en) | Interface testing method, device, equipment and storage terminal | |
| CN117170670A (en) | Online activity management method, system, device and storage medium | |
| CN113076252A (en) | Interface testing 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 |