Interface joint debugging method, device, electronic device and computer readable medium

By generating and sending data application information sequences, obtaining the access application interface joint debugging prompt information, and performing application interface request checksum calls, it solves the problem of difficulty in error information feedback and complicated comparison program writing in interface joint debugging, and realizes efficient interface joint debugging and improved user experience.

CN119088711BActive Publication Date: 2025-05-23PARK DO CREDIT CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202411233957.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-09-04
Publication Date
2025-05-23
Estimated Expiration
2044-09-04

AI Technical Summary

Technical Problem

During the interface connection process, it is difficult for the user to obtain the error information of the failed request in a timely manner, resulting in a reduced efficiency of the interface connection and taking a long time; at the same time, it is necessary to write a result comparison program for each data application interface, resulting in a poor user experience.

Method used

Provide an interface joint debugging method, including generating an information sequence of accessed and unattached data applications, sending it to a user terminal, obtaining access application interface joint debugging prompt information, performing application interface request verification, calling data applications, obtaining response data, and encrypting and processing and parsing the response data, and finally generating and sending the interface joint debugging result.

Benefits of technology

By timely checking and feedbacking error messages in interface requests or response data, the interface joint debugging consumption is shortened, the joint debugging efficiency is improved, and the user experience is improved.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119088711B_ABST
    Figure CN119088711B_ABST
Patent Text Reader

Abstract

The embodiments of the present disclosure disclose an interface joint debugging method, device, electronic device and computer-readable medium. A specific implementation of the method includes: generating an accessed data application information sequence and a non-accessed data application information sequence; in response to receiving the first selection information for the accessed data application information, obtaining access application interface joint debugging prompt information; in response to receiving the application interface request information, verifying the application interface request information to obtain the interface request verification result; in response to determining that the interface request verification result meets the preset verification pass condition, calling the target accessed data application to obtain access application response data; encrypting the access application response data to obtain encrypted response data, and sending the encrypted response data to the target user terminal; based on the access application response data and the user interface call result data, generating the interface joint debugging result. This implementation can shorten the interface joint debugging time and improve the joint debugging efficiency.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments of the present disclosure relate to the field of computer technology, and in particular to an interface joint debugging method, device, electronic device, and computer-readable medium. Background Art

[0002] In order to meet the data needs of users, data application providers provide more data application interfaces through the data application access platform. The user end can obtain the required data from the data application interface and parse it locally to obtain the required data. Before calling the data application interface, the user end also needs to debug the interface with the local parsing program. At present, when performing interface joint debugging, the method usually adopted is: the user writes and sends the interface joint debugging test request locally according to the debugging example. If the request fails and no response data is returned, all codes need to be checked, or the data application provider needs to feedback detailed error information to the user end according to the interface test request log so that the interface can be debugged again. If the request successfully returns the response data, the user end parses the response data and uses the pre-written result comparison program to compare the parsed data with the expected response data of the interface for consistency to determine whether the interface joint debugging is successful.

[0003] However, in practice, it is found that when the above method is used for interface joint debugging, the following technical problems often occur:

[0004] First, since it is difficult for the user end to obtain error information about request failure in a timely manner, the efficiency of interface joint debugging is reduced, resulting in a longer time-consuming interface joint debugging.

[0005] Second, if a locally written result comparison program is used to compare the parsed data with the expected response data of the interface for consistency, each user with data requirements will need to write a result comparison program for the data application to be connected, and the response data returned by each data application interface will be different. For each data application connected, the user will need to spend a lot of extra time to write the corresponding result comparison programs, which makes it difficult to complete the interface debugging in a timely manner and the user experience is poor.

[0006] The above information disclosed in this Background section is only for enhancement of understanding of the background of the present disclosure concept and therefore it may contain information that does not form the prior art that is already known to a person of ordinary skill in the art. Summary of the invention

[0007] The content of this disclosure is used to introduce concepts in a brief form, which will be described in detail in the detailed implementation section below. The content of this disclosure is not intended to identify the key features or essential features of the technical solution claimed for protection, nor is it intended to limit the scope of the technical solution claimed for protection.

[0008] Some embodiments of the present disclosure propose an interface joint debugging method, an apparatus, an electronic device, and a computer-readable medium to solve one or more of the technical problems mentioned in the above background technology section.

[0009] In a first aspect, some embodiments of the present disclosure provide an interface joint debugging method, the method comprising: in response to receiving data application query information sent by a target user terminal, generating an accessed data application information sequence and a non-accessed data application information sequence, and sending the accessed data application information sequence and the non-accessed data application information sequence to the target user terminal for interface joint debugging testing of the data application; in response to receiving first selection information for any accessed data application information in the accessed data application information sequence, obtaining access application interface joint debugging prompt information corresponding to the target accessed data application, and sending the access application interface joint debugging prompt information to the target user terminal, so that the target user can perform local data application development according to the access application interface joint debugging prompt information, wherein the target accessed data application corresponds to the selected accessed data application information; in response to receiving For the application interface request information of the above-mentioned target connected data application, based on the preset access application input parameter information sequence, the above-mentioned application interface request information is verified and processed to obtain the interface request verification result; in response to determining that the above-mentioned interface request verification result meets the preset verification pass condition, based on the above-mentioned application interface request information, the above-mentioned target connected data application is called to obtain access application response data; the above-mentioned access application response data is encrypted to obtain encrypted response data, and the above-mentioned encrypted response data is sent to the above-mentioned target user terminal for parsing; in response to receiving the user interface call result data, based on the above-mentioned access application response data and the above-mentioned user interface call result data, an interface joint debugging result is generated, and the above-mentioned interface joint debugging result is sent to the above-mentioned target user terminal for display, wherein the above-mentioned user interface call result data is generated as a result of parsing the above-mentioned encrypted response data according to the above-mentioned local data application.

[0010] In a second aspect, some embodiments of the present disclosure provide an interface joint debugging device, the device comprising: a first generating and sending unit, configured to generate an accessed data application information sequence and an unaccessed data application information sequence in response to receiving data application query information sent by a target user terminal, and send the accessed data application information sequence and the unaccessed data application information sequence to the target user terminal for interface joint debugging testing of the data application; an acquiring and sending unit, configured to acquire access application interface joint debugging prompt information corresponding to the target accessed data application in response to receiving first selection information for any accessed data application information in the accessed data application information sequence, and send the access application interface joint debugging prompt information to the target user terminal for the target user to perform local data application development according to the access application interface joint debugging prompt information, wherein the target accessed data application corresponds to the selected accessed data application information; a verification processing unit, configured to For the application interface request information of the above-mentioned target connected data application, based on the preset access application input parameter information sequence, the above-mentioned application interface request information is verified and processed to obtain the interface request verification result; the calling unit is configured to, in response to determining that the above-mentioned interface request verification result meets the preset verification pass condition, call the above-mentioned target connected data application based on the above-mentioned application interface request information to obtain access application response data; the encryption processing and sending unit is configured to encrypt the above-mentioned access application response data to obtain encrypted response data, and send the above-mentioned encrypted response data to the above-mentioned target user terminal for parsing; the second generating and sending unit is configured to, in response to receiving the user interface calling result data, generate the interface joint debugging result based on the above-mentioned access application response data and the above-mentioned user interface calling result data, and send the above-mentioned interface joint debugging result to the above-mentioned target user terminal for display, wherein the above-mentioned user interface calling result data is generated as a result of parsing the above-mentioned encrypted response data according to the above-mentioned local data application.

[0011] In a third aspect, some embodiments of the present disclosure provide an electronic device comprising: one or more processors; a storage device on which one or more programs are stored, and when the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any implementation manner of the above-mentioned first aspect.

[0012] In a fourth aspect, some embodiments of the present disclosure provide a computer-readable medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the method described in any implementation manner of the above-mentioned first aspect is implemented.

[0013] The above-mentioned embodiments of the present disclosure have the following beneficial effects: through the interface joint debugging method of some embodiments of the present disclosure, the time consumption of interface joint debugging can be shortened and the efficiency of interface joint debugging can be improved. Specifically, the reason for the long time consumption of interface joint debugging is that it is difficult for the user end to obtain the error information of the request failure in time, which reduces the efficiency of interface joint debugging, thereby causing the interface joint debugging to take a long time. Based on this, the interface joint debugging method of some embodiments of the present disclosure, first, in response to receiving the data application query information sent by the target user terminal, generates an accessed data application information sequence and an unaccessed data application information sequence, and sends the above-mentioned accessed data application information sequence and the above-mentioned unaccessed data application information sequence to the above-mentioned target user terminal, so as to perform interface joint debugging test on the data application. Thus, it is convenient to perform joint debugging on the accessed data application and the user's local program in the subsequent process. Secondly, in response to receiving the first selection information for any accessed data application information in the above-mentioned accessed data application information sequence, obtain the access application interface joint debugging prompt information corresponding to the target accessed data application, and send the above-mentioned access application interface joint debugging prompt information to the above-mentioned target user terminal, so that the above-mentioned target user can develop local data applications according to the above-mentioned access application interface joint debugging prompt information. Among them, the above-mentioned target accessed data application corresponds to the selected accessed data application information. Thus, it is convenient for users to develop local programs for interface joint debugging according to the joint debugging prompt information of the data application to be joint debugged. Then, in response to receiving the application interface request information for the above-mentioned target accessed data application, based on the preset access application input parameter information sequence, the above-mentioned application interface request information is verified and processed to obtain the interface request verification result. Thus, in the interface joint debugging process, it is possible to timely determine whether the interface test request sent by the local program is correct. Then, in response to determining that the above-mentioned interface request verification result meets the preset verification pass condition, based on the above-mentioned application interface request information, the above-mentioned target accessed data application is called to obtain the access application response data. Thus, when the interface test request is correct, the corresponding data application can be called to obtain the response data corresponding to the test request. Afterwards, the above-mentioned access application response data is encrypted to obtain the encrypted response data, and the above-mentioned encrypted response data is sent to the above-mentioned target user terminal for parsing. Thus, it is convenient to verify the response data after the user terminal is parsed, so that the user can determine whether the local parsing program has an error. Finally, in response to receiving the user interface call result data, an interface joint debugging result is generated based on the access application response data and the user interface call result data, and the interface joint debugging result is sent to the target user terminal for display. Among them, the user interface call result data is generated by parsing the encrypted response data according to the local data application. In this way, the verified interface joint debugging result can be sent to the user in a timely manner, so that the user can adjust the local parsing program in a timely manner.Therefore, the interface joint debugging method of some embodiments of the present disclosure can timely check the error information in the interface request or the response data after parsing, and timely feed back the error information to the user terminal for re-interface joint debugging until the joint debugging is successful. Thus, the time consumption of interface joint debugging can be shortened and the efficiency of joint debugging can be improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the accompanying drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and that components and elements are not necessarily drawn to scale.

[0015] Figure 1 is a flow chart of some embodiments of the interface joint debugging method according to the present disclosure;

[0016] Figure 2 is a schematic diagram of the structure of some embodiments of the interface joint debugging device according to the present disclosure;

[0017] Figure 3 It is a schematic diagram of the structure of an electronic device suitable for implementing some embodiments of the present disclosure. DETAILED DESCRIPTION

[0018] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.

[0019] It should also be noted that, for ease of description, only the parts related to the invention are shown in the drawings. In the absence of conflict, the embodiments and features in the embodiments of the present disclosure can be combined with each other.

[0020] It should be noted that the concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0021] It should be noted that the modifications of "one" and "plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".

[0022] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or information.

[0023] The present disclosure will be described in detail below with reference to the accompanying drawings and in conjunction with embodiments.

[0024] Figure 1 The process 100 of some embodiments of the interface joint debugging method according to the present disclosure is shown. The interface joint debugging method includes the following steps:

[0025] Step 101, in response to receiving data application query information sent by a target user terminal, generating an accessed data application information sequence and a non-accessed data application information sequence, and sending the accessed data application information sequence and the non-accessed data application information sequence to the target user terminal for interface joint debugging testing of the data application.

[0026] In some embodiments, the execution subject (e.g., computing device) of the interface joint debugging method may generate a connected data application information sequence and a non-connected data application information sequence in response to receiving the data application query information sent by the target user terminal, and send the above-mentioned connected data application information sequence and the above-mentioned non-connected data application information sequence to the above-mentioned target user terminal for interface joint debugging test for data application. Among them, the above-mentioned target user terminal may be a terminal device used by the target user to log in to the data application access platform. The above-mentioned target user may be a data demander who has logged in to the data application access platform. The above-mentioned data application access platform may be a website for data demanders to access data applications according to data needs. The data application may be an application that provides data resources or services to data demanders through an application interface. For example, the data application may be, but is not limited to, one of the following: a credit scoring application, a credit subject risk control portrait generation application, and a credit risk identification application. The data demander may be an entity or individual who desires to obtain data for decision support. The above-mentioned data application query information may include a user identifier and a user industry identifier. The above-mentioned user identifier may be a unique identifier of the target user. The above-mentioned user industry identifier may be a unique identifier of the industry in which the target user is located. The above-mentioned sequence of information about accessed data applications may be a sequence of information about each data application to which the user has access rights, arranged in order of access rights application time. The above-mentioned sequence of information about non-accessed data applications may be a sequence of information about each data application that has not been accessed by the above-mentioned target user, arranged in descending order of access volume. The above-mentioned access volume may be the number of users who have successfully applied for access rights corresponding to the data application.

[0027] As an example, first, the execution subject may select user access information matching the user identifier from the user access information set according to the user identifier. Each user access information in the user access information set may include an access user identifier and an associated data application information sequence. The access user identifier may be an identifier of a user with data application access rights. The associated data application information in the associated data application information sequence may include a data application identifier. The data application identifier may be a unique identifier of a data application. Matching the user identifier may be that the access user identifier included in the user access information is the same as the user identifier. Then, the associated data application information sequence included in the selected user access information is determined as an accessed data application information sequence. Afterwards, according to the user industry identifier, industry-associated application information matching the user industry identifier is selected from the industry-associated application information set. The industry-associated application information in the industry-associated application information set may include an industry identifier and a high-frequency access data application information sequence. The industry identifier may be a unique identifier of an industry. For example, the industry may be, but is not limited to, one of the following: financial industry, real estate industry. The high-frequency access data application information sequence may be an information sequence of the top 5 data applications in the corresponding industry in terms of access volume. Matching the above-mentioned user industry identifier may be that the industry identifier included in the industry-related application information is the same as the above-mentioned user industry identifier. Next, high-frequency access data application information that is different from each of the accessed data application information in the above-mentioned accessed data application information sequence is selected in turn from the high-frequency access data application information sequence included in the selected industry-related application information as the non-accessed data application information, and a non-accessed data application information sequence is obtained. Finally, the above-mentioned accessed data application information sequence and the above-mentioned non-accessed data application information sequence are sent to the above-mentioned target user terminal. The above-mentioned target user can select the data application for which the interface joint debugging is desired through the target user terminal.

[0028] Step 102, in response to receiving the first selection information for any accessed data application information in the accessed data application information sequence, obtaining the access application interface debugging prompt information corresponding to the target accessed data application, and sending the access application interface debugging prompt information to the target user terminal, so that the target user can develop local data applications according to the access application interface debugging prompt information.

[0029] In some embodiments, the execution subject may, in response to receiving the first selection information for any accessed data application information in the accessed data application information sequence, obtain access application interface joint debugging prompt information corresponding to the target accessed data application, and send the access application interface joint debugging prompt information to the target user terminal, so that the target user can develop local data applications according to the access application interface joint debugging prompt information. Among them, the target accessed data application corresponds to the selected accessed data application information. The first selection information may be information about the data application identifier of the target accessed data application selected by the target user. The access application interface joint debugging prompt information may include debugging precaution information and debugging example information. The debugging precaution information may be information for prompting the user to perform joint debugging of the local data application and the data interface corresponding to the accessed data application. For example, the precautions may include but are not limited to at least one of the following: code parser version, request method, and error-prone data information. Error-prone data information may be information about errors that have occurred multiple times during the joint debugging interaction process of each joint debugging user in the historical period. The debugging example information may be information about examples for interface debugging. The local data application may be an application developed by the user end for parsing data obtained from the data interface.

[0030] As an example, the execution subject may obtain access application interface joint debugging prompt information corresponding to the target connected data application from the cloud server, and send the access application interface joint debugging prompt information to the target user terminal. The target user may develop a local data application based on the access application interface joint debugging prompt information.

[0031] Step 103, in response to receiving the application interface request information for the target connected data application, based on a preset access application input parameter information sequence, the application interface request information is verified and processed to obtain an interface request verification result.

[0032] In some embodiments, the execution subject may, in response to receiving the application interface request information for the target accessed data application, verify the application interface request information in various ways based on a preset access application input parameter information sequence to obtain an interface request verification result. Among them, the application interface request information may be information of an HTTP (Hypertext Transfer Protocol) request to access the interface provided by the target accessed data application. The access application input parameter information sequence may be an information sequence of various parameters input into the target accessed data application. The access application input parameter information in the access application input parameter information sequence may include an input parameter name and an input parameter value. The input parameter name may be the name of the input parameter. For example, the input parameter may be an ID number. The input parameter value may be the value of the input parameter. The interface request verification result may indicate whether the input parameters included in the interface request are exactly the same as the parameters required for the access application.

[0033] In some optional implementations of some embodiments, the execution subject may perform verification processing on the application interface request information based on a preset access application input parameter information sequence through the following steps to obtain an interface request verification result:

[0034] The first step is to parse the above application interface request information to obtain a parameter string. The above parameter string can be a query string in an HTTP request. The above application interface request information can be parsed through the HTTP protocol and URL (Uniform Resource Locator) parsing method to obtain a parameter string.

[0035] In the second step, the parameter string is segmented once to obtain a segmented string group. The segmented string in the segmented string group can represent a key-value pair. The parameter string can be segmented once by a string segmentation function and a first preset character to obtain a segmented string group. The first preset character can be an "&" character. For example, the string segmentation function can be a split function.

[0036] The third step is to perform secondary segmentation processing on each segmented string in the segmented string group to obtain an input parameter information group. Each input parameter information in the input parameter information group may include a parameter name and a parameter value. For each segmented string in the segmented string group, the segmented string is subjected to secondary segmentation processing by the string segmentation function and a second preset character to obtain input parameter information. The second preset character may be a "=" character.

[0037] The fourth step is to determine the number of each input parameter information in the above input parameter information group as the first parameter number.

[0038] The fifth step is to determine the number of each access application input parameter information in the access application input parameter information sequence as the second parameter number.

[0039] Step 6: In response to determining that the number of the first parameters is the same as the number of the second parameters, for each access application input parameter information in the access application input parameter information sequence, perform the following steps:

[0040] The first sub-step is, in response to determining that the target input parameter information does not exist in the above-mentioned input parameter information group, generating parameter name error information based on the above-mentioned access application input parameter information and the preset key name error information template. The above-mentioned target input parameter information can be the input parameter information whose parameter name included in the above-mentioned input parameter information group matches the above-mentioned access application input parameter information. Matching with the above-mentioned access application input parameter information can be that the parameter name included in the input parameter information is the same as the input parameter name included in the above-mentioned access application input parameter information. The above-mentioned preset key name error information template can be a template text pre-set for filling in parameter name error information. For example, the above-mentioned preset key name error information template can be "Error message: Error type identifier__, missing input parameter__, there may be a spelling error in the parameter name, please check!". The preset key name error type identifier and the input parameter name included in the above-mentioned access application input parameter information can be filled into the above-mentioned preset key name error information template to obtain the parameter name error information. The above-mentioned key name error type identifier can be a unique identifier of the key name error type. The key name error type can characterize that the key name of the parameter has an error.

[0041] The second sub-step is, in response to determining that the target input parameter information exists in the input parameter information group, selecting the target input parameter information from the input parameter information group.

[0042] The third sub-step is to perform parameter value matching processing on the above-mentioned access application input parameter information and the above-mentioned target input parameter information to obtain a parameter value matching result. The above-mentioned parameter value matching result can indicate whether the parameter value of the actual input interface is consistent with the parameter value required by the access application. The above-mentioned parameter value matching result may include a matching result identifier. The above-mentioned matching result identifier may be 0 or 1. When the above-mentioned matching result identifier is 0, it indicates that the input parameter value is consistent with the parameter value required by the access application. When the above-mentioned matching result identifier is 1, it indicates that the input parameter value is inconsistent with the parameter value required by the access application, and the above-mentioned parameter value matching result may also include a matching error information group. The matching error information in the above-mentioned matching error information group may be information of the parameter value error type. The parameter value error type may include but is not limited to parameter value data type error and parameter value precision error. The preset parameter value matching interface may be called to perform parameter value matching processing on the above-mentioned access application input parameter information and the above-mentioned target input parameter information to obtain a parameter value matching result. The above-mentioned parameter value matching interface may encapsulate a parameter value matching method for comparing two parameter values. The above parameter value matching method can match the type, length or precision of two parameter values ​​and output the parameter value matching result.

[0043] In the seventh step, the obtained error information of each parameter name and the matching result of each parameter value are determined as the interface request verification result. It should be noted that when the parameter names are correct, the error information of each parameter name can be empty.

[0044] Optionally, the above execution entity may further perform the following steps:

[0045] In the first step, in response to determining that the first parameter number is different from the second parameter number, parameter number error information is generated. The parameter number error information may indicate that the number of parameters actually input to the interface is inconsistent with the number of parameters required for the access application. A preset input parameter number error identifier may be determined as the parameter number error information. The input parameter number error identifier may indicate that the number of parameters actually input to the interface is inconsistent with the number of parameters required for the access application.

[0046] The second step is to match the above-mentioned input parameter information group and the above-mentioned access application input parameter information sequence to obtain a key value matching result. Among them, the above-mentioned key value matching result can represent whether the various parameter names and parameter values ​​of the actual input interface are consistent with the various input parameter names and input parameter values ​​of the parameters required for the access application. You can refer to the above-mentioned parameter comparison step to match and compare the above-mentioned input parameter information group and the above-mentioned access application input parameter information sequence to obtain the error information of each parameter name and the matching results of each parameter value, and determine the obtained error information of each parameter name and the matching results of each parameter value as the key value matching result. The above-mentioned parameter comparison step will not be repeated here.

[0047] In the third step, the parameter number error information and the key value matching result are determined as the interface request verification result.

[0048] Step 104, in response to determining that the interface request verification result meets the preset verification pass condition, based on the application interface request information, calling the target accessed data application to obtain access application response data.

[0049] In some embodiments, the execution subject may, in response to determining that the interface request verification result satisfies the preset verification pass condition, call the target connected data application based on the application interface request information to obtain access application response data. The preset verification pass condition may be that the interface request verification result indicates that the input parameters included in the interface request are exactly the same as the parameters required by the access application. The access application response data may be the response data in json format returned by the target connected data application in response to the application interface request information.

[0050] Optionally, the above-mentioned execution entity may, in response to determining that the above-mentioned interface request verification result does not meet the above-mentioned preset verification pass condition, send the above-mentioned interface request verification result to the above-mentioned target user terminal, so that the above-mentioned target user can adjust the above-mentioned application interface request information and perform interface joint debugging test on the accessed data application according to the adjusted application interface request information.

[0051] Step 105: encrypt the access application response data to obtain encrypted response data, and send the encrypted response data to the target user terminal for parsing.

[0052] In some embodiments, the execution subject may encrypt the access application response data to obtain encrypted response data, and send the encrypted response data to the target user terminal for analysis. The encrypted response data may be encrypted access application response data. The access application response data may be encrypted using a preset encryption algorithm to obtain encrypted response data, and the encrypted response data may be sent to the target user terminal for analysis.

[0053] As an example, the encryption algorithm described above may be an algorithm combining AES symmetric encryption and RSA asymmetric encryption.

[0054] Step 106, in response to receiving the user interface call result data, generate an interface joint debugging result based on the access application response data and the user interface call result data, and send the interface joint debugging result to the target user terminal for display.

[0055] In some embodiments, the execution subject may generate an interface joint debugging result in response to receiving the user interface call result data, based on the access application response data and the user interface call result data, and send the interface joint debugging result to the target user terminal for display in various ways. The user interface call result data may be generated as a result of parsing the encrypted response data according to the local data application. The interface joint debugging result may indicate whether the response data obtained by parsing after the user calls the interface is exactly the same as the response data actually output by the access application.

[0056] Optionally, the user interface call result data may be generated by the target user terminal through the following steps:

[0057] In the first step, according to the decryption algorithm corresponding to the encryption algorithm, the local data application parses and outputs the encrypted response data to obtain decrypted response data.

[0058] In the second step, in response to detecting a click operation on the first upload method radio button in the response result comparison page, a text box control and a one-key comparison button control are displayed in the above-mentioned response result comparison page. Among them, the above-mentioned first upload method radio button control can be a radio button control for users to upload text by copying and pasting. The above-mentioned text box control can be a control for pasting text corresponding to the decrypted response data. The above-mentioned one-key comparison button control can be a button control for submitting the text in the text box control for comparison with the expected response result. The above-mentioned response result comparison page is a page in the above-mentioned data application access platform. The above-mentioned response result comparison page can also include a second upload method radio button control. The above-mentioned second upload method radio button control can be a radio button control for uploading an image of the user's screenshot including the decrypted response data. In practice, each connected data application that is undergoing interface joint debugging can correspond to a unique response result comparison page.

[0059] The third step is to determine the text data in the text box control as the user interface call result data in response to detecting a click operation on the one-key comparison button control.

[0060] Optionally, the target user terminal may further perform the following steps:

[0061] In the first step, in response to detecting a click operation on the second upload mode radio button in the response result comparison page, an editable block element and a one-key comparison button control are displayed in the response result comparison page. The editable block element may be a div element with a contenteditable attribute.

[0062] In the second step, in response to detecting a paste operation on the above-mentioned editable block element, a response result screenshot image is obtained from the clipboard of the target user terminal, and the response result screenshot image is displayed in the page area corresponding to the above-mentioned editable block element. The above-mentioned response result screenshot image can be an image obtained by the target user after taking a screenshot of the above-mentioned decoded response data.

[0063] The third step is to, in response to detecting a click operation on the one-key comparison button control, determine the response result screenshot image as the user interface call result data.

[0064] In some optional implementations of some embodiments, the execution subject may generate an interface joint debugging result based on the access application response data and the user interface call result data through the following steps:

[0065] The first step is, in response to determining that the above-mentioned user interface call result data meets the preset image data condition, performing image recognition processing on the above-mentioned user interface call result data to obtain user-side response data, and generating an interface joint debugging result based on the above-mentioned user-side response data and the above-mentioned access application response data. Among them, the above-mentioned preset image data condition may be that the above-mentioned user interface call result data is an image. The above-mentioned user-side response data may be text data displayed in the image. First, the above-mentioned user interface call result data may be subjected to image recognition processing by an optical character recognition method to obtain user-side response data. Then, the above-mentioned user-side response data and the above-mentioned access application response data may be matched by a string matching method to obtain an interface joint debugging result.

[0066] In some optional implementations of some embodiments, the execution subject may perform image recognition processing on the user interface call result data to obtain user-side response data through the following steps:

[0067] Step 1: In response to determining that the user interface call result data meets the preset image type condition, the user interface call result data is convolved to obtain an initial feature map. The preset image type condition may be that the user interface call result data is an image. The user interface call result data may be convolved using a 3*3 convolution kernel to obtain an initial feature map.

