CN115658452B

CN115658452B - Buried point verification method, buried point verification device, readable storage medium, and electronic device

Info

Publication number: CN115658452B
Application number: CN202211347823.2A
Authority: CN
Inventors: 陈锦海; 曹偲; 邹衍芳; 杨义春; 胡持; 程实; 王健
Original assignee: Hangzhou Netease Cloud Music Technology Co Ltd
Current assignee: Hangzhou Netease Cloud Music Technology Co Ltd
Priority date: 2022-10-31
Filing date: 2022-10-31
Publication date: 2025-01-28
Anticipated expiration: 2042-10-31
Also published as: CN115658452A

Abstract

The embodiment of the disclosure relates to a buried point verification method, a buried point verification device, a readable storage medium and electronic equipment, and relates to the technical field of computers. The embedded point verification method comprises the steps of receiving embedded point reporting information of an application program client, responding to the embedded point reporting information comprising pit position information, matching the pit position information with pit positions in a target pit position library, and verifying the embedded point reporting information based on a target verification rule library according to a matching result, wherein the target pit position library and the target verification rule library are determined according to embedded points in an embedded point task to be verified. The embedded point verification method and device can improve efficiency and accuracy of embedded point verification.

Description

Buried point verification method, buried point verification device, readable storage medium, and electronic apparatus

Technical Field

Embodiments of the present disclosure relate to the field of computer technology, and more particularly, to a buried point verification method, a buried point verification device, a computer readable storage medium, and an electronic apparatus.

Background

This section is intended to provide a background or context for the embodiments of the disclosure recited in the claims, which description herein is not admitted to be prior art by inclusion in this section.

The embedded point is used for collecting some information in a specific process in the application and tracking the use condition of the application so as to provide data support for the subsequent further optimized product. And the buried points are checked, so that the accuracy of the collected information can be ensured.

The first is to carry out rule matching check on a server side or to issue a buried point demand rule stored on a buried point platform to a client side in a development stage through real-time uploading of logs, and check the buried point generated in real time on the client side, and the second is to carry out comparison and abnormal fluctuation monitoring on the buried point of a new version and an old version after the gray level or the whole quantity of the buried point is released on line so as to identify whether the buried point data has problems.

Disclosure of Invention

However, the first solution only focuses on whether the buried point is correct or not, and the multiple reports or missing reports of the buried point cannot be checked, so the accuracy of the check is not enough. In the second scheme, the problem can be found according to the fluctuation of the new and old buried point data after the buried point is on line, the problem finding period is long, the problem can be found accurately according to the fluctuation of the new and old data only if the coverage amount of a user depending on a new version reaches a certain duty ratio, the buried point verification efficiency is low, in addition, the problem can be found after the buried point is on line, and the defect of delay in problem finding exists.

Therefore, an improved buried point verification method is very needed, the accuracy of buried point verification and the efficiency of buried point verification can be improved, more problems can be found before the buried points are on line, and hysteresis of problem finding is avoided as much as possible.

In this context, embodiments of the present disclosure desirably provide a buried point verification method, a buried point verification apparatus, a computer-readable storage medium, and an electronic device.

According to a first aspect of the embodiment of the disclosure, a buried point verification method is provided, which comprises the steps of receiving buried point reporting information of an application program client, responding to the buried point reporting information including pit information, matching the pit information with pits in a target pit library, and verifying the buried point reporting information based on a target verification rule library according to a matching result, wherein the target pit library and the target verification rule library are determined according to buried points in a buried point task to be verified.

In an optional implementation manner, the verification of the buried point report information based on the target verification rule base according to the matching result includes obtaining buried point object identifiers included in the pit position information in response to successful matching, and verifying first buried point parameters in the buried point report information based on verification rules of the first buried point parameters associated with the buried point object identifiers in the target verification rule base for each buried point object identifier.

In an alternative implementation mode, the verification of the embedded point report information based on the target verification rule base according to the matching result comprises the step of responding to the matching failure and adding a pit matching failure label to the embedded point report information.

In an optional implementation manner, after receiving the embedded point report information of the application program client, the method further comprises determining a second embedded point parameter associated with an embedded point report event triggering the embedded point report information, checking the second embedded point parameter in the embedded point report information according to a check rule of the second embedded point parameter in the target check rule base, and/or checking the public parameter in the embedded point report information according to a check rule corresponding to the public parameter in the target check rule base.

In an optional implementation manner, in a case where the embedded point report information includes embedded point report information corresponding to an embedded point test task, the embedded point task to be checked includes a first embedded point task in the embedded point test task and a second embedded point task on which an application program targeted by the embedded point test task is online.

In an optional implementation manner, the method for determining the to-be-verified buried point task includes obtaining a value of a preset field in the buried point reporting information, and determining the to-be-verified buried point task according to the value of the preset field, wherein the preset field is used for indicating a version of the application program client, and the to-be-verified buried point task includes an online buried point task corresponding to the version of the application program client.

In an optional implementation manner, the method further comprises the steps of updating a first quantity and a second quantity according to the received embedded point reporting information, responding to an operation of requesting to display a check result of the first check mode, and displaying the first quantity and the second quantity corresponding to the embedded point reporting event, wherein the first quantity comprises the quantity of the embedded point reporting event indicated by the embedded point reporting information, and the second quantity comprises the quantity of embedded point pit bits corresponding to the embedded point reporting event indicated by the embedded point reporting information.

In an alternative implementation mode, the method further comprises the operation of responding to the request to display the verification result of the first verification mode, and the verification result of the embedded point reporting information is displayed sequentially according to the reporting time of the embedded point reporting information.

In an alternative implementation mode, in the case that the embedded point report information includes embedded point report information corresponding to an embedded point test task, the method further includes determining target embedded point pit positions including an enumerated type of embedded point parameter, and determining that the embedded point test task test is completed in the case that each enumerated value of each target embedded point pit position is successfully matched.

In an optional implementation manner, the method further comprises describing target buried point parameters of a constraint value range according to a verification rule not passing through the buried point reporting information, and verifying the target buried point parameters according to a candidate value library which is associated with the target buried point parameters in advance.

In an alternative implementation mode, the method further comprises updating one or more of a third quantity, a fourth quantity, a fifth quantity, a sixth quantity and a seventh quantity according to the embedded point attribution parameter value in the embedded point attribution parameter information, wherein the third quantity is used for representing the quantity of embedded point attribution parameter value illegal embedded point attribution information, the fifth quantity is used for representing the quantity of embedded point attribution parameter value illegal embedded point attribution information, the sixth quantity is used for representing the quantity of embedded point attribution parameter value degradation processing, the seventh quantity is used for representing the quantity of embedded point attribution parameter values of various types of embedded point reporting events corresponding to the embedded point attribution parameter value, under the condition that an attribution point attribution parameter value indicated by the embedded point attribution parameter value does not belong to an embedded point attribution parameter value, the attribution point attribution value illegal embedded point attribution parameter value is determined, under the condition that an attribution point attribution parameter value to be used for determining information to be subjected to a corresponding to a field is not corresponding to an attribution point attribution parameter value, and under the condition that an attribution parameter value to be subjected to a preset field is not confirmed is detected, and the attribution value is reasonably matched with the attribution parameter value.

In an optional implementation mode, the method further comprises the steps of recording embedded point reporting information of any application program client according to the reporting time sequence of the embedded point reporting information, responding to a query request of target embedded point reporting information, and acquiring other embedded point reporting information which is within a preset range with the reporting sequence of the target embedded point reporting information so as to display the target embedded point reporting information and the other embedded point reporting information.

In an optional implementation manner, the embedded point reporting information includes embedded point reporting information generated by the application program client triggered according to a test case of an embedded point test task, where the test case is generated based on an embedded point pit to be tested of the embedded point test task.

In an alternative embodiment, in the case that the embedded point report information includes embedded point report information corresponding to an embedded point test task, the method further includes simulating test data corresponding to a test link in the embedded point test task through a virtual object, so as to perform integrity check on the embedded point test task based on the test link.

According to a second aspect of the embodiment of the disclosure, a buried point verification device is provided, which comprises a buried point information receiving module, a verification module and a verification module, wherein the buried point information receiving module is configured to receive buried point reporting information of an application program client, the buried point information is matched with a buried point in a target buried point library in response to the buried point reporting information including the buried point information, the verification module is configured to verify the buried point reporting information based on a target verification rule library according to a matching result, and the target buried point library and the target verification rule library are determined according to buried points in a buried point task to be verified.

In an optional implementation manner, the embedded point verification device may further include a second embedded point parameter verification module and/or a third embedded point parameter verification module, where the second embedded point parameter verification module is configured to determine, after receiving embedded point reporting information of an application program client, a second embedded point parameter associated with an embedded point reporting event triggering the embedded point reporting information, verify the second embedded point parameter in the embedded point reporting information according to a verification rule of the second embedded point parameter in the target verification rule base, and the third embedded point parameter verification module is configured to verify a common parameter in the embedded point reporting information according to a verification rule corresponding to the common parameter in the target verification rule base.

In an optional implementation mode, the embedded point verification device further comprises a quantity display module, wherein the quantity display module comprises an updating unit and a display unit, the updating unit is configured to update a first quantity and a second quantity according to received embedded point reporting information, the display unit is configured to respond to an operation of requesting to display a verification result of a first verification mode and display the first quantity and the second quantity corresponding to the embedded point reporting event, the first quantity comprises the quantity of the embedded point reporting event indicated by the embedded point reporting information, and the second quantity comprises the quantity of embedded point pit bits corresponding to the embedded point reporting event indicated by the embedded point reporting information.

In an optional implementation manner, the embedded point verification device further includes a sequential display verification result module, and the sequential display verification result module is configured to respond to an operation of requesting to display the verification result of the first verification mode, and sequentially display the verification result of the embedded point reporting information according to the reporting time of the embedded point reporting information.

In an alternative implementation manner, in the case that the report information of the buried point includes report information of a buried point corresponding to a test task of the buried point, the device further includes a task completion degree checking module, and the task completion degree checking module is configured to determine target buried point pits including enumerated type buried point parameters, and determine that the test task of the buried point is completed in the case that each enumerated value of each target buried point pit is successfully matched.

In an optional implementation manner, the buried point verification device further comprises a candidate verification module, wherein the candidate verification module is configured to verify the target buried point parameter according to a candidate value library which is associated with the target buried point parameter in advance, aiming at the target buried point parameter which does not pass through a verification rule description constraint value range in the buried point report information.

In an alternative implementation mode, the buried point verification device further comprises a quantity updating module, wherein the quantity updating module is configured to update one or more of a third quantity, a fourth quantity, a fifth quantity, a sixth quantity and a seventh quantity according to the buried point attribution parameter value in the buried point attribution information, the third quantity is used for representing the quantity of buried point attribution parameter value as empty buried point reporting information, the fourth quantity is used for representing the quantity of buried point attribution parameter value illegal buried point reporting information, the fifth quantity is used for representing the quantity of buried point attribution parameter value illegal buried point attribution information, the sixth quantity is used for representing the quantity of buried point attribution parameter value degraded, the seventh quantity is used for representing the quantity of various buried point attribution parameter values of a buried point attribution event corresponding to the buried point attribution parameter value, in the case that the position indicated by the buried point attribution parameter value does not belong to the buried point attribution parameter value is not included, the situation that the position indicated by the buried point attribution parameter value is not included in the field, the attribution parameter value is not included in the preset parameter value, and the situation that the attribution parameter value is not included in the field is confirmed to be used for confirming that the position information corresponding to the value of the buried point attribution parameter value is included in the field is not included.

In an optional implementation manner, the embedded point verification device further comprises a detail display module, wherein the detail display module is configured to record embedded point reporting information of any application program client according to the reporting time sequence of the embedded point reporting information, respond to a query request of target embedded point reporting information and acquire other embedded point reporting information which is within a preset range with the reporting sequence of the target embedded point reporting information so as to display the target embedded point reporting information and the other embedded point reporting information.

In an alternative embodiment, in the case that the embedded point report information includes the embedded point report information corresponding to the embedded point test task, the embedded point verification device further includes an integrity verification module, where the integrity verification module is configured to simulate test data corresponding to a test link in the embedded point test task through a virtual object, so as to perform integrity verification on the embedded point test task based on the test link.

According to a third aspect of embodiments of the present disclosure, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the buried point verification method described in the first aspect above.

According to a fourth aspect of embodiments of the present disclosure, there is provided an electronic device comprising a processor, and a memory for storing executable instructions of the processor, wherein the processor is configured to perform the buried point verification method of the first aspect described above via execution of the executable instructions.

According to the buried point verification method, the buried point verification device, the computer-readable storage medium and the electronic equipment, under the condition that buried point report information of an application program client is received, the buried point report information is responded to comprise pit information, the pit information is matched with pits in a target pit library, verification can be conducted on the buried point report information based on a target verification rule library according to a matching result, and the target pit library and the target verification rule library are determined according to buried points in a buried point task to be verified. On one hand, the method and the device can automatically check the buried point based on the pit position, can check the multiple and leakage of the buried point and improve the accuracy of the buried point check, and on the other hand, the method and the device can determine a target check rule base based on the buried point task to be checked, further can automatically check the buried point based on the buried point tasks corresponding to each stage after the development, integration, gray scale and online release of the buried point, improve the efficiency of the buried point check, and can check the buried point in the development stage when the buried point task to be checked is the buried point task in the development stage so as to discover the buried point problem as early as possible before the buried point is online.

Drawings

The above, as well as additional purposes, features, and advantages of exemplary embodiments of the present disclosure will become readily apparent from the following detailed description when read in conjunction with the accompanying drawings. Several embodiments of the present disclosure are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings, in which:

FIG. 1 illustrates a schematic diagram of a buried point verification method according to an embodiment of the present disclosure;

FIG. 2 is a flow chart of a method for verifying buried point report information according to pit-level matching results according to an embodiment of the present disclosure;

FIG. 3 illustrates a schematic diagram of a buried point parameter configuration page, according to an embodiment of the present disclosure;

FIG. 4 illustrates a flow diagram of another method of verifying a buried point according to an embodiment of the present disclosure;

FIG. 5 illustrates a flow diagram of a method of determining whether a buried point test task is test complete, according to an embodiment of the present disclosure;

FIG. 6 illustrates a multi-terminal interactive flow diagram when performing buried point verification according to an embodiment of the present disclosure;

FIG. 7 illustrates a flow diagram of another method of verifying an online buried point task in real time according to an embodiment of the present disclosure;

FIG. 8 illustrates a flow diagram of a method of manual bill of lading point verification in accordance with an embodiment of the present disclosure;

FIG. 9 shows a schematic diagram of a buried point verifying apparatus according to a disclosed embodiment;

Fig. 10 shows a block diagram of an electronic device according to an embodiment of the present disclosure.

In the drawings, the same or corresponding reference numerals indicate the same or corresponding parts.

Detailed Description

The principles and spirit of the present disclosure will be described below with reference to several exemplary embodiments. It should be understood that these embodiments are presented merely to enable one skilled in the art to better understand and practice the present disclosure and are not intended to limit the scope of the present disclosure in any way. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

Those skilled in the art will appreciate that embodiments of the present disclosure may be implemented as a system, apparatus, device, method, or computer program product. Accordingly, the present disclosure may be embodied in the form of entirely hardware, entirely software (including firmware, resident software, micro-code, etc.) or in a combination of hardware and software.

According to an embodiment of the present disclosure, there are provided a buried point verification method, a buried point verification device, a computer-readable storage medium, and an electronic apparatus.

Any number of elements in the figures are for illustration and not limitation, and any naming is used for distinction only, and not for any limiting sense.

The principles and spirit of the present disclosure are described in detail below with reference to several representative embodiments thereof.

Summary of The Invention

The inventor of the present disclosure finds that in some existing buried point verification schemes, only whether the buried point is correct or not is concerned, and verification cannot be performed on multiple reports or missed reports of the buried point, so that the verification accuracy is not sufficient. In other existing buried point verification schemes, problems can be found according to fluctuation of new and old buried point data after the buried point is on line, the problem finding period is long, the problems can be found accurately according to fluctuation of the new and old data only when the coverage amount of a user depending on a new version reaches a certain duty ratio, the efficiency of buried point verification is low, in addition, the problems can be found after the buried point is on line, and the defect of delay of problem finding exists.

In view of the above, the basic idea of the disclosure is to provide a physical sign embedded point verification method, an embedded point verification device, a computer readable storage medium and an electronic device, in the case of receiving embedded point report information of an application client, in response to the embedded point report information including pit information, match the pit information with pits in a target pit library, and verify the embedded point report information based on a target verification rule library according to a matching result, wherein the target pit library and the target verification rule library are determined according to embedded points in a task to be verified. On one hand, the method and the device can automatically check the buried point based on the pit position, can check the multiple and leakage of the buried point and improve the accuracy of the buried point check, and on the other hand, the method and the device can determine a target check rule base based on the buried point task to be checked, further can automatically check the buried point based on the buried point tasks corresponding to each stage after the development, integration, gray scale and online release of the buried point, improve the efficiency of the buried point check, and can check the buried point in the development stage when the buried point task to be checked is the buried point task in the development stage so as to discover the buried point problem as early as possible before the buried point is online.

Having described the basic principles of the present disclosure, various non-limiting embodiments of the present disclosure are specifically described below.

Application scene overview

It should be noted that the following application scenarios are only shown for facilitating understanding of the spirit and principles of the present disclosure, and embodiments of the present disclosure are not limited in this respect. Rather, embodiments of the present disclosure may be applied to any scenario where applicable.

The method can be used for verifying the buried point in the development stage, and then after the verification is passed, the buried point is online to collect application use data (such as access number, visitor number, stay time, page browsing number and the like), so that the tracked application use condition can be used for providing data support for further optimization of the application, and in the information recommendation scene, the collected historical data related to the behavior of the user can be verified by using the buried point verification method provided by the invention to determine whether the collected historical data related to the behavior of the user is accurate or not, and further user images can be accurately depicted so as to recommend information to the user.

The method and the device can be applied to the scene of optimizing the application program client, for example, after the embedded point is online, the embedded point information reported by the application program client can be verified according to the embedded point verification method, the verification result is counted, and then the verification result is analyzed to determine which pages or controls in the application program client need to be optimized, so that the interactive experience of a user is improved.

Exemplary method

In the related art, the buried point verification scheme only focuses on whether the buried point is correct or not, and the buried point cannot be verified for multiple reports or missing reports, so that the accuracy of the buried point verification is insufficient. In other buried point verification schemes, problems can be found according to fluctuation of new and old buried point data after the buried point is on line, the problem finding period is long, the problems can be found accurately according to fluctuation of the new and old data only when the coverage amount of users of a new version reaches a certain duty ratio, the efficiency of buried point verification is low, in addition, the problems can be found after the buried point is on line, and the defect of delayed finding of the buried point problems exists.

Exemplary embodiments of the present disclosure first provide a buried point verification method to overcome at least all or part of the above-described drawbacks of the related art.

FIG. 1 illustrates a buried point verification method in an exemplary embodiment of the present disclosure, which may include:

Step S110, receiving embedded point report information of an application program client, and matching the embedded point information with the pit in a target pit library in response to the embedded point report information including the pit information;

Step S120, checking the information reported by the buried points based on a target checking rule base according to the matching result;

The target pit position library and the target verification rule library are determined according to the buried points in the buried point task to be verified.

Each step in fig. 1 is described in detail below.

And step S110, receiving embedded point report information of the application program client, and matching the embedded point information with the pits in the target pit library in response to the embedded point report information including the pit information.

In an exemplary embodiment, the application client in step S110 may include a buried test task application client. The embedded point test task application program client can be understood as an application program client used by a developer when testing a developed embedded point task.

When the embedded point developer tests the embedded point task, the used application program client is the client corresponding to the application program to be tested. For example, the embedded point developer modifies the embedded point of the application program of version 1.0 to complete the development of the new embedded point task, and after the completion, the new embedded point task and the embedded point task of the application program of version 1.0 can be combined to generate the application program to be tested, and then the generated application program to be tested is installed in any terminal device, so as to obtain the application program client to be tested.

In the case where the application client in step S110 includes an application client that is used by a developer when testing a developed buried point task, the buried point report information in step S110 may include buried point report information corresponding to the buried point test task.

The buried point is tested and checked in the buried point testing stage, so that the accuracy and the integrity of the newly added buried point in the development process of the buried point task can be ensured to a great extent. However, considering that the test of the embedded point is often on the required development code branch, that is, each developer is responsible for testing the embedded point task branch developed by himself, the embedded point task branch may still be modified after the test is completed, and other conflicts may exist in the process of merging with the newly added embedded point of other branches into the main distributing branch, so that the embedded point after the test is completed may be modified. In other words, the code of the buried task branch distance composition, gray scale and full scale line-up after the test is completed has a certain gap and a certain variation possibility. Therefore, after the embedded point test is completed, the embedded point verification method in the present disclosure can be used for verification of the embedded point task integration, the gray scale and the on-line state.

The gradation distribution is a distribution mode capable of smoothly transitioning between black and white. On which an a/B test can be performed, i.e. letting a part of the users continue to use the product property a and a part of the users start to use the product property B, if the users do not have any objection to B, the range is gradually expanded and all users are migrated to B. The gray level release can ensure the stability of the whole system, and the problems can be found and adjusted during the initial gray level so as to ensure the influence degree, namely, the control part of users use the latest release version. Full release refers to when all users access the program after clicking release, the current latest release version is used.

Based on this, in another exemplary embodiment, the application client of step S110 may include any application client corresponding after the buried task is synthesized, gray scale, or full release is online. For an application, the upgrade is optimized continuously, and different versions are generated. Therefore, the versions of the application used by different users may be different, and the application client in step S110 may include any version of the application client.

In other words, the buried point verification method provided by the exemplary embodiment of the present disclosure may not only verify the buried point in the buried point test stage, but also continue to verify the buried point information reported by the application program client after the buried point task is synthesized or online, so as to perform timely leak detection and repair on the problem not found in the buried point task test, thereby verifying the buried point in an overall aspect and improving the accuracy of the information reported by the buried point.

In an exemplary application scenario, when a trigger operation occurs in an application client, the application client may report the embedded point information corresponding to the trigger operation. Then, the embedded point information reported by the application program client can be checked.

For example, it may be determined whether the information reported by the buried point includes pit information, and the information reported by the buried point may be checked according to the determination result.

For example, if the embedded point report information includes a field identifier corresponding to the pit information, it may be determined that the embedded point report information includes the pit information, or else it may be determined that the embedded point report information does not include the pit information, that is, the currently reported embedded point information may be an event embedded point, or the like. Taking field identification spm (Super Content Model, super position model, refer to parameter field expressing pit position in report information of buried point) as an example, when the report information of buried point includes spm field, it can be determined that the report information of buried point includes pit position information.

Under the condition that the buried point report information contains pit information, the pit information in the buried point report information can be matched with the pits in the target pit library so as to verify the buried point report information.

The target pit position library is determined according to the buried points in the buried point task to be checked. The target pit position library is determined according to the pit positions corresponding to the buried points in the buried point task to be checked.

In an exemplary embodiment, in the case that the report information of the embedded point in step S110 includes the report information of the embedded point corresponding to the embedded point test task, the embedded point task to be checked includes a first embedded point task in the embedded point test task and a second embedded point task on which the application program targeted by the embedded point test task is online.

For example, the buried point verification method in the present disclosure may perform real-time test verification of buried points facing the requirement of the buried point task. The developer can carry out real-time test and verification on the buried point task which is responsible for development, namely, when the buried point test is carried out, the specific buried point task can be selected. For the buried point test task, when checking the buried point test task, a target pit position library can be determined according to all the buried points of which the application program has issued online and the pit positions of the buried points in the buried point task to be tested (online is not issued).

For the developer, each time when a new embedded point task is developed, one or more operations of adding, modifying, deleting and the like can be performed on the basis of the embedded point task corresponding to an application program (on line) of a certain version. In general, one or more of the operations of adding, modifying, deleting, etc. are performed on the basis of the embedded point task corresponding to the application program of the latest version, so as to complete the development of the new embedded point task. The embedded point tasks in the application programs of the latest version are all already released and online, so that the embedded point tasks to be checked comprise a first embedded point task in the embedded point test tasks and a second embedded point task of the application programs for which the embedded point test tasks are already online under the condition that the embedded point report information comprises embedded point report information corresponding to the embedded point test tasks.

Of course, the developer may develop the new embedded point task on the basis of any historical version of the application program as required, and the exemplary embodiment is not limited thereto. Under the condition that a developer develops a new embedded point task on the basis of any historical version of the application program, the embedded point task to be checked can comprise the current embedded point task to be tested and the embedded point task corresponding to the historical version of the application program.

In an exemplary application scenario, after the embedded point management platform completes development of a new embedded point task, a developer may select the new embedded point task at the embedded point management platform, and then log in the embedded point management platform by using a client scan code corresponding to an online history version (such as a current latest version) of an application program corresponding to the new embedded point task. Because the developer performs code scanning login, when the code scanning login is performed, the version of the application program client used by the developer can be obtained, and the to-be-verified buried point task can be determined according to all the on-line buried point tasks corresponding to the version of the application program client used by the developer and the to-be-tested buried point tasks manually selected by the developer (namely, the new buried point tasks completed by the developer), so that a target pit position library and a target verification rule library are determined according to the to-be-verified buried point tasks, and verification test of the to-be-tested buried point tasks is performed.

In the method, when the embedded point task test is carried out, the embedded point task to be checked comprises not only the embedded point task newly developed at present but also the history embedded point task which is already online, so that the new embedded point and the old embedded point can be checked simultaneously to test whether the new embedded point task has an influence on the correctness of the old embedded point task or not, the correct old embedded point is prevented from being changed into the wrong embedded point in the new embedded point task development process, and the accuracy of embedded point verification is further improved.

In another exemplary embodiment, the determining manner of the to-be-verified buried point task in step S110 may include obtaining a value of a preset field in the buried point reporting information, and determining the to-be-verified buried point task according to the value of the preset field. The preset field is used for indicating the version of the application program client, and the to-be-verified embedded point task comprises an online embedded point task corresponding to the version of the application program client.

As described above, in order to ensure the comprehensiveness of the buried point verification, the buried point can be verified at each stage after the code integration, the gray level distribution and the full distribution are on line, so as to discover the buried point problem as early as possible, and thus correct in time. However, for code integration, gray level release and full release online, the buried point task to be checked cannot be determined by the manner of the buried point task to be tested and active code scanning login selected by a developer as in the test stage.

Based on this, in the present disclosure, in order to ensure that the embedded point can be automatically checked at each stage of the embedded point task test, after integration, after gray level release, and after full release, the version of the application program client corresponding to the currently reported embedded point information may also be determined by carrying a preset field in the embedded point reporting information and by the value of the preset field.

For example, when the embedded point report information is packaged, a unique UUID (Universally Unique Identifier, universal unique identification code) corresponding to the version of the application client may be embedded in the embedded point report information according to the version of the application client. Meanwhile, the mapping relation between each UUID and the corresponding application program client version is stored in the embedded point management platform. Therefore, when the embedded point management platform (i.e. the server side) receives the embedded point reporting information, the application program client version corresponding to the UUID can be searched according to the UUID in the embedded point reporting information, and further the embedded point task to be verified is determined according to the embedded point task of which the application program client version is online.

For the embedded point testing stage, the embedded point task to be checked is the on-line embedded point task corresponding to the determined application program end version and the embedded point task to be tested selected by the developer, and for the stage of embedded point task integration, gray level release and full release, the embedded point task to be checked is the all on-line embedded point tasks corresponding to the determined application program quantity client version.

By the method, the buried point tasks to be verified in each stage of buried point test, integration, gray scale and release can be accurately determined, so that the reference (namely the target pit position library and the target verification rule library) for buried point verification can be accurately determined based on the buried point tasks to be verified, the buried points can be automatically verified in each stage, and the efficiency of buried point verification is improved.

After the task of the buried point to be checked is determined, a target buried point library can be determined according to the buried point to be checked, and under the condition that the information of the buried point to be reported comprises the information of the buried point, the information of the buried point to be reported and the buried point in the target buried point library can be matched, so that the checking result of the information reported by the buried point can be determined according to the matching result.

With continued reference to fig. 1, in step S120, according to the matching result, the report information of the buried point is verified based on the target verification rule base.

The target verification rule base is determined according to the buried points in the buried point task to be verified. In other words, the target verification rule base includes parameter configuration rules corresponding to the buried points in the buried point task to be verified. The determination manner of the task to be verified is already described in detail in the above step S110, and reference is made to the determination manner, and details are not repeated here.

Fig. 2 is a flow chart illustrating a method for verifying information reported from a buried point according to a pit-level matching result according to an embodiment of the present disclosure. Referring to fig. 2, the method may include steps S210 to S240.

In step S210, pit information in the report information of the buried point and pits in the target pit library are matched, and in response to successful matching, the process goes to step S220, and in response to failure of matching, the process goes to step S240.

In step S220, a buried point object identifier included in the pit information is acquired.

In an exemplary embodiment, a pit may be understood as the only one location in a client application that may be described.

Pages are understood to be an entire area which is exclusively displayed on a certain user interface level, such as a newly opened bottom page, a TAB (TAB/TAB), a channel and the like, and are generally used for organizing a plurality of contents for distribution or are carried as actual functions of a single content, and the information such as circulation exposure and stay time of the pages has great significance for analysis of applications. An element may be understood as a UI (User Interface) component and/or element of a page that may be interacted with by a User, such as a list element, a button, a slidable content module, etc. Listings and modules are typically used to carry content distribution with click-through rates that have an analytical meaning for the content distribution effect, buttons are typically used to carry user interactions, and buttons are typically mounted on the underlying page of a certain content unit or content function.

Both pages and elements can be buried objects. The sub-pages and the elements can be included in one page, and for one page, the page itself, the sub-pages and the elements in the page can be used as embedded point objects in the page, and users can perform custom setting according to own requirements.

For example, in response to a trigger operation for an application client, a page node tree of a target display page to which the trigger operation is exposed may be determined, and then a buried object tree may be generated according to attribute information of nodes in the page node tree. The buried object tree may be generated according to nodes in the page node tree configured with the buried object identifiers.

After the buried point object tree is generated, a buried point object identification chain from the buried point object to a root object in the buried point object tree can be determined based on a father-son relationship in the buried point object tree and buried point object identifications configured for the buried point objects in the buried point object tree in advance, and position attribute information of the buried point objects is added in the buried point object identification chain so as to obtain pit position information of the buried point objects.

A buried Object Id (oid for short) is an identity of a page or element of a buried point at a client, and the same oid may be used to represent the same UI style, the same content unit, the same interaction form, or a specific UI of the client. When a developer develops a buried point, a buried point object identifier can be configured for each buried point object.

Considering that some repeated type elements have the same hierarchy in the page, for example, the object identifiers of each list element in the list multiplexing unit are the same and all belong to the same hierarchy, that is, the object identifiers of each list element in the list multiplexing unit are the object identifiers of the list unit, and the hierarchy of each list element is the hierarchy of the list unit.

To solve this problem, in an alternative embodiment, position attribute information of the buried object may be added to the buried object identification chain to obtain pit information in the buried report information.

For example, the currently exposed buried object is_ oid1, the buried object identifier of the parent node in the buried object tree is oid2, the parent node of the parent node is the root node, and the buried object identifier of the root node is oid3, wherein the position attribute information of oid2 is pos2, and the pit information in the buried report information corresponding to the buried object may be oid1| oid2:pos2| oid3. Then, the current value of the buried point parameter associated with each buried point object identifier in the pit position information can be reported.

When the information reported by the buried point is verified, the buried point parameters associated with the buried point object indicated by the buried point object identification in the pit position information can be verified. Therefore, the buried object identification included in the pit information can be acquired.

In step S230, for each buried point object identifier, the first buried point parameter in the reported information of the buried point is verified based on the verification rule of the first buried point parameter associated with the buried point object identifier in the target verification rule base.

The first buried point parameter associated with the buried point object identifier may be understood as a private parameter of the buried point object indicated by the buried point object identifier.

By way of example, fig. 3 shows a schematic diagram of a buried point parameter configuration page according to an embodiment of the present disclosure. As can be seen from fig. 3, for the buried object, it may be configured with a private parameter (i.e. the first buried parameter described above), and may also be configured with an event parameter and a global public parameter.

The private parameter may be understood as a parameter of a buried object that only belongs to a buried object indicated by a certain buried object identifier. The event parameters can be understood as parameters that need to be reported when the client side generates a corresponding event. If the page exposure event is configured as a buried point reporting event in the buried point management platform, the page exposure event is associated with an event parameter 1, and the page exposure event is configured for the buried point object 1, then when the buried point object 1 is exposed, the event parameter 1 corresponding to the page exposure event needs to be reported. As shown in fig. 3, a page exposure start event and a page exposure end event are configured for the page1, that is, when the page1 starts exposure or ends exposure, the event parameter 1 associated with the corresponding page exposure start event or page exposure end event needs to be reported. The global common parameter may be understood as a parameter that any embedded point object in the whole application client may be configured, i.e. a parameter that is not only a embedded point object that can belong to a specific embedded point object identifier. Such as global public parameter V1 in fig. 3.

For example, the buried point developer may configure corresponding buried point parameters for each buried point object in advance in the buried point management platform, for example, may configure corresponding buried point parameters for each buried point object in the page shown in fig. 3, and simultaneously configure corresponding value rules for each buried point parameter. The value rule can be used as a check rule for the buried point parameter.

For each buried point object identifier included in the pit information, the current value of the first buried point parameter associated with the buried point object identifier and the value rule of the first buried point parameter in the target verification rule base can be matched, and if the matching fails, the verification of the first buried point parameter fails. If the value rule of a certain first buried point parameter is 0 or 1, when the value of the first buried point parameter is any one of 0 or 1 in the current buried point report information, the current verification of the first buried point verification parameter is successful, but if the value of the first buried point parameter is other than 0 or 1, such as 5, the current verification of the first buried point verification parameter is failed.

In other words, it may be determined whether the value of each first buried point parameter having the value rule in the current buried point report information is within the range constrained by the corresponding value rule, if so, the current verification of the first buried point parameter is successful, and if not, the current verification of the first buried point parameter is failed.

In step S240, a tag that fails to match pit bits is added to the embedded point report information.

For example, in response to receiving the embedded point report information, whether the embedded point report information includes pit information may be determined first, and in the case where the embedded point report information includes pit information, the pits included in the embedded point report information may be matched with the pits in the target pit library. If the matching is successful, the information of the buried point to be reported is reporting information generated by the pit bit in the buried point task, and if the matching is failed, the information of the buried point to be reported is not reporting information generated by the pit bit in the buried point task, and a tag of failure in pit bit matching can be added to the reporting information of the buried point.

For example, under the condition that pit information is successfully matched, a tag with successful pit matching can be added to the information reported by the successfully matched buried point. Thus, the number and leakage of buried points can be checked by the tags with successful pit matching and added pit matching or failed pit matching. For example, an unmatched pit is an unnecessary buried pit in the buried task, i.e., a multi-buried pit, and if the unmatched pit is not a pit in the buried task to be tested after the test operation of the buried task to be tested is completed, the unmatched pit is a less-buried pit.

As previously mentioned, parameters of the buried object may also have one or more of event parameters or common parameters. Based on the above, after receiving the embedded point report information of the application program client, the second embedded point parameter associated with the embedded point report event triggering the embedded point report information can be determined, the second embedded point parameter in the embedded point report information is checked according to the check rule of the second embedded point parameter in the target check rule base, and/or the public parameter in the embedded point report information is checked according to the check rule corresponding to the public parameter in the target check rule base. The second buried point parameter can be understood as the event parameter.

For example, after receiving the embedded point report information of the application program client, the parameter identification field in the embedded point report information, the event parameter identification field in the target verification rule base and the global parameter identification field may be matched to determine the event parameter and the global parameter in the embedded point report information. And then, matching the current value of the event parameter or the global parameter determined in the embedded point report information with a value rule of the event parameter or the global parameter in a target verification rule base, and determining whether the current value is in a value range constrained by the corresponding value rule or not so as to verify the event parameter and the global parameter in the embedded point report information. Meanwhile, when the embedded point report information includes pit information, the verification of the private parameter associated with each embedded point object in the pit information may be further performed according to the steps S210 to S240.

By way of example, fig. 4 shows a flow diagram of another method for verifying a buried point according to an embodiment of the present disclosure. Referring to fig. 4, the method may include steps S401 to S412. Wherein:

In step S401, receiving the report information of the buried point, in step S402, judging whether the report information of the buried point has the information of the buried point, if yes, going to step S403, otherwise going to step S411, in step S403, matching the information of the buried point in the report information of the buried point with the buried point in the target buried-point library, in step S404, judging whether the report information of the buried-point is successfully matched, if so, going to step S405, otherwise going to step S412, determining a buried-point object list corresponding to the buried-point object contained in the report information of the buried-point in step S405, judging whether the buried-point object list is empty in step S406, if yes, going to step S411, otherwise, going to step S407 to step S411, obtaining a first buried-point object in the buried-point object list, in step S407, judging whether the first buried-point object is configured with a parameter rule, if not, going to step S409, otherwise, going to step S412, going to step S408, going to the first buried-point, and step S408, continuing to check the step S408, and checking the parameter until the first buried-point is a parameter is completely matched with the first buried-point object, and then going to step S408, and checking the parameter is completed.

For example, after receiving the report information of the embedded point, it may be first determined whether there is pit information in the report information of the embedded point, and if there is no pit information, the event parameters and/or the common parameters in the report information of the embedded point are directly checked. If the pit information exists, the pit information in the pit report information and the pit in a target pit library (the target pit library is determined based on the pit in the to-be-verified pit task) are matched, if the matching fails, a mark of failure in pit matching is added for the pit report information, if the matching is successful, a pit object list corresponding to the pit objects contained in the pit information is determined, each pit object in the pit object list is traversed, whether the private parameters are configured for the traversed pit objects is determined, if the private parameters are checked, and if the private parameters are not configured, the public parameters or the event parameters configured for the pit objects are checked. After traversing the buried point object list, checking other event parameters or common parameters in the reported information of the buried point can be continued.

Of course, after receiving the report information of the buried point, whether pit information exists in the report information of the buried point can be not judged, and the common parameters and/or the event parameters in the report information of the buried point can be checked directly according to the common parameters and/or the event parameters in the target check rule base. After the verification of the public parameter and/or the event parameter is completed, judging whether pit information exists in the report information of the embedded point, if no pit information exists, finishing the verification of the report information of the embedded point, if the pit information exists, matching the pit information with the pit in the target pit database, obtaining the embedded point object in the pit information, verifying the value of each private parameter of each embedded point object in the pit information in the current report information of the embedded point according to the verification rule of the private parameter of the embedded point object in the target verification rule database, and directly adding a tag of pit matching failure for the pit information which fails.

In an exemplary embodiment, when the embedded point test is performed, the embedded point report may be triggered by a manual operation of a tester, so as to obtain the embedded point report information. In order to further improve accuracy of the embedded point test, in the embedded point test stage, the number of embedded point reporting events of each type and the number of pits corresponding to the embedded point reporting events, which occur at the client side, can be counted, so that a tester can find out the situation of more and missing of the embedded point reporting information.

Based on the above, the buried point verification method in the disclosure may further include updating a first number and a second number according to the received buried point reporting information, and displaying the first number and the second number corresponding to the buried point reporting event in response to an operation requesting to display a verification result of the first verification mode, wherein the first number includes the number of the buried point reporting event indicated by the buried point reporting information, and the second number includes the number of buried point pit bits corresponding to the buried point reporting event indicated by the buried point reporting information.

For example, when receiving the report information of the buried point, the report event of the buried point indicated by the report information of the buried point may be determined, and then the number of report events of the buried point is updated, i.e. 1 is added on the basis of the number counted before. The embedded point reporting event indicated by the embedded point reporting information can be understood as an event which causes reporting of the current embedded point information, if a page exposure event occurs currently, and the embedded point information reporting is performed at this time, the number of page exposure events is increased by 1. And determining whether the embedded point report information contains pit positions, if so, judging whether the embedded point report information is generated in the current pit positions in the test process, if so, not performing any processing, and if not, updating the number of the embedded point pit positions corresponding to the embedded point report event indicated by the embedded point report information, namely adding 1 on the basis of the number of the embedded point pit positions corresponding to the embedded point report event counted before.

By updating the first number and the second number of statistics, the accuracy of the time of the buried points and the accuracy of the number of the buried points can be analyzed by the tester. If a point is buried in 7 pit positions aiming at a page exposure event in a certain point burying task, a tester performs 16 times of operations in the testing process, after the tester completes the testing operation, the tester can trigger a first checking mode checking result display control, and then the first quantity and the second quantity corresponding to the point burying reporting event in the testing process can be displayed. If the first number is 16 and the second number is 7, the tester can determine that the point burying time and the point burying pit number of the point burying task are correctly developed.

In an exemplary embodiment, in response to a request to display the first verification result, the verification results of the embedded point report information are sequentially displayed according to the report time of the embedded point report information.

For example, after the test operation is completed, the tester may trigger the first verification mode verification result display control to display the verification result of the reporting information of the buried point according to the sequence of the reporting time of the reporting information of the buried point. The latest embedded point report information may be displayed at the forefront or the latest embedded point report information may be displayed at the rearrear, which is not particularly limited in the present exemplary embodiment. The verification result may include results that are verified, failed, not matched to pit information, failed to verify, etc. The report information of the buried point can be understood to include pit information when the pit information is not matched, but the pit information is not successfully matched with the pits in the target pit library.

In other words, in the verification result display page of the first verification mode, one or more of the first number, the second number, and the display list of the verification results of the embedded point report information sequentially displayed may be displayed. Under the condition that the check result display page of the first check mode comprises a display list of check results of the embedded point reporting information which is sequentially displayed, the trigger operation of the user on the check result record of any embedded point reporting information is responded, and the check details of the embedded point reporting information can be displayed. And reporting information to the embedded points which are not verified, wherein error information prompt can be carried out near the parameters which are not verified in the verification details so as to carry out error prompt on the testers, thereby facilitating the testers to find problems as soon as possible and correct the problems, and further improving the test efficiency.

For example, in the case where the embedded point report information includes the embedded point report information corresponding to the embedded point test task, fig. 5 shows a flowchart of a method for determining whether the embedded point test task is tested to be completed according to an embodiment of the present disclosure. Referring to fig. 5, the method may include steps S510 to S520. In step S510, determining target buried point pit positions comprising enumerated buried point parameters, and in step S520, determining that the buried point test task test is completed under the condition that each enumerated value of each target buried point pit position is successfully matched.

For example, when the information verification of the embedded point report is performed in the embedded point test stage, besides the accuracy of counting the number of the embedded point pits, and avoiding the multiple and leakage of the embedded point pits, the completion of the embedded point test task test is determined only when each enumeration value of each enumeration type of embedded point parameter in each embedded point pit is successfully matched, and the online of the embedded point task is allowed. Thus, the accuracy of the buried point of each buried point task branch can be more completely ensured.

In an exemplary scenario, not all buried parameters may be accurately constrained to a range of values by descriptive rules when performing buried point verification. For example, a certain parameter can only be restricted to be a value which cannot be null by a rule, but cannot be restricted to be a value range by a rule.

Based on the above, in an exemplary embodiment, the method for verifying the buried point in the present disclosure may further include describing, for the target buried point parameter in the buried point report information, that is, the constraint value range without passing the verification rule, and verifying the target buried point parameter according to the candidate value library associated with the target buried point parameter in advance.

For example, for the parameter that cannot describe the value range by a simple rule, the correlation can be performed by correlating with the relevant correct value pseudo table (i.e. the candidate value library) of the buried point parameter stored in the server, and the correctness of the value of the buried point parameter can be checked by including judgment. The parameter is checked by judging whether the value of the parameter is successfully matched with a certain value in the correct value pseudo-table.

Taking the internet easy cloud music client as an example, for example, the value of the internet easy cloud music client cannot be constrained by a simple rule, but the songs included in the internet easy cloud music song list library can be known, so that whether the corresponding song names are in the song list library can be judged according to the reported song name parameters, if so, the verification is passed, and otherwise, the parameter verification fails.

Further, in the present disclosure, in each stage of the buried point development test, the buried point integration, the gray level distribution, and the full-scale distribution, besides performing a value rule check on the value of the buried point parameter and performing a statistical check (such as the check of the first number, the second number, and the enumerated parameters described above), a buried point attribution check may be performed, that is, it may be checked whether the value of the attribution parameter in the buried point report information is correct.

Based on the above, the method for verifying the buried point in the disclosure may further include updating one or more of a third quantity, a fourth quantity, a fifth quantity, a sixth quantity and a seventh quantity according to the buried point attribution parameter value in the buried point attribution information, wherein the third quantity is used for representing the quantity of the buried point attribution information with the empty buried point attribution parameter value, the fourth quantity is used for representing the quantity of the buried point attribution information with the illegal buried point attribution parameter value, the fifth quantity is used for representing the quantity of the buried point attribution information with the unreasonable buried point attribution parameter value, the sixth quantity is used for representing the quantity of the buried point attribution parameter value which is degraded, and the seventh quantity is used for representing the quantity of the buried point attribution parameter value of each type of the buried point reporting event corresponding to the buried point attribution parameter value.

In an exemplary embodiment, the buried point attribution parameter value is determined to be illegal in the case that the pit indicated by the pit information in the buried point attribution parameter value does not belong to the buried point pit, the buried point attribution parameter value is determined to be unreasonable in the case that the to-be-confirmed pit indicated by the pit information in the buried point attribution parameter value belongs to the buried point pit, but the candidate buried point attribution parameter value of the buried point reporting event corresponding to the to-be-confirmed pit information fails to match, and the buried point attribution parameter value is determined to be demoted in the case that a preset field identifier is included in the buried point attribution parameter value, the preset field identifier being used for identifying the generated buried point attribution parameter value after triggering the pit without the buried point object in the application client.

For example, statistics and summarization can be performed on the conditions of empty attribution, illegal attribution pit, unreasonable attribution pit, attribution degradation, attribution type distribution and the like so as to verify the buried point, so that the problems existing in the current buried point are analyzed according to the summarization result, and the buried point is optimized.

Based on the seventh number, the distribution of the values of the buried point-attribution parameters of each type of buried point reporting event can be determined. Taking a song playing event in the internet cloud music client as an example, after the new embedded point task is online in full, counting the number of embedded point attribution parameter values of different types corresponding to the song playing event according to the embedded point task of each version, for example, the embedded point attribution parameter values are the number of search types, the embedded point attribution parameter values are the number of automatic playing types and the like, and then analyzing the duty ratio of the embedded point attribution parameter values of each type. Comparing the current duty ratio with the duty ratio of the previous version to analyze the fluctuation condition of the embedded point of the song playing event, determining whether the embedded point needs to be optimized according to the fluctuation condition or judging whether the embedded point has problems according to the fluctuation condition, if so, determining that the embedded point of the song playing event has problems when the fluctuation exceeds a certain range, further analyzing the cause of the problems, and optimizing and correcting the problems.

By checking the buried point attribution parameters, attribution errors caused by unreasonable business interaction and processing logic and missing buried points can be checked, so that the comprehensiveness of buried point checking is further improved, and the accuracy of subsequent buried points is further improved in an auxiliary manner.

In an exemplary scenario, during any one of the integration stage, gray level distribution, and full level distribution, the relevant site does not exist when the problem occurs, and it is often difficult for the problem to be directly reproduced (when the problem is not in the test stage, the developer uses a test package to test locally and can reproduce the problem), so that the investigation and confirmation of the buried point problem is often a pain point, and great workload is required. Based on the above, in the process of checking the buried point, the method can provide the query capability of the detail buried point log detail of the user by taking the front and back of the buried point with the problem as the anchor point, so as to quickly locate the problem.

In an exemplary embodiment, the embedded point verification method in the disclosure may further include recording embedded point reporting information of an application client according to a reporting time sequence of the embedded point reporting information for any application client, and acquiring other embedded point reporting information within a preset range with the reporting sequence of the target embedded point reporting information in response to a query request of the target embedded point reporting information so as to display the target embedded point reporting information and the other embedded point reporting information. The preset range can be customized according to requirements, such as reporting information of front and back 2 buried points.

For example, the target embedded point report information may include embedded point report information that fails verification. If verification results of the 120 th embedded point report information in the embedded point report information are verification failure, when a user log detail control associated with the 120 th embedded point report information is clicked, 118 th to 122 th embedded point report information can be displayed. Therefore, the current operation path of the user can be automatically restored, so that research personnel can be assisted in analyzing error reasons, and the efficiency of checking the buried point problem is improved.

In one exemplary application scenario, the embedded point reporting information in the present disclosure may include automatically generated embedded point reporting information based on a user's manually triggered operation of an application client.

In another exemplary application scenario, the embedded point reporting information in the present disclosure may further include triggering embedded point reporting information generated by the application client according to a test case of the embedded point test task, where the test case is generated based on the embedded point pit bit to be tested of the embedded point test task.

For example, in the present disclosure, pit positions of buried points are determined based on a buried point object tree, which can accurately describe each buried point position. Therefore, in the embedded point test task, test cases can be written according to all pit positions of the embedded point task to be checked so as to issue a covered user operation path to an application program test client, and full-coverage test before the embedded point task is online is realized through a full-traversal mode, so that the problem of insufficient embedded point coverage possibly caused by manual operation is avoided, the accuracy of embedded point test is improved, and the test efficiency before the embedded point task is online can be improved. And related buried points can be automatically shunted to the buried point management platform for verification in the traversal process, so that a verification result is output, and the full automation of buried point test verification is realized.

Meanwhile, in the process of testing based on manual operation, if the judgment of whether the parameter value exists, whether the parameter value accords with the value taking rule, whether the parameter value is judged to be correct in the candidate value library and other conditions, the logic of whether the parameter value is or not cannot be automatically and accurately checked. For example, for a related song list recommendation card in a song list detail page of the internet easy cloud music, even if the content value of the related song list recommendation card can be checked by carrying out the content judgment through a song list library (i.e. a candidate value library) in the internet easy cloud music, if the song list 1 and the song list 2 are both in the song list library, the current song list cannot be checked, and whether the current song list is truly "song list 1" or not is not "song list 2". By writing the test case, absolute correctness checking can be performed on the value of the embedded point parameter based on the test case, if the embedded point parameter is written in the test case, the song 1 is triggered, and the song reported by the embedded point report information can be compared with the song in the test case, so that automatic correctness checking is performed on the absolute correctness of the content of the song.

In an exemplary embodiment, in a case that the embedded point report information includes the embedded point report information corresponding to the embedded point test task, the embedded point verification method in the present disclosure may further include simulating, by the virtual object, test data corresponding to a test link in the embedded point test task, so as to perform integrity verification on the embedded point test task based on the test link.

For example, although the user's usage data is personalized and its buried results may not be fixed or exhaustive, it is often limited and can be maintained for pages, pits, and logic in the client that generate buried points. Based on the above, for some important scenes, specific data can be issued through a rock (simulation, in the test process, for some objects which are not easy to construct or acquire, a test method of a simulation test is purchased by a mode of creating a virtual object), so that the buried point result of each pit in the scene can be obtained, and a corresponding complete check link is constructed, so that the absolute accuracy of the index caliber of the core scene is ensured. Of course, the integrity of its link may be checked based on the rock for any scenario, which is not particularly limited by the present exemplary embodiment.

Next, fig. 6 shows a multi-terminal interaction flow diagram when performing buried point verification according to an embodiment of the present disclosure. The method includes the steps of firstly, as shown in fig. 6, packing a client, in step S611, generating a unique UUID according to a version of the client when the client packs embedded point reporting information, in step S612, adding the UUID into a packet, and in step S613, uploading the packet UUID, the packet information and the embedded point task to be checked to a packet information database of a server.

The second step is the log reporting procedure of the client, for example, in step S621, the client obtains the UUID in the packet, and in step S622, the embedded point reporting information and the UUID are reported to the server together.

After the server receives the report information of the buried point, the buried point checking flow of the server can be started. For the service end buried point checking flow, in step S631, the service end may determine a buried point task to be checked corresponding to the buried point reporting information from the packet information database according to the packet UUID in the buried point reporting information, so as to determine a target checking rule base and a target pit position base according to the buried point task to be checked, and in step S632, perform rule checking on the buried point reporting information according to the target checking rule base and the target pit position base, and may perform statistical checking, attribution checking, and parameter value coverage checking. After the verification is completed, the server can store the packet UUID, the embedded point reporting information and the verification result together into a log database.

The log database and the packet information database can assist the server to query the log and the report. For example, the complex condition can be converted into a packet list according to the screening condition of the packet, and a large amount of complex packet information can be prevented from being input into the client packet. Based on the query statement including the package UUID, a filtering query can be performed in the log database, so that a log satisfying the auxiliary package screening condition can be obtained.

Fig. 7 shows a flow diagram of another method of verifying an online buried point task in real time according to an embodiment of the present disclosure. Referring to fig. 7, in step S701, the log format of the received report information of the buried point is parsed, in step S702, the packet UUID in the report information of the buried point is extracted, in step S703, a local buffer is obtained according to the packet UUID, in step S704, the check result is calculated, including rule check, attribute check, statistical check (the first number, the second number, the third number, the fourth number, the fifth number, the sixth number and the seventh number as described above), parameter value coverage check (the enumeration value coverage check is performed on the parameters of the enumeration type as described above), in step S705, the check result is submitted to the queue, in step S706, the check result is obtained by the single thread processing flow and submitted to the queue, in step S707, the private to-be-submitted list in the thread is written, in step S708, it is determined whether the number in the to-be-submitted list is greater than the preset value or whether the last writing time occurs before the preset time, if so, then the step S709 is transferred to step S709, otherwise the step S709 is transferred to step S709, the data in the batch is written in the to the database to be submitted, and the database is not processed in the empty list in step S710.

The processing in steps S701 to S705 may be performed by computing threads, where each computing thread corresponds to a part of a message queue, so that multiple message queues or multiple parts of a single thread may be processed by multiple threads at the same time. In step S703, the verification rule may be cached in the local public storage area with the packet UUID as a key and the rule as a value corresponding to the key. The check result in step S705 may be stored in the common memory area, and then, in step S706, the single thread acquires the check result from the queue in the common memory area.

By accumulating a plurality of verification results and writing the verification results into the log database in batches, the number of concurrent writing can be reduced, and the writing stability can be improved.

As described above, the present disclosure may implement buried point verification from different stages, such as a buried point task development stage, a buried point task integration stage, a buried point task gray scale stage, a buried point task online stage, etc., and ensure the comprehensiveness of buried point verification. The method comprises the steps of providing real-time uploading and automatic verification capability of logs through webscoket (protocols for carrying out full duplex communication on single TCP (Transmission Control Protocol, transmission control protocol) connection) through a buried point management platform in a demand development stage, providing timely verification test of demand-oriented increment and historical storage buried points, defining tasks to be verified through establishing accurate association relation between integrated products and synthesized branches and tasks in a demand integration stage, realizing automatic verification of related buried points through internal manual use and machine automation traversal of the integrated products, and carrying out further verification on the buried points through identification (UUID) shunt of the online logs in a demand gray scale and online stage, and simultaneously carrying out accurate verification on fluctuation conditions of the buried points by counting the fluctuation conditions of the buried points. But this may still not guarantee that 100% of all problems are found before being online.

Based on this, a closed-loop manual bill of lading and follow-up procedure can also be established for buried point problems that fail to be found by automatic verification. As shown in fig. 8, in step S801, the business and algorithm parties can analyze whether the reported data table has problems according to their own experience, in step S802, if the data table is clear that there are problems, a data problem list can be listed, and in step S803, the research personnel of the data warehouse can analyze the cause of the problems in the problem list, such as which of task abnormality, buried point abnormality, version problem, etc. And for the data problems determined to be the buried point abnormality, the buried point problem list corresponding to the gray level version and the full online version respectively can be arranged. In step S804, the problem may be confirmed and developed and repaired, and the new buried point and the old buried point may be self-tested.

Through the flow shown in fig. 8, the buried point problem discovered after the line is on line can be timely confirmed and repaired, and the accuracy of the buried point is further ensured.

The buried point verification method provided by the disclosure can effectively realize forward guarantee of the quality of the data buried point, so that buried point problems can be found as early as possible, effective problem finding and intercepting can be formed at various stages of demand development, integrated regression, gray scale online, full-scale online and the like, and the purposes of reducing the data buried point problems, accelerating the problem finding speed, improving the problem positioning and solving the speed can be achieved.

Furthermore, the buried point verification method in the present disclosure is to perform verification for buried point objects, and has good expansibility and universality, and is suitable for any business and large front end platform frames.

Meanwhile, the buried point verification method can verify the buried point at each stage, and the accuracy of buried point data is comprehensively guaranteed.

Exemplary apparatus

The exemplary embodiment of the disclosure also provides a buried point checking device. Referring to fig. 9, the buried point verifying apparatus 900 may include a buried point information receiving module 910 and a verifying module 920. Wherein:

a buried point information receiving module 910 configured to receive buried point reporting information of an application client, and match the buried point information with a buried point in a target buried point library in response to the buried point reporting information including the buried point information;

and the verification module 920 is configured to verify the report information of the buried point based on a target verification rule base according to the matching result.

In an alternative implementation manner, based on the foregoing embodiment, the target pit location library and the target verification rule library are determined according to the buried points in the buried point task to be verified.

In an alternative implementation manner, based on the foregoing embodiment, the verification module 920 may be specifically configured to obtain, in response to successful matching, a buried point object identifier included in the pit information, and for each buried point object identifier, verify, based on a verification rule of a first buried point parameter associated with the buried point object identifier in the target verification rule base, a first buried point parameter in the buried point report information.

In an alternative embodiment, based on the foregoing embodiment, the verification module 920 may be specifically configured to add a tag with a pit matching failure to the embedded point report information in response to a matching failure.

In an alternative embodiment, the embedded point verification device 900 may further include a second embedded point parameter verification module and/or a third embedded point parameter verification module, where the second embedded point parameter verification module is configured to determine, after receiving the embedded point reporting information of the application client, a second embedded point parameter associated with an embedded point reporting event that triggers the embedded point reporting information, verify the second embedded point parameter in the embedded point reporting information according to a verification rule of the second embedded point parameter in the target verification rule base, and the third embedded point parameter verification module is configured to verify the common parameter in the embedded point reporting information according to a verification rule corresponding to the common parameter in the target verification rule base.

In an optional implementation manner, in a case where the embedded point report information includes embedded point report information corresponding to an embedded point test task, the embedded point task to be checked includes a first embedded point task in the embedded point test task and a second embedded point task on which an application program for which the embedded point test task is directed is online.

In an optional implementation manner, the method for determining the to-be-verified buried point task includes obtaining a value of a preset field in the buried point report information, and determining the to-be-verified buried point task according to the value of the preset field, wherein the preset field is used for indicating a version of the application program client, and the to-be-verified buried point task includes an online buried point task corresponding to the version of the application program client.

In an alternative implementation manner, the embedded point verification device 900 may further include a quantity display module, wherein the quantity display module includes an updating unit and a display unit, the updating unit is configured to update a first quantity and a second quantity according to the received embedded point reporting information, the display unit is configured to display the first quantity and the second quantity corresponding to the embedded point reporting event in response to an operation of requesting to display the verification result of the first verification mode, and the first quantity includes the quantity of the embedded point reporting event indicated by the embedded point reporting information, and the second quantity includes the quantity of the embedded point pit bits corresponding to the embedded point reporting event indicated by the embedded point reporting information.

In an alternative embodiment, the embedded point verification device 900 may further include a sequential display verification result module, where the sequential display verification result module is configured to respond to an operation of requesting to display the verification result of the first verification mode, and sequentially display the verification result of the embedded point report information according to the report time of the embedded point report information.

In an alternative embodiment, in a case where the report information of the buried point includes report information of a buried point corresponding to a test task of the buried point, the apparatus 900 may further include a task completion checking module configured to determine a target buried point pit including an enumerated type of buried point parameter, and determine that the test task of the buried point test is completed if each enumerated value of each target buried point pit matches successfully.

In an optional implementation manner, the buried point verification device may further include a candidate verification module, wherein the candidate verification module is configured to verify the target buried point parameter according to a candidate value library associated with the target buried point parameter in advance, aiming at the target buried point parameter of which the constraint value range is not described by a verification rule in the buried point report information.

In an alternative implementation mode, the buried point verification device further comprises a quantity updating module, wherein the quantity updating module is configured to update one or more of a third quantity, a fourth quantity, a fifth quantity, a sixth quantity and a seventh quantity according to the buried point attribution parameter value in the buried point attribution information, the third quantity is used for representing the quantity of buried point attribution information with the empty buried point attribution parameter value, the fourth quantity is used for representing the quantity of buried point attribution information with the illegal buried point attribution parameter value, the fifth quantity is used for representing the quantity of buried point attribution information with the unreasonable buried point attribution parameter value, the sixth quantity is used for representing the quantity of buried point attribution parameter values of various types of buried point attribution parameter values corresponding to the buried point attribution information, in the case that the buried point attribution parameter value is not in a buried point position, the buried point attribution parameter value is not in a buried point attribution, the condition that the buried point attribution parameter value is not in a buried point attribution point, the buried point attribution parameter value is not in a buried point attribution, the condition that the information is not in a buried point attribution parameter value is not in a buried point, the buried point attribution parameter value is not in a buried point, the field, and the attribution parameter value is not in a predetermined condition that the information is not in a buried point attribution parameter value is not in a map, and is detected, and the condition that the attribution parameter value is not in a map-used to a map, is determined is used to confirm to a map.

In an optional implementation manner, the embedded point verification device may further include a detail display module, wherein the detail display module is configured to record embedded point reporting information of any application program client according to a reporting time sequence of the embedded point reporting information, respond to a query request of target embedded point reporting information, and acquire other embedded point reporting information which is within a preset range with the reporting sequence of the target embedded point reporting information so as to display the target embedded point reporting information and the other embedded point reporting information.

In an alternative embodiment, in the case that the report information of the buried point includes the report information of the buried point corresponding to the test task of the buried point, the buried point checking device may further include an integrity checking module configured to simulate the test link corresponding to the test task of the buried point through the virtual object.

In addition, other specific details of the embodiments of the present disclosure are described in the foregoing embodiments of the method, and are not described herein.

Exemplary storage Medium

A storage medium according to an exemplary embodiment of the present disclosure is described below.

In the present exemplary embodiment, the above-described method may be implemented by a program product, such as a portable compact disc read only memory (CD-ROM) and including program code, and may be run on a device, such as a personal computer. However, the program product of the present disclosure is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of a readable storage medium include an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The computer readable signal medium may include a data signal propagated in baseband or as part of a carrier wave with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RE, etc., or any suitable combination of the foregoing.

Program code for carrying out operations of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).

Exemplary electronic device

An electronic device of an exemplary embodiment of the present disclosure is described with reference to fig. 10. The electronic device may be a client or a server.

The electronic device 1000 shown in fig. 10 is merely an example and should not be construed as limiting the functionality and scope of use of the disclosed embodiments.

As shown in fig. 10, the electronic device 1000 is embodied in the form of a general purpose computing device. Components of electronic device 1000 may include, but are not limited to, at least one processing unit 1010, at least one memory unit 1020, a bus 1030 connecting different system components (including memory unit 1020 and processing unit 1010), and a display unit 1040.

Wherein the storage unit stores program code that is executable by the processing unit 1010 such that the processing unit 1010 performs steps according to various exemplary embodiments of the present disclosure described in the above section of the present specification. For example, the processing unit 1010 may perform the method steps shown in fig. 1, etc.

The memory unit 1020 may include volatile memory units such as a random access memory unit (RAM) 1021 and/or a cache memory unit 1022, and may further include a read only memory unit (ROM) 1023.

Storage unit 1020 may also include a program/utility 1024 having a set (at least one) of program modules 1025, such program modules 1025 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.

Bus 1030 may include a data bus, an address bus, and a control bus.

The electronic device 1000 can also communicate with one or more external devices 1100 (e.g., keyboard, pointing device, bluetooth device, etc.) through input/output (I/O) interface 1050. The electronic device 1000 also includes a display unit 1040 that is connected to an input/output (I/O) interface 1050 for displaying. Also, electronic device 1000 can communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet, through network adapter 1060. As shown, the network adapter 1060 communicates with other modules of the electronic device 1000 over the bus 1030. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with the electronic device 1000, including, but not limited to, microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.

It should be noted that while several modules or sub-modules of the apparatus are mentioned in the detailed description above, such partitioning is merely exemplary and not mandatory. Indeed, the features and functionality of two or more units/modules described above may be embodied in one unit/module in accordance with embodiments of the present disclosure. Conversely, the features and functions of one unit/module described above may be further divided into ones that are embodied by a plurality of units/modules.

Furthermore, although the operations of the methods of the present disclosure are depicted in the drawings in a particular order, this is not required or suggested that these operations must be performed in this particular order or that all of the illustrated operations must be performed in order to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step to perform, and/or one step decomposed into multiple steps to perform.

While the spirit and principles of the present disclosure have been described with reference to several particular embodiments, it is to be understood that this disclosure is not limited to the particular embodiments disclosed nor does it imply that features in these aspects are not to be combined to benefit from this division, which is done for convenience of description only. The disclosure is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

Claims

1. The buried point checking method is characterized by comprising the following steps of:

receiving embedded point report information of an application program client, and matching the embedded point information with a pit in a target pit library in response to the embedded point report information including the pit information;

according to the matching result, checking the reported information of the buried points based on a target checking rule base;

the target pit position library and the target verification rule library are determined according to the buried points in the buried point task to be verified;

Updating one or more of the third quantity, the fourth quantity, the fifth quantity, the sixth quantity and the seventh quantity according to the buried point attribution parameter value in the buried point reporting information;

The third quantity is used for representing the quantity of the embedded point reporting information with the empty embedded point attribution parameter value, the fourth quantity is used for representing the quantity of the embedded point reporting information with the illegal embedded point attribution parameter value, the fifth quantity is used for representing the quantity of the embedded point reporting information with the unreasonable embedded point attribution parameter value, the sixth quantity is used for representing the quantity of the embedded point reporting information with the degraded embedded point attribution parameter value, and the seventh quantity is used for representing the quantity of the embedded point attribution parameter values of various types of the embedded point reporting events corresponding to the embedded point reporting information;

Determining that the buried point attribution parameter value is illegal under the condition that pit information in the buried point attribution parameter value indicates that pit does not belong to the buried point pit;

Determining that the buried point attribution parameter value is unreasonable under the condition that the to-be-confirmed pit indicated by the pit information in the buried point attribution parameter value belongs to the buried point pit, but the matching of the to-be-confirmed pit and the pit information in the candidate buried point attribution parameter value of the buried point reporting event corresponding to the buried point reporting information fails;

Determining that the buried point attribution parameter value is degraded under the condition that the buried point attribution parameter value comprises a preset field identifier, wherein the preset field identifier is used for identifying the generated buried point attribution parameter value after triggering pit positions without buried point objects in the application program client;

Wherein the pit bit is the only location in the client application that can be described.

2. The method for checking the buried point according to claim 1, wherein the checking the reported information of the buried point based on the target checking rule base according to the matching result comprises:

acquiring a buried point object identifier included in the pit information in response to successful matching;

And aiming at each buried point object identifier, checking the first buried point parameter in the buried point reporting information based on the checking rule of the first buried point parameter associated with the buried point object identifier in the target checking rule base.

3. The method for checking the buried point according to claim 1, wherein the checking the reported information of the buried point based on the target checking rule base according to the matching result comprises:

And responding to the matching failure, and adding a tag with failed pit matching for the embedded point reporting information.

4. The embedded point verification method according to claim 1, wherein after receiving the embedded point report information of the application client, the method further comprises:

Determining a second buried point parameter associated with a buried point reporting event triggering the buried point reporting information, and checking the second buried point parameter in the buried point reporting information according to a checking rule of the second buried point parameter in the target checking rule base, and/or

And checking the public parameters in the embedded point reporting information according to the checking rules corresponding to the public parameters in the target checking rule library.

5. The method according to claim 1, wherein in the case where the report information of the buried point includes report information of a buried point corresponding to a buried point test task, the buried point task to be verified includes a first buried point task of the buried point test task and a second buried point task of which an application program for the buried point test task is online.

6. The method for verifying a buried point according to claim 1, wherein the determining manner of the buried point task to be verified includes:

acquiring a value of a preset field in the embedded point reporting information, and determining the embedded point task to be checked according to the value of the preset field;

the preset field is used for indicating the version of the application program client, and the to-be-verified embedded point task comprises an online embedded point task corresponding to the version of the application program client.

7. The method of buried point verification according to claim 1, further comprising:

Updating the first quantity and the second quantity according to the received report information of the buried points;

responding to the operation of requesting to display the verification result of the first verification mode, and displaying the first quantity and the second quantity corresponding to the embedded point reporting event;

the first number includes the number of buried point reporting events indicated by the buried point reporting information, and the second number includes the number of buried point pits corresponding to the buried point reporting events indicated by the buried point reporting information.

8. The method of buried point verification according to claim 1, further comprising:

and responding to the operation of requesting to display the check result of the first check mode, and sequentially displaying the check result of the report information of the buried point according to the report time of the report information of the buried point.

9. The method according to claim 1, wherein in a case where the report information of the buried point includes report information of the buried point corresponding to the buried point test task, the method further comprises:

Determining a target buried point pit position comprising an enumeration type buried point parameter;

and under the condition that each enumeration value of each target buried point pit position is successfully matched, determining that the buried point test task test is completed.

10. The buried point verification method according to any one of claims 1 to 9, further comprising:

And describing target buried point parameters of a constraint value range according to a verification rule not passing through the buried point reporting information, and verifying the target buried point parameters according to a candidate value library which is associated with the target buried point parameters in advance.

11. The method of buried point verification according to claim 1, further comprising:

Recording embedded point reporting information of an application program client according to the reporting time sequence of the embedded point reporting information aiming at any application program client;

And responding to a query request of reporting information of the target embedded point, and acquiring other embedded point reporting information of which the reporting sequence of the reporting information of the target embedded point is within a preset range so as to display the reporting information of the target embedded point and the reporting information of the other embedded points.

12. The method of claim 1, wherein the embedded point report information includes embedded point report information generated by the application client triggered according to a test case of an embedded point test task, wherein the test case is generated based on an embedded point pit bit to be tested of the embedded point test task.

13. The method according to claim 1, wherein in a case where the report information of the buried point includes report information of the buried point corresponding to the buried point test task, the method further comprises:

And simulating test data corresponding to the test link in the embedded point test task through the virtual object so as to carry out integrity check on the embedded point test task based on the test link.

14. A buried point verification device, comprising:

the embedded point information receiving module is configured to receive embedded point reporting information of an application program client, and match the embedded point information with pits in a target pit library in response to the embedded point reporting information including pit information;

The verification module is configured to verify the information reported by the buried points based on a target verification rule base according to the matching result;

15. A computer readable storage medium, on which a computer program is stored, which computer program, when being executed by a processor, implements the method of any one of claims 1 to 13.

16. An electronic device, comprising:

One or more processors;

Storage means for storing one or more programs which when executed by the one or more processors cause the one or more processors to implement the method of any of claims 1 to 13.