A method and device for testing buried points

Abstract

The present application relates to a method and device for burying point testing, the method comprising: obtaining burying point data of a client, wherein the burying point data is generated based on detected user operations; when identifying and generating burying point data, applying the environment of the client as an environment identification result; according to the environment identification result, performing burying point testing based on the burying point data to obtain the result of the burying point testing, wherein the burying point testing method comprises a first method and a second method, if the environment identification result shows that the current environment is a test environment, the burying point data is processed in the first method, if the environment identification result shows that the current environment is an online use environment, the burying point data is processed in the second method, and the second method is obtained by removing the burying point coverage completeness test in the first method. The burying point testing method and device in this specification adopt different testing methods for different environments. Among them, the online use process does not need to detect the completeness of the burying points.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a buried point testing method and device. Background Art

[0002] With the development of the Internet, people are becoming more and more dependent on the Internet, and their daily lives are often closely related to the client. In order to better serve users, data embedding technology has emerged.

[0003] Usually, client developers will set tracking points in the client, and then the tracking point data collected by the tracking point can be applied to multiple fields such as big data analysis. If the tracking point performance is poor, it may cause the collected tracking point data to be abnormal, and data processing based on abnormal tracking point data may lead to adverse consequences.

[0004] During the online use of the client, the server usually tests the tracking points in multiple clients at the same time, which may cause too many clients to be tested, resulting in server overload. Summary of the invention

[0005] The present application provides a method and device for tracking test to solve the problem in the prior art that it is difficult to coordinate the tracking test process with the processing capability of the server.

[0006] In a first aspect, the present application provides a method for tracking test points, which is applied to a server and includes:

[0007] Acquire the client's buried point data, wherein the buried point data is generated based on the detected user operation; determine the operating environment when the client generates the buried point data based on the buried point data as the environment identification result; according to the environment identification result, perform a buried point test based on the buried point data to obtain a result of the buried point test, wherein the buried point test method includes a first method and a second method, if the environment identification result shows that the current operating environment is a test environment, then the first method is used to process the buried point data, if the environment identification result shows that the current operating environment is an online use environment, then the second method is used to process the buried point data, and the second method is obtained by removing the buried point coverage completeness test in the first method.

[0008] In an optional embodiment of the present specification, the buried point data includes a key for identifying the buried point and a value corresponding to the key, wherein a buried point test is performed based on the buried point data to obtain the result of the buried point test, including: for each buried point, if there is a value corresponding to the key of the buried point in the buried point data, then the buried point is determined to be a valid buried point as the buried point coverage completeness test result of the buried point; if there is no value corresponding to the key of the buried point in the buried point data, then the buried point is determined to be an invalid buried point as the buried point coverage completeness test result of the buried point.

[0009] In an optional embodiment of the present specification, at least one of the first method and the second method includes a buried point setting accuracy test, and the buried point data includes a key for identifying the buried point and a value corresponding to the key, wherein the buried point test is performed based on the buried point data to obtain a result of the buried point test, including: for each value in the buried point data, if the value is within the value range defined by the protocol, then the valid buried point is used as the buried point setting accuracy test result of the buried point identified by the key corresponding to the value; if the value is not within the value range defined by the protocol, then the invalid buried point is used as the buried point setting accuracy test result of the buried point identified by the key corresponding to the value.

[0010] In an optional embodiment of the present specification, before executing the buried point test based on the buried point data, the method also includes: determining a reference key; for each value in the buried point data, if the key-value pair to which the value belongs has a preceding key, then storing the value when the preceding key matches the reference key; executing the buried point test based on the buried point data, including: executing the buried point test based on each stored value.

[0011] In an optional embodiment of the present specification, the first method is used to process the buried point data, including: after obtaining the result of the buried point test, determining the data processing efficiency of the server during the test; if the data processing efficiency is greater than or equal to the efficiency threshold, increasing the amount of simulated users in the test environment so that the client regenerates the buried point data according to the detected user operation of adding users, and sends it to the test server; if the data processing efficiency is less than the efficiency threshold, determining the current amount of simulated users as a specified number, wherein the specified number represents the data processing performance of the server; obtaining the buried point data resent by the client; based on the buried point data resent by the client, processing the buried point data using the first method to obtain the result of the buried point test again, and updating the data processing efficiency of the server during this test until the data processing efficiency is less than the efficiency threshold; storing the specified number.

[0012] In a second aspect, the present application provides a method for processing buried point data, characterized in that the method is applied to a client, and the method includes: storing pending data locally, wherein the pending data is generated based on the data collection method shown by the buried point and according to the detected user operation; obtaining the amount of pending data stored locally, and determining the actual length of time from the current moment to the last time the buried point data was sent to the server; if at least one of the sending conditions is met, the locally stored pending data is determined as buried point data, wherein the sending conditions include: the amount of pending data stored locally is greater than or equal to a first quantity threshold, and the actual duration is greater than or equal to a duration threshold; and sending the buried point data to the server.

[0013] In an optional embodiment of the present specification, after sending the burial point data to the server, the method further includes: deleting the locally stored burial point data; if at least one of the sending conditions is met, then determining the locally stored pending data as the burial point data, the method further includes: if the amount of the locally stored burial point data is greater than or equal to a second quantity threshold, then deleting the locally stored burial point data.

[0014] In the third aspect, the present application provides a tracking point testing device, which is applied to the server side, including: a tracking point data acquisition module, configured to: obtain the tracking point data of the client, wherein the tracking point data is generated according to the detected user operation. An environment identification module, configured to: identify the operating environment of the client when generating the tracking point data, as the environment identification result. A testing module, configured to: perform tracking point testing based on the tracking point data according to the environment identification result, and obtain the result of the tracking point testing, wherein the tracking point testing method includes a first method and a second method, if the environment identification result shows that the current operating environment is a test environment, the first method is used to process the tracking point data, if the environment identification result shows that the current operating environment is an online use environment, the second method is used to process the tracking point data, and the second method is obtained by removing the tracking point coverage completeness test in the first method.

[0015] In a fourth aspect, the present application provides a point-of-sale data processing device, which is applied to a client, including:

[0016] The pending data storage module is configured to store the pending data locally, wherein the pending data is generated based on the data collection method shown by the buried point and according to the detected user operation. The actual duration determination module is configured to obtain the amount of pending data stored locally and determine the actual duration from the current moment to the last time the buried point data was sent to the server. The sending condition judgment module is configured to determine the locally stored pending data as buried point data if at least one of the sending conditions is met, wherein the sending conditions include: the amount of locally stored pending data is greater than or equal to the first quantity threshold, and the actual duration is greater than or equal to the duration threshold. The sending module is configured to send the buried point data to the server.

[0017] In a fifth aspect, the present application provides an electronic device, including a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus;

[0018] Memory, used to store computer programs;

[0019] The processor is used to implement the steps of any buried point testing method in the first aspect, or implement the steps of any buried point data processing method in the second aspect when executing the program stored in the memory.

[0020] In a sixth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, characterized in that when the computer program is executed by a processor, the computer program implements the steps of any of the buried point testing methods in the first aspect, or implements the steps of any of the buried point data processing methods in the second aspect.

[0021] The above technical solution provided by the embodiment of the present application has the following advantages compared with the prior art:

[0022] The tracking point testing method and device in this specification adopt different testing methods for different operating environments. In this specification, the tracking point completeness test is completed in the test environment, which ensures that the tracking points in the client can meet the server's requirements for tracking point performance to a large extent. In the subsequent online use process, there is no need to test the completeness of the tracking points, which effectively reduces the pressure of the server on tracking point detection during the online use of the client. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0024] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0025] Figure 1 A schematic diagram of a scenario involved in a tracking point test process provided in an embodiment of the present application;

[0026] Figure 2 A schematic diagram of a process flow of a buried point test process provided in an embodiment of the present application;

[0027] Figure 3 A flowchart of a data processing process for a buried point provided in an embodiment of the present application;

[0028] Figure 4 To correspond to Figure 2 A schematic diagram of a buried point test device for some steps of the method process;

[0029] Figure 5 To correspond to Figure 3 A schematic diagram of a buried point data processing device for some steps of the method process;

[0030] Figure 6 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0031] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0032] In the scenarios involved in the execution of the tracking test method in this specification, the server can be connected to one or more clients. Figure 1 In the scenario shown, the server is connected to n clients. This specification does not limit the specific types of the server and the client. For example, in an optional embodiment of this specification, at least one of the server and the client is a hardware device. In another optional embodiment of this specification, at least one of the server and the client is an application.

[0033] The tracking point test method in this specification is at least applicable to the scenario where the test environment and the online use environment are switched. In the test environment, the client can be a virtual client.

[0034] like Figure 2 As shown, the buried point test method in this specification may include the following steps:

[0035] S200: Obtain the client's tracking data.

[0036] Among them, the buried point data is generated based on the tested user operations. In the test environment, the user operations can be virtual user operations. The buried points involved in the process in this description may not be unique, so the buried point data obtained may not be unique. The buried point data obtained in this step can be data collected at a certain moment, or it can be data collected within a certain time period.

[0037] The tracking point in this specification may be a section of code executed by the client, and the tracking point data may be data collected by the client during the process of executing the code represented by the tracking point.

[0038] S202: Determine the operating environment when the client generates the burying point data based on the burying point data, as the environment identification result.

[0039] In an optional embodiment of the present specification, the buried point data plays a triggering role in this step, and the server is triggered to identify the client's operating environment when the buried point data is obtained. In another optional embodiment of the present specification, the server can parse the buried point data to obtain information representing the client's operating environment. In another optional embodiment of the present specification, the buried point data can play the role of both triggering and providing information about the client's operating environment in this step.

[0040] The operating environment of the client in this specification includes at least a test environment and an online use environment. The processes in this specification are for scenarios where the test environment and the online use environment can be switched. In the test environment, since the tracking points have not yet been deployed online at this time, there is still a strong adjustment capability for the tracking points, and the testing of the tracking points will not affect the users using the client, so the tracking points can be tested more comprehensively. Even if a large test overhead is generated during the test process, there is no need to worry about the test process in the test environment having a negative impact on the user experience, so that the comprehensiveness of the test can be prioritized in the test environment.

[0041] In the online usage environment, on the one hand, it is necessary to achieve the purpose of tracking test, and on the other hand, it is necessary to avoid affecting the user experience when using the client. In view of this, this manual determines what test method to use for tracking by identifying the steps of the current running environment.

[0042] In an optional embodiment of the present specification, the client executes a specified script to obtain its installation location in the terminal and / or the unique identifier of the terminal on which the client is installed as the specified data. If the specified data can be obtained (exemplarily, the obtained specified data is not empty), it indicates that the client is a real client and the operating environment of the application client is an online use environment, then the first data is added to the specified field to obtain the buried point data. If the specified data cannot be obtained (exemplarily, the obtained specified data is empty), it indicates that the client is a virtual client and the operating environment of the application client is a test environment, then the second data is added to the specified field to obtain the buried point data.

[0043] After receiving the tracking data, the server can identify that the current operating environment is a test environment based on the data in the specified field. If the specified field is filled with the first data, the current operating environment is an online use environment. If the specified field is filled with the second data, the current operating environment is a test environment.

[0044] S204: According to the environmental recognition result, a buried point test is performed based on the buried point data to obtain a result of the buried point test.

[0045] The process in this specification is to achieve the testing purpose in both the test environment and the online use environment, and in the test environment, the comprehensiveness of the test is prioritized, and in the online use environment, the user experience is prioritized. The methods of point-of-sale testing used in the test process in this specification include the first method and the second method. If the environment identification result shows that the current operating environment is a test environment, the first method is used to process the point-of-sale data. If the environment identification result shows that the current operating environment is an online use environment, the second method is used to process the point-of-sale data. The second method is obtained by removing the completeness test from the first method.

[0046] The tracking point coverage completeness test usually needs to traverse each tracking point, and a certain amount of resources will be consumed during the test. If the tracking point coverage completeness test is implemented during online use, on the one hand, it will occupy the data processing resources of the terminal where the client is installed. On the other hand, when the client sends the tracking point data collected during the tracking point coverage completeness test to the server, it will consume the user's traffic resources and bring a negative experience to the user.

[0047] In this specification, the purpose of the buried point coverage completeness test is to test whether the buried point data corresponding to the buried point can be collected to identify whether the buried point is a redundant buried point. If the buried point data corresponding to the buried point cannot be collected, it indicates that the buried point is a redundant buried point. If the buried point data corresponding to the buried point can be collected, it indicates that the buried point is not a redundant buried point. If the buried point coverage completeness test for the buried point in the test environment is completed before the test of the online use environment, the test purpose can be achieved even if the buried point coverage completeness test is not performed in the online use environment.

[0048] It should be noted that, in an optional embodiment of the present specification, the result obtained by removing the buried point coverage completeness test in the first method can be directly used as the second method.

[0049] In another optional embodiment of this specification, other test items can be added to the result obtained by removing the buried point coverage completeness test in the first method, or other test items can be removed to obtain the second method. It can be seen that the first method and the second method in this specification can also differ in other test items besides whether they include the buried point coverage completeness test, which will not be described one by one here.

[0050] The buried point data used in the process of this specification can be data collected based on the buried points within a specified period (preset), or the buried point data can be data collected in real time based on the buried points.

[0051] In an optional embodiment of the present specification, each buried point data contains an identification field and a value field. The identification field is added with the key of the buried point corresponding to the buried point data, and the value field is added with the value corresponding to the buried point data. The key is identified from the buried point when the client executes the buried point, and the value is collected by the client when executing the buried point.

[0052] The process of the buried point coverage completeness test can be: obtain the key of each buried point (the key of the buried point is used to identify the purchase order), and establish a first corresponding table of key-value relationships. Search in the buried point data, for each buried point (specifically, for each key in the first corresponding table of key-value relationships), if there is a value corresponding to the key of the buried point (the key can be recorded in the first corresponding table of key-value relationships) in the buried point data, then the buried point is determined to be a valid buried point as the buried point coverage completeness test result of the buried point, if there is no value corresponding to the key of the buried point in the buried point data, then the buried point is determined to be an invalid buried point as the buried point coverage completeness test result of the buried point. Optionally, the first corresponding table of key-value relationships may include a first column for recording keys and a second column for recording values. In the process of performing the buried point coverage completeness test, the value determined for each key can be added to the corresponding position in the second column. This is to achieve the recording of the buried point coverage completeness test results.

[0053] The point coverage completeness test can be performed in real time. After obtaining a point data, the point coverage completeness test result based on the obtained point data is completed. After performing the point coverage completeness test on all points, the point coverage completeness test results of each point are summarized to obtain the first result, and then subsequent processing can be performed based on the first result.

[0054] Optionally, after the coverage completeness test of the tracking points is completed, the invalid tracking points among the tracking points are deleted, and the remaining valid tracking points are used as the tracking points for application in the online usage environment.

[0055] In an optional embodiment of the present specification, at least one of the first method and the second method for implementing the test of the buried point includes a buried point setting accuracy test. The process of the buried point setting accuracy test can be: for each value in the buried point data, if the value is within the value range defined by the protocol, the valid buried point is determined as the buried point setting accuracy test result of the buried point corresponding to the value; if the value is not within the value range defined by the protocol, the invalid buried point is determined as the buried point setting accuracy test result of the buried point corresponding to the value.

[0056] Optionally, a second corresponding table of key-value relationships can be established, in which the keys of various buried points are pre-added (can be added to the first column of the second corresponding table of key-value relationships), and for each key, the value corresponding to the key is screened out in the buried point data, and if the value is within the value range defined by the protocol (preset), the value is added to the second corresponding table of key-value relationships (can be added to the second column of the second corresponding table of key-value relationships) until the second corresponding table of key-value relationships is traversed. There are no values ​​outside the value range defined by the protocol in the second corresponding table of key-value relationships, which facilitates improving the subsequent processing efficiency of the values ​​in the second corresponding table of key-value relationships.

[0057] In addition, in another optional embodiment, a blank second corresponding table of key-value relationships may be pre-established, and then the key of each buried point and the value corresponding to the key of each buried point may be identified from the buried point data.

[0058] Optionally, after executing several accuracy tests on the setting of embedding points, if the proportion of empty values ​​in the second corresponding table of the key-value relationship obtained in each accuracy test of the setting of a certain embedding point is greater than a preset proportion threshold, it indicates that the values ​​collected when the client executes the embedding point are often outside the value range defined by the protocol, and the setting of the embedding point may be unreasonable. The embedding point is determined to be an invalid embedding point, so that corresponding adjustments can be made to the invalid embedding point in subsequent steps.

[0059] In an optional embodiment of the present specification, the key-value relationship may be a one-to-one correspondence between a key Key and a value Value, and may have the following format: (Key-Value). In another optional embodiment of the present specification, the key-value relationship may be a correspondence between a prefix key Krefix key, a key Key, and a value Value, and may be represented in the following format: [Krefix key–(Key–Value)].

[0060] In order to match the corresponding relationship with the leading key, the tracking data includes the leading key field and the combination field. The combination field is composed of the identification field and the value field. The leading key function can be determined according to the actual business needs.

[0061] In an optional embodiment of the present specification, the leading key is used to identify the source of the data (the data can be presented in the following forms: control, page, icon, text box) targeted by the user operation (such as single click operation, double click operation, sliding operation, etc.). The source can be shared by other users (for example, the corresponding leading key is S in this case), and the source can be pushed by an advertising platform (for example, the corresponding leading key is P in this case).

[0062] In other optional embodiments of the present specification, the prefix key may also have other identification functions besides the data source, which are not listed here one by one.

[0063] Based on the data format with a prefix key, in an optional embodiment of the present specification, after acquiring the buried data, the reference key is first determined (for example, S is a reference key, and P is not a reference key). For each value in the buried data, if the key-value pair to which the value belongs has a prefix key, the value is stored if the prefix key matches the reference key (for example, the same). Then, based on the stored values, a buried test is performed. For buried data whose prefix key does not match the reference key, it can be deleted or handed over to other departments for processing.

[0064] In a further optional embodiment of the present specification, the burying point test process in the present specification can not only achieve the purpose of testing the burying point, but also test the pressure bearing capacity of the server while testing the burying point to determine the data processing capacity of the server. Specifically, the process of determining the pressure bearing capacity of the server can be to determine the data processing efficiency of the server during the test after obtaining the result of the burying point test (when the burying point test includes k times, it can be after each test result is obtained, or after all the results of k times are obtained). If the data processing efficiency is greater than or equal to the efficiency threshold, the amount of simulated users in the test environment is increased so that the client regenerates the burying point data according to the detected user operation of adding users and sends it to the test server; if the data processing efficiency is less than the efficiency threshold, the current amount of simulated users is determined to be a specified number, wherein the specified number represents the data processing performance of the server, and the larger the specified number, the greater the data processing performance of the server. Obtain the burying point data resent by the client. Based on the burying point data resent by the client, the burying point data is processed in the first way to obtain the result of the burying point test again, and the data processing efficiency of the server during this test is updated until the data processing efficiency is less than the efficiency threshold. The specified amount of storage identifies the maximum data processing capacity of the server under ideal conditions.

[0065] Among them, the definition of data processing efficiency can be determined according to actual needs. For example, the average response time of the server to the buried data is negatively correlated with the data processing efficiency.

[0066] The above are mainly the steps performed by the server in the tracking point test process in this manual. Now the steps performed by the client in the tracking point test process are described. Figure 3 In this manual, the client has pre-set embedding points.

[0067] S300: Storing the pending data locally.

[0068] The pending data is generated based on the data collection method shown by the buried points and according to the detected user operations.

[0069] S302: Obtain the amount of pending data stored locally, and determine the actual length of time from the current time to the last time the tracking data was sent to the server.

[0070] S304: If at least one of the sending conditions is met, the pending data stored locally is determined as buried point data.

[0071] The sending conditions may include: the amount (size) of the locally stored pending data is greater than or equal to a first quantity threshold, and the actual duration (time) is greater than or equal to a duration threshold.

[0072] S306: Send the tracking data to the server.

[0073] Optionally, after sending the tracking data to the server, the locally stored tracking data is deleted.

[0074] In the process of this specification, the client collects pending data according to the data collection method shown by the buried point (that is, the data collected by the client executing the code shown by the buried point) and will not send it to the server immediately. On the one hand, the frequent transmission of data will occupy the communication resources of the terminal to which the client belongs, and on the other hand, it will also occupy the communication resources of the server. The process in this specification can effectively reduce the communication resources consumed by the communication between the client and the server, and avoid affecting the performance of other functions of the client.

[0075] In an optional embodiment of the present specification, if the amount of locally stored burial point data is greater than or equal to a second quantity threshold, the locally stored burial point data is deleted.

[0076] In the actual application process, the client may provide some offline services, or it may be used offline due to network disconnection and other phenomena. At this time, the buried point data collected based on the buried point continues to accumulate locally and cannot be sent to the server. By setting the sending conditions according to the actual duration, it is also possible to timely clean up the locally stored and relatively old buried point data. On the one hand, the relatively old buried point data may have lost its processing value. On the other hand, it can also release the local storage space of the client. The second quantity threshold identifies the amount of locally stored buried point data at which the buried point data should be deleted.

[0077] Optionally, the deletion of the buried data based on the second quantity threshold will not affect the storage of the pending data by the client. That is, before the pending data is determined to be buried data, the pending data will not be deleted based on the determination of the second quantity threshold.

[0078] At least one of the first quantity threshold and the second quantity threshold in this specification may be an empirical value. In addition, in other optional embodiments, the second quantity threshold may be obtained from the server. Specifically, the server determines the number of clients that maintain communication connections with it and the amount of buried data received within the specified time interval (preset) at specified time intervals. The second quantity threshold is obtained based on the determined number of clients and the amount of buried data, and the second quantity threshold is negatively correlated with the number of clients and negatively correlated with the amount of buried data.

[0079] Based on the same idea, this specification further provides a buried point test device, which is applied to the server, such as Figure 4 As shown, the buried point test device includes one or more of the following modules:

[0080] The buried point data acquisition module 400 is configured to: acquire the buried point data of the client, wherein the buried point data is generated according to the detected user operation.

[0081] The environment identification module 402 is configured to: determine the operating environment when the client generates the burying point data based on the burying point data, as the environment identification result.

[0082] The test module 404 is configured as follows: according to the environment identification result, a point-of-sale test is performed based on the point-of-sale data to obtain the result of the point-of-sale test, wherein the point-of-sale test method includes a first method and a second method. If the environment identification result shows that the current operating environment is a test environment, the point-of-sale data is processed in the first method. If the environment identification result shows that the current operating environment is an online use environment, the point-of-sale data is processed in the second method. The second method is obtained by removing the point-of-sale coverage completeness test in the first method.

[0083] In an optional embodiment of the present specification, the test module 404 is specifically configured as follows: for each buried point, if there is a value corresponding to the key of the buried point in the buried point data, the buried point is determined to be a valid buried point as the buried point coverage completeness test result of the buried point; if there is no value corresponding to the key of the buried point in the buried point data, the buried point is determined to be an invalid buried point as the buried point coverage completeness test result of the buried point.

[0084] In an optional embodiment of the present specification, at least one of the first method and the second method includes a buried point setting accuracy test, and the buried point data includes a key for identifying the buried point and a value corresponding to the key. The test module 404 is specifically configured as follows: for each value in the buried point data, if the value is within the value range defined by the protocol, the valid buried point is used as the buried point setting accuracy test result of the buried point identified by the key corresponding to the value; if the value is not within the value range defined by the protocol, the invalid buried point is used as the buried point setting accuracy test result of the buried point identified by the key corresponding to the value.

[0085] In an optional embodiment of the present specification, the buried point testing device may also include a prefix key detection module, configured to: determine a reference key; for each value in the buried point data, if the key-value pair to which the value belongs has a prefix key, then store the value if the prefix key matches the reference key.

[0086] In an optional embodiment of the present specification, the test module 404 is specifically configured to perform a buried point test based on the stored values.

[0087] In an optional embodiment of the present specification, the tracking point testing device may also include a stress testing module 404, which is configured to: after obtaining the result of the tracking point test, determine the data processing efficiency of the server during the test; if the data processing efficiency is greater than or equal to the efficiency threshold, increase the number of simulated users in the test environment so that the client regenerates the tracking point data according to the detected user operation of adding users, and sends it to the test server; if the data processing efficiency is less than the efficiency threshold, determine the current number of simulated users as a specified number, wherein the specified number represents the data processing performance of the server; obtain the tracking point data resent by the client; based on the tracking point data resent by the client, use the first method to process the tracking point data to re-obtain the result of the tracking point test, and update the data processing efficiency of the server during this test until the data processing efficiency is less than the efficiency threshold; store the specified number.

[0088] Based on the same idea, this specification further provides a buried point data processing device, which is applied to the client, such as Figure 5 As shown, the buried point data processing device includes one or more of the following modules:

[0089] The pending data storage module 500 is configured to store the pending data locally, wherein the pending data is generated based on the data collection method shown by the buried point and according to the detected user operation.

[0090] The actual duration determination module 502 is configured to: obtain the amount of pending data stored locally, and determine the actual duration from the current time to the last time the buried data was sent to the server.

[0091] The sending condition judgment module 504 is configured as follows: if at least one of the sending conditions is met, the locally stored pending data is determined as buried data, wherein the sending conditions include: the amount of locally stored pending data is greater than or equal to a first quantity threshold, and the actual duration is greater than or equal to a duration threshold.

[0092] The sending module 506 is configured to send the buried point data to the server.

[0093] In an optional embodiment of the present specification, the burial point data processing device may further include a deletion module configured to delete the burial point data stored locally after sending the burial point data to the server.

[0094] In an optional embodiment of the present specification, the sending condition judgment module 504 is specifically configured as follows: if at least one of the sending conditions is met, the locally stored pending data is determined as the buried point data, and the method further includes: if the amount of the locally stored buried point data is greater than or equal to a second quantity threshold, the locally stored buried point data is deleted.

[0095] like Figure 6 As shown, the embodiment of the present application provides a buried point test device, including a processor 111, a communication interface 112, a memory 113 and a communication bus 114, wherein the processor 111, the communication interface 112, and the memory 113 communicate with each other through the communication bus 114.

[0096] Memory 113, used for storing computer programs;

[0097] In one embodiment of the present application, the processor 111 is used to implement the control method of the embedded point test provided by any one of the aforementioned method embodiments when executing the program stored in the memory 113.

[0098] An embodiment of the present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of the embedded point test provided in any of the aforementioned method embodiments are implemented.

[0099] It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0100] The above is only a specific embodiment of the present invention, so that those skilled in the art can understand or implement the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but should conform to the widest scope consistent with the principles and novel features applied herein.

Claims

1. A buried point testing method, characterized in that: The method is applied to the server, and the method includes: Acquire the buried point data of the client, wherein the buried point data is generated according to the detected user operation; According to the buried data, determining the operating environment when the client generates the buried data as an environment identification result; According to the environment identification result, the buried point test is performed based on the buried point data to obtain the result of the buried point test, wherein the buried point test method includes a first method and a second method. If the environment identification result shows that the current operating environment is a test environment, the first method is used to process the buried point data. If the environment identification result shows that the current operating environment is an online use environment, the second method is used to process the buried point data. The second method is obtained by removing the buried point coverage completeness test from the first method. The buried point coverage completeness test is used to traverse each buried point to see whether the corresponding buried point data is collected to distinguish whether the buried point is a redundant buried point. If the buried point data corresponding to the buried point cannot be collected, it indicates that the buried point is a redundant buried point. If the buried point data corresponding to the buried point is collected, it indicates that the buried point is not a redundant buried point. The process of the buried point coverage completeness test includes: obtaining the key of each buried point, the key of the buried point is used to identify the buy order, and establishing a first corresponding table of key-value relationships; for each key in the first corresponding table of key-value relationships, searching in the buried point data, if there is a value corresponding to the key of the buried point in the buried point data, then the buried point is determined to be a valid buried point as the buried point coverage completeness test result of the buried point, if there is no value corresponding to the key of the buried point in the buried point data, then the buried point is determined to be an invalid buried point as the buried point coverage completeness test result of the buried point, the first corresponding table of key-value relationships includes a first column for recording keys and a second column for recording values. In the process of executing the buried point coverage completeness test, the value determined for each key is added to the corresponding position in the second column to realize the recording of the buried point coverage completeness test result.

2. The method according to claim 1, characterized in that: The buried point data includes a key for identifying a buried point and a value corresponding to the key, wherein a buried point test is performed based on the buried point data to obtain a result of the buried point test, including: For each buried point, if there is a value corresponding to the key of the buried point in the buried point data, the buried point is determined to be a valid buried point as the buried point coverage completeness test result of the buried point; if there is no value corresponding to the key of the buried point in the buried point data, the buried point is determined to be an invalid buried point as the buried point coverage completeness test result of the buried point.

3. The method according to claim 1, characterized in that At least one of the first mode and the second mode includes a burying point setting accuracy test, the burying point data includes a key for identifying a burying point and a value corresponding to the key, wherein the burying point test is performed based on the burying point data to obtain a result of the burying point test, including: For each value in the buried point data, if the value is within the value range defined by the protocol, the valid buried point is used as the buried point setting accuracy test result of the buried point identified by the key corresponding to the value; if the value is not within the value range defined by the protocol, the invalid buried point is used as the buried point setting accuracy test result of the buried point identified by the key corresponding to the value.

4. The method according to claim 1, characterized in that: Before performing the buried point test based on the buried point data, the method further includes: determining a reference key; for each value in the buried point data, if the key-value pair to which the value belongs corresponds to a preceding key, storing the value when the preceding key matches the reference key; Performing a buried point test based on the buried point data includes: performing a buried point test based on each stored value.

5. The method according to claim 1, characterized in that The first method is used to process the buried point data, including: After obtaining the results of the tracking test, determine the data processing efficiency of the server during the test; If the data processing efficiency is greater than or equal to the efficiency threshold, the amount of simulated users in the test environment is increased, so that the client regenerates the tracking data according to the detected user operation of adding users, and sends it to the test server; if the data processing efficiency is less than the efficiency threshold, the current amount of simulated users is determined to be a specified number, wherein the specified number represents the data processing performance of the server; Obtain the buried point data resent by the client; Based on the tracking data resent by the client, the tracking data is processed in the first way to obtain the tracking test result again, and the data processing efficiency of the server during this test is updated until the data processing efficiency is less than the efficiency threshold; The specified quantity is stored.

6. A method for processing buried point data, characterized in that: The method is applied to a client, and the method comprises: The pending data is stored locally, wherein the pending data is generated based on the data collection method shown by the buried point and according to the detected user operation; Get the amount of pending data stored locally and determine the actual time from the current time to the last time the tracking data was sent to the server. If at least one of the sending conditions is met, the locally stored pending data is determined as the buried data, wherein the sending conditions include: the amount of the locally stored pending data is greater than or equal to the first quantity threshold, and the actual duration is greater than or equal to the duration threshold; The buried point data is sent to the server, wherein the server is used to determine the operating environment when the client generates the buried point data according to the buried point data as an environment identification result; according to the environment identification result, a buried point test is performed based on the buried point data to obtain a result of the buried point test, wherein the buried point test method includes a first method and a second method, if the environment identification result shows that the current operating environment is a test environment, the first method is used to process the buried point data, if the environment identification result shows that the current operating environment is an online use environment, the second method is used to process the buried point data, the second method is obtained by removing the buried point coverage completeness test in the first method, the buried point coverage completeness test is used to traverse each buried point to see whether the corresponding buried point data is collected, so as to distinguish whether the buried point is a redundant buried point, if the buried point data corresponding to the buried point cannot be collected If there is no data, it indicates that the buried point is a redundant buried point. If the buried point data corresponding to the buried point is collected, it indicates that the buried point is not a redundant buried point. The process of buried point coverage completeness test includes: obtaining the key of each buried point, the key of the buried point is used to identify the buy order, and establishing a first corresponding table of key-value relationship; for each key in the first corresponding table of key-value relationship, searching in the buried point data, if there is a value corresponding to the key of the buried point in the buried point data, the buried point is determined to be a valid buried point as the buried point coverage completeness test result of the buried point, if there is no value corresponding to the key of the buried point in the buried point data, the buried point is determined to be an invalid buried point as the buried point coverage completeness test result of the buried point, the first corresponding table of key-value relationship includes a first column for recording keys and a second column for recording values. In the process of executing the buried point coverage completeness test, the value determined for each key is added to the corresponding position in the second column to realize the recording of the buried point coverage completeness test result.

7. The method according to claim 6, characterized in that After sending the buried point data to the server, the method further includes: deleting the buried point data stored locally; If at least one of the sending conditions is met, the locally stored pending data is determined as buried point data, and the method further includes: if the amount of locally stored buried point data is greater than or equal to a second quantity threshold, deleting the locally stored buried point data.

8. A buried point testing device, characterized in that: Applied to the server, the device comprises: The buried point data acquisition module is configured to: acquire buried point data of the client, wherein the buried point data is generated according to the detected user operation; An environment identification module is configured to: determine, based on the buried point data, an operating environment when the client generates the buried point data as an environment identification result; A test module is configured to: perform a buried point test based on the buried point data according to the environment identification result to obtain a result of the buried point test, wherein the buried point test method includes a first method and a second method, if the environment identification result shows that the current operating environment is a test environment, the first method is used to process the buried point data, if the environment identification result shows that the current operating environment is an online use environment, the second method is used to process the buried point data, the second method is obtained by removing the buried point coverage completeness test from the first method, the buried point coverage completeness test is used to traverse each buried point to see whether the corresponding buried point data is collected to distinguish whether the buried point is a redundant buried point, if the buried point data corresponding to the buried point cannot be collected, it indicates that the buried point is a redundant buried point, if the buried point data corresponding to the buried point is collected, it indicates that the buried point is not a redundant buried point; The process of the buried point coverage completeness test includes: obtaining the key of each buried point, the key of the buried point is used to identify the buy order, and establishing a first corresponding table of key-value relationships; for each key in the first corresponding table of key-value relationships, searching in the buried point data, if there is a value corresponding to the key of the buried point in the buried point data, then the buried point is determined to be a valid buried point as the buried point coverage completeness test result of the buried point, if there is no value corresponding to the key of the buried point in the buried point data, then the buried point is determined to be an invalid buried point as the buried point coverage completeness test result of the buried point, the first corresponding table of key-value relationships includes a first column for recording keys and a second column for recording values. In the process of executing the buried point coverage completeness test, the value determined for each key is added to the corresponding position in the second column to realize the recording of the buried point coverage completeness test result.

9. A buried point data processing device, characterized in that: Applied to a client, the device comprises: A pending data storage module is configured to: store the pending data locally, wherein the pending data is generated based on the data collection method shown by the buried point and according to the detected user operation; The actual duration determination module is configured to: obtain the amount of pending data stored locally, and determine the actual duration from the current time to the last time the tracking data was sent to the server; The sending condition judgment module is configured to: if at least one of the sending conditions is met, determine the locally stored pending data as the buried point data, wherein the sending conditions include: the amount of the locally stored pending data is greater than or equal to the first quantity threshold, and the actual duration is greater than or equal to the duration threshold; A sending module is configured to: send the buried point data to a server, wherein the server is used to determine the operating environment when the client generates the buried point data based on the buried point data as an environment identification result; according to the environment identification result, perform a buried point test based on the buried point data to obtain a result of the buried point test, wherein the buried point test method includes a first method and a second method, if the environment identification result shows that the current operating environment is a test environment, the first method is used to process the buried point data, if the environment identification result shows that the current operating environment is an online use environment, the second method is used to process the buried point data, the second method is obtained by removing the buried point coverage completeness test from the first method, the buried point coverage completeness test is used to traverse each buried point to see whether the corresponding buried point data is collected, so as to distinguish whether the buried point is a redundant buried point, if the corresponding buried point data cannot be collected If the buried point data is not collected, it indicates that the buried point is a redundant buried point. If the buried point data corresponding to the buried point is collected, it indicates that the buried point is not a redundant buried point. The process of buried point coverage completeness test includes: obtaining the key of each buried point, the key of the buried point is used to identify the buy order, and establishing a first corresponding table of key-value relationship; for each key in the first corresponding table of key-value relationship, searching in the buried point data, if there is a value corresponding to the key of the buried point in the buried point data, the buried point is determined to be a valid buried point as the buried point coverage completeness test result of the buried point, if there is no value corresponding to the key of the buried point in the buried point data, the buried point is determined to be an invalid buried point as the buried point coverage completeness test result of the buried point, the first corresponding table of key-value relationship includes a first column for recording keys and a second column for recording values. In the process of executing the buried point coverage completeness test, the value determined for each key is added to the corresponding position in the second column to realize the recording of the buried point coverage completeness test result.

10. An electronic device, characterized in that: It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; Memory, used to store computer programs; The processor is used to implement the steps of any one of the buried point testing methods of claims 1-7 when executing the program stored in the memory.

Images