CN112685098B - Method for verifying data of front-end receiving server - Google Patents
Method for verifying data of front-end receiving server Download PDFInfo
- Publication number
- CN112685098B CN112685098B CN202011618045.7A CN202011618045A CN112685098B CN 112685098 B CN112685098 B CN 112685098B CN 202011618045 A CN202011618045 A CN 202011618045A CN 112685098 B CN112685098 B CN 112685098B
- Authority
- CN
- China
- Prior art keywords
- data
- model data
- real
- real data
- server
- 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.)
- Active
Links
Images
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a method for verifying data of a front-end receiving server end, which comprises the following steps: configuring an interface document and a request interface address between a front end and a server end; configuring model data according to the interface document; when real data returned by the server end in response to the data request of the front end is monitored, the real data and corresponding model data are verified; and when the real data and the corresponding model data do not match, correcting the real data and recording an error log. The embodiment of the invention uses non-descriptive model data, and the data structure is concise. And error logs can be checked and recorded, type fault tolerance is realized through correction, the existence of error types is not considered any more, and the code is simpler and easy to maintain.
Description
Technical Field
The present invention relates to the field of front-end data processing technologies, and in particular, to a method for verifying data received by a front-end server, an electronic device, and a computer-readable storage medium.
Background
The front-end and back-end development are separated and then typically contract the interface document. Although interface documentation is agreed, in rigorous development, neither the data sent by the front-end to the back-end nor the data sent by the back-end to the front-end is trustworthy. Therefore, the data structure and type need to be checked to ensure the logic correctness of the subsequent service.
With the frequent front-end and back-end communication, the checking is more and more, and very similar judgment logic is written, so that the code amount is increased, and the code is more obscure and difficult to maintain.
The data type of the front-end and back-end communication is typically json, and the prior art uses either the djv library or the ajv library to verify that the model data defined in the json-schema implementation library meets expectations. However, the model data includes necessary (bolt, string, number, array, object) types in json data, and also includes some attributes such as description information ($ id: unique identifier of current data; title: data description; default: default data value), and the attributes form a tree-shaped model data structure, so that the model data volume defined in the json-schema realization library is large, and the data structure is complex.
And comparing the model data with the real data during verification to obtain whether the model data is matched with the real data, wherein the matching returns true, and the mismatching returns false. Therefore, only a global check result can be returned, data after type fault tolerance cannot be returned, and fault tolerance also needs to be processed in each service.
Disclosure of Invention
Embodiments of the present invention provide a method for verifying data received by a front end from a server, an electronic device, and a computer-readable storage medium, which are used to solve at least one of the above technical problems.
In a first aspect, an embodiment of the present invention provides a method for verifying that a front end receives server-side data, including:
configuring an interface document and a request interface address between a front end and a server end;
configuring model data according to the interface document;
when real data returned by the server end in response to the data request of the front end is monitored, the real data and corresponding model data are verified;
and when the real data and the corresponding model data do not match, correcting the real data and recording an error log.
In a second aspect, an embodiment of the present invention provides a storage medium, where one or more programs including execution instructions are stored, where the execution instructions can be read and executed by an electronic device (including but not limited to a computer, a server, or a network device, etc.) to perform any of the above methods for verifying that the front end receives server-side data according to the present invention.
In a third aspect, an electronic device is provided, comprising: at least one processor, and a memory communicatively coupled to the at least one processor, wherein the memory stores instructions executable by the at least one processor, and the instructions are executable by the at least one processor to enable the at least one processor to perform any of the above-described front end receiving server-side data verification methods of the present invention.
In a fourth aspect, an embodiment of the present invention further provides a computer program product, where the computer program product includes a computer program stored on a storage medium, where the computer program includes program instructions, and when the program instructions are executed by a computer, the computer is caused to execute any one of the foregoing methods for verifying front-end received server-side data.
The embodiment of the invention has the beneficial effects that: the embodiment of the invention uses non-descriptive model data, and the data structure is concise. And error logs can be checked and recorded, type fault tolerance is realized through correction, the existence of error types is not considered any more, and the code is simpler and easy to maintain.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 is a flowchart of an embodiment of a method for verifying that server-side data is received by a front-end according to the present invention;
FIG. 2 is a flowchart illustrating another embodiment of a method for verifying receipt of server-side data by a front-end according to the present invention;
FIG. 3 is a flowchart illustrating a method for verifying receipt of server-side data by a front-end according to another embodiment of the present invention;
FIG. 4 is a flowchart illustrating a method for verifying receipt of server-side data by a front-end according to another embodiment of the present invention;
fig. 5 is a schematic structural diagram of an embodiment of an electronic device of the invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.
The invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
As used in this disclosure, "module," "device," "system," and the like are intended to refer to a computer-related entity, either hardware, a combination of hardware and software, or software in execution. In particular, for example, an element may be, but is not limited to being, a process running on a processor, an object, an executable, a thread of execution, a program, and/or a computer. Also, an application or script running on a server, or a server, may be an element. One or more elements may be in a process and/or thread of execution and an element may be localized on one computer and/or distributed between two or more computers and may be operated by various computer-readable media. The elements may also communicate by way of local and/or remote processes based on a signal having one or more data packets, e.g., from a data packet interacting with another element in a local system, distributed system, and/or across a network in the internet with other systems by way of the signal.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
As shown in fig. 1, an embodiment of the present invention provides a method for verifying data received by a front end from a server, including:
s10, configuring interface document and request interface address between front end and server end.
And S20, configuring model data according to the interface document.
Illustratively, non-descriptive model data is configured from the interface document.
Illustratively, the encapsulated XMLHTTPRequest object mounts the interface document and non-descriptive model data.
And S30, when the real data returned by the server end responding to the data request of the front end is monitored, verifying the real data and the corresponding model data.
And S40, when the real data and the corresponding model data do not match, correcting the real data and recording an error log.
The embodiment of the invention uses non-descriptive model data, and the data structure is concise. And error logs can be checked and recorded, type fault tolerance is realized through correction, the existence of error types is not considered any more, and the code is simpler and easy to maintain.
In some embodiments, the non-descriptive model data is configured to be identical in structure to the real data. The embodiment of the invention uses non-descriptive model data, and the data structure is concise. And the data structure of the non-descriptive model data is configured to be the same as the structure of the real data, so that only data type verification is needed when the real data and the model data are verified, the verification of the data structure is not needed, and the code amount and various expenses required by code running are greatly reduced.
In some embodiments, the corresponding model data is the model data corresponding to the request interface address for monitoring the real data.
In some embodiments, the method for verifying that the front-end receives the server-end data further includes: after configuring model data according to the interface document, establishing a mapping relation table between the model data and the request interface address, wherein the request interface address corresponds to the model data. In the embodiment, the model data and the request interface address are bound in a configuration mode, so that later maintenance is simpler.
Fig. 2 is a flowchart illustrating another embodiment of a method for verifying that data is received by a front end at a server side according to the present invention. In this embodiment, when the real data returned by the server in response to the data request of the front end is monitored, the verifying the real data and the corresponding model data includes:
s31, when monitoring the real data returned by the server end responding to the data request of the front end, acquiring the current request interface address;
s32, inquiring the mapping relation table to determine that the model data corresponding to the current request interface address is corresponding model data;
and S33, verifying the real data and the corresponding model data.
In this embodiment, a situation that a plurality of request interface addresses for performing communication between the front end and the server end exist is considered, so when real data returned by the server end is monitored, the current request interface address is determined first, and then model data corresponding to the current request interface address is queried according to a mapping relation table between the request interface address and the model data established before, so as to verify the real data. Mutual crosstalk of data between different request interface addresses is avoided.
Fig. 3 is a flowchart illustrating another embodiment of a method for verifying that data is received by a front end at a server side according to the present invention. In this embodiment, verifying the real data and the corresponding model data includes:
s331, checking whether the data types of the real data and the corresponding model data are consistent;
s332, if the actual data and the corresponding model data are consistent, determining that the actual data and the corresponding model data are matched with each other;
s333, if the actual data and the corresponding model data are not consistent, determining that the actual data and the corresponding model data are not matched.
In the embodiment, only data type verification is needed when the real data and the model data are verified, and verification of a data structure is not needed, so that the code amount and various expenses required by code running are greatly reduced.
Fig. 4 is a flowchart illustrating another embodiment of a method for verifying that data is received by a front end at a server side according to the present invention. In this embodiment the following steps are included:
step 1: the front end and the back end appoint an interface document and a requested interface address;
step 2: defining model data according to the interface document, and corresponding the model data to the interface address;
and 3, step 3: when the monitored request data is returned, analyzing the bound model data according to the real data and the current interface;
and 4, step 4: judging whether model data corresponding to the mapping interface exists or not, if not, returning the data, and if so, executing the step 5;
and 5: circularly checking the model data and the real data;
step 6: and detecting whether the types are matched, correcting the current type according to the type of the model data in a mismatching manner, recording an error log, and matching the returned data.
The embodiment of the invention is not realized according to a json-schema draft, but encapsulates an XHR (XMLHttpRequest) module and mounts non-descriptive model data, so that the model data is more concise. And by binding the model data and the request interface, performing recursive check on the real data and the model data, recording error type logs, and correcting error types to obtain the processed expected data. The development does not consider the existence of error types any more, so that the code is simpler and is easy to maintain.
After the interface document is defined, the model data is defined according to the interface document, so that the model data is more concise.
For example:
take the following json data as an example
The prior art requires the generation of model data as follows
Obviously, the data size of the descriptive model data is relatively large, so the scheme uses the non-descriptive model data as follows:
the invention binds the model data and the request interface in a configuration mode, so that the later maintenance is simpler.
The model data and the real data are consistent in structure, and the cyclic verification is simpler; and when the type is wrong, the error type is corrected, so that the type error does not need to be considered in subsequent development, redundant judgment does not need to be added, the error rate is reduced, and the maintenance is easier. The user experience is not influenced, and an error log is recorded; meanwhile, the problem can be reported to the server side to be discovered as early as possible.
It should be noted that for simplicity of explanation, the foregoing method embodiments are described as a series of acts or combination of acts, but those skilled in the art will appreciate that the present invention is not limited by the order of acts, as some steps may occur in other orders or concurrently in accordance with the invention. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required by the invention. In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to the related descriptions of other embodiments.
In some embodiments, the present invention provides a non-transitory computer-readable storage medium, in which one or more programs including executable instructions are stored, where the executable instructions can be read and executed by an electronic device (including but not limited to a computer, a server, or a network device, etc.) to perform any one of the above methods for verifying that data at a server is received by a front end of the present invention.
In some embodiments, the present invention further provides a computer program product, which includes a computer program stored on a non-volatile computer-readable storage medium, where the computer program includes program instructions, and when the program instructions are executed by a computer, the computer executes any of the above methods for verifying that the front-end receives server-side data.
In some embodiments, an embodiment of the present invention further provides an electronic device, which includes: at least one processor, and a memory communicatively coupled to the at least one processor, wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform a method for verifying receipt of server-side data by a front end.
In some embodiments, the present invention further provides a storage medium having a computer program stored thereon, where the computer program is used to implement a method for verifying that data at a front end receives server end data when the computer program is executed by a processor.
Fig. 5 is a schematic hardware structure diagram of an electronic device for performing a method for verifying that data at a server end is received at a front end according to another embodiment of the present application, and as shown in fig. 5, the electronic device includes:
one or more processors 510 and memory 520, with one processor 510 being an example in fig. 5.
The apparatus for performing the method for verifying that the front end receives the server-side data may further include: an input device 530 and an output device 540.
The processor 510, the memory 520, the input device 530, and the output device 540 may be connected by a bus or other means, and the bus connection is exemplified in fig. 5.
The memory 520 is a non-volatile computer-readable storage medium, and can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules, such as program instructions/modules corresponding to the verification method for receiving server-side data at the front end in the embodiment of the present application. The processor 510 executes various functional applications of the server and data processing by executing the nonvolatile software programs, instructions and modules stored in the memory 520, namely, implements the verification method for receiving the server-side data in the front end of the above method embodiment.
The memory 520 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 from use of a verification device that receives server-side data at the front end, and the like. Further, the memory 520 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some embodiments, memory 520 optionally includes memory located remotely from processor 510, which may be connected via a network to a verification device that the front end receives server-side data. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The input device 530 may receive input numeric or character information and generate signals related to user settings and function control of the verification device that the front end receives server-side data. The output device 540 may include a display device such as a display screen.
The one or more modules are stored in the memory 520 and when executed by the one or more processors 510 perform a method of verifying that the front end receives server-side data in any of the above-described method embodiments.
The product can execute the method provided by the embodiment of the application, and has the corresponding functional modules and beneficial effects of the execution method. For technical details that are not described in detail in this embodiment, reference may be made to the methods provided in the embodiments of the present application.
The electronic device of the embodiments of the present application exists in various forms, including but not limited to:
(1) mobile communication devices, which are characterized by mobile communication capabilities and are primarily targeted at providing voice and data communications. Such terminals include smart phones (e.g., iphones), multimedia phones, functional phones, and low-end phones, among others.
(2) The ultra-mobile personal computer equipment belongs to the category of personal computers, has calculation and processing functions and generally has the characteristic of mobile internet access. Such terminals include PDA, MID, and UMPC devices, such as ipads.
(3) Portable entertainment devices such devices may display and play multimedia content. Such devices include audio and video players (e.g., ipods), handheld game consoles, electronic books, as well as smart toys and portable car navigation devices.
(4) And other electronic devices with data interaction functions.
The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.
Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a general hardware platform, and certainly can also be implemented by hardware. Based on such understanding, the above technical solutions substantially or contributing to the related art may be embodied in the form of a software product, which may be stored in a computer-readable storage medium, such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method according to the embodiments or some parts of the embodiments.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.
Claims (9)
1. A method for verifying data of a front-end receiving server side comprises the following steps:
configuring an interface document and a request interface address between a front end and a server end;
configuring model data according to the interface document;
when real data returned by the server end in response to the data request of the front end is monitored, the real data and corresponding model data are verified;
correcting the real data and recording an error log when the real data and the corresponding model data do not match,
wherein configuring model data according to the interface document comprises: and configuring non-descriptive model data according to the interface document, wherein the data structure of the non-descriptive model data is configured to be the same as that of the real data, so that only data type verification is needed when the real data and the model data are verified, and verification of the data structure is not needed.
2. The method of claim 1, wherein configuring non-descriptive model data from the interface document comprises: and mounting the interface document and the non-descriptive model data by the encapsulated XMLHTTPRequest object.
3. The method of claim 2, wherein the non-descriptive model data is configured to be structurally identical to the real data.
4. The method according to any one of claims 1 to 3, wherein the corresponding model data is the model data corresponding to the request interface address for listening to the real data.
5. The method of claim 4, further comprising: after configuring model data according to the interface document, establishing a mapping relation table between the model data and the request interface address, wherein the request interface address corresponds to the model data.
6. The method of claim 5, wherein when monitoring real data returned by the server in response to the data request of the front end, checking the real data and the corresponding model data comprises:
when real data returned by the server end responding to the data request of the front end is monitored, acquiring a current request interface address;
inquiring the mapping relation table to determine that the model data corresponding to the current request interface address is corresponding model data;
and verifying the real data and the corresponding model data.
7. The method of claim 6, wherein verifying the real data and the corresponding model data comprises:
checking whether the data types of the real data and the corresponding model data are consistent;
if the real data and the corresponding model data are consistent, determining that the real data and the corresponding model data are matched with each other;
if not, determining that the real data and the corresponding model data do not match.
8. An electronic device, comprising: at least one processor, and a memory communicatively coupled to the at least one processor, wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the steps of the method of any one of claims 1-7.
9. A storage medium having a computer program stored thereon, the computer program, when being executed by a processor, performing the steps of the method as set forth in any one of the claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011618045.7A CN112685098B (en) | 2020-12-31 | 2020-12-31 | Method for verifying data of front-end receiving server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011618045.7A CN112685098B (en) | 2020-12-31 | 2020-12-31 | Method for verifying data of front-end receiving server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112685098A CN112685098A (en) | 2021-04-20 |
| CN112685098B true CN112685098B (en) | 2022-07-08 |
Family
ID=75453633
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011618045.7A Active CN112685098B (en) | 2020-12-31 | 2020-12-31 | Method for verifying data of front-end receiving server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112685098B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150242262A1 (en) * | 2014-02-26 | 2015-08-27 | Microsoft Corporation | Service metric analysis from structured logging schema of usage data |
| CN109656781A (en) * | 2018-12-20 | 2019-04-19 | 北京量子保科技有限公司 | A kind of blog management method, system, medium and electronic equipment |
| CN109710535A (en) * | 2018-12-29 | 2019-05-03 | 苏州思必驰信息科技有限公司 | Service method of calibration and system for voice dialogue platform |
-
2020
- 2020-12-31 CN CN202011618045.7A patent/CN112685098B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150242262A1 (en) * | 2014-02-26 | 2015-08-27 | Microsoft Corporation | Service metric analysis from structured logging schema of usage data |
| CN109656781A (en) * | 2018-12-20 | 2019-04-19 | 北京量子保科技有限公司 | A kind of blog management method, system, medium and electronic equipment |
| CN109710535A (en) * | 2018-12-29 | 2019-05-03 | 苏州思必驰信息科技有限公司 | Service method of calibration and system for voice dialogue platform |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112685098A (en) | 2021-04-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108984389B (en) | Application program testing method and terminal equipment | |
| CN105099811A (en) | Interface testing method and device | |
| CN112714158B (en) | Transaction processing method, relay network, cross-link gateway, system, medium and equipment | |
| CN107102908B (en) | Data verification method, data fault tolerance method and device | |
| CN110995703B (en) | Service processing request processing method and device, and electronic device | |
| CN112732499A (en) | Test method and device based on micro-service architecture and computer system | |
| CN117278434A (en) | Flow playback method and device and electronic equipment | |
| CN116204438A (en) | Test case generation method, automatic test method and related device | |
| CN103067372A (en) | Method and login system with which cloud terminal logins cloud server | |
| CN113608692A (en) | Method, system, equipment and medium for verifying data consistency of storage system | |
| CN112671574B (en) | Front-end and back-end joint debugging method and device, proxy equipment and storage medium | |
| CN104598374A (en) | Failure script correcting method and equipment | |
| CN116743619B (en) | Network service testing method, device, equipment and storage medium | |
| CN115730935A (en) | Data processing method, device and equipment based on block chain and readable storage medium | |
| CN112685098B (en) | Method for verifying data of front-end receiving server | |
| CN104536884A (en) | Code testing method and device | |
| CN117076330A (en) | Access verification method, system, electronic equipment and readable storage medium | |
| CN109740306B (en) | Method and device for authorizing application software based on mixed scheme | |
| CN109005469B (en) | Message format conversion method and device, storage medium and android terminal | |
| US10212036B2 (en) | Performance testing method, performance testing apparatus performing the same and storage medium storing the same | |
| CN110362294A (en) | Development task executes method, apparatus, electronic equipment and storage medium | |
| CN103188117B (en) | Information interaction server simulation testing device and method | |
| CN114466000A (en) | CDN gateway source returning method and device | |
| CN110597517A (en) | Method and device for dynamically analyzing mat file | |
| CN112711434A (en) | Resource package processing method and device, terminal equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 215123 building 14, Tengfei Innovation Park, 388 Xinping street, Suzhou Industrial Park, Suzhou City, Jiangsu Province Applicant after: Sipic Technology Co.,Ltd. Address before: 215123 building 14, Tengfei Innovation Park, 388 Xinping street, Suzhou Industrial Park, Suzhou City, Jiangsu Province Applicant before: AI SPEECH Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |