CN112269706A - Interface parameter verification method, apparatus, electronic device, and computer-readable medium - Google Patents
Interface parameter verification method, apparatus, electronic device, and computer-readable medium Download PDFInfo
- Publication number
- CN112269706A CN112269706A CN202011279136.2A CN202011279136A CN112269706A CN 112269706 A CN112269706 A CN 112269706A CN 202011279136 A CN202011279136 A CN 202011279136A CN 112269706 A CN112269706 A CN 112269706A
- Authority
- CN
- China
- Prior art keywords
- parameter
- interface
- verified
- verification
- name
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2205—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing using arrangements specific to the hardware being tested
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2247—Verification or detection of system hardware configuration
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2273—Test methods
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
本申请公开了一种接口参数校验方法和装置，涉及云计算技术领域，进一步涉及数据测试、数据通信领域。该方法的一具体实施方式包括：加载参数校验规则，参数校验规则用于对至少一个接口的接口参数进行校验；接收网络中的接口校验请求消息；提取接口校验请求消息中的接口名称和待校验接口参数；基于参数校验规则，对待校验接口参数进行校验，并返回校验结果。该实施方式节省了开发成本。
The present application discloses an interface parameter verification method and device, which relate to the technical field of cloud computing, and further relate to the fields of data testing and data communication. A specific implementation of the method includes: loading a parameter verification rule, which is used to verify interface parameters of at least one interface; receiving an interface verification request message in the network; extracting the interface verification request message from the interface verification request message. Interface name and interface parameters to be verified; based on the parameter verification rules, the parameters of the interface to be verified are verified, and the verification result is returned. This embodiment saves development costs.
Description
Technical Field
The present application relates to the field of cloud computing technologies, and in particular, to the field of data testing and data communication, and in particular, to a method and an apparatus for checking an interface parameter, an electronic device, and a computer-readable medium.
Background
Application programs and application programs often need to realize specific business logic through interface calling, such as: the "goods management program" calls the interface provided by the "order management program" to obtain all the associated orders for a single good. When the interface is called, information is transmitted through interface parameters, such as: in the above scenario, the product ID is an interface parameter passed to the order manager by the product manager.
Each parameter when the interface is called needs to be written by a developer to form a corresponding check logic. If the number of parameters in the interface calling is large or the number of fields in the interface calling needs to be increased or decreased frequently, the workload of developers is large, and the development cost is high.
Disclosure of Invention
An interface parameter checking method, an interface parameter checking device, an electronic device and a computer readable medium are provided.
According to a first aspect, there is provided an interface parameter verification method, including: loading a parameter verification rule, wherein the parameter verification rule is used for verifying the interface parameters of at least one interface; receiving an interface checking request message in a network; extracting an interface name and an interface parameter to be checked in the interface checking request message; and verifying the interface parameters to be verified based on the parameter verification rule corresponding to the interface name, and returning a verification result.
According to a second aspect, there is provided an interface parameter checking apparatus, comprising: a loading unit configured to load a parameter verification rule, the parameter verification rule being used for verifying an interface parameter of at least one interface; a receiving unit configured to receive an interface verification request message in a network; an extraction unit configured to extract an interface name and an interface parameter to be verified in the interface verification request message; and the checking unit is configured to check the interface parameter to be checked based on the parameter checking rule corresponding to the interface name and return a checking result.
According to a third aspect, there is provided an electronic device comprising: at least one processor; and a memory communicatively connected to the at least one processor, wherein the memory stores instructions executable by the at least one processor, the instructions being executable by the at least one processor to enable the at least one processor to perform the method as described in any one of the implementations of the first aspect.
According to a fourth aspect, there is provided a non-transitory computer readable storage medium having stored thereon computer instructions for causing a computer to perform a method as described in any one of the implementations of the first aspect.
According to the interface parameter verification method and device provided by the embodiment of the application, a parameter verification rule for verifying the interface parameters of at least one interface is loaded; secondly, receiving an interface checking request message in the network; then, extracting the interface name and the interface parameter to be checked in the interface checking request message; and finally, checking the interface parameter to be checked based on the parameter checking rule corresponding to the interface name, and returning a checking result. Therefore, all interface parameters to be verified in the interface verification message can be verified through the loaded parameter verification rule, the automation of interface parameter verification is improved, and the development cost of technicians in verifying the interface parameters to be verified is saved.
It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present disclosure, nor do they limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.
Drawings
The drawings are included to provide a better understanding of the present solution and are not intended to limit the present application. Wherein:
FIG. 1 is a flow diagram of one embodiment of an interface parameter verification method according to the present application;
fig. 2 is a flowchart of a method for extracting interface parameters to be verified from an interface verification request message according to the present application;
FIG. 3 is a flowchart illustrating the verification of interface parameters to be verified according to the present application;
FIG. 4 is a flow chart of another embodiment of an interface parameter verification method of the present application;
FIG. 5 is a schematic structural diagram of an embodiment of an interface parameter verification apparatus according to the present application;
fig. 6 is a block diagram of an electronic device for implementing an interface parameter verification method according to an embodiment of the present application.
Detailed Description
The following description of the exemplary embodiments of the present application, taken in conjunction with the accompanying drawings, includes various details of the embodiments of the application for the understanding of the same, which are to be considered exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present application. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
FIG. 1 illustrates a flow 100 according to one embodiment of an interface parameter verification method of the present application. The interface parameter checking method comprises the following steps:
The parameter checking rule is used for checking the interface parameters of at least one interface.
In this embodiment, the parameter verification rule is a predetermined verification rule, and all interface parameters of the interface that needs to be called currently may be verified. The parameter verification rule corresponds to at least one interface name, and each interface name can correspond to a parameter verification rule related to the verification of a plurality of interface parameters.
Wherein, the interface parameter is verified to include: whether the interface parameter meets the requirements of the attribute (the type of the parameter, the size range of the parameter value, etc.) of the interface parameter is judged, for example, the checking rule includes: whether the interface parameter is empty, whether the type of the interface parameter meets the preset type requirement, whether the length of the interface parameter meets the preset length, and the like.
Further, since the interface call request including the interface parameter needs to satisfy the requirement of the network transmission protocol in the network (for example, local area network or internet) transmission process, the performing the check rule on the interface parameter may further include checking whether the interface call request including the interface parameter satisfies the network transmission protocol of the interface parameter, and certainly, the performing the check rule on the interface parameter may also be: after determining that the interface call request containing the interface parameters meets the network transmission protocol of the interface parameters, whether the interface parameters meet the requirements of the attributes of the interface parameters can be checked.
Optionally, in this embodiment, the verifying the interface parameter by the parameter verification rule may further include: format processing is performed on the acquired interface parameters (for example, the interface parameters are converted into types corresponding to the interface parameters), and then whether the interface parameters subjected to actual format processing meet the requirements of the types corresponding to the interface parameters is judged.
In this embodiment, the interface parameter verification method and the execution subject thereon may obtain the parameter verification rule in real time from the terminal or from the database, and verify the interface parameter in the received verification request message based on the verification logic of the parameter verification rule after loading the parameter verification rule.
In this embodiment, the network may be the internet or a local area network. The interface verification request message is a message which is sent by an application program to another application program in the process of calling the interface of another application program to realize the specific service logic and is about the interface parameter to be verified.
Specifically, the interface verification request message includes interface parameters to be verified, and based on different transmission protocols, the positions of the interface parameters to be verified in the interface verification request message are different. For example, based on the HTTP (HyperText Transfer Protocol) transmission Protocol, the interface parameters to be verified may be located at three positions, namely Query (request line), Header (request Header), and Body (request Body), of the corresponding Protocol in the interface verification request message.
And 103, extracting the interface name and the interface parameter to be checked in the interface checking request message.
In this embodiment, after the execution main body receives the interface verification request message, the interface name and the interface parameter to be verified in the interface verification request message may be extracted by an Interceptor (e.g., an Interceptor tool).
Optionally, before extracting the interface name and the interface parameter to be verified in the interface verification request message, the service requirement information in the interface verification request message may be pre-verified, the interface verification request message generally carries the service requirement information of itself, for example, "obtain a piece of goods detail information according to a goods ID", at this time, the request carries a goods ID, the goods ID is the service requirement information of itself, the goods ID may be verified first, and the pre-verification is completed if the verification passes.
And 104, verifying the interface parameter to be verified based on the parameter verification rule corresponding to the interface name, and returning a verification result.
In this embodiment, the parameter verification rule includes at least one parameter verification rule corresponding to the interface name, and since different interface names have different parameter verification rules, the extracted interface name may be used as an index to search and determine the parameter verification rule corresponding to the interface name in the parameter verification rule.
Further, the parameter verification rule corresponding to the interface name includes at least one parameter verification rule corresponding to the interface parameter, and the interface parameter includes: the name of the interface parameter and the parameter value corresponding to the name of the interface parameter may be indexed by the name of the interface parameter, and a parameter verification rule corresponding to the interface parameter to be verified in the parameter verification rule corresponding to the name of the interface is searched and determined.
In this embodiment, the interface parameter to be verified is one of the at least one interface parameter, and the interface parameter to be verified includes: the name of the interface parameter to be verified and the parameter value corresponding to the name of the interface parameter to be verified. As shown for example one.
The first embodiment is as follows: {
"paramName":"emailAddress",
"apiName":"submitEmailAddress",
"position":"Query",
"using":"ture",
"type":"string",
"required":true,
"maxLength":100,
"minLength":5,
"pattern":"^[a-z0-9A-Z]+[-|a-z0-9A-Z._]+@([a-z0-9A-Z]+(-[a-z0-9A-Z]+)？\\.)+[a-z]{2,}$"}
The parameter verification rule corresponding to the interface name shown in the first embodiment represents:
and verifying the submitemEmailAddress of the interface name and the name emailAddress of the parameter to be verified of the position Query, wherein the maximum length of the name of the parameter to be verified is 100, the minimum length of the name of the parameter to be verified is 5, and the parameter value corresponding to the name of the parameter to be verified needs to meet the regular expression of the pattern part.
In this embodiment, the verification result includes: and when the verification result is that the verification is passed, a subsequent interface calling mode can be carried out. And when the verification result is that the interface parameter to be verified is not verified, determining that the interface parameter to be verified is illegal, and sending an abnormal message or/and an alarm.
The interface parameter verification method provided by the embodiment of the application comprises the steps of firstly loading a parameter verification rule for verifying the interface parameter of at least one interface; secondly, receiving an interface checking request message in the network; then, extracting the interface name and the interface parameter to be checked in the interface checking request message; and finally, checking the interface parameter to be checked based on the parameter checking rule corresponding to the interface name, and returning a checking result. Therefore, all interface parameters to be verified in the interface verification message can be verified through the loaded parameter verification rule, the automation of interface parameter verification is improved, and the development cost of technicians in verifying the interface parameters to be verified is saved.
In this embodiment, the interface parameters to be checked include: in some optional implementation manners of this embodiment, as shown in fig. 2, the method for extracting the interface parameter to be verified in the interface verification request message includes the following steps:
In this optional implementation manner, after the execution main body receives the interface verification request message, the interceptor may extract the name of the interface parameter to be verified in the interface verification request message.
In this optional implementation manner, the parameter verification rule corresponding to the interface name includes a parameter verification rule corresponding to at least one interface parameter, and since the name of the interface parameter to be verified is already determined, the parameter verification rule corresponding to the name of the interface parameter to be verified can be determined from the parameter verification rule corresponding to the at least one interface parameter, and the name of the interface parameter to be verified is verified by using the parameter verification rule corresponding to the name of the interface parameter to be verified. The specific verification process for verifying the name of the interface parameter to be verified may be based on the type and length of the name of the interface parameter to be verified.
Of course, the location in the interface verification request message may also be verified based on the name of the interface parameter to be verified, in some optional implementation manners of this embodiment, the verifying the name of the interface parameter to be verified based on the parameter verification rule corresponding to the interface name includes: determining the position of the name of the interface parameter to be verified in the interface verification request message; determining a parameter verification rule corresponding to a parameter to be verified from the parameter verification rules corresponding to the interface names; and determining that the name of the interface parameter to be verified passes verification in response to the fact that the position of the name of the interface parameter to be verified in the interface verification request message is matched with the position of the name of the interface parameter to be verified recorded in the parameter verification rule corresponding to the parameter to be verified.
In this optional implementation manner, based on the interface verification request message of the HTTP transmission protocol, the attribute of the interception tool that extracts the encoded data may be used to obtain the parameters of the Query, the Header, and the Body in the interface verification request message, and the parameters are stored respectively, so as to determine the location of the name of the interface parameter to be verified in the interface verification request message. Further, a parameter verification rule corresponding to the parameter to be verified defines a location of the name of the parameter to be verified of the current interface, as shown in example two.
Example two: {
"paramName":"products.specification.price",
"apiName":"batchSubmitProduct",
"position":"Body",
"using":"true",
"type":"Float",
"required":true,
"maxDigital":5,
"minDigital":1
}
The parameter verification rule corresponding to the parameter to be verified shown in example two represents that:
verifying the interface name batchSubmitProduct, the position Body and the interface parameter name products to be verified, wherein the maximum decimal digit of the parameter value corresponding to the interface parameter name to be verified is 5, and the minimum decimal digit is 1.
In this optional implementation manner, whether the position of the name of the interface parameter to be verified in the interface verification request message matches the position of the name of the interface parameter to be verified recorded in the parameter verification rule corresponding to the parameter to be verified, so as to verify whether the name of the interface parameter to be verified is verified correctly, for some interface verification request messages based on a network transmission protocol, such as HTTP and RMI (Remote Method Invocation), because the position of each interface parameter is fixed, an effective result of the name of the interface parameter to be verified can be obtained, and the reliability of the verification result is ensured.
Step 203, in response to determining that the name of the interface parameter to be verified passes verification, extracting a parameter value.
In this optional implementation manner, the interceptor may be used to extract the parameter value corresponding to the name of the interface parameter to be verified in the interface verification request message.
In the optional implementation mode, firstly, the name of the interface parameter to be verified is extracted from the interface verification request message, and the name of the interface parameter to be verified is verified based on a parameter verification rule corresponding to the interface name; and finally, after the name of the interface parameter to be verified passes the verification, extracting the parameter value, and ensuring the reliability of the extraction of the interface parameter to be verified in the way of extracting, verifying and re-extracting.
In another optional implementation manner of this embodiment, the to-be-verified interface parameters include: the name of the interface parameter to be verified and the parameter value corresponding to the name of the interface parameter to be verified may also be extracted in sequence, and then the name of the interface parameter to be verified and the parameter value corresponding to the interface parameter to be verified in the interface verification request message may be respectively verified, in some optional implementation manners of this embodiment, as shown in fig. 3, the method for verifying the interface parameter to be verified includes the following steps:
In this optional implementation manner, the parameter verification rule corresponding to the interface name includes a parameter verification rule corresponding to at least one interface parameter, and since the name of the interface parameter to be verified is already determined, the parameter verification rule corresponding to the name of the interface parameter to be verified may be determined in the parameter verification rule corresponding to the at least one interface parameter, and the name of the interface parameter to be verified is verified by using the parameter verification rule corresponding to the name of the interface parameter to be verified. The specific verification process for verifying the name of the interface parameter to be verified may be based on the type and length of the name of the interface parameter to be verified.
In some optional implementation manners of this embodiment, the verifying the to-be-verified interface parameter name based on the parameter verification rule corresponding to the interface name includes: determining the position of the name of the interface parameter to be verified in the interface verification request message; determining a parameter verification rule corresponding to a parameter to be verified from the parameter verification rules corresponding to the interface names; and determining that the name of the interface parameter to be verified passes verification in response to the fact that the position of the name of the interface parameter to be verified in the interface verification request message is matched with the position of the name of the interface parameter to be verified recorded in the parameter verification rule corresponding to the parameter to be verified.
In this optional implementation manner, whether the position of the name of the interface parameter to be verified in the interface verification request message matches the position of the name of the interface parameter to be verified recorded in the parameter verification rule corresponding to the parameter to be verified, is determined, and for some network transmission protocols, such as HTTP and RMI-based interface verification request messages, because the position of each interface parameter is fixed, an effective result of the name of the interface parameter to be verified can be obtained, and the reliability of the verification result is ensured.
In this embodiment, the parameter verification rule corresponding to the interface name includes a parameter verification rule corresponding to a parameter to be verified, and the parameter verification rule corresponding to the parameter to be verified may include: and the data type of the parameter value corresponding to the name of the interface parameter to be checked, such as character string, integer, floating point, boolean, enumeration and list. The data type of the parameter value corresponding to the name of the interface parameter to be verified can be used for verifying the parameter value corresponding to the name of the interface parameter to be verified.
In some optional implementation manners of this embodiment, the parameter verification rule corresponding to the parameter to be verified may include: the preset data type and the syndrome rule for carrying out numerical verification on the parameter value, the verification on the parameter value comprises the following steps:
performing data type conversion on the parameter values according to a preset data type; responding to the fact that the data type of the converted parameter value is the same as the preset data type, and detecting whether the converted parameter value meets a syndrome rule or not; and determining that the parameter value passes the verification in response to the detection result that the converted parameter value meets the syndrome rule.
In this optional implementation manner, since the extracted parameter values are generally character strings and are not favorable for data type verification, data type conversion is performed on the parameter values according to the preset data types, which is favorable for data type verification on one hand, and on the other hand, whether the extracted parameter values are correctly transmitted in the interface verification request message can be confirmed.
In this optional implementation manner, the syndrome rule is used to check whether the specific value of the parameter value meets the requirement, and the maximum decimal place number and the minimum decimal place number in the regular expression in the first example and the second example all belong to the syndrome rule.
According to the method for verifying the parameter values, provided by the optional implementation mode, firstly, the extracted parameter values are subjected to data type conversion and are changed into the preset data types in the parameter verification rules, whether the converted parameter values meet the syndrome rules or not is verified in response to the converted parameter values being the same as the preset data types, and the reliability of verifying the parameter values is improved.
According to the method for verifying the interface parameter to be verified provided by the optional implementation mode, after the interface name, the name of the interface parameter to be verified and the parameter value corresponding to the name of the interface parameter to be verified are extracted, the interface name, the name of the interface parameter and the parameter value are sequentially verified, and the reliability of the verification of the interface parameter to be verified is improved.
In order to update the parameter verification rule, for all the above embodiments, the parameter verification rule may also be updated by reading a database, and referring to fig. 4, a flow 400 of another embodiment of the interface parameter verification method of the present application is shown, where the interface parameter verification method includes the following steps:
The parameter checking rule is used for checking the interface parameters of at least one interface.
In this embodiment, the preset parameter verification rule is a preset parameter verification rule, which may be placed in some applications or databases in advance, and the interface parameter verification method and the execution subject thereon may obtain the preset parameter verification rule by calling an interface or accessing a database. Of course, the preset parameter verification rule may also be the same parameter verification rule as the parameter verification rule in the embodiment shown in fig. 1.
And step 404, verifying the interface parameter to be verified based on the parameter verification rule corresponding to the interface name, and returning a verification result.
It should be understood that the operations and features in the steps 401 to 404 correspond to those in the steps 101 and 104, respectively, and therefore, the description of the operations and features in the steps 101 and 104 applies to the steps 401 to 404, which is not described herein again.
In this embodiment, the time for periodically reading the parameter calibration rule of the database may be set according to the requirement of the execution subject, and all the reading times covering the update time of the parameter calibration rule in the database are within the protection scope of this embodiment.
In this embodiment, when the parameter verification rule of the database is different from the preset parameter verification rule, it is indicated that the parameter verification rule of the database is the latest parameter verification rule, and the latest parameter verification rule is reloaded by returning to step 401, so that it can be ensured that the version of the rule according to which the parameter verification method is based is always the latest version.
The interface parameter verification method provided by this embodiment periodically reads the parameter verification rule in the database, and when the parameter verification rule in the database is different from the preset parameter verification rule, replaces the parameter verification rule in the database with the preset parameter verification rule, thereby achieving the periodic update of the parameter verification rule and ensuring the real-time performance of the interface parameter verification.
With further reference to fig. 5, as an implementation of the methods shown in the above-mentioned figures, the present application provides an embodiment of an interface parameter checking apparatus, where the embodiment of the apparatus corresponds to the embodiment of the method shown in fig. 1, and the apparatus is specifically applicable to various electronic devices.
As shown in fig. 5, the interface parameter verification apparatus 500 provided in this embodiment includes: the system comprises a loading unit 501, a receiving unit 502, an extracting unit 503 and a checking unit 504. The loading unit 501 may be configured to load a parameter verification rule, where the parameter verification rule is used to verify an interface parameter of at least one interface. The receiving unit 502 may be configured to receive an interface verification request message in a network. The extracting unit 503 may be configured to extract the interface name and the interface parameter to be verified in the interface verification request message. The checking unit 504 may be configured to check the interface parameter to be checked based on a parameter checking rule corresponding to the interface name, and return a checking result.
In this embodiment, in the interface parameter verification apparatus 500: the detailed processing of the loading unit 501, the receiving unit 502, the extracting unit 503, and the verifying unit 504 and the technical effects thereof can refer to the related descriptions of step 101, step 102, step 103, and step 104 in the corresponding embodiment of fig. 1, which are not described herein again.
In some optional implementation manners of this embodiment, the interface parameter to be verified includes: the name of the interface parameter to be verified and the parameter value corresponding to the name of the interface parameter to be verified, the extracting unit 503 includes: a parameter extraction module (not shown), a parameter verification module (not shown), and a value extraction module (not shown). The parameter extraction module may be configured to extract a name of an interface parameter to be verified from the interface verification request message. The parameter verification module may be configured to verify the name of the interface parameter to be verified based on a parameter verification rule corresponding to the name of the interface. The value extraction module may be configured to extract the parameter value in response to determining that the name of the interface parameter to be verified passes verification.
In some optional implementation manners of this embodiment, the interface parameter to be verified includes: the name of the interface parameter to be verified and the parameter value corresponding to the name of the interface parameter to be verified; the verification unit 504 includes: a parameter check module (not shown), a value check module (not shown). The parameter verification module may be configured to verify the name of the interface parameter to be verified based on a parameter verification rule corresponding to the interface name. The value checking module may be configured to check the parameter value in response to determining that the name of the interface parameter to be checked passes the check.
In some optional implementation manners of this embodiment, the parameter checking module includes: a location sub-module (not shown), a determination sub-module (not shown), and a verification sub-module (not shown). And the positioning submodule determines the position of the name of the interface parameter to be verified in the interface verification request message. The determining submodule may be configured to determine a parameter verification rule corresponding to a parameter to be verified from the parameter verification rules corresponding to the interface names. The verification sub-module may be configured to determine that the name of the interface parameter to be verified passes verification in response to that the position of the name of the interface parameter to be verified in the interface verification request message matches the position of the name of the interface parameter to be verified recorded in the parameter verification rule corresponding to the parameter to be verified.
In some optional implementation manners of this embodiment, the parameter verification rule corresponding to the parameter to be verified includes: the preset data type and the syndrome rule used for carrying out numerical value verification on the parameter value, the value verification module comprises: a conversion submodule (not shown), a detection submodule (not shown), and a verification submodule (not shown). The conversion submodule may be configured to perform data type conversion on the parameter value according to a preset data type. The detection sub-module may be configured to detect whether the converted parameter value satisfies the syndrome rule in response to that the data type of the converted parameter value is the same as a preset data type. The check submodule may be configured to determine that the parameter value passes the check in response to the detection result being that the converted parameter value satisfies the check submodule rule.
In some optional implementations of this embodiment, the apparatus 500 further includes: a read unit (not shown), a replacement unit (not shown). The reading unit may be configured to periodically read a parameter verification rule of the database. The above replacement unit may be configured to replace the parameter verification rule with the parameter verification rule of the database in response to determining that the parameter verification rule of the database is different from the parameter verification rule.
In the interface parameter verification apparatus provided in the embodiment of the present application, first, a loading unit 501 loads a parameter verification rule for verifying an interface parameter of at least one interface; secondly, the receiving unit 502 receives an interface check request message in the network; then, the extracting unit 503 extracts the interface name and the interface parameter to be verified in the interface verification request message; finally, the checking unit 504 checks the interface parameter to be checked based on the parameter checking rule corresponding to the interface name, and returns the checking result. Therefore, all interface parameters to be verified in the interface verification message can be verified through the loaded parameter verification rule, the automation of interface parameter verification is improved, and the development cost of technicians in verifying the interface parameters to be verified is saved.
According to an embodiment of the present application, an electronic device and a readable storage medium are also provided.
Fig. 6 is a block diagram of an electronic device according to an embodiment of the present application. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the present application that are described and/or claimed herein.
As shown in fig. 6, the electronic apparatus includes: one or more processors 601, memory 602, and interfaces for connecting the various components, including a high-speed interface and a low-speed interface. The various components are interconnected using different buses and may be mounted on a common motherboard or in other manners as desired. The processor may process instructions for execution within the electronic device, including instructions stored in or on the memory to display graphical information of a GUI on an external input/output apparatus (such as a display device coupled to the interface). In other embodiments, multiple processors and/or multiple buses may be used, along with multiple memories and multiple memories, as desired. Also, multiple electronic devices may be connected, with each device providing portions of the necessary operations (e.g., as a server array, a group of blade servers, or a multi-processor system). In fig. 6, one processor 601 is taken as an example.
The memory 602 is a non-transitory computer readable storage medium as provided herein. The memory stores instructions executable by the at least one processor, so that the at least one processor executes the interface parameter verification method provided by the application. The non-transitory computer-readable storage medium of the present application stores computer instructions for causing a computer to perform the interface parameter verification method provided herein.
The memory 602 is a non-transitory computer readable storage medium, and can be used to store non-transitory software programs, non-transitory computer executable programs, and modules, such as program instructions/modules (e.g., the loading unit 501, the receiving unit 502, the extracting unit 503, and the verifying unit 504 shown in fig. 5) corresponding to the interface parameter verifying method in the embodiment of the present application. The processor 601 executes various functional applications and data processing of the server by running non-transitory software programs, instructions and modules stored in the memory 602, that is, implementing the interface parameter checking method in the above method embodiment.
The memory 602 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the electronic device of the interface parameter verification method, and the like. Further, the memory 602 may include high speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory 602 optionally includes memory located remotely from the processor 601, and these remote memories may be connected over a network to the electronics of the interface parameter verification method. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The electronic device of the interface parameter checking method may further include: an input device 603 and an output device 604. The processor 601, the memory 602, the input device 603, and the output device 604 may be connected by a bus 605 or other means, and are exemplified by the bus 605 in fig. 6.
The input device 603 may receive input numeric or character information and generate key signal inputs related to user settings and function control of the electronic device of the interface parameter verification method, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, a pointing stick, one or more mouse buttons, a track ball, a joystick, or other input devices. The output devices 604 may include a display device, auxiliary lighting devices (e.g., LEDs), and tactile feedback devices (e.g., vibrating motors), among others. The display device may include, but is not limited to, a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display, and a plasma display. In some implementations, the display device can be a touch screen.
Various implementations of the systems and techniques described here can be realized in digital electronic circuitry, integrated circuitry, application specific ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
These computer programs (also known as programs, software applications, or code) include machine instructions for a programmable processor, and may be implemented using high-level procedural and/or object-oriented programming languages, and/or assembly/machine languages. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and/or device (e.g., magnetic discs, optical disks, memory, Programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal used to provide machine instructions and/or data to a programmable processor.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.
The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The Server may be a cloud Server, which is also called a cloud computing Server or a cloud host, and is a host product in a cloud computing service system, so as to solve the defects of high management difficulty and weak service expansibility in the conventional physical host and Virtual Private Server (VPS) service.
It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present application may be executed in parallel, sequentially, or in different orders, and the present invention is not limited thereto as long as the desired results of the technical solutions disclosed in the present application can be achieved.
The above-described embodiments should not be construed as limiting the scope of the present application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (14)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011279136.2A CN112269706B (en) | 2020-11-16 | 2020-11-16 | Interface parameter verification method, device, electronic device and computer readable medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011279136.2A CN112269706B (en) | 2020-11-16 | 2020-11-16 | Interface parameter verification method, device, electronic device and computer readable medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112269706A true CN112269706A (en) | 2021-01-26 |
| CN112269706B CN112269706B (en) | 2024-04-05 |
Family
ID=74340677
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011279136.2A Active CN112269706B (en) | 2020-11-16 | 2020-11-16 | Interface parameter verification method, device, electronic device and computer readable medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112269706B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113377361A (en) * | 2021-06-28 | 2021-09-10 | 浙江孚临科技有限公司 | Method for realizing timing verification of data source based on linux crontad and jar packets |
| CN113535776A (en) * | 2021-05-28 | 2021-10-22 | 国网辽宁省电力有限公司 | Parameter validity checking method and system applied to monitoring device |
| CN114666258A (en) * | 2022-03-22 | 2022-06-24 | 阿波罗智联(北京)科技有限公司 | Interface test method, device, electronic equipment and medium |
| CN119324792A (en) * | 2024-08-26 | 2025-01-17 | 中移互联网有限公司 | Interface request processing method and device |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080256612A1 (en) * | 2007-04-13 | 2008-10-16 | Cognos Incorporated | Method and system for stateless validation |
| WO2018006789A1 (en) * | 2016-07-04 | 2018-01-11 | 中兴通讯股份有限公司 | Parameter checking method and apparatus, and network management server and computer storage medium |
| CN108132880A (en) * | 2017-12-21 | 2018-06-08 | 武汉斑马快跑科技有限公司 | A kind of parameter verification method and device |
| CN109101812A (en) * | 2018-08-28 | 2018-12-28 | 北京神州绿盟信息安全科技股份有限公司 | A kind of parameter verification method, apparatus, computing device and storage medium |
| CN109344642A (en) * | 2018-08-31 | 2019-02-15 | 平安科技（深圳）有限公司 | Interface rules method of calibration, device, computer equipment and storage medium |
| CN109408381A (en) * | 2018-10-10 | 2019-03-01 | 四川新网银行股份有限公司 | A kind of product data automatic Verification platform and method based on data check template |
| CN109597816A (en) * | 2018-10-30 | 2019-04-09 | 京信通信系统（中国）有限公司 | Parameter verification method, apparatus, computer storage medium and embedded device |
| CN109871294A (en) * | 2019-01-31 | 2019-06-11 | 北京百度网讯科技有限公司 | Method and apparatus for verifying data, processing requests |
| CN110389765A (en) * | 2019-07-24 | 2019-10-29 | 深圳市盟天科技有限公司 | Parameter verification method and parameter verification system |
| CN110390069A (en) * | 2019-07-31 | 2019-10-29 | 中国工商银行股份有限公司 | The method, apparatus of data check calculates equipment and medium |
| WO2020124286A1 (en) * | 2018-12-16 | 2020-06-25 | 吉安市井冈山开发区金庐陵经济发展有限公司 | Authentication method |
| CN111679975A (en) * | 2020-05-28 | 2020-09-18 | 平安普惠企业管理有限公司 | Document generating method, device, electronic device and medium |
| CN111782517A (en) * | 2020-06-23 | 2020-10-16 | 浙江保融科技有限公司 | Automatic file checking method |
-
2020
- 2020-11-16 CN CN202011279136.2A patent/CN112269706B/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080256612A1 (en) * | 2007-04-13 | 2008-10-16 | Cognos Incorporated | Method and system for stateless validation |
| WO2018006789A1 (en) * | 2016-07-04 | 2018-01-11 | 中兴通讯股份有限公司 | Parameter checking method and apparatus, and network management server and computer storage medium |
| CN108132880A (en) * | 2017-12-21 | 2018-06-08 | 武汉斑马快跑科技有限公司 | A kind of parameter verification method and device |
| CN109101812A (en) * | 2018-08-28 | 2018-12-28 | 北京神州绿盟信息安全科技股份有限公司 | A kind of parameter verification method, apparatus, computing device and storage medium |
| CN109344642A (en) * | 2018-08-31 | 2019-02-15 | 平安科技（深圳）有限公司 | Interface rules method of calibration, device, computer equipment and storage medium |
| CN109408381A (en) * | 2018-10-10 | 2019-03-01 | 四川新网银行股份有限公司 | A kind of product data automatic Verification platform and method based on data check template |
| CN109597816A (en) * | 2018-10-30 | 2019-04-09 | 京信通信系统（中国）有限公司 | Parameter verification method, apparatus, computer storage medium and embedded device |
| WO2020124286A1 (en) * | 2018-12-16 | 2020-06-25 | 吉安市井冈山开发区金庐陵经济发展有限公司 | Authentication method |
| CN109871294A (en) * | 2019-01-31 | 2019-06-11 | 北京百度网讯科技有限公司 | Method and apparatus for verifying data, processing requests |
| CN110389765A (en) * | 2019-07-24 | 2019-10-29 | 深圳市盟天科技有限公司 | Parameter verification method and parameter verification system |
| CN110390069A (en) * | 2019-07-31 | 2019-10-29 | 中国工商银行股份有限公司 | The method, apparatus of data check calculates equipment and medium |
| CN111679975A (en) * | 2020-05-28 | 2020-09-18 | 平安普惠企业管理有限公司 | Document generating method, device, electronic device and medium |
| CN111782517A (en) * | 2020-06-23 | 2020-10-16 | 浙江保融科技有限公司 | Automatic file checking method |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113535776A (en) * | 2021-05-28 | 2021-10-22 | 国网辽宁省电力有限公司 | Parameter validity checking method and system applied to monitoring device |
| CN113377361A (en) * | 2021-06-28 | 2021-09-10 | 浙江孚临科技有限公司 | Method for realizing timing verification of data source based on linux crontad and jar packets |
| CN114666258A (en) * | 2022-03-22 | 2022-06-24 | 阿波罗智联(北京)科技有限公司 | Interface test method, device, electronic equipment and medium |
| CN114666258B (en) * | 2022-03-22 | 2023-11-07 | 阿波罗智联(北京)科技有限公司 | Interface testing method, device, electronic equipment and medium |
| CN119324792A (en) * | 2024-08-26 | 2025-01-17 | 中移互联网有限公司 | Interface request processing method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112269706B (en) | 2024-04-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110765024B (en) | Simulation test method, simulation test device, electronic equipment and computer readable storage medium | |
| CN112182037B (en) | Data verification method, device, equipment and storage medium | |
| CN112269706A (en) | Interface parameter verification method, apparatus, electronic device, and computer-readable medium | |
| CN111258609A (en) | Upgrading method and device of Kubernetes cluster, electronic equipment and medium | |
| CN111666206A (en) | Method, device, equipment and storage medium for acquiring influence range of change code | |
| CN111639027B (en) | Test method and device and electronic equipment | |
| CN111752843A (en) | Method, device, electronic equipment and readable storage medium for determining influence surface | |
| CN111698326B (en) | Method and device for determining cost attribution of cloud service resources | |
| CN111475164B (en) | Component dependency detection method, device and electronic device | |
| CN112015468A (en) | Interface document processing method and device, electronic equipment and storage medium | |
| CN111813623A (en) | A page monitoring method, device, electronic device and storage medium | |
| CN112732312B (en) | Method and device for updating application program, electronic device and medium | |
| CN115222176A (en) | Risk control methods, devices, equipment and media | |
| CN111241396B (en) | Information pushing method and device, electronic equipment and storage medium | |
| CN116009847A (en) | Code generation method, device, electronic equipment and storage medium | |
| US11662927B2 (en) | Redirecting access requests between access engines of respective disk management devices | |
| CN114978964A (en) | Communication announcement configuration method, device, equipment and medium based on network self-checking | |
| CN112822302B (en) | Data normalization method and device, electronic equipment and storage medium | |
| CN110909390B (en) | Task auditing method and device, electronic equipment and storage medium | |
| CN111159010A (en) | Defect collecting method, defect reporting method and related device | |
| CN112084000A (en) | Container cluster testing method and device | |
| CN119031053A (en) | Parameter verification rule generation method and device | |
| CN114661274A (en) | Method and device for generating intelligent contract | |
| CN112052347A (en) | Image storage method and device and electronic equipment | |
| CN113961229A (en) | Method for generating application program installation package and method for running application program |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |