CN114978937B

CN114978937B - Page data verification method and device

Info

Publication number: CN114978937B
Application number: CN202110221072.9A
Authority: CN
Inventors: 胡皓
Original assignee: Tencent Technology Beijing Co Ltd
Current assignee: Tencent Technology Beijing Co Ltd
Priority date: 2021-02-26
Filing date: 2021-02-26
Publication date: 2023-09-01
Anticipated expiration: 2041-02-26
Also published as: CN114978937A

Abstract

The application provides a page data verification method and device; to artificial intelligence techniques, the method comprising: receiving a connection request sent by a first terminal when a page to be tested is displayed, and establishing connection with the first terminal based on a connection identifier of the first terminal; receiving page data of the page to be tested, which is sent by the first terminal, through connection with the first terminal; the connection identifier and the page data are sent to a second terminal, so that the second terminal displays the page data associated with the connection identifier in a data verification page; and sending the verification rule to the second terminal so that the second terminal displays a verification result of the page data based on the verification rule in the data verification page. The application can improve the page test efficiency.

Description

Page data verification method and device

Technical Field

The present application relates to page data processing technologies, and in particular, to a method and apparatus for checking page data.

Background

With the development of business, the demand for data governance is increasing. Through data management, the data performance of the service can be quickly obtained, the service strategy can be timely changed, and the user conversion rate can be improved. As a first loop in a data governance link, data acquisition is an important component. In the prior art, after a test page is accessed to a report acquisition software development suite, development, test and data product personnel often need to check data after waiting for the data to land so as to verify the correctness of the data, but because a data chain is longer, the report acquisition page data is not visual enough, the report acquisition page data cannot be checked in real time, and the requirements of accuracy, rapidness and no influence on service report and page data check cannot be met.

Accordingly, there is a lack of an effective scheme for rapidly testing page data in the related art.

Disclosure of Invention

The embodiment of the application provides a page data verification method, a device, electronic equipment and a computer readable storage medium, which can improve page test efficiency.

The technical scheme of the embodiment of the application is realized as follows:

the embodiment of the application provides a page data verification method, which is applied to a server and comprises the following steps:

receiving a connection request sent by a first terminal when a page to be tested is displayed, and establishing connection with the first terminal based on a connection identifier of the first terminal; receiving page data of the page to be tested, which is sent by the first terminal, through connection with the first terminal; the connection identifier and the page data are sent to a second terminal, so that the second terminal displays the page data associated with the connection identifier in a data verification page; and sending the verification rule to the second terminal so that the second terminal displays a verification result of the page data based on the verification rule in the data verification page.

The embodiment of the application provides a page data verification device, which is arranged on a server and comprises:

The connection module is used for receiving a connection request sent by a first terminal when a page to be tested is displayed, and establishing connection with the first terminal based on a connection identifier of the first terminal; the receiving module is used for receiving the page data of the page to be tested, which is sent by the first terminal, through the connection with the first terminal; the first sending module is used for sending the connection identifier and the page data to a second terminal so that the second terminal displays the page data associated with the connection identifier in a data verification page; and the second sending module is used for sending the verification rule to the second terminal so that the second terminal displays a verification result of the page data based on the verification rule in the data verification page.

In the above scheme, the connection module is further configured to generate a connection identifier for the first terminal when the connection request sent by the first terminal is received for the first time; generating a new connection identifier for the first terminal when the historical connection identifier generated for the first terminal before receiving the connection request of the first terminal has failed; wherein the connection identifier is used for establishing the connection with the first terminal.

In the above scheme, the connection module is further configured to receive an address of the page to be tested sent by the second terminal, where the address of the page to be tested is obtained by the second terminal in the displayed configuration page; generating a graphic code corresponding to the page to be tested based on the address of the page to be tested, sending the graphic code to the second terminal for display, wherein the graphic code is used for the first terminal to scan to display the page to be tested, and sending the connection request.

In the above scheme, the receiving module is further configured to correlate the page data sent by the first terminal with the connection identifier of the first terminal, and store the page data in the database; receiving a page data request sent by the second terminal; the page data request sent by the second terminal is sent when the connection identifier of the first terminal is input in the configuration page of the second terminal, or is sent when the connection identifier of the first terminal displayed in a device list by the second terminal is triggered, wherein the device list comprises the connection identifiers of a plurality of terminals; and inquiring the page data associated with the connection identification of the first terminal from the database.

In the above scheme, the connection identifier is generated by calling a connection identifier service; the connection module is further used for acquiring connection state information and synchronizing the connection state information to the connection identification service; the connection state information comprises a connection identifier, connection time and page type of a terminal connected with the server; and generating a device list based on the connection state information through the connection identification service, and sending the device list to the second terminal so that the second terminal displays the device list in the configuration page.

In the above scheme, the page data includes one or more of page buried point data, page structure data and page operation data; the page data is used for the second terminal to execute the following operations: when the page data comprise the page embedded point data, displaying the page embedded point data in a parameter panel area of the data verification page; when the page data comprises the page buried point data and the page structure data, carrying out matching processing on the page buried point data and the page structure data, and displaying the matching processing result in a buried point distribution area of the data verification page; the embedded point distribution area corresponds to the page structure to be tested, and a module for embedding the data is displayed; and when the page data comprises the page operation data, displaying the page operation data in a report stream display area of the data verification page, wherein the page operation data are arranged according to the receiving time.

In the above scheme, the verification rule is used for the second terminal to execute the following operations: and verifying the page operation data according to the verification rule to obtain error page operation data, and marking the error page operation data in a reporting stream display area of the data verification page.

In the above scheme, the verification rule is used for the second terminal to execute the following operations: when the wrong page operation data in the report stream display area of the data verification page is selected, determining page buried data related to the wrong page operation data according to the wrong page operation data; verifying the page buried data according to the verification rule, and determining error parameters in the page buried data of the page operation data causing the errors; and identifying the error parameters in a parameter panel area of the data verification page, and displaying the verification rule violated by the error parameters.

In the above scheme, the verification rule is used for the second terminal to execute the following operations: when the wrong page operation data in the reporting stream display area of the data verification page is selected, verifying the page buried point data according to the verification rule to determine a buried point module which causes the wrong page operation data in a buried point distribution area of the data verification page; and identifying the buried point module corresponding to the wrong page operation data in the buried point distribution area of the data verification page.

The embodiment of the application provides a page data verification method, which is applied to a second terminal and comprises the following steps:

receiving page data which is sent by a server and is associated with a connection identifier of a first terminal, and displaying the page data in a data verification page of a second terminal; the page data is sent to the server by the first terminal when the first terminal displays a page to be tested, and is sent based on the connection established by the connection identifier; and receiving a verification rule sent by the server, and displaying a verification result of the page data based on the verification rule in the data verification page.

The embodiment of the application provides a page data verification device, which is arranged at a second terminal and comprises:

the first display module is used for receiving page data which is sent by the server and is associated with the connection identifier of the first terminal, and displaying the page data in the data verification page of the second terminal; the page data is sent to the server by the first terminal when the first terminal displays a page to be tested, and is sent based on the connection established by the connection identifier; and the second display module is used for receiving the verification rule sent by the server and displaying the verification result of the page data based on the verification rule in the data verification page.

In the above scheme, the first display module is further configured to display a configuration page; acquiring an address of the page to be tested, which is input in the configuration page, and sending the address to the server so that the server generates a graphic code corresponding to the page to be tested; and receiving the graphic code sent by the server and displaying the graphic code in the configuration page, wherein the graphic code is used for the first terminal to scan so as to display the page to be tested, and sending a connection request.

In the above scheme, the first display module is further configured to send a page data request to the server when receiving the connection identifier of the first terminal input in the configuration page; when a device list comprising connection identifiers of a plurality of terminals is displayed in a configuration page and the connection identifier of the first terminal in the device list is triggered, sending a page data request to the server; wherein the page data request is for requesting the page data.

In the above scheme, the page data includes one or more of page buried point data, page structure data and page operation data; the first display module is further configured to display the page embedded point data in a parameter panel area of the data verification page when the page data includes the page embedded point data; when the page data comprises the page buried point data and the page structure data, carrying out matching processing on the page buried point data and the page structure data, and displaying the matching processing result in a buried point distribution area of the data verification page; the embedded point distribution area corresponds to the page structure to be tested, and a module for embedding the data is displayed; and when the page data comprises the page operation data, displaying the page operation data in a report stream display area of the data verification page, wherein the page operation data are arranged according to the receiving time.