[0068] Step 2: Input the above initial feature map into the local feature extraction layer included in the pre-trained image character recognition model to obtain a sequence of local feature maps. Among them, the above local feature extraction layer can be composed of MaxViT (Multi-Axis Vision Transformer) modules. The local feature maps in the above sequence of local feature maps can be the feature maps corresponding to the image patches obtained by dividing the image. The above image character recognition model can also include a feature map flattening layer, a multi-scale feature extraction module, a multi-scale attention encoding module, a position information extraction module, and a self-attention decoding module. The above feature map flattening layer can be used to flatten the feature map into a one-dimensional vector. The above multi-scale feature extraction module can be used to perform multi-scale feature extraction on the image. The above multi-scale feature extraction module can be composed of a backbone network based on a convolutional neural network. The above multi-scale attention encoding module can be used to encode the multi-scale features according to the attention mechanism. The above multi-scale attention encoding module can be composed of a transformer encoder based on a multi-scale attention mechanism. The above position information extraction module can include a position curve fitting layer, a curve selection layer, a curve sampling layer, and a position encoding layer. The above position curve fitting layer can be used to fit the morphological curves formed by each character in the image. The above curve selection layer can be used to select each curve with a higher fitting score. The above curve sampling layer can be used to sample the curves. The above position encoding layer can be used to encode the character position information in the image. The above self-attention decoding module can be used to decode the extracted image character features to obtain a character sequence. The above self-attention decoding module can be a transformer decoder based on the self-attention mechanism.

[0069] Step 3: Use the feature map flattening layer included in the above image character recognition model to perform a flattening process on each local feature map in the above sequence of local feature maps to obtain a sequence of flattened feature vectors. Among them, the flattened feature vectors in the above sequence of flattened feature vectors can represent the features of a local area of the image.

[0070] Step 4: Use the multi-scale feature extraction module included in the above image character recognition model to perform multi-scale feature extraction on the above user interface call result data to obtain a multi-scale feature map set.

[0071] Step 5: Use the multi-scale attention encoding module included in the above image character recognition model to perform an encoding process on the above multi-scale feature map set to obtain an attention-encoded feature map set.

[0072] Step 6, using the position curve fitting layer in the position information extraction module, based on the attention encoding feature atlas, generate a Bezier center curve information set. The Bezier center curve information in the Bezier center curve information set may include a Bezier curve equation and a curve score. The curve score may characterize the confidence of the Bezier curve equation. For each attention encoding feature map in the attention encoding feature map, the position curve fitting layer may sequentially perform operations such as dimensionality reduction, vector normalization, and curve fitting.

[0073] Step 7: sort the Bezier center curve information set using the curve selection layer in the position information extraction module to obtain a Bezier center curve information sequence, and select the Bezier center curve information of the first preset value from the Bezier center curve information sequence as the target Bezier center curve information sequence. The preset value may be a pre-set value. For example, the preset value may be 5.

[0074] Step eight, using the curve sampling layer in the position information extraction module, uniformly sample each target Bezier center curve information in the target Bezier center curve information sequence to obtain a sampling point coordinate group sequence.

[0075] Step 9: Using the position encoding layer in the position information extraction module, position encoding is performed on the coordinates of each sampling point in the sampling point coordinate group sequence to obtain a position feature vector set. The position encoding layer can perform position encoding on the coordinates of each sampling point in the sampling point coordinate group sequence to obtain a position feature vector set by sequentially performing sinusoidal position encoding and multi-layer perceptron operations.

[0076] Step ten: input the flattened feature vector sequence and the position feature vector set into the self-attention decoding module included in the image character recognition model to obtain user-side response data.

[0077] Optionally, the above-mentioned image character recognition model can be trained and optimized by using a conventional cross entropy loss function and a gradient descent algorithm.

[0078] In the second step, in response to determining that the user interface call result data does not meet the preset image data condition, the user interface call result data and the access application response data are subjected to string matching processing to generate a string matching result. The string matching result can indicate whether the user interface call result data and the access application response data are completely identical. The user interface call result data and the access application response data can be subjected to string matching processing by the string matching method to generate a string matching result.

[0079] The third step is, in response to determining that the above string matching result satisfies the preset incomplete matching condition, performing type conversion processing on the above user interface call result data to obtain first dictionary type result data. Among them, the above first dictionary type result data can be a dictionary type interface call result. The above first dictionary type result data can include various first dictionary items. Each first dictionary item is a key-value pair. The above user interface call result data can be converted into a dictionary by a method of converting a JSON (JavaScript Object Notation) string to obtain the first dictionary type result data.

[0080] The fourth step is to determine the second dictionary type result data corresponding to the access application response data. The second dictionary type result data may be the expected response data of the target accessed application of the dictionary type. The expected response data may be the data that the predicted data application needs to output normally. The first dictionary type result data may include each second dictionary item. The second dictionary type result data corresponding to the access application response data may be determined by the method of converting the JSON string into a dictionary.

[0081] Step 5: Match the first dictionary type result data with the second dictionary type result data to obtain the interface joint debugging result. Specifically, the following steps can be performed:

[0082] In the first sub-step, for each second dictionary item in the second dictionary type result data, the following sub-steps may be performed:

[0083] Sub-step 1: In response to determining that the target first dictionary item does not exist in each first dictionary item in the first dictionary type result data, a preset response parameter missing flag is determined as response parameter key name error information. The target first dictionary item is a first dictionary item in each first dictionary item included in the first dictionary type result data, the key included in which is the same as the key included in the second dictionary item. The preset response parameter missing flag can indicate that the response parameter item is missing.

[0084] Sub-step two: in response to determining that there is a target first dictionary item among the first dictionary items in the first dictionary type result data, selecting a target first dictionary item from the first dictionary items in the first dictionary type result data.

[0085] Sub-step three, in response to determining that the value included in the above-mentioned target first dictionary item is different from the value included in the above-mentioned second dictionary item, the value included in the above-mentioned second dictionary item is used as a reference value, the value included in the above-mentioned target first dictionary item is used as an error value, and the preset response value error identifier, the above-mentioned reference value, and the above-mentioned error value are filled into the preset response data error template to obtain response value error information. The above-mentioned preset response value error identifier can represent that an error has occurred in the response value. The above-mentioned preset response data error template can be a pre-set template. For example, the above-mentioned preset response data error template can be "Error information: error type identifier__, reference value__, error value__!".

[0086] Sub-step four: in response to determining that the value included in the above-mentioned target first dictionary item is the same as the value included in the above-mentioned second dictionary item, determining the preset response value correctness mark as the response value verification correctness information.

[0087] In the second sub-step, the obtained response parameter key name error information, response value error information and response value verification information are determined as the interface joint debugging result.

[0088] The above-mentioned interface joint debugging result generation step and its related content, as an inventive point of an embodiment of the present disclosure, solve the technical problem 2 mentioned in the background technology, "it is difficult to complete the interface joint debugging in time, and the user experience is poor". The reasons for the difficulty in completing the interface joint debugging in time and the poor user experience are often as follows: if the parsed data and the expected response data of the interface are compared for consistency through the locally written result comparison program, each data demand user needs to write a result comparison program for the data application to be accessed, and there are differences in the response data returned by each data application interface. For each data application to be accessed, the user needs to spend a lot of extra time to write the corresponding result comparison program. If the above problems are solved, the effect of completing the interface joint debugging in time and improving the user experience can be achieved. In order to achieve this effect, first, the user interface call result data is obtained. Among them, the user interface call result data can be a string text of the parsed response data copied by the user, or a screenshot of the parsed response data provided by the user. Then, according to the data type of the user interface call result data, different methods are used to verify whether the string text corresponding to the access application response data and the user interface call result data is consistent (same). When the user interface call result data is a text string, it can be verified by a string matching method. When the result data of the user interface call is an image, the string text in the image can be identified and then verified by the string matching method. As a result, there is no need for the user terminal to write a result comparison program, so that the user local and application interface can complete the joint debugging in time, so that the user can obtain the required data in time. In turn, the user experience is improved.