In the above scheme, the second display module is further configured to verify the page operation data according to the verification rule, obtain erroneous page operation data, and identify the erroneous page operation data in a reporting pipeline display area of the data verification page.

In the above solution, the second display module is further configured to determine, when the erroneous page operation data in the report pipeline display area of the data verification page is selected, page buried data related to the erroneous page operation data according to the erroneous page operation data; verifying the page buried data according to the verification rule, and determining error parameters in the page buried data of the page operation data causing the errors; and identifying the error parameters in a parameter panel area of the data verification page, and displaying the verification rule violated by the error parameters.

In the above scheme, the second display module is further configured to, when the erroneous page operation data in the reporting pipeline display area of the data verification page is selected, verify the page buried point data according to the verification rule, so as to determine a buried point module that causes the erroneous page operation data in a buried point distribution area of the data verification page; and identifying the buried point module corresponding to the wrong page operation data in the buried point distribution area of the data verification page.

An embodiment of the present application provides an electronic device, including:

a memory for storing executable instructions;

and the processor is used for realizing the page data verification method provided by the embodiment of the application when executing the executable instructions stored in the memory.

The embodiment of the application provides a computer readable storage medium which stores executable instructions for realizing the page data verification method provided by the embodiment of the application when being executed by a processor.

The embodiment of the application has the following beneficial effects:

the method comprises the steps that page data of a first terminal when displaying a page to be tested are displayed in a data verification page of a second terminal in real time through a server, and timely visual projection of the page data is achieved; the verification rule is sent to the second terminal, so that the second terminal displays the verification result of the page data based on the verification rule in the data verification page, the second terminal can realize quick verification by acquiring the verification rule of the server, the verification result of the page data in the first terminal is checked, and the development and test efficiency of the page are improved.

Drawings

FIG. 1 is a schematic diagram of an architecture of a page data verification system 100 according to an embodiment of the present application;

Fig. 2A is a schematic structural diagram of a server 200 according to an embodiment of the present application;

fig. 2B is a schematic structural diagram of a second terminal 400 according to an embodiment of the present application;

FIG. 3A is a schematic flow chart of a page data verification method according to an embodiment of the present application;

FIG. 3B is a schematic flow chart of a page data verification method according to an embodiment of the present application;

FIG. 3C is a schematic flow chart of a page data verification method according to an embodiment of the present application;

FIG. 4 is a schematic diagram of a configuration page provided by an embodiment of the present application;

FIG. 5 is a schematic diagram of a buried point distribution area of a data verification page according to an embodiment of the present application;

FIG. 6 is a schematic diagram of a report pipeline display area of a data check page according to an embodiment of the present application;

FIG. 7 is a parameter panel area of a data check page provided by an embodiment of the present application;

FIG. 8 is a data verification page provided by an embodiment of the present application, including a reporting pipeline display area, a buried point distribution area, and a parameter panel area;

FIG. 9 is a schematic diagram of a block chain network based page data verification system 100 according to an embodiment of the present application;

FIG. 10 is a Block Structure (Block Structure) according to an embodiment of the present application;

FIG. 11 is a schematic flow chart of a page data verification method according to an embodiment of the present application;

FIG. 12 is a schematic flow chart of a page data verification method according to an embodiment of the present application;

FIG. 13 is a schematic flow chart of a page data verification method according to an embodiment of the present application;

fig. 14 is a schematic diagram of a target page according to an embodiment of the present application.

Detailed Description

The present application will be further described in detail with reference to the accompanying drawings, for the purpose of making the objects, technical solutions and advantages of the present application more apparent, and the described embodiments should not be construed as limiting the present application, and all other embodiments obtained by those skilled in the art without making any inventive effort are within the scope of the present application.

In the following description, reference is made to "some embodiments" which describe a subset of all possible embodiments, but it is to be understood that "some embodiments" can be the same subset or different subsets of all possible embodiments and can be combined with one another without conflict.

In the following description, the terms "first", "second", "third" and the like are merely used to distinguish similar objects and do not represent a specific ordering of the objects, it being understood that the "first", "second", "third" may be interchanged with a specific order or sequence, as permitted, to enable embodiments of the application described herein to be practiced otherwise than as illustrated or described herein.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of the application only and is not intended to be limiting of the application.

Before describing embodiments of the present application in further detail, the terms and terminology involved in the embodiments of the present application will be described, and the terms and terminology involved in the embodiments of the present application will be used in the following explanation.

1) Data burial points: to collect relevant data of a Page, such as Page View or click volume (PV), number of Visitor Visits (VV), etc., related technologies for capturing, processing and transmitting user behaviors or events and implementation processes thereof.

2) A software development kit (SDK, software Development Kit) is typically a collection of development tools that some software engineers create application software for a particular software package, software framework, hardware platform, operating system, etc.

3) The H5 page is a page designed by adopting the HTML5 front-end technology and can be understood as a mobile-end webpage.

4) A mobile Application (APP) page is a page of a mobile client of an application program.

5) A WEB page is a WEB page, which includes WEB pages composed of text, images, and other elements.

6) A web socket Server (WebSocket Server), which is a Server for providing WebSocket services, is a protocol that performs full duplex communication over a single TCP connection.

7) Remote dictionary service (dis, remote Dictionary Server) is an open source API written in ANSIC language, supporting network, log-type, key-Value database based on memory and persistent, and providing multiple languages.

In the related art, for a Web/H5 or APP page, the reported service data needs to be checked after the data is landed, for example, a software developer is first enabled to perform data embedding on the page to be tested, and after simple testing, the data product operation and maintenance person can obtain the service data (such as PV, VV, exposure click rate, etc.) of the page to be tested; the verification of the service data reported by the page to be tested often requires that the service data such as the operation and maintenance personnel of the data product fall into the database before the service data falls into the database, so as to verify the correctness of the service data by verifying the service data and follow-up service data aggregation analysis, and the mode can cause positioning problems (such as whether the service data is reported, whether the data is missing or not) with very long time period under the condition of very large data volume, so that the requirements of accurately and rapidly reporting the service and verifying the page data cannot be met.

In view of the foregoing technical problems, embodiments of the present application provide a method, an apparatus, an electronic device, and a computer readable storage medium for verifying page data, which are capable of quickly verifying page data, and an exemplary application of the method for verifying page data provided in the embodiments of the present application is described below.

Next, an exemplary application system architecture of a server implementing the page data verification method provided by the embodiment of the present application is described, referring to fig. 1, fig. 1 is a schematic diagram of an architecture of a page data verification system 100 provided by the embodiment of the present application, where the page data verification system 100 includes: server 200, first terminal 300 and second terminal 400. The first terminal 300 and the second terminal 400 are connected to the server 200 through a network, which may be a wide area network or a local area network, or a combination of both.

In some embodiments, the second terminal 400 displays a configuration page, and sends the address of the page to be tested input by the developer to the server 200; the server 200 generates a graphic code corresponding to the page to be tested based on the address of the page to be tested, and sends the graphic code to the second terminal 400 for display; the first terminal 300 scans the graphic code displayed by the second terminal 400, displays a page to be tested, and because the SDK for connecting and reporting page data is implanted in the page to be tested, when the first terminal 300 displays the page to be tested, the SDK starts a connection function to send a connection request to the server 200, the server 200 establishes connection with the first terminal 300 based on the connection identifier of the first terminal 300, after connection is established, the first terminal 300 sends the page data of the page to be tested to the server 200, and meanwhile, the server 200 acquires connection state information and synchronizes the connection state information to a connection identifier service running in the server; generating a device list based on the connection state information and transmitting the device list to the second terminal 400 to cause the second terminal 400 to be displayed in the configuration page; when the connection identifier of the first terminal 300 is input into the configuration page of the second terminal 400, or when the connection identifier of the first terminal 300 displayed in the device list by the second terminal 400 is triggered, the second terminal 400 displays a data check page, and displays page data associated with the connection identifier of the first terminal 300 in the data check page; the second terminal 400 acquires the check rule from the server 200 to display a check result of the page data based on the check rule in the data check page.

In some embodiments, the server 200 may be an independent physical server, or may be a server cluster or a distributed system formed by a plurality of physical servers, for example, the connection identifier service may be a cloud server that operates independently of other servers of the server 200, or may provide cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs, and basic cloud computing services such as big data and artificial intelligence platforms. The first terminal, the second terminal and the server may be directly or indirectly connected through wired or wireless communication, which is not limited in the embodiment of the present application.

Next, the structures of the terminal and the server for implementing the page data verification method provided by the embodiment of the application are described. As described above, the electronic device provided by the embodiment of the present application may be the server 200 in fig. 1. Referring to fig. 2A, fig. 2A is a schematic structural diagram of a server 200 according to an embodiment of the present application, and the server 200 shown in fig. 2A includes: at least one processor 210, a memory 250, at least one network interface 220. The various components in server 200 are coupled together by bus system 240. It is understood that the bus system 240 is used to enable connected communications between these components. The bus system 240 includes a power bus, a control bus, and a status signal bus in addition to the data bus. But for clarity of illustration the various buses are labeled as bus system 240 in fig. 2A.

The processor 210 may be an integrated circuit chip with signal processing capabilities such as a general purpose processor, such as a microprocessor or any conventional processor, or the like, a digital signal processor (DSP, digital Signal Processor), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or the like.

The memory 250 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid state memory, hard drives, optical drives, and the like. Memory 250 optionally includes one or more storage devices physically located remote from processor 210.

Memory 250 includes volatile memory or nonvolatile memory, and may also include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read Only Memory (ROM), and the volatile Memory may be a random access Memory (RAM, random Access Memory). The memory 250 described in embodiments of the present application is intended to comprise any suitable type of memory.

In some embodiments, memory 250 is capable of storing data to support various operations, examples of which include programs, modules and data structures, or subsets or supersets thereof, as exemplified below.

An operating system 251 including system programs for handling various basic system services and performing hardware-related tasks, such as a framework layer, a core library layer, a driver layer, etc., for implementing various basic services and handling hardware-based tasks;

network communication module 252 for reaching other computing devices via one or more (wired or wireless) network interfaces 220, exemplary network interfaces 220 include: bluetooth, wireless compatibility authentication (WiFi), and universal serial bus (USB, universal Serial Bus), etc.;

in some embodiments, the page data verification device provided in the embodiments of the present application may be implemented in a software manner, and fig. 2A shows a page data verification device 255 stored in a memory 250, which may be software in the form of a program and a plug-in, and includes the following software modules: the connection module 2551, the receiving module 2552, the first transmitting module 2553 and the second transmitting module 2554 are logical, and thus may be arbitrarily combined or further split according to the implemented functions. The functions of the respective modules will be described hereinafter.

As described above, the electronic device provided in the embodiment of the present application may also be the second terminal 400 in fig. 1. Referring to fig. 2B, fig. 2B is a schematic structural diagram of a second terminal 400 according to an embodiment of the present application, and the second terminal 400 shown in fig. 2 includes: at least one processor 410, a memory 450, at least one network interface 420, and a user interface 430. The various components in the second terminal 400 are coupled together by a bus system 440. It is understood that the bus system 440 is used to enable connected communication between these components. The bus system 440 includes a power bus, a control bus, and a status signal bus in addition to the data bus. But for clarity of illustration the various buses are labeled in fig. 2 as bus system 440.

The processor 410, like the processor 210 described above, may be referred to as described above.

The user interface 430 includes one or more output devices 431, including one or more speakers and/or one or more visual displays, that enable presentation of the media content. The user interface 430 also includes one or more input devices 432, including user interface components that facilitate user input, such as a keyboard, mouse, microphone, touch screen display, camera, other input buttons and controls.

Memory 450, like memory 250 above, may be described with reference to the above.

In some embodiments, memory 450 is capable of storing data to support various operations, examples of which include programs, modules and data structures, or subsets or supersets thereof, as exemplified below. The operating system 451, the network communication module 452, and the presentation module 453 are described above.

An input processing module 454 for detecting one or more user inputs or interactions from one of the one or more input devices 432 and translating the detected inputs or interactions.

In some embodiments, the page data verification device provided in the embodiments of the present application may be implemented in software, and fig. 2B shows the page data verification device 455 stored in the memory 450, which may be software in the form of a program and a plug-in, and includes the following software modules: the first display module 4551 and the second display module 4552 are logical, and thus may be arbitrarily combined or further split according to the functions to be implemented. The functions of the respective modules will be described hereinafter.

In the following, a method for checking page data provided by the embodiment of the present application is illustrated by the first terminal 300, the second terminal 400, and the server 200 in fig. 1. Referring to fig. 3A, fig. 3A is a schematic flow chart of a page data verification method according to an embodiment of the present application, and will be described with reference to the steps shown in fig. 3A.

In step 101, the second terminal displays a configuration page; and acquiring the address of the page to be tested, which is input in the configuration page, and sending the address to the server.

In some embodiments, referring to fig. 4, fig. 4 is a schematic diagram of a configuration page provided by an embodiment of the present application. Where 401 is an input control for the address of the page to be tested that is input by the developer. The input controls herein may be button controls, text field controls, selection class controls, and the like.

It should be noted that the pages to be tested include, but are not limited to, APP pages, H5/Web pages, computer (PC, personal Computer) client pages, and the like. As an example, the page to be tested may be an APP page in a mobile phone (first terminal), and the graphic code on the configuration page of the second terminal is scanned by a scanning function in the mobile phone, so as to display the page to be tested in the mobile phone. As other examples, the page to be tested may also be a PC-side page, and the scanning of the graphics code on the configuration page of the second terminal by the PC side (the first terminal) may be implemented by externally connecting a scanning device to the PC side, for example, the scanning device may be a scanning gun.

In step 102, the server generates a graphics code corresponding to the page to be tested based on the address of the page to be tested.

It should be noted that the graphic code is a coding manner of an input address of a page to be tested, which is a manner of realizing that the first terminal opens the page to be tested, for example, the server may code the address of the page to be tested into a two-dimensional code for the first terminal to scan.

In the embodiment of the application, the server converts the address of the page to be tested into the graphic code, so that a developer of the first terminal can quickly open the page to be tested by scanning the graphic code, and the operation of the developer is simplified.

In step 103, the second terminal receives the graphic code sent by the server and displays the graphic code in the configuration page.

In some embodiments, referring to fig. 4, 402 is a displayed graphic code. The graphic code may be a two-dimensional code, a bar code, or the like, and is used for the first terminal to scan, so as to test a page at the first terminal and send a connection request with the server.

In some embodiments, the second terminal may store the input address of the page to be tested and the generated graphic code, display the historical input address of the page to be tested on the configuration page of the second terminal, and directly display the stored graphic code corresponding to the historical input page to be tested when the developer selects the historical input page to be tested.

In the embodiment of the application, the time for repeatedly generating the graphic code by the server according to the page address to be tested is saved, the operation of the server is reduced, and the processing efficiency of the server is improved.

In step 104, the first terminal scans the graphic code to display the page to be tested, and sends a connection request to the server.

It should be noted that, the connection between the first terminal and the server may be implemented by an SDK implanted in the page to be tested, that is, the first terminal starts a connection function through the SDK after opening the page to be tested, and sends a connection request with the server. The functions of connection and data reporting of the page to be tested can be realized by the SDK implanted in the page to be tested.

In step 105, the server establishes a connection with the first terminal based on the connection identification of the first terminal.

In some embodiments, the connection with the first terminal established based on the connection identifier of the first terminal is a long connection, for example, the Server may be a WebSocket Server, i.e. the long connection is established through the WebSocket Server. It should be noted that, establishing a connection with the first terminal based on the connection identifier of the first terminal means that the connection with the first terminal is identified by the connection identifier, and the connection identifier is added to the page data received through the connection to be different from the page data of the page to be tested of the other terminal.

In some examples, when the server receives a connection request sent by the first terminal when displaying a page to be tested for the first time, the connection request carries a terminal identifier, namely, an identifier of the first terminal, the server generates a connection identifier for the first terminal based on the identifier of the first terminal, so as to be used for establishing connection with the first terminal, and the identifier of the first terminal and the connection identifier form a data structure and are stored in a database. Subsequently, when receiving a connection request sent by the first terminal, the server searches a connection identifier corresponding to the identifier of the first terminal in the database according to the identifier of the first terminal carried in the connection request, and establishes connection with the first terminal based on the searched connection identifier.

In step 106, the server receives the page data of the page to be tested sent by the first terminal through the connection with the first terminal, and sends the connection identifier and the page data to the second terminal.

In some embodiments, the server receives the page data of the page to be tested sent by the first terminal through the long connection with the first terminal, and sends the connection identifier and the page data to the second terminal. The server maintains page data reported by each page to be tested through the connection identifier; the connection identifier is used for identifying that the transmitted page data comes from the page data of the first terminal so as to be different from the page data of the pages to be tested of other terminals.

In the embodiment of the application, the server receives the page data of the first terminal through the long connection with the first terminal, and the connection is not required to be frequently established and closed, so that the use of a processor of the server, the blocking of a network and the subsequent response time are reduced.

In step 107, the second terminal receives the page data associated with the connection identifier of the first terminal and sent by the server, and displays the page data in the data verification page.

In some embodiments, the page data includes one or more of page buried point data, page structure data, and page operation data. Referring to fig. 3B, fig. 3B is a schematic flow chart of a page data verification method according to an embodiment of the present application, which shows step 107 in fig. 3A, and may also be implemented by executing steps 1071 to 1073, and will be described in connection with the steps.

In step 1071, when the page data includes the page buried point data and the page structure data, the second terminal performs a matching process on the page buried point data and the page structure data, and displays a result of the matching process in the buried point distribution area of the data verification page. The embedded point distribution area corresponds to the structure of the page to be tested, and a module for embedding the data is displayed.

In some embodiments, the page embedded point data refers to code data for collecting reported page operation data and performing embedded point operation on a page to be tested. The second terminal performs matching processing on the embedded point data and the page structure data, and the matching processing result is displayed in the embedded point distribution area of the data verification page, which can be realized by the following modes: the second terminal performs page rendering according to the page structure data to generate a page corresponding to the structure of the page to be tested, wherein the page corresponding to the structure of the page to be tested comprises all page modules of the page to be tested; the second terminal performs data embedding operation on page elements of the page module of the page corresponding to the structure of the page to be tested according to the page embedding data to obtain a page subjected to the data embedding operation; and matching the page subjected to the data embedding operation with the page corresponding to the structure of the page to be tested to obtain a matched page, displaying the matched page in an embedding point distribution area of the data verification page by the second terminal, displaying a module subjected to the data embedding operation and a module which is marked to not perform the data embedding operation by the matched page, and superposing the page operation data acquired by the page embedding data in the page module in a visual mode.

For example, referring to fig. 5, fig. 5 is a schematic diagram of a buried point distribution area of a data verification page according to an embodiment of the present application. Wherein 501 is a module that does not perform a data embedding operation, 502 is a module that has performed a data embedding operation, and 503 is a visualization module of page operation data acquired by a page embedding operation. Wherein, the point refers to clicking, the exposure refers to exposure, the reverse refers to reverse exposure, and the register refers to keyword tape covers.

In some embodiments, the buried point distribution area of the data verification page is a page that dynamically synchronizes the page to be tested. The embedded point distribution area of the data verification page can synchronously update the page structure data of the page to be tested, for example, the page structure data obtained after the page to be tested slides and the page structure data obtained after the page to be tested is switched. For example, when the first terminal switches from displaying the page to be tested to displaying the second page to be tested, updating the page structure data of the second page to be tested and sending the updated page structure data to the second terminal; so that the embedded point distribution area of the data verification page of the second terminal can dynamically synchronize the page to be tested in the first terminal.

In the embodiment of the application, which modules in the page to be tested do not carry out the embedded point operation can be visually displayed through the embedded point distribution area of the data verification page, and the modules which do not carry out the data embedded point operation can be quickly and intuitively positioned.

In step 1072, when the page data includes the page operation data, the second terminal displays the page operation data in the report stream display area of the data check page. Wherein the page operation data is arranged according to the reception time.

In some embodiments, the page operation data includes a click of a page to be tested, an exposure of a page to be tested, a back exposure of a page to be tested, and the like. The second terminal receives the page operation data sent by the server in real time, and the page operation data is sent to the server by the first terminal in real time when the first terminal displays the page to be tested. And displaying the received page operation data in the reporting flow display area of the data check page according to the descending order or the ascending order of the receiving time.

In some examples, the report pipeline display area of the data check page supports custom display of the reported page operation data, and when a certain custom type is selected in the input control, only the page operation data belonging to the custom type is displayed in the report pipeline display area. For example, the custom type may be an element exposure, a click, etc.

For example, referring to fig. 6, fig. 6 is a schematic diagram of a report pipeline display area of a data check page according to an embodiment of the present application. Wherein 601 is a custom type selection class control in the reporting pipeline display area, 602 is a certain piece of page operation data, the content of the page operation data includes the serial number of the page operation data, the type to which the page operation data belongs, and the time of reporting the page operation data, and 603 is a custom type switching control in the reporting pipeline display area. For example, the custom type may also include displaying only errors, displaying only erroneous page operation data by opening a display only error reporting pipeline display area, e.g., by opening a toggle control 603.

In the embodiment of the application, the type and time of the page operation data reported by the page to be tested are visually displayed through the reporting flow display area of the data check page, so that each piece of reported page operation data can be quickly and intuitively checked.

In step 1073, when the page data includes the page buried point data, the second terminal displays the page buried point data in the parameter panel area of the data check page.

In some embodiments, after the second terminal obtains the page buried point data, the second terminal displays the page buried point data in the parameter panel area of the data check page in addition to displaying the page data in the buried point distribution area of the data check page, so that after the subsequent check processing, errors and violated check rules in the page buried point data are displayed. For example, referring to fig. 7, fig. 7 is a parameter panel area of a data check page provided in an embodiment of the present application.

In the embodiment of the application, the page embedded point data of the page to be tested is visually displayed through the parameter panel area of the data verification page, so that error parameters in the page embedded point data can be quickly and intuitively checked in the subsequent verification processing.

In step 108, the server sends the verification rule to the second terminal.

In some embodiments, when the second terminal requests the page data, the second page requests the server to acquire the verification rule, and the server sends the verification rule to the second terminal for the second terminal to verify the page data.

In step 109, the second terminal receives the check rule sent by the server, and displays a check result of the page data based on the check rule in the data check page.

In some embodiments, displaying the verification result of the page data based on the verification rule in the data verification page may be achieved by: and checking the page operation data according to the checking rule to obtain wrong page operation data, and identifying the wrong page operation data in a reporting stream display area of the data checking page.

In some examples, referring to fig. 3C, fig. 3C is a schematic flow chart of a page data verification method provided in the embodiment of the present application, which shows step 109 in fig. 3A, and may also be implemented by executing steps 1091 to 1093, which will be described in connection with the steps.

In step 1091, when the erroneous page operation data in the report stream presentation area of the data check page is selected, the second terminal determines the page buried point data related to the erroneous page operation data according to the erroneous page operation data.

As an example, referring to fig. 8, fig. 8 is a data verification page provided by an embodiment of the present application, where the data verification page includes a reporting pipeline display area, a buried point distribution area, and a parameter panel area. Wherein 801 is the identification symbol of the erroneous page operation data, 805 is the erroneous page operation data, 803 is the relevant parameter of the page buried point data, and when the erroneous page operation data 805 in the reporting pipeline display area of the data check page is selected, the second terminal determines the page buried point data related to the erroneous page operation data according to the erroneous page operation data 805, and displays the page buried point data in the parameter panel area, for example 803 shown in fig. 8, that is, the relevant parameter of reporting the erroneous page operation data in the page buried point data.

In step 1092, the second terminal checks the page buried point data related to the erroneous page operation data according to the check rule, and determines an error parameter in the page buried point data that causes the erroneous page operation data.

As an example, referring to fig. 8, 804 is an error parameter in the page buried point data of the page operation data 805 that causes an error. And verifying the page buried point data related to the wrong page operation data according to the verification rule acquired from the server, and determining error parameters 804 in the page buried point data of the wrong page operation data.

In step 1093, the second terminal identifies the error parameters in the page buried point data in the parameter panel area of the data check page, and displays the check rule violated by the error parameters in the page buried point data.

As an example, referring to fig. 8, 802 is a verification result of parameter information. The second terminal checks the page buried data related to the erroneous page operation data according to the check rule, and after determining the error parameter (the page buried data violating the check rule, i.e. the erroneous page buried data), identifies the error parameter 804, for example, by using a red mark 804, and displays the error parameter and the check rule violated by the error parameter in the check result 802 of the parameter information.

In the embodiment of the application, the verification result of the page data of the page to be tested is visually displayed through three functional areas (the reporting stream display area, the buried point distribution area and the parameter panel area) in the data verification page, the verification result of the page data can be visually checked in real time, error parameters in the page data causing errors can be quickly and accurately positioned, and corresponding solving measures are provided. The parameter panel area is marked with the error parameter in the page buried point data, so that whether the error parameter has the associated error in the context of the page buried point data can be conveniently and intuitively checked; and displaying the check rule violated by the error parameter in the page buried point data in the parameter panel area, so that a developer can conveniently carry out corresponding modification measures according to the check rule violated by display.

In some embodiments, when erroneous page operation data in the reporting pipeline display area of the data check page is selected, checking the page buried point data according to a check rule to determine a buried point module that causes erroneous page operation data in the buried point distribution area of the data check page; and identifying the buried point module corresponding to the wrong page operation data in the buried point distribution area of the data verification page.

As an example, if an error occurs in 805 caused by no embedding operation on the data in the page to be tested, when the erroneous page operation data in the reporting pipeline display area of the data check page is selected, the embedding module corresponding to the erroneous page operation data is identified in the embedding distribution area of the data check page. Referring to fig. 8, 806 is a buried point module that causes erroneous page operation data, i.e., a module that does not perform data buried points. When erroneous page operation data 805 is selected, 806 is identified.

In the embodiment of the application, the embedded point module (the error page data caused by the missing embedded point module) which causes the error page data can be rapidly and accurately positioned through the linkage of the reporting pipeline display area and the embedded point distribution area in the data verification page, so that the cause of the error page data can be rapidly and accurately positioned. The embedded point module which causes the wrong page data is identified in the embedded point distribution area, so that a developer can intuitively know the module of the missing data embedded point in the page to be tested.

In some embodiments, when the server receives a connection request sent by the first terminal for the first time, the server generates a connection identifier for the first terminal; when a historical connection identifier generated by a server for a first terminal before a connection request of the first terminal is received is invalid, the server generates a new connection identifier for the first terminal; wherein the connection identifier is used for establishing a connection with the first terminal.

In some examples, the server generates a new connection identifier for the first terminal in order to identify the first terminal, so as to be different from other terminals, and when the server generates corresponding connection identifiers for the plurality of terminals, the correspondence between the first terminal and the connection identifiers may be stored in the database. Determining that the historical connection identifier generated by the server for the first terminal has failed prior to receiving the connection request of the first terminal may be achieved by looking up the historical connection identifier corresponding to the first terminal in the database, and determining that the historical connection identifier has failed when an unused time length (an interval time from a last use time to a current time when looking up) of the historical connection identifier exceeds a time length threshold.

In the embodiment of the application, through an expiration mechanism of the connection identifier, the connection identifier of the first terminal without uploading data for a long time is taken as invalid while the identification function of the connection identifier on the page data of the page to be tested of the first terminal is ensured, and the storage space of the server is saved.

In some embodiments, the server stores the received page data in the database because it is difficult to synchronize the page data of the page to be tested sent by the first terminal with the timing of displaying the page data in the data check page in the second terminal. That is, the method can be realized by the following way that the server correlates the page data sent by the first terminal with the connection identifier of the first terminal and stores the page data in the database; receiving a page data request sent by a second terminal; the page data request sent by the second terminal is sent when the connection identifier of the first terminal is input in the configuration page of the second terminal and the page data is triggered to be checked in the data check page, or is sent when the connection identifier of the first terminal displayed in the equipment list by the second terminal is triggered, wherein the equipment list comprises the connection identifiers of a plurality of terminals; page data associated with the connection identity of the first terminal is queried from a database.

In some examples, the page data request sent by the second terminal may be implemented by: when the second terminal receives the connection identification of the first terminal input in the configuration page, sending a page data request to a server; when a device list comprising connection identifiers of a plurality of terminals is displayed in a configuration page and the connection identifier of a first terminal in the device list is triggered, sending a page data request to a server; wherein the page data request is for requesting page data.

In some examples, the server associates the page data sent by the first terminal with the connection identifier of the first terminal and stores the page data in the database, which may be implemented by the following ways: when the server receives page data sent by the first terminal, the page data and connection identification generated by the server for the first terminal are stored into a database to form structural data. When the data check page is not yet connected, the page data is stored in the database, and therefore, the data is not lost. When receiving the page data request, the server can query the database for the page data associated with the connection identification of the first terminal to display the page data on the data check page.

It should be noted that, the connection identifier of the first terminal is input and triggered to view the page data in the data check page, or the connection identifier of the first terminal displayed in the device list by the second terminal is triggered to display the data check page, and the page data is displayed in the data check page.

For example, referring to fig. 4, 403 is a text field control for entering a connection identification, 404 is a button control for viewing page data, and 405 is a selection class control for a list of devices. The page data request may be sent to the server by entering a connection identifier at the text field control and clicking on the button control 404; the connection identifier of the first terminal displayed in the device list may be selected and sent to the server to obtain the page data sent by the server, so that the data check page is displayed on the second terminal, and the page data is displayed in the data check page.

In the embodiment of the application, when the page data of the page to be tested is pushed to the data verification page, the page data is temporarily stored in the database, so that the data pushed by the page to be tested is not lost when the data verification page is not connected yet.

In some embodiments, the connection identity is generated by invoking a connection identity service; after establishing a connection with the first terminal based on the connection identification of the first terminal, the following operations may also be performed: acquiring connection state information and synchronizing the connection state information to a connection identification service; the connection state information comprises a connection identifier, connection time and page type of a terminal connected with the server; and generating a device list based on the connection state information through the connection identification service, and transmitting the device list to the second terminal so that the second terminal displays the device list in the configuration page.

In some examples, a plurality of connection identifiers may be displayed in the device list, where each connection identifier corresponds to a page to be tested of a terminal, an address of a page to be tested that has been opened once may be displayed in the device list, a time for opening the page to be tested, and a type of the page to be tested. Referring to fig. 4, 406 is a page address to be tested that has been once opened, 407 is a page type of opening, i.e., H5 page, and 408 is a time when the page to be tested is opened.

In the embodiment of the application, the connection state is synchronized to the data verification page through the connection identification service, so that the connection among the first terminal, the second terminal and the server can be intuitively and conveniently carried out through the configuration page.

In some embodiments, page data of a page to be tested is uploaded to a state database of a blockchain network for storage; invoking a smart contract in the blockchain network to cause the smart contract to: acquiring page data from a blockchain maintained by a node of a blockchain network; and carrying out consensus processing on the page data, and returning the page data as a calling result when the consensus is passed. In the embodiment of the application, the blockchain network comprises a server, and the reliability of the page data and the reliability of the obtained page data verification result can be ensured through a consensus mechanism among nodes; of course, the page data verification result can also be stored in the upper chain.

Referring to fig. 9, fig. 9 is a schematic architecture diagram of a page data verification system 100 based on a blockchain network according to an embodiment of the present application, where any machine, such as the server 200, the first terminal 300, and the second terminal 400 shown in fig. 1, may join the blockchain network to form a node, and the node includes a hardware layer, an intermediate layer, an operating system layer, and an application layer. The mapping of the server 200 to the node 500-2 of the blockchain network 500, the mapping of the first terminal 300 to the node 500-3 of the blockchain network 500, and the mapping of the second terminal 400 to the node 500-4 of the blockchain network 500 are exemplarily shown in fig. 9, each node (e.g., the nodes 500-2 to 500-4) having a consensus function and a billing (i.e., a function of maintaining a status database, such as a KV database).

The first terminal 300 sends page data of a page to be tested to a node 500-3 of a blockchain network in a mode of calling an intelligent contract, and the node 500-3 performs consensus with other nodes 500-2 and 500-4 of the blockchain; after the consensus is passed, the node 500-2 uplinks the page data of the page to be tested and stores the page data into a block chain; the second terminal 400 (i.e., node 500-1) sends a page data request to the server 200 (i.e., node 500-2), and the server 200 invokes the intelligent contract to retrieve the page data stored in the blockchain network and sends it to the second terminal 400 to display the page data in the data check page of the second terminal.

The blockchain comprises a series of blocks (blocks) which are connected with each other according to the generated sequence time, the new blocks are not removed once being added into the blockchain, and record data submitted by nodes in the blockchain system are recorded in the blocks. Referring to fig. 10, fig. 10 is a schematic diagram of a Block Structure (Block Structure) according to an embodiment of the present application, where each Block includes a hash value of the page data and the page data stored in the Block (hash value of the Block), and a hash value of a previous Block, and each Block is connected by the hash value to form a Block chain. In addition, the block may include information such as a time stamp at the time of block generation. Blockchain (Blockchain) is essentially a de-centralized database, a string of data blocks that are generated in association using cryptographic methods.

In the following, a page data verification method provided by the embodiment of the present application is taken as an example to be separately executed by the server 200 in fig. 1. Referring to fig. 11, fig. 11 is a schematic flow chart of a page data verification method according to an embodiment of the present application, and the steps shown in fig. 11 will be described.

In step 201, the server receives a connection request sent by the first terminal when displaying a page to be tested, and establishes a connection with the first terminal based on a connection identifier of the first terminal.

In step 202, the server receives, through connection with the first terminal, page data of a page to be tested sent by the first terminal.

In step 203, the server sends the connection identifier and the page data to the second terminal, so that the second terminal displays the page data associated with the connection identifier in the data verification page.

In step 204, the server sends the verification rule to the second terminal, so that the second terminal displays the verification result of the page data based on the verification rule in the data verification page.

It should be noted that, in the embodiments of the present application, the corresponding steps implemented by the server in the foregoing description can be implemented, and the embodiments may be combined with each other without conflict.

In the following, a page data verification method provided by the embodiment of the present application is separately executed by the second terminal 400 in fig. 1 as an example. Referring to fig. 12, fig. 12 is a schematic flow chart of a page data verification method according to an embodiment of the present application, and the steps shown in fig. 12 will be described.

In step 301, the second terminal receives the page data associated with the connection identifier of the first terminal and displays the page data in the data check page of the second terminal. The page data is sent to the server by the first terminal when the first terminal displays the page to be tested, and is sent based on connection established by the connection identifier.

In step 302, the second terminal receives the check rule sent by the server, and displays a check result of the page data based on the check rule in the data check page.

It should be noted that, in the embodiment of the present application, the corresponding steps implemented by the second terminal can be implemented, and the embodiments may be combined with each other without collision.

In the following, an exemplary application of the embodiment of the present application in a practical application scenario will be described. Taking a certain APP page in the mobile phone as a page to be tested as an example, the first terminal is the mobile phone, and the second terminal is the PC terminal. The mobile phone is used for running a target page (namely a page to be tested), uploading operation data of a user aiming at the target page, and the PC side is used for a developer to check verification data of the tested page. According to the embodiment of the application, the data verification is advanced to the development engineering, the background server distributes the connection key (namely the connection identifier) for the pages to be tested (namely the target pages) in the mobile phone, and the data reported by each page to be tested is maintained through the connection key. The mobile phone end reports page data through the connection key, the server maintains the data reported by each page to be tested through the connection key, when the PC end (operating data check page) sends a request of the key of a specific page, the server can send the corresponding page data to the PC end (at the data check page) for display, and the data check rule is issued to the PC end, so that the result of data check can be displayed at the PC end. Therefore, the service data reported by the mobile phone is visually projected to the PC end, the configured verification rule is pulled by the PC end to carry out quick verification, and the cause of errors is accurately positioned, so that the development productivity is improved.

Referring to fig. 13, fig. 13 is a schematic flow chart of a page data verification method according to an embodiment of the present application. The steps shown in fig. 13 will be described in detail.

In step 1301, when the mobile phone opens the target page, the mobile phone loads the reporting SDK, and the reporting acquisition SDK enables the reporting data synchronization plug-in.

In some embodiments, the mobile phone opening the target page is achieved by: the PC end displays the configuration page, and the mobile phone scans the two-dimensional code of the configuration page in the PC end to open the target page. The target page is a page for collecting the SDK by reporting, referring to FIG. 4, when the PC receives the website of the target page, the configuration page of the PC displays the two-dimensional code of the target page. After the mobile phone scans the two-dimensional code, the mobile phone displays a target page, referring to fig. 14, and fig. 14 is a schematic diagram of the target page provided by the embodiment of the application. The mobile phone opens a target page containing a reporting acquisition SDK, and the reporting acquisition SDK enables a reporting data synchronization plug-in.

It should be noted that, the target page is an arbitrary user access platform, for example: APP client, H5/Web page or PC client, etc., the data verification page is realized by browser Web page form.

In step 1302, the reporting data synchronization plug-in the handset establishes a long connection with the WebSocket Server and requests to obtain a connection key.

It should be noted that, in some embodiments, the reporting data synchronization plug-in may not be used, the function of the reporting data synchronization plug-in is integrated in the SDK, and implemented through the SDK, and after the reporting data synchronization plug-in is enabled, the target page may acquire a connection key from the background server. The WebSocket Server is a background Server and is used for opening a target page and a data verification page, and essentially pushes target page data to one or more data verification pages in a long connection mode, and stores page data to a Redis so as to ensure that the data pushed by the target page cannot be lost when the data verification pages are not connected.

In some embodiments, referring to FIG. 4, when the configuration page at the PC side receives this connection key entered by the developer (e.g., entered 2699 at the location of the connection key), and clicks on the "View report" button 404, the target page and the data check page have established a connection through the WebSocket Server.

In step 1303, the WebSocket Server generates a connection key through the key service, and returns the key to the mobile phone.

It should be noted that, the key service is a connection identification service, and the background server allocates connection keys to the mobile phones, where one mobile phone corresponds to one connection key. The connection key service is used to generate connection keys for new devices or for state maintenance of existing keys. In order to facilitate the use, the characteristics of the connection equipment are stored, so that the same key is used when the same equipment is connected at different times as much as possible, namely one key corresponds to one mobile phone.

In some examples, a key may have an expiration mechanism, if a key service does not obtain page data uploaded by a device for a long period of time after a key is assigned to the device, the assigned key is invalidated, and the device subsequently needs to re-apply for a new key. That is, each key has a life cycle, and automatically fails after expiration, and after a device is connected with the key service and exceeds the life cycle, the device needs to re-apply the key and upload the page data. The configuration page of the PC may obtain a list of device connection keys (including a plurality of device connection keys) for the PC to switch or select the data check page.

In step 1304, the mobile phone starts pushing page data of the target page to the key corresponding to the mobile phone in the WebSocket Server.

In some embodiments, after the mobile phone takes the connection key through the data synchronization plug-in, the mobile phone starts pushing the page data of the target page to the key corresponding to the mobile phone in the WebSocket Server.

It should be noted that the page data includes report stream and report structure data. The report stream is page operation data, and the report structure data is page structure data.

In step 1305, the WebSocket Server stores the page data in the database.

In some embodiments, after the WebSocket Server obtains the page data, the display condition of the corresponding data check page is determined, and the page data is temporarily stored in a database, for example, a remote dictionary service (Redis, remote Dictionary Server).

The data verification page is used for establishing long connection with the WebSocket Server through the mobile phone, receiving reporting stream and reporting structure data pushed by the WebSocket Server, realizing data visualization, and verifying the correctness of the data in real time by pulling a data verification rule service.

In step 1306, the configuration page of the PC obtains the connection key list of the current device from the connection key service, so as to open a data check page corresponding to the selected connection key.

In some embodiments, when the PC side does not display the data check page, the configuration page of the PC side obtains the connection key list of the current device from the connection key service. For the developer to select the corresponding connection device.