[0089] In addition, in the process of solving the above-mentioned technical problems 1 and 2, it is also considered that the existing solution "first detects the position of the text, then crops the text area from the original image, and finally recognizes the text in the cropped area". In solving the problem of image character recognition, there is a technical problem that "due to the sequential execution of detection and recognition, it is easy to cause the reasoning speed to decrease, and when the detection is inaccurate, it is easy to cause the execution error to accumulate, resulting in low accuracy of character text recognition". Therefore, when executing the above-mentioned user-side response data generation step, this solution uses the above-mentioned image character recognition model to simultaneously detect and recognize the text string. In addition, because the above-mentioned image character recognition model can better extract image features and reduce model parameters through the MaxViT network, and in the process of position encoding, it can better focus on the key areas in the image through the multi-scale attention module, thereby facilitating the decoding of the results after decoding the image features and position encoding, the accuracy of the decoding results can be improved. Thus, user-side response data with higher accuracy can be obtained. Furthermore, a more accurate interface joint debugging result can be obtained.

[0090] Optionally, the execution subject may also, in response to determining that the interface joint debugging result satisfies a preset debugging failure condition, update the access application interface joint debugging prompt information based on the interface joint debugging result to obtain updated access application interface joint debugging prompt information for local data application development for the target connected data application. Among them, the preset debugging failure condition may be: the interface joint debugging result indicates that the response data obtained by parsing after the user calls the interface is not completely the same as the response data actually output by the access application. The updated access application interface joint debugging prompt information may be the updated access application interface joint debugging prompt information. The debugging precautions information included in the access application interface joint debugging prompt information may be updated according to the error information included in the interface joint debugging result to obtain updated access application interface joint debugging prompt information.

[0091] As an example, the above-mentioned execution entity can count the frequency of occurrence of error types based on the interface joint debugging results corresponding to the above-mentioned target user and the interface joint debugging results corresponding to other joint debugging users, and according to the frequency of occurrence of the above-mentioned error types, arrange the various precautions included in the debugging precautions information in the access application interface joint debugging prompt information in descending order to obtain updated access application interface joint debugging prompt information.

[0092] Optionally, the above execution entity may further perform the following steps:

[0093] The first step is to send a preset access application form page to the target user terminal in response to receiving the second selection information for any non-access data application information in the non-access data application information sequence, so that the target user can apply for access to the target non-access data application. The target non-access data application can correspond to the selected non-access data application information. The second selection information can be information of the data application identifier of the target non-access data application selected by the target user. The access application form page can be a web page for the user to fill in the access application form. The access application form can be a form for applying for data application access authority.

[0094] In the second step, in response to receiving the access application form information for the above-mentioned target non-access data application, the access application form information is verified and processed to obtain the form verification result. Among them, the access application form information can be the information of the access application form filled out by the target user. The above-mentioned form verification result can indicate whether the access application form information filled out by the target user meets the access conditions of the target non-access data application. The preset form verification interface can be called to verify the access application form information and obtain the form verification result. The above-mentioned form verification interface can be encapsulated with a form verification method. The above-mentioned form verification method can be used to perform compliance checks on each form item in the access application form. The compliance check may include but is not limited to at least one of the following: type check, length check.

[0095] In the third step, in response to determining that the form verification result meets the preset verification pass condition, the access application interface joint debugging prompt information corresponding to the target non-access data application is sent to the target user terminal for interface joint debugging of the accessed data application. Among them, the preset verification pass condition can be: the form verification result indicates that the access application form information filled in by the target user meets the access condition of the target non-access data application.

[0096] The above-mentioned embodiments of the present disclosure have the following beneficial effects: through the interface joint debugging method of some embodiments of the present disclosure, the time consumption of interface joint debugging can be shortened and the efficiency of interface joint debugging can be improved. Specifically, the reason for the long time consumption of interface joint debugging is that it is difficult for the user end to obtain the error information of the request failure in time, which reduces the efficiency of interface joint debugging, thereby causing the interface joint debugging to take a long time. Based on this, the interface joint debugging method of some embodiments of the present disclosure, first, in response to receiving the data application query information sent by the target user terminal, generates an accessed data application information sequence and an unaccessed data application information sequence, and sends the above-mentioned accessed data application information sequence and the above-mentioned unaccessed data application information sequence to the above-mentioned target user terminal, so as to perform interface joint debugging test on the data application. Thus, it is convenient to perform joint debugging on the accessed data application and the user's local program in the subsequent process. Secondly, in response to receiving the first selection information for any accessed data application information in the above-mentioned accessed data application information sequence, obtain the access application interface joint debugging prompt information corresponding to the target accessed data application, and send the above-mentioned access application interface joint debugging prompt information to the above-mentioned target user terminal, so that the above-mentioned target user can develop local data applications according to the above-mentioned access application interface joint debugging prompt information. Among them, the above-mentioned target accessed data application corresponds to the selected accessed data application information. Thus, it is convenient for users to develop local programs for interface joint debugging according to the joint debugging prompt information of the data application to be joint debugged. Then, in response to receiving the application interface request information for the above-mentioned target accessed data application, based on the preset access application input parameter information sequence, the above-mentioned application interface request information is verified and processed to obtain the interface request verification result. Thus, in the interface joint debugging process, it is possible to timely determine whether the interface test request sent by the local program is correct. Then, in response to determining that the above-mentioned interface request verification result meets the preset verification pass condition, based on the above-mentioned application interface request information, the above-mentioned target accessed data application is called to obtain the access application response data. Thus, when the interface test request is correct, the corresponding data application can be called to obtain the response data corresponding to the test request. Afterwards, the above-mentioned access application response data is encrypted to obtain the encrypted response data, and the above-mentioned encrypted response data is sent to the above-mentioned target user terminal for parsing. Thus, it is convenient to verify the response data after the user terminal is parsed, so that the user can determine whether the local parsing program has an error. Finally, in response to receiving the user interface call result data, an interface joint debugging result is generated based on the access application response data and the user interface call result data, and the interface joint debugging result is sent to the target user terminal for display. Among them, the user interface call result data is generated by parsing the encrypted response data according to the local data application. In this way, the verified interface joint debugging result can be sent to the user in a timely manner, so that the user can adjust the local parsing program in a timely manner.Therefore, the interface joint debugging method of some embodiments of the present disclosure can timely check the error information in the interface request or the response data after parsing, and timely feed back the error information to the user terminal for re-interface joint debugging until the joint debugging is successful. Thus, the time consumption of interface joint debugging can be shortened and the efficiency of joint debugging can be improved.

[0097] Further references Figure 2 As an implementation of the methods shown in the above figures, the present disclosure provides some embodiments of an interface joint debugging device. These device embodiments are similar to Figure 1 Corresponding to the method embodiments shown, the interface joint debugging device 200 can be specifically applied to various electronic devices.

[0098] like Figure 2As shown, the interface joint debugging device 200 of some embodiments includes: a first generating and sending unit 201, an acquiring and sending unit 202, a verification processing unit 203, a calling unit 204, an encryption processing and sending unit 205 and a second generating and sending unit 206. Among them, the first generation and sending unit 201 is configured to generate an accessed data application information sequence and a non-accessed data application information sequence in response to receiving data application query information sent by the target user terminal, and send the above-mentioned accessed data application information sequence and the above-mentioned non-accessed data application information sequence to the above-mentioned target user terminal for interface joint debugging test for the data application; the acquisition and sending unit 202 is configured to obtain access application interface joint debugging prompt information corresponding to the target accessed data application in response to receiving the first selection information for any accessed data application information in the above-mentioned accessed data application information sequence, and send the above-mentioned access application interface joint debugging prompt information to the above-mentioned target user terminal, so that the above-mentioned target user can perform local data application development according to the above-mentioned access application interface joint debugging prompt information, wherein the above-mentioned target accessed data application corresponds to the selected accessed data application information; the verification processing unit 203 is configured to respond to receiving the first selection information for the above-mentioned target accessed data application Application interface request information, based on a preset access application input parameter information sequence, verifies the above application interface request information to obtain an interface request verification result; a calling unit 204 is configured to, in response to determining that the above interface request verification result meets the preset verification pass condition, call the above target accessed data application based on the above application interface request information to obtain access application response data; an encryption processing and sending unit 205 is configured to encrypt the above access application response data to obtain encrypted response data, and send the above encrypted response data to the above target user terminal for parsing; a second generation and sending unit 206 is configured to, in response to receiving the user interface call result data, generate an interface joint debugging result based on the above access application response data and the above user interface call result data, and send the above interface joint debugging result to the above target user terminal for display, wherein the above user interface call result data is generated as a result of parsing the above encrypted response data according to the above local data application.

[0099] It can be understood that the units recorded in the interface joint debugging device 200 are similar to those in the reference Figure 1 Therefore, the operations, features and beneficial effects described above for the method are also applicable to the interface joint debugging device 200 and the units included therein, and will not be described in detail here.

[0100] Further references Figure 3 , which shows a structural schematic diagram of an electronic device 300 suitable for implementing some embodiments of the present disclosure. Figure 3 The electronic device shown is merely an example and should not impose any limitations on the functions and scope of use of the embodiments of the present disclosure.

[0101] As Figure 3 shown, the electronic device 300 may include a processing device (such as a central processing unit, a graphics processing unit, etc.) 301, which may perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 302 or a program loaded from a storage device 308 into a random access memory (RAM) 303. In the RAM 303, various programs and data required for the operation of the electronic device 300 are also stored. The processing device 301, the ROM 302, and the RAM 303 are connected to each other through a bus 304. An input / output (I / O) interface 305 is also connected to the bus 304.

[0102] Generally, the following devices may be connected to the I / O interface 305: an input device 306 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 307 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 308 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 309. The communication device 309 may allow the electronic device 300 to communicate with other devices wirelessly or wirelesly to exchange data. Although Figure 3 the electronic device 300 with various devices is shown, it should be understood that it is not required to implement or include all the shown devices. Instead, more or fewer devices may be implemented or included. Figure 3 Each block shown in

[0103] particular, according to some embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, some embodiments of the present disclosure include a computer program product that includes a computer program carried on a computer-readable medium, and the computer program includes program codes for performing the methods shown in the flowcharts. In such some embodiments, the computer program may be downloaded and installed from a network through the communication device 309, or installed from the storage device 308, or installed from the ROM 302. When the computer program is executed by the processing device 301, the above-mentioned functions defined in the methods of some embodiments of the present disclosure are performed.

[0104] It should be noted that in some embodiments of the present disclosure, the above-mentioned computer-readable medium may be a computer-readable signal medium, a computer-readable storage medium, or any combination of the two. A computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In some embodiments of the present disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program, which can be used by or in conjunction with an instruction execution system, apparatus, or device. In some embodiments of the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries computer-readable program code. Such a propagated data signal may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0105] In some embodiments, the client and the server can communicate using any currently known or future-developed network protocol such as HTTP (HyperText Transfer Protocol), and can be interconnected with digital data communication in any form or medium (e.g., a communication network). Examples of communication networks include local area networks ("LANs"), wide area networks ("WANs"), the Internet (e.g., the Internet), and end-to-end networks (e.g., ad hoc end-to-end networks), as well as any currently known or future-developed network.

[0106] The above-mentioned computer-readable medium may be included in the above-mentioned device; or it may exist independently and not be assembled into the electronic device. The above-mentioned computer-readable medium carries one or more programs. When the above-mentioned one or more programs are executed by the electronic device, the electronic device: generates an accessed data application information sequence and a non-accessed data application information sequence in response to receiving data application query information sent by the target user terminal, and sends the above-mentioned accessed data application information sequence and the above-mentioned non-accessed data application information sequence to the above-mentioned target user terminal for interface joint debugging test for the data application; obtains access application interface joint debugging prompt information corresponding to the target accessed data application in response to receiving the first selection information for any accessed data application information in the above-mentioned accessed data application information sequence, and sends the above-mentioned access application interface joint debugging prompt information to the above-mentioned target user terminal, so that the above-mentioned target user can develop local data applications according to the above-mentioned access application interface joint debugging prompt information, wherein the above-mentioned target accessed data application is related to the selected accessed data application information. Corresponding; in response to receiving application interface request information for the above-mentioned target accessed data application, based on a preset access application input parameter information sequence, the above-mentioned application interface request information is verified and processed to obtain an interface request verification result; in response to determining that the above-mentioned interface request verification result meets the preset verification pass condition, based on the above-mentioned application interface request information, the above-mentioned target accessed data application is called to obtain access application response data; the above-mentioned access application response data is encrypted to obtain encrypted response data, and the above-mentioned encrypted response data is sent to the above-mentioned target user terminal for parsing; in response to receiving user interface call result data, based on the above-mentioned access application response data and the above-mentioned user interface call result data, an interface joint debugging result is generated, and the above-mentioned interface joint debugging result is sent to the above-mentioned target user terminal for display, wherein the above-mentioned user interface call result data is generated as a result of parsing the above-mentioned encrypted response data according to the above-mentioned local data application.

[0107] Computer program code for performing the operations of some embodiments of the present disclosure may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0108] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0109] The units described in some embodiments of the present disclosure may be implemented by software or by hardware. The described units may also be set in a processor, for example, may be described as: a processor comprising: a first generating and sending unit, an acquiring and sending unit, a verification processing unit, a calling unit, an encryption processing and sending unit, and a second generating and sending unit. Among them, the names of these units do not constitute a limitation on the units themselves under certain circumstances. For example, the first generating and sending unit may also be described as "a unit that generates an accessed data application information sequence and a non-accessed data application information sequence, and sends the above-mentioned accessed data application information sequence and the above-mentioned non-accessed data application information sequence to the above-mentioned target user terminal".