In step 1307, when the data check page of the PC side is opened, the WebSocket Server pushes page data to the data check page.

In some embodiments, when a connection device in a configuration page of the PC side is selected, the PC side opens a data check page, the data check page of the PC side establishes a long connection with the websocket Server, and the websocket Server pushes page data (i.e., report stream and report structure data) to the PC side, so that the PC side performs visualization and stream display on the page data.

In some embodiments, referring to fig. 8, the data check page specific function in the second terminal is divided into the following three parts: 1) Buried point distribution map (i.e., buried point distribution area): the module synchronously displays the elements of the target page for which the data embedding points are made, which is equivalent to the visualization of the data of the embedded point module, and can synchronize all operations of the target page, such as sliding up, page switching and the like. The second terminal determines which buried modules are missing by comparing the buried distribution map (i.e., the result of matching the page buried data with the page structure data) with the target page, so that it can be quickly determined which modules are not added with the buried data, for example 806. 2) Reporting flow display (reporting flow display area): the module enumerates the reporting pipeline of the real-time page data (i.e. page operation data) generated by the target page, and displays which page operation data reporting is problematic by pulling a data verification rule, referring to fig. 8, the dot 801 is used to identify the problematic page operation data 805, and it should be noted that the problematic page operation data display form is not limited. The module also supports custom display or keyword filtering of certain types of reports, such as only looking at exposure types, click types or reports of keywords with covers, and the like, and also can only look at false reports. When a piece of page operation data in the reporting pipeline display region is selected, a corresponding module can be displayed in the buried point distribution diagram (for example, a missing module can be identified by 806), and detailed information causing the page operation data error can be displayed in the parameter panel. 3) The parameter panel (parameter panel area) is used for showing detailed parameters of the page buried point data of the reported page operation data. If the page buried data does not meet the data check rule (i.e., check rule), the corresponding error parameter may be exhibited, as shown at 804 in FIG. 8.

In step 1308, the PC side requests the data verification rule of the current target page from the data verification rule service, and verifies the page data in real time.

The data verification rule service is used for receiving a request of a data verification page, the data verification page obtains the data verification rule, and real-time verification is carried out on page data. For example, the data verification rule may be a rule of parameter length range, value range, whether it is a necessary parameter, or the like.

In the embodiment of the application, the data verification is advanced to the reporting outlet, and the data verification rule is pulled to verify the data in real time through visualization of the buried point data and reporting running water display, so that development and testing personnel can quickly and effectively locate and correct the erroneous reporting data, and the working efficiency is improved.

An exemplary structure in which the page data verification apparatus provided in the embodiment of the present application is implemented as a software module is described below in conjunction with fig. 2A and 2B, and in some embodiments, as shown in fig. 2A, the software module stored in the page data verification apparatus 255 of the memory 250 may include: a connection module 2551, configured to receive a connection request sent by a first terminal when displaying a page to be tested, and establish connection with the first terminal based on a connection identifier of the first terminal; a receiving module 2552, configured to receive, through a connection with the first terminal, page data of the to-be-tested page sent by the first terminal; a first sending module 2553, configured to send the connection identifier and the page data to a second terminal, so that the second terminal displays the page data associated with the connection identifier in a data verification page; and the second sending module 2554 is configured to send a verification rule to the second terminal, so that the second terminal displays a verification result of the page data based on the verification rule in the data verification page.

In some embodiments, the connection module 2551 is further configured to, when the connection request sent by the first terminal is received for the first time, or when a historical connection identifier generated for the first terminal before the connection request of the first terminal is received has failed, generate a new connection identifier for the first terminal, for use in establishing the connection with the first terminal.

In some embodiments, the connection module 2551 is further configured to receive an address of the page to be tested sent by the second terminal, where the address of the page to be tested is obtained by the second terminal in the displayed configuration page; generating a graphic code corresponding to the page to be tested based on the address of the page to be tested, sending the graphic code to the second terminal for display, and enabling the graphic code to be used for the first terminal to scan to display the page to be tested and sending the connection request.

In some embodiments, the receiving module 2552 is further configured to associate the page data sent by the first terminal with the connection identifier of the first terminal, and store the page data in a database; receiving a page data request sent by the second terminal; the page data request sent by the second terminal is sent when the connection identifier of the first terminal is input in the configuration page of the second terminal, or is sent when the connection identifier of the first terminal displayed in a device list by the second terminal is triggered, wherein the device list comprises the connection identifiers of a plurality of terminals; and inquiring the page data associated with the connection identification of the first terminal from the database.

In some embodiments, the connection identity is generated by invoking a connection identity service; the connection module 2551 is further configured to obtain connection status information, and synchronize the connection status information to the connection identifier service; the connection state information comprises a connection identifier, connection time and page type of a terminal connected with the server; and generating a device list based on the connection state information through the connection identification service, and sending the device list to the second terminal so that the second terminal displays the device list in the configuration page.

In some embodiments, the page data includes one or more of page buried point data, page structure data, and page operation data; the page data is used for the second terminal to execute the following operations: when the page data comprise the page embedded point data, displaying the page embedded point data in a parameter panel area of the data verification page; when the page data comprises the page buried point data and the page structure data, carrying out matching processing on the page buried point data and the page structure data, and displaying the matching processing result in a buried point distribution area of the data verification page; the embedded point distribution area corresponds to the page structure to be tested, and a module for embedding the data is displayed; and when the page data comprises the page operation data, displaying the page operation data in a report stream display area of the data verification page, wherein the page operation data are arranged according to the receiving time.

In some embodiments, the checking rule is used for the second terminal to: and verifying the page operation data according to the verification rule to obtain error page operation data, and marking the error page operation data in a reporting stream display area of the data verification page.

In some embodiments, the check rule is used for the second terminal to perform the following operations: when the wrong page operation data in the report stream display area of the data verification page is selected, determining page buried data related to the wrong page operation data according to the wrong page operation data; verifying the page buried data according to the verification rule, and determining error parameters in the page buried data of the page operation data causing the errors; and identifying the error parameters in a parameter panel area of the data verification page, and displaying the verification rule violated by the error parameters.

In some embodiments, the check rule is used for the second terminal to perform the following operations: when the wrong page operation data in the reporting stream display area of the data verification page is selected, verifying the page buried point data according to the verification rule to determine a buried point module which causes the wrong page operation data in a buried point distribution area of the data verification page; and identifying the buried point module corresponding to the wrong page operation data in the buried point distribution area of the data verification page.

In some embodiments, as shown in FIG. 2B, the software modules stored in the page data checking means 455 of the memory 450 may include:

a first display module 4551, configured to receive page data associated with a connection identifier of a first terminal sent by a server, and display the page data in a data check page of the second terminal; the page data is sent to the server by the first terminal when the first terminal displays a page to be tested, and is sent based on the connection established by the connection identifier; and the second display module 4552 is configured to receive the verification rule sent by the server, and display a verification result of the page data based on the verification rule in the data verification page.

In some embodiments, the first display module 4551 is further configured to display a configuration page; acquiring an address of the page to be tested, which is input in the configuration page, and sending the address to the server so that the server generates a graphic code corresponding to the address of the page to be tested; and receiving the graphic code sent by the server and displaying the graphic code in the configuration page, wherein the graphic code is used for the first terminal to scan to display the page to be tested, and sending a connection request.

In some embodiments, the first display module 4551 is further configured to send a page data request to the server when receiving the connection identifier of the first terminal input in the configuration page; when a device list comprising connection identifiers of a plurality of terminals is displayed in a configuration page and the connection identifier of the first terminal in the device list is triggered, sending a page data request to the server; wherein the page data request is for requesting the page data.

In some embodiments, the page data includes one or more of page buried point data, page structure data, and page operation data; the first display module 4551 is further configured to display the page buried point data in a parameter panel area of the data verification page when the page data includes the page buried point data; when the page data comprises the page buried point data and the page structure data, carrying out matching processing on the page buried point data and the page structure data, and displaying the matching processing result in a buried point distribution area of the data verification page; the embedded point distribution area corresponds to the page structure to be tested, and a module for embedding the data is displayed; and when the page data comprises the page operation data, displaying the page operation data in a report stream display area of the data verification page, wherein the page operation data are arranged according to the receiving time.

In some embodiments, the second display module 4552 is further configured to verify the page operation data according to the verification rule to obtain erroneous page operation data, and identify the erroneous page operation data in a report pipeline display area of the data verification page.

In some embodiments, the second display module 4552 is further configured to, when the erroneous page operation data in the report pipeline display area of the data verification page is selected, determine, according to the erroneous page operation data, page buried data related to the erroneous page operation data; verifying the page buried data according to the verification rule, and determining error parameters in the page buried data of the page operation data causing the errors; and identifying the error parameters in a parameter panel area of the data verification page, and displaying the verification rule violated by the error parameters.

In some embodiments, the second display module 4552 is further configured to, when the erroneous page operation data in the reporting pipeline display area of the data verification page is selected, verify the page buried point data according to the verification rule to determine a buried point module that causes the erroneous page operation data in a buried point distribution area of the data verification page; and identifying the buried point module corresponding to the wrong page operation data in the buried point distribution area of the data verification page.

Embodiments of the present application provide a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions, so that the computer device executes the page data verification method according to the embodiment of the present application.

Embodiments of the present application provide a computer readable storage medium storing executable instructions that, when executed by a processor, cause the processor to perform a page data verification method provided by embodiments of the present application, for example, the page data verification method shown in fig. 11 and 12.

In some embodiments, the computer readable storage medium may be FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; but may be a variety of devices including one or any combination of the above memories.

In some embodiments, the executable instructions may be in the form of programs, software modules, scripts, or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and they may be deployed in any form, including as stand-alone programs or as modules, components, subroutines, or other units suitable for use in a computing environment.

As an example, the executable instructions may, but need not, correspond to files in a file system, may be stored as part of a file that holds other programs or data, for example, in one or more scripts in a hypertext markup language (HTML, hyper Text Markup Language) document, in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code).

As an example, executable instructions may be deployed to be executed on one computing device or on multiple computing devices located at one site or, alternatively, distributed across multiple sites and interconnected by a communication network.

In summary, according to the embodiment of the application, the verification result of the page data of the page to be tested is visually displayed through the three functional areas (the reporting pipeline display area, the buried point distribution area and the parameter panel area) in the data verification page, so that the verification result of the page data can be intuitively checked in real time, the error parameters of the page data causing errors can be quickly and accurately positioned, and corresponding solving measures are provided; the time for repeatedly generating the graphic code by the server according to the page address to be tested is saved, the operation of the server is reduced, and the processing efficiency of the server is improved; the time for repeatedly generating the graphic code by the server according to the page address to be tested is saved, the operation of the server is reduced, and the processing efficiency of the server is improved; the modules which do not perform the embedded point operation in the page to be tested are visually displayed through the embedded point distribution area of the data verification page, so that the modules which do not perform the embedded point operation can be quickly and intuitively positioned; the type and time of the page operation data reported by the page to be tested are visually displayed through the reporting stream display area of the data check page, and each piece of reported page operation data can be quickly and intuitively checked; and visually displaying the embedded point data of the page to be tested through the parameter panel area of the data verification page so as to quickly and intuitively check error parameters in the embedded point data of the page during subsequent verification processing.

The foregoing is merely exemplary embodiments of the present application and is not intended to limit the scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and scope of the present application are included in the protection scope of the present application.

Claims

1. A method for verifying page data, applied to a server, the method comprising:

receiving a connection request sent by a first terminal when a page to be tested is displayed, and establishing connection with the first terminal based on a connection identifier of the first terminal;

receiving page data of the page to be tested, which is sent by the first terminal, through connection with the first terminal;

the connection identifier and the page data are sent to a second terminal, so that the second terminal displays the page data associated with the connection identifier in a data verification page;

and sending the verification rule to the second terminal so that the second terminal displays a verification result of the page data based on the verification rule in the data verification page.

2. The method of claim 1, wherein prior to receiving a connection request sent by the first terminal while displaying the page to be tested, the method further comprises:

Receiving an address of the page to be tested, which is sent by the second terminal, wherein the address of the page to be tested is obtained from a displayed configuration page by the second terminal;

generating a graphic code corresponding to the page to be tested based on the address of the page to be tested, sending the graphic code to the second terminal for display, wherein the graphic code is used for the first terminal to scan to display the page to be tested, and sending the connection request.

3. The method of claim 1, further comprising, prior to transmitting the connection identification and the page data to a second terminal:

the method comprises the steps of associating page data sent by a first terminal with a connection identifier of the first terminal and storing the page data into a database;

receiving a page data request sent by the second terminal;

and inquiring the page data associated with the connection identification of the first terminal from the database.

4. The method of claim 3, wherein the step of,

the connection identifier is generated by calling a connection identifier service;

after establishing a connection with the first terminal based on the connection identification of the first terminal, the method further comprises:

Acquiring connection state information and synchronizing the connection state information to the connection identification service;

the connection state information comprises a connection identifier, connection time and page type of a terminal connected with the server;

and generating a device list based on the connection state information through the connection identification service, and sending the device list to the second terminal so that the second terminal displays the device list in a configuration page.

5. A method for verifying page data, applied to a second terminal, the method comprising:

receiving page data which is sent by a server and is associated with a connection identifier of a first terminal, and displaying the page data in a data verification page of a second terminal; the page data is sent to the server by the first terminal when the first terminal displays a page to be tested, and is sent based on the connection established by the connection identifier;

and receiving a verification rule sent by the server, and displaying a verification result of the page data based on the verification rule in the data verification page.

6. The method of claim 5, wherein the step of determining the position of the probe is performed,

The page data comprises one or more of page buried point data, page structure data and page operation data;

the displaying the page data in the data check page of the second terminal comprises the following steps:

when the page data comprise the page embedded point data, displaying the page embedded point data in a parameter panel area of the data verification page;

when the page data comprises the page buried point data and the page structure data, carrying out matching processing on the page buried point data and the page structure data, and displaying the matching processing result in a buried point distribution area of the data verification page; the embedded point distribution area corresponds to the page structure to be tested, and a module for embedding the data is displayed;

and when the page data comprises the page operation data, displaying the page operation data in a report stream display area of the data verification page, wherein the page operation data are arranged according to the receiving time.

7. The method of claim 5, wherein displaying in the data check page a check result of the page data based on the check rule comprises:

Checking the page operation data according to the checking rule to obtain error page operation data, and marking the error page operation data in a reporting stream display area of the data checking page;

the method further comprises the steps of:

when the wrong page operation data in the report stream display area of the data verification page is selected, determining page buried data related to the wrong page operation data according to the wrong page operation data;

verifying the page buried data according to the verification rule, and determining error parameters in the page buried data of the page operation data causing the errors;

and identifying error parameters in the page embedded point data in a parameter panel area of the data verification page, and displaying a verification rule violated by the error parameters in the page embedded point data.

8. The method of claim 7, wherein the method further comprises:

when the wrong page operation data in the reporting stream display area of the data verification page is selected, verifying the page buried point data according to the verification rule to determine a buried point module which causes the wrong page operation data in a buried point distribution area of the data verification page;

And identifying the buried point module corresponding to the wrong page operation data in the buried point distribution area of the data verification page.

9. The page data verification device is characterized by being arranged on a server and comprising the following components:

the connection module is used for receiving a connection request sent by a first terminal when a page to be tested is displayed, and establishing connection with the first terminal based on a connection identifier of the first terminal;

the receiving module is used for receiving the page data of the page to be tested, which is sent by the first terminal, through the connection with the first terminal;

the first sending module is used for sending the connection identifier and the page data to a second terminal so that the second terminal displays the page data associated with the connection identifier in a data verification page;

and the second sending module is used for sending the verification rule to the second terminal so that the second terminal displays a verification result of the page data based on the verification rule in the data verification page.

10. The page data verification device is characterized by being arranged at a second terminal and comprising:

the first display module is used for receiving page data which is sent by the server and is associated with the connection identifier of the first terminal, and displaying the page data in the data verification page of the second terminal; the page data is sent to the server by the first terminal when the first terminal displays a page to be tested, and is sent based on the connection established by the connection identifier;

And the second display module is used for receiving the verification rule sent by the server and displaying the verification result of the page data based on the verification rule in the data verification page.