[0110] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0111] The above descriptions are only some preferred embodiments of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of the invention involved in the embodiments of the present disclosure is not limited to the technical solutions formed by a specific combination of the above-mentioned technical features, but should also cover other technical solutions formed by any combination of the above-mentioned technical features or their equivalent features without departing from the above-mentioned inventive concept. For example, the above-mentioned features are replaced with the technical features with similar functions disclosed in the embodiments of the present disclosure (but not limited to) and the technical solutions formed.

Claims

1. An interface joint debugging method, comprising: In response to receiving data application query information sent by a target user terminal, generating an accessed data application information sequence and a non-accessed data application information sequence, and sending the accessed data application information sequence and the non-accessed data application information sequence to the target user terminal for performing an interface joint debugging test on the data application; In response to receiving first selection information for any accessed data application information in the accessed data application information sequence, obtaining access application interface joint debugging prompt information corresponding to a target accessed data application, and sending the access application interface joint debugging prompt information to the target user terminal, so that the target user can perform local data application development according to the access application interface joint debugging prompt information, wherein the target accessed data application corresponds to the selected accessed data application information; In response to receiving the application interface request information for the target accessed data application, based on a preset access application input parameter information sequence, verifying the application interface request information to obtain an interface request verification result; In response to determining that the interface request verification result meets a preset verification pass condition, based on the application interface request information, calling the target accessed data application to obtain access application response data; Encrypting the access application response data to obtain encrypted response data, and sending the encrypted response data to the target user terminal for parsing; In response to receiving user interface call result data, an interface debugging result is generated based on the access application response data and the user interface call result data, and the interface debugging result is sent to the target user terminal for display, wherein the user interface call result data is generated as a result of parsing the encrypted response data according to the local data application.

2. The method according to claim 1, wherein: The method further comprises: In response to determining that the interface request verification result does not meet the preset verification pass condition, the interface request verification result is sent to the target user terminal so that the target user can adjust the application interface request information and perform interface joint debugging test on the accessed data application according to the adjusted application interface request information.

3. The method according to claim 1, wherein: The verifying and processing the application interface request information based on the preset access application input parameter information sequence to obtain the interface request verification result includes: Parsing the application interface request information to obtain a parameter string; Performing a segmentation process on the parameter character string to obtain a segmented character string group; Performing secondary segmentation processing on each segmented character string in the segmented character string group to obtain an input parameter information group, wherein each input parameter information in the input parameter information group includes a parameter name and a parameter value; Determine the number of each input parameter information in the input parameter information group as a first parameter number; Determine the number of each access application input parameter information in the access application input parameter information sequence as the second parameter number; In response to determining that the number of the first parameters is the same as the number of the second parameters, for each access application input parameter information in the access application input parameter information sequence, performing the following parameter comparison step: In response to determining that the target input parameter information does not exist in the input parameter information group, generating parameter name error information based on the access application input parameter information and a preset key name error information template, wherein the target input parameter information is input parameter information whose parameter name included in the input parameter information group matches the access application input parameter information; In response to determining that target input parameter information exists in the input parameter information group, selecting target input parameter information from the input parameter information group; Performing parameter value matching processing on the access application input parameter information and the target input parameter information to obtain a parameter value matching result; The obtained error information of each parameter name and the matching result of each parameter value are determined as the interface request verification result.

4. The method according to claim 3, wherein: The method further comprises: In response to determining that the first number of parameters is not the same as the second number of parameters, generating parameter number error information; Performing matching processing on the input parameter information group and the access application input parameter information sequence to obtain a key value matching result; The parameter number error information and the key value matching result are determined as the interface request verification result.

5. The method according to any one of claims 1 to 4, wherein: The generating the interface joint debugging result based on the access application response data and the user interface call result data includes: In response to determining that the user interface call result data meets the preset image data condition, performing image recognition processing on the user interface call result data to obtain user side response data, and generating an interface joint debugging result based on the user side response data and the access application response data; In response to determining that the user interface call result data does not meet the preset image data condition, performing string matching processing on the user interface call result data and the access application response data to generate a string matching result; In response to determining that the string matching result satisfies a preset incomplete matching condition, performing type conversion processing on the user interface call result data to obtain first dictionary type result data; Determine second dictionary type result data corresponding to the access application response data; The first dictionary type result data and the second dictionary type result data are matched to obtain an interface joint debugging result.

6. The method according to claim 1, wherein: The method further comprises: In response to determining that the interface joint debugging result meets the preset debugging failure condition, based on the interface joint debugging result, the access application interface joint debugging prompt information is updated to obtain updated access application interface joint debugging prompt information for local data application development for the target connected data application.

7. The method according to claim 1, wherein: The method further comprises: In response to receiving second selection information for any non-access data application information in the non-access data application information sequence, sending a preset access application form page to the target user terminal for the target user to apply for access to a target non-access data application, wherein the target non-access data application corresponds to the selected non-access data application information; In response to receiving the access application form information for the target non-access data application, verifying the access application form information to obtain a form verification result; In response to determining that the form verification result meets the preset verification pass condition, the access application interface joint debugging prompt information corresponding to the target non-accessed data application is sent to the target user terminal for interface joint debugging for the accessed data application.

8. An interface joint debugging device, comprising: A first generating and sending unit is configured to generate an accessed data application information sequence and a non-accessed data application information sequence in response to receiving data application query information sent by a target user terminal, and send the accessed data application information sequence and the non-accessed data application information sequence to the target user terminal for performing an interface joint debugging test on the data application; an acquiring and sending unit, configured to, in response to receiving first selection information for any accessed data application information in the accessed data application information sequence, acquire access application interface joint debugging prompt information corresponding to a target accessed data application, and send the access application interface joint debugging prompt information to the target user terminal, so that the target user can perform local data application development according to the access application interface joint debugging prompt information, wherein the target accessed data application corresponds to the selected accessed data application information; A verification processing unit is configured to, in response to receiving application interface request information for the target accessed data application, perform verification processing on the application interface request information based on a preset access application input parameter information sequence to obtain an interface request verification result; A calling unit, configured to, in response to determining that the interface request verification result satisfies a preset verification pass condition, call the target accessed data application based on the application interface request information to obtain access application response data; An encryption processing and sending unit is configured to encrypt the access application response data to obtain encrypted response data, and send the encrypted response data to the target user terminal for parsing; The second generating and sending unit is configured to generate an interface debugging result in response to receiving user interface call result data, based on the access application response data and the user interface call result data, and send the interface debugging result to the target user terminal for display, wherein the user interface call result data is generated as a result of parsing the encrypted response data according to the local data application.

9. An electronic device, comprising: one or more processors; a storage device having one or more programs stored thereon, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 7.

10. A computer readable medium having a computer program stored thereon, wherein: When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Citation Information

Patent Citations

  • Joint debugging system, joint debugging method, computer equipment and storage medium

    CN110427324A

  • Interface calling method and device, interface data storage method and device, equipment and storage medium

    CN112287009A