A detection method, a detection device, an electronic device and a readable storage medium
By detecting the changes in buried points in real time during the application development and testing stage, the lag problem of detection results is solved, the efficiency and buried points of application iteration are improved, and the rapid and accurate application release is achieved.
Patent Information
- Application Number
- CN201911150584.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2019-11-21
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2040-11-12
AI Technical Summary
In the process of rapid iteration of applications, the detection results in the prior art have lag, increasing the number of application iterations and time consumption, making it difficult to effectively monitor and improve the quality and utilization of buried points during the development and testing stage.
During the version construction and testing of the application to be upgraded, we can detect changes before and after the buried point in real time, obtain the buried point attribute information and scene information before and after the upgrade, and perform matching and comparison to determine whether the application has been successfully upgraded, and then develop and test it. The problem was discovered and corrected in stages.
It improves the real-time and release efficiency of application detection, reduces time consumption, improves the quality and utilization of buried points, and ensures the fast and accurate iteration of applications.
Smart Images

Figure CN111858293B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to a detection method, a detection device, an electronic device and a readable storage medium. Background Art
[0002] Against the backdrop of the rapid development of the Internet industry, a variety of applications have emerged one after another, greatly facilitating people's lives and entertainment. In order to adapt more quickly to the development of Internet technology and the convenience and security of people's use of applications, the application versions of applications need to be quickly iterated. In the process of rapid iteration of applications, it is necessary to ensure the stability and correctness of the applications.
[0003] At present, in the rapid iteration process of applications, most of the time, tracking points are carried out in the applications. After the updated version of the application is released, that is, after the entire process of version building, testing and release of the entire application upgrade is completed, the data of real online users after the application is released is collected to analyze the user usage scenarios, and patches or upgrades are used again to correct problems when they occur. However, in the process of rapid iteration and delivery of applications, the detection results obtained in this way are lagging, which will increase the number of application iterations, increase the workload and time consumption of version iterations. Summary of the invention
[0004] In view of this, the purpose of the present application is to provide a detection method, a detection device, an electronic device and a readable storage medium, by detecting the changes before and after the tracking points in real time during the version construction and testing process before the release of the application to be upgraded to determine whether the upgrade of the application to be upgraded is successful or not. In this way, each tracking point can be monitored in real time during the construction and testing process of the upgraded version. Before the new version is released, the application to be upgraded can be detected with the help of the tracking points during the development and testing stage, and the tracking point problems can be fully discovered during the development and testing stage to improve the quality and utilization of the tracking points, which is conducive to improving the real-time nature of application detection, timeliness of delivery and release efficiency, and helps to reduce time consumption.
[0005] According to one aspect of the present application, a detection method is provided, the detection method comprising:
[0006] Obtain at least one pre-upgrade embedding point in the application to be upgraded, as well as attribute information of each pre-upgrade embedding point and scenario information corresponding to each pre-upgrade embedding point;
[0007] In the process of building an upgraded version of the application to be upgraded, scanning the version building data of the application to be upgraded to obtain at least one post-upgrade tracking point and attribute information of each post-upgrade tracking point;
[0008] During the running test after the upgraded version of the application to be upgraded is built, the scene information corresponding to each post-upgrade tracking point is obtained;
[0009] Based on the attribute information of each pre-upgrade buried point, the scene information corresponding to each pre-upgrade buried point, the attribute information of each post-upgrade buried point and the scene information corresponding to each post-upgrade buried point, determine whether the application to be upgraded has been successfully upgraded.
[0010] In some embodiments of the present application, in the process of running the test after the upgraded version of the application to be upgraded is built, obtaining the scene information corresponding to each post-upgrade tracking point includes:
[0011] During the running test after the upgraded version of the application to be upgraded is built, the application scenario where each post-upgrade tracking point is triggered is detected, and the stack data at the corresponding application scenario when each post-upgrade tracking point is triggered is collected;
[0012] Based on the generated stack data and the application scenario, determine the scenario information corresponding to each upgraded tracking point.
[0013] In some embodiments of the present application, determining whether the application to be upgraded is successfully upgraded based on the attribute information of each pre-upgrade buried point, the scene information corresponding to each pre-upgrade buried point, the attribute information of each post-upgrade buried point, and the scene information corresponding to each post-upgrade buried point includes:
[0014] Match the attribute information of each post-upgrade buried point with the attribute information of the corresponding pre-upgrade buried point, and match the scene information corresponding to each post-upgrade buried point with the scene information corresponding to the corresponding pre-upgrade buried point;
[0015] If the attribute information of each post-upgrade buried point is consistent with the attribute information of the corresponding pre-upgrade buried point, and the scene information corresponding to each post-upgrade buried point is consistent with the scene information corresponding to the corresponding pre-upgrade buried point, it is determined that the application to be upgraded has been successfully upgraded.
[0016] In some embodiments of the present application, after matching the attribute information of each post-upgrade burying point with the attribute information of the corresponding pre-upgrade burying point, and matching the scene information corresponding to each post-upgrade burying point with the scene information corresponding to the corresponding pre-upgrade burying point, the detection method further includes:
[0017] For each post-upgrade tracking point, if the attribute information of the post-upgrade tracking point is inconsistent with the attribute information of the corresponding pre-upgrade tracking point, and the scene information corresponding to the post-upgrade tracking point is inconsistent with the scene information corresponding to the corresponding pre-upgrade tracking point, it is determined that the upgrade of the application to be upgraded has failed.
[0018] In some embodiments of the present application, after determining that the upgrade of the application to be upgraded fails, the detection method further includes:
[0019] The upgraded application to be upgraded is sent to the manual detection terminal, and an alarm message of upgrade failure is sent to the manual detection terminal.
[0020] In some embodiments of the present application, after matching the attribute information of each post-upgrade burying point with the attribute information of the corresponding pre-upgrade burying point, and matching the scene information corresponding to each post-upgrade burying point with the scene information corresponding to the corresponding pre-upgrade burying point, the detection method further includes:
[0021] For each post-upgrade tracking point, if the attribute information of the post-upgrade tracking point is inconsistent with the attribute information of the corresponding pre-upgrade tracking point, or the scene information corresponding to the post-upgrade tracking point is inconsistent with the scene information corresponding to the corresponding pre-upgrade tracking point, the data of the post-upgrade tracking point is reviewed;
[0022] If the result of the data review shows that the tracking point change after the upgrade is less than the preset change threshold, it is determined that the upgrade of the application to be upgraded is successful.
[0023] In the above embodiment, when the attribute information of the post-upgrade tracking point is inconsistent with the attribute information of the corresponding pre-upgrade tracking point, the data of the post-upgrade tracking point with inconsistent attribute information is reviewed through the following steps:
[0024] Based on the attribute information of the post-upgrade burying point with inconsistent attribute information and the attribute information of the corresponding pre-upgrade burying point, detecting the difference between the burying point position of the post-upgrade burying point and the burying point position of the corresponding pre-upgrade burying point;
[0025] If the difference is smaller than the preset position threshold, and the burial point feature of the burial point after the upgrade is consistent with the burial point feature of the corresponding burial point before the upgrade, it is determined that the burial point change of the burial point after the upgrade is smaller than the preset change threshold.
[0026] In the above embodiment, when the scene information corresponding to the post-upgrade burying point is inconsistent with the scene information corresponding to the pre-upgrade burying point, the data of the post-upgrade burying point with inconsistent scene information is reviewed through the following steps:
[0027] Based on the scene information of the post-upgrade tracking point with inconsistent scene information and the scene information of the corresponding pre-upgrade tracking point, detect whether the scene deviation between the application scene when the post-upgrade tracking point is triggered and the application scene when the corresponding pre-upgrade tracking point is triggered is less than a preset deviation threshold;
[0028] If the scene deviation is less than the preset deviation threshold, and the stack data generated when the post-upgrade tracking point is triggered is consistent with the stack data generated when the corresponding pre-upgrade tracking point is triggered, it is determined that the tracking point change of the post-upgrade tracking point is less than the preset change threshold.
[0029] In some embodiments of the present application, the attribute information includes a burial point location and a burial point feature, and the burial point feature includes at least one of a burial point type, a burial point method name, and a burial point method data.
[0030] In some embodiments of the present application, the scenario information includes the application scenario in which the burrowing point is triggered and the stack data generated when the burrowing point is triggered.
[0031] According to another aspect of the present application, a detection device is provided, the detection device comprising:
[0032] A pre-upgrade embedding point information acquisition module is used to acquire at least one pre-upgrade embedding point in the application to be upgraded, as well as attribute information of each pre-upgrade embedding point and scenario information corresponding to each pre-upgrade embedding point;
[0033] A post-tracking point attribute acquisition module is used to scan the version construction data of the application to be upgraded during the process of building an upgraded version of the application to be upgraded, and obtain at least one post-upgrade tracking point and attribute information of each post-upgrade tracking point;
[0034] A post-buffering scene acquisition module is used to obtain scene information corresponding to each post-upgraded buried point during the running test after the upgraded version of the application to be upgraded is built;
[0035] The upgrade determination module is used to determine whether the application to be upgraded has been successfully upgraded based on the attribute information of each pre-upgrade buried point, the scene information corresponding to each pre-upgrade buried point, the attribute information of each post-upgrade buried point, and the scene information corresponding to each post-upgrade buried point.
[0036] In some embodiments of the present application, when the post-buried point scene acquisition module is used to obtain the scene information corresponding to each post-upgrade buried point during the operation test after the upgraded version of the application to be upgraded is built, the post-buried point scene acquisition module is specifically used to:
[0037] During the running test after the upgraded version of the application to be upgraded is built, the application scenario where each post-upgrade tracking point is triggered is detected, and the stack data at the corresponding application scenario when each post-upgrade tracking point is triggered is collected;
[0038] Based on the generated stack data and the application scenario, determine the scenario information corresponding to each upgraded tracking point.
[0039] In some embodiments of the present application, when the upgrade determination module is used to determine whether the application to be upgraded is successfully upgraded based on the attribute information of each pre-upgrade buried point, the scene information corresponding to each pre-upgrade buried point, the attribute information of each post-upgrade buried point, and the scene information corresponding to each post-upgrade buried point, the upgrade determination module is specifically used to:
[0040] Match the attribute information of each post-upgrade buried point with the attribute information of the corresponding pre-upgrade buried point, and match the scene information corresponding to each post-upgrade buried point with the scene information corresponding to the corresponding pre-upgrade buried point;
[0041] If the attribute information of each post-upgrade buried point is consistent with the attribute information of the corresponding pre-upgrade buried point, and the scene information corresponding to each post-upgrade buried point is consistent with the scene information corresponding to the corresponding pre-upgrade buried point, it is determined that the application to be upgraded has been successfully upgraded.
[0042] In some embodiments of the present application, the detection device further includes a failure determination module, and the failure determination module is used to:
[0043] For each post-upgrade tracking point, if the attribute information of the post-upgrade tracking point is inconsistent with the attribute information of the corresponding pre-upgrade tracking point, and the scene information corresponding to the post-upgrade tracking point is inconsistent with the scene information corresponding to the corresponding pre-upgrade tracking point, it is determined that the upgrade of the application to be upgraded has failed.
[0044] In some embodiments of the present application, the detection device further includes a warning information sending module, and the warning information sending module is used to:
[0045] The upgraded application to be upgraded is sent to the manual detection terminal, and an alarm message of upgrade failure is sent to the manual detection terminal.
[0046] In some embodiments of the present application, the detection device further includes a data review module, and the data review module is used to:
[0047] For each post-upgrade tracking point, if the attribute information of the post-upgrade tracking point is inconsistent with the attribute information of the corresponding pre-upgrade tracking point, or the scene information corresponding to the post-upgrade tracking point is inconsistent with the scene information corresponding to the corresponding pre-upgrade tracking point, the data of the post-upgrade tracking point is reviewed;
[0048] If the result of the data review shows that the tracking point change after the upgrade is less than the preset change threshold, it is determined that the upgrade of the application to be upgraded is successful.
[0049] In the above embodiment, when the attribute information of the post-upgrade tracking point is inconsistent with the attribute information of the corresponding pre-upgrade tracking point, the data review module performs data review on the post-upgrade tracking point with inconsistent attribute information through the following steps:
[0050] Based on the attribute information of the post-upgrade burying point with inconsistent attribute information and the attribute information of the corresponding pre-upgrade burying point, detecting the difference between the burying point position of the post-upgrade burying point and the burying point position of the corresponding pre-upgrade burying point;
[0051] If the difference is smaller than the preset position threshold, and the burial point feature of the burial point after the upgrade is consistent with the burial point feature of the corresponding burial point before the upgrade, it is determined that the burial point change of the burial point after the upgrade is smaller than the preset change threshold.
[0052] In the above embodiment, when the scene information corresponding to the post-upgrade burying point is inconsistent with the scene information corresponding to the pre-upgrade burying point, the data review module performs data review on the post-upgrade burying point with inconsistent scene information through the following steps:
[0053] Based on the scene information of the post-upgrade tracking point with inconsistent scene information and the scene information of the corresponding pre-upgrade tracking point, detect whether the scene deviation between the application scene when the post-upgrade tracking point is triggered and the application scene when the corresponding pre-upgrade tracking point is triggered is less than a preset deviation threshold;
[0054] If the scene deviation is less than the preset deviation threshold, and the stack data generated when the post-upgrade tracking point is triggered is consistent with the stack data generated when the corresponding pre-upgrade tracking point is triggered, it is determined that the tracking point change of the post-upgrade tracking point is less than the preset change threshold.
[0055] In some embodiments of the present application, the attribute information includes a burial point location and a burial point feature, and the burial point feature includes at least one of a burial point type, a burial point method name, and a burial point method data.
[0056] In some embodiments of the present application, the scenario information includes the application scenario in which the burrowing point is triggered and the stack data generated when the burrowing point is triggered.
[0057] An embodiment of the present application also provides an electronic device, comprising: a processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor and the memory communicate through the bus, and when the machine-readable instructions are executed by the processor, the steps of the detection method as described above are performed.
[0058] An embodiment of the present application further 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 above-mentioned detection method are executed.
[0059] The detection method, detection device, electronic device and readable storage medium provided in the embodiments of the present application obtain at least one pre-upgrade tracking point in the application to be upgraded, as well as the attribute information of each pre-upgrade tracking point and the scene information corresponding to each pre-upgrade tracking point; in the process of building an upgraded version of the application to be upgraded, scan the version build data of the application to be upgraded to obtain at least one post-upgrade tracking point and the attribute information of each post-upgrade tracking point; in the process of running the application to be upgraded after completing the upgrade version construction, obtain the scene information corresponding to each post-upgrade tracking point; based on the attribute information of each pre-upgrade tracking point, the scene information corresponding to each pre-upgrade tracking point, the attribute information of each post-upgrade tracking point and the scene information corresponding to each post-upgrade tracking point, determine whether the application to be upgraded is successfully upgraded.
[0060] Compared with the prior art methods, the present application obtains at least one post-upgrade tracking point and the attribute information of each post-upgrade tracking point during the process of building the upgraded version of the application to be upgraded, and the scene information corresponding to each post-upgrade tracking point during the test process, and matches and compares the attribute information and scene information of each post-upgrade tracking point with the acquired attribute information and scene information of the corresponding pre-upgrade tracking point, and determines whether the application to be upgraded is successfully upgraded based on the matching and comparison results. In this way, by detecting the tracking points in real time during the version construction and testing process before the release of the application to be upgraded, it is determined whether the upgrade of the application to be upgraded is successful or not. In this way, each tracking point can be monitored in real time during the construction and testing process of the upgraded version. Before the new version is released, the tracking points can be fully used to detect the application to be upgraded in the development and testing stage, and the tracking point problems can be fully discovered during the development and testing stage to improve the quality and utilization of the tracking points, which is conducive to improving the real-time performance, delivery timeliness and release efficiency of application detection, and helps to reduce time consumption.
[0061] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, preferred embodiments are specifically cited below and described in detail with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0062] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.
[0063] Figure 1 A schematic diagram of the architecture of a detection system provided in an embodiment of the present application;
[0064] Figure 2A schematic diagram of a detection method provided in an embodiment of the present application;
[0065] Figure 3 A schematic flow chart of a detection method provided in another embodiment of the present application;
[0066] Figure 4 One of the structural schematic diagrams of a detection device provided in this application;
[0067] Figure 5 A second structural schematic diagram of a detection device provided in an embodiment of the present application;
[0068] Figure 6 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0069] To make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme 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 only a part of the embodiments of the present application, rather than all of the embodiments. The components of the embodiments of the present application usually described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, each other embodiment obtained by those skilled in the art without making creative work belongs to the scope of protection of the present application.
[0070] In order to enable those skilled in the art to use the contents of this application, the following implementation method is given in combination with the specific application scenario "detecting the upgrade status of the application to be upgraded through tracking points". For those skilled in the art, the general principles defined here can be applied to other embodiments and application scenarios without departing from the spirit and scope of this application. Although this application is mainly described around the use of tracking points before the upgrade and tracking points during the upgrade process to detect the upgrade status of the application to be upgraded, it should be understood that this is only an exemplary embodiment.
[0071] It should be noted that the term "comprising" will be used in the embodiments of the present application to indicate the existence of the features declared thereafter, but does not exclude the addition of other features.
[0072] One aspect of the present application relates to a detection system. During the upgrade process of the application to be upgraded, the detection system detects the changes before and after the tracking point in real time to determine whether the upgrade of the application to be upgraded is successful or not. Each tracking point can be monitored in real time during the construction and testing process of the upgraded version. Before the new version is released, the tracking point can be fully used to detect the application to be upgraded during the development and testing stage, and the tracking point problems can be fully discovered during the development and testing stage to improve the quality and utilization of the tracking point, which is conducive to improving the real-time, delivery timeliness and release efficiency of application detection, and helps to reduce time consumption.
[0073] It is worth noting that before the present application was filed, in the rapid iteration process of the application, most of the time, point embedding was performed in the application. After the updated version of the application was released, that is, after the entire process of version building, testing and release of the entire application upgrade was completed, the data of real online users after the application was released was collected to analyze the user usage scenario, and patches or upgrades were used again to correct the problems after they occurred. However, in the process of rapid iteration and delivery of the application, the detection results obtained in this way have a lag, which will increase the number of application iterations, increase the workload and time consumption of version iterations.
[0074] However, the detection method, detection device, electronic device and readable storage medium provided by the present application are aimed at the detection stage of the version construction (development) and testing stage in the upgrade process. By scanning the code and obtaining the runtime stack data, the changes of the tracking points can be detected in advance. During the version construction and testing process of the application to be upgraded, the tracking points after the upgrade and the tracking points before the upgrade can be detected in real time to determine whether the upgrade of the application to be upgraded is successful or not. In this way, each tracking point can be monitored in real time during the construction and testing process of the upgraded version. Before the new version is released, the tracking points can be fully utilized to detect the application to be upgraded in the development and testing stage, and the tracking point problems can be fully discovered in the development and testing stage to improve the quality and utilization of the tracking points, which is conducive to improving the real-time performance, delivery timeliness and release efficiency of application detection, and helps to reduce time consumption.
[0075] Figure 1 The schematic diagram of the architecture of a detection system provided in an embodiment of the present application is as follows: The detection system may include one or more of a server 110 , a network 120 , a client 130 , and a database 140 .
[0076] In some embodiments, the server 110 may include a processor. The processor may process information and / or data related to the service request to perform one or more functions described in the present application. For example, the processor may determine the target vehicle based on the service request obtained from the client 130. In some embodiments, the processor may include one or more processing cores (e.g., a single-core processor (S) or a multi-core processor (S)). By way of example only, the processor may include a central processing unit (CPU), an application specific integrated circuit (ASIC), an application specific instruction set processor (ASIP), a graphics processing unit (GPU), a physical processing unit (PPU), a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic device (PLD), a controller, a microcontroller unit, a reduced instruction set computer (RISC), or a microprocessor, or any combination thereof.
[0077] In some embodiments, the client 130 may be a mobile device or a fixed terminal for use by the client, such as a tablet computer, a laptop computer, a smart mobile device, etc.
[0078] In some embodiments, database 140 may be connected to network 120 to communicate with one or more components in the detection system (e.g., server 110, client 130, etc.). One or more components in the detection system may access data or instructions stored in database 140 via network 120. In some embodiments, database 140 may be directly connected to one or more components in the detection system, or database 140 may also be part of server 110.
[0079] The following is combined with the above Figure 1 The contents described in the detection system shown provide a detailed description of the detection method provided in the embodiments of the present application.
[0080] Reference Figure 2 As shown, Figure 2A flow chart of a detection method provided in an embodiment of the present application is provided. The detection method can be executed by one or more processors in the above detection system. The specific execution process is as follows:
[0081] S201. Obtain at least one pre-upgrade embedding point in the application to be upgraded, as well as attribute information of each pre-upgrade embedding point and scenario information corresponding to each pre-upgrade embedding point.
[0082] In this step, at least one pre-upgrade tracking point before the to-be-upgraded version is upgraded is obtained from the historical usage version of the to-be-upgraded application, as well as the attribute information of each pre-upgrade tracking point and the scene information corresponding to each tracking point in the settings of the historical version.
[0083] The historical version used may be the last historical updated version before the upgrade, or may be the version that is configured for the first time when the application to be upgraded is generated.
[0084] Here, the attribute information includes the buried point location and buried point features, and the buried point features include at least one of the buried point type, the buried point method name, and the buried point method data.
[0085] Among them, when the burying method is the code burying method, the burying position may refer to the specific location of the burying code in the construction code of the application (such as lines Y to Z of the Xth function); the burying feature may refer to the class to which the burying point belongs, the class function that executes the burying point, and the code segment corresponding to the class function, and the attribute information of the burying point is stored in the corresponding burying point configuration file.
[0086] Here, the scene information includes the application scene when the embedding point is triggered and the stack data generated when the embedding point is triggered. The application scene when the embedding point is triggered can be based on the scene function corresponding to the embedding point. When the embedding point is triggered, a screen switching process will be generated in the front-end display part, and a new interface will be displayed. At this time, the corresponding back-end program part will generate the corresponding stack data of the switched screen. The scene information corresponding to a certain embedding point is composed of the switched front-end display screen and the corresponding stack data of the back-end.
[0087] For example, there is a query button in the front-end display screen, and a query embedding point is set in the program code corresponding to the query button. During the test, when the query button is clicked, it will jump to a query result interface, and on the back-end program side, stack data related to the query result interface will be generated. The query result interface and the stack data related to the query result interface together constitute the scene information of the query embedding point.
[0088] Among them, for all burial points, the specific contents included in the burial point information and scene information are consistent, that is, the following burial point information all include the burial point location and burial point features, and the burial point features include at least one of the burial point type, the burial point method name and the burial point method data; the following scene information all include the application scenario when the burial point is triggered and the stack data generated when the burial point is triggered.
[0089] S202: During the process of building an upgraded version of the application to be upgraded, scan the version building data of the application to be upgraded to obtain at least one post-upgrade tracking point and attribute information of each post-upgrade tracking point.
[0090] In this step, during the process of building an upgraded version for the application to be upgraded, the logic of scanning code is inserted to scan the build data of the application to be upgraded, obtain at least one upgraded tracking point of the application to be upgraded indicated in the build data, and obtain the attribute information corresponding to each upgraded tracking point.
[0091] Among them, in the embodiment of the present application, the post-upgrade tracking points are all the tracking points in the development and testing stages during the application upgrade process, and all post-upgrade tracking points are relative to the tracking points in the historical version, that is, the post-upgrade tracking points mentioned below are all tracking points in the development and testing stages.
[0092] Here, all the embedded points in the build data of the version to be upgraded are stored in the configuration file. When the build is triggered in a certain scenario, the logic of scanning the code will scan the embedded point type, embedded point method name and embedded point method data in the configuration file corresponding to the embedded point, and so on, until all the embedded points in the build data are scanned, all the embedded points and the attribute information corresponding to each embedded point are collected, a file is generated, and the file is uploaded to the server.
[0093] S203: During the running test of the application to be upgraded after the upgraded version is built, the scenario information corresponding to each upgraded tracking point is obtained.
[0094] In this step, after the build data configuration of the application to be upgraded is completed, the application to be upgraded is put into the test process. During the test, the tracking point is triggered at each triggerable node to obtain the scene information corresponding to each upgrade tracking point.
[0095] Here, the scenario information includes the application scenario corresponding to the triggered embedding point and the corresponding stack data after the embedding point is triggered.
[0096] For example, for a display interface on an application, a tracking point can be set on the query jump button on the display interface. After the query button is triggered, the application scenario is the page that jumps after the query node is triggered. The data stored in the stack can be the relevant corresponding data of the page after the page jumps after the button is triggered. The data is pushed into the stack in a preset order to generate a specific stack sequence.
[0097] S204. Determine whether the application to be upgraded is successfully upgraded based on the attribute information of each buried point before the upgrade, the scene information corresponding to each buried point before the upgrade, the attribute information of each buried point after the upgrade, and the scene information corresponding to each buried point after the upgrade.
[0098] In this step, the burying point location and burying point characteristics indicated by the attribute information of each burying point after the upgrade are compared with the burying point location and burying point characteristics indicated in the attribute information of each corresponding burying point before the upgrade. At the same time, the application scenario and generated stack data in which each post-upgrade burying point is triggered indicated by the scene information of each burying point after the upgrade are compared with the application scenario and generated stack data in which each post-upgrade burying point is triggered indicated by the scene information of each corresponding pre-upgrade burying point. Based on the comparison results of the two dimensions, the upgrade result of the application to be upgraded is determined.
[0099] Among them, the post-upgrade tracking points that need to be compared correspond to the pre-upgrade tracking points one by one, that is, the post-upgrade tracking points for upgrade comparison are the pre-upgrade tracking points that already existed in the previous version. For the post-upgrade tracking points newly added in the upgraded version build, since there are no corresponding pre-upgrade tracking points and no basis for comparison reference, the post-upgrade tracking points newly added in the upgraded version build are not matched and compared.
[0100] Here, when determining the result based on the comparison of two dimensions, if the matching criteria are met / not met in both dimensions, the upgrade success / failure of the upgrade application can be directly determined; if the matching criteria are met in only one of the dimensions, further review is required on the dimension that does not meet the matching criteria.
[0101] Among them, in the attribute information dimension, the comparison of the matching of the post-upgrade tracking point with the pre-upgrade tracking point can be compared from at least one aspect of the location of the post-upgrade tracking point and the pre-upgrade tracking point, as well as the type of tracking point, the name of the tracking method and the tracking method data; in the scenario information dimension, the comparison of the matching of the post-upgrade tracking point with the pre-upgrade tracking point can be compared from two aspects: the application scenario triggered by the post-upgrade tracking point and the stack data generated when it is triggered.
[0102] The detection method provided in the embodiment of the present application obtains at least one pre-upgrade tracking point in the application to be upgraded, as well as the attribute information of each pre-upgrade tracking point and the scene information corresponding to each pre-upgrade tracking point; in the process of building an upgraded version of the application to be upgraded, scans the version build data of the application to be upgraded to obtain at least one post-upgrade tracking point and the attribute information of each post-upgrade tracking point; in the process of running the application to be upgraded after completing the upgrade version construction, obtains the scene information corresponding to each post-upgrade tracking point; based on the attribute information of each pre-upgrade tracking point, the scene information corresponding to each pre-upgrade tracking point, the attribute information of each post-upgrade tracking point and the scene information corresponding to each post-upgrade tracking point, determines whether the application to be upgraded is successfully upgraded.
[0103] Compared with the prior art methods, the present application obtains at least one post-upgrade tracking point and the attribute information of each post-upgrade tracking point by scanning the version building data of the application to be upgraded during the process of building the upgraded version of the application to be upgraded, and the scene information corresponding to each post-upgrade tracking point during the test process, and matches and compares the attribute information and scene information of each post-upgrade tracking point with the acquired attribute information and scene information of the corresponding pre-upgrade tracking point, and determines whether the application to be upgraded is successfully upgraded based on the matching and comparison results. In this way, each tracking point can be monitored in real time during the construction and testing process of the upgraded version before release. Before the new version is released, the tracking points can be fully used to detect the application to be upgraded during the development and testing stage, and the tracking point problems can be fully discovered during the development and testing stage to improve the quality and utilization of the tracking points, which is conducive to improving the real-time performance, delivery timeliness and release efficiency of application detection, and helps to reduce time consumption.
[0104] Reference Figure 3 As shown, Figure 3 A flow chart of a detection method provided in another embodiment of the present application is shown. The detection method can be executed by one or more processors in the above detection system. Figure 3 As shown in , the specific execution process is:
[0105] S301. Obtain at least one pre-upgrade embedding point in the application to be upgraded, as well as attribute information of each pre-upgrade embedding point and scenario information corresponding to each pre-upgrade embedding point.
[0106] S302: During the process of building an upgraded version of the application to be upgraded, scan the version building data of the application to be upgraded to obtain at least one post-upgrade tracking point and attribute information of each post-upgrade tracking point.
[0107] S303: During the running test after the upgraded version of the application to be upgraded is built, the scenario information corresponding to each post-upgrade tracking point is obtained.
[0108] S304: Match the attribute information of each post-upgrade buried point with the attribute information of the corresponding pre-upgrade buried point, and match the scene information corresponding to each post-upgrade buried point with the scene information corresponding to the corresponding pre-upgrade buried point.
[0109] In this step, each post-upgrade buried point is matched with the corresponding pre-upgrade buried point in terms of the buried point position and buried point features indicated by the attribute information; and each post-upgrade buried point is matched with the corresponding pre-upgrade buried point in terms of the application scenario in which the buried point is triggered as indicated by the scenario information and the stack data generated when the buried point is triggered.
[0110] Among them, the correspondence between the upgraded buried points and the upgraded buried points can be made through the buried point names. The buried point names can be the names indicating the detection functions of the corresponding buried points, or can be the corresponding digital numbers according to the order of the buried points when the buried points are generated.
[0111] Here, for the matching of the location of the buried point, for the code buried point, the matching of the location of the buried point can be to match the specific location of the buried point after the upgrade and the buried point before the upgrade in the code, such as the Y line of the X function in the code; for the matching of the buried point attribute, the class to which the buried point belongs, the method in the class to which it belongs, and the specific code of the corresponding method can be matched. For the matching of the application scenario when the buried point is triggered, it can be the application scenario displayed by the entire application when the corresponding buried point is triggered. For example, in a certain display interface on the application, the buried point at the query node of the display interface will jump to the query interface that meets the query conditions when the buried point is triggered. At this time, the query interface after the jump that meets the query conditions can be regarded as an application scenario; the stack data generated when the buried point is triggered can be matched from the memory space occupied by the stack corresponding to the corresponding buried point, the number of data in the stack, the type, and the order of each data. Whether to upload the corresponding stack data when the buried point is triggered is determined by the background server. For the matching of the scene information of the buried point without stack data, it is only necessary to match the corresponding application scenario.
[0112] S305. If the attribute information of each buried point after the upgrade is consistent with the attribute information of the corresponding buried point before the upgrade, and the scene information corresponding to each buried point after the upgrade is consistent with the scene information corresponding to the corresponding buried point before the upgrade, it is determined that the application to be upgraded has been successfully upgraded.
[0113] In this step, for the matching judgment of S304, if each post-upgrade buried point matches the pre-upgrade buried point in the attribute information dimension and also matches the pre-upgrade buried point in the scene information dimension, then it is determined that the upgrade of the application to be upgraded is successful.
[0114] Here, the matching of the buried point attribute information is carried out from two aspects: the buried point location and the buried point feature. The matching of the buried point location can refer to the consistency of the location of the corresponding buried point before and after the upgrade in the entire application construction; the matching of the buried point feature can refer to the consistency of the class, method and specific code of the method to which the buried point belongs. The matching of the buried point application scenario can refer to the consistency of the corresponding triggering scenario or the scenario switched after the triggering when the corresponding buried point is triggered; the consistency of the triggered stack data can refer to the consistency of the memory space occupied by the two corresponding stack sequences, the number of data in the stack, and the order of each data in the stack.
[0115] Among them, the description of steps S301 to S303 can refer to the description of steps S201 to S203, and can achieve the same technical effect, which is not repeated here.
[0116] Furthermore, step 303 includes: in the process of running the test after the upgraded version of the application to be upgraded is built, detecting the application scenario in which each post-upgrade tracking point is triggered, and collecting the stack data at the corresponding application scenario when each post-upgrade tracking point is triggered; based on the generated stack data and the application scenario, determining the scene information corresponding to each post-upgrade tracking point.
[0117] In this step, after the construction of the application to be upgraded is completed, for each post-upgrade tracking point, the application scenario in which each post-upgrade tracking point is triggered is detected, and the stack data generated when each post-upgrade tracking point is triggered is collected, and the application scenario corresponding to the same post-upgrade tracking point and the generated stack data set are combined to generate the scenario information corresponding to the upgrade tracking point.
[0118] Here, the application scenarios and stack data collection when the tracking point is triggered can be manually triggered to cover all scenarios and all stack data corresponding to all upgraded tracking points.
[0119] For example, for a display interface on a certain application, in the button function test of the display interface, a query button is displayed on the page. When a display interface on the application is constructed, a buried point is placed at the query button. During the test, the query button is clicked to trigger the buried point. At this time, the corresponding application scenario can be the display content of the interface after clicking the query button; the stack data generated by triggering the query button may include the display data of the interface after the jump, etc. The application scenario information and the stack data are packaged together to generate scenario information of the buried point at the query button.
[0120] Furthermore, after step 304, the detection method also includes: for each post-upgrade tracking point, if the attribute information of the post-upgrade tracking point is inconsistent with the attribute information of the corresponding pre-upgrade tracking point, and the scene information corresponding to the post-upgrade tracking point is inconsistent with the scene information corresponding to the corresponding pre-upgrade tracking point, it is determined that the upgrade of the application to be upgraded has failed.
[0121] In this step, for each upgraded tracking point, if the attribute information and corresponding scene information of the same upgraded tracking point are inconsistent with those of the tracking point before the upgrade, the upgrade of the application to be upgraded fails.
[0122] Furthermore, after determining that the application to be upgraded has failed to be upgraded, the detection method further includes: sending the upgraded application to be upgraded to a manual detection terminal, and sending an alarm message of upgrade failure to the manual detection terminal.
[0123] In this step, after determining that the application to be upgraded has failed to upgrade, the upgraded application to be upgraded is sent to the manual detection terminal, and an alarm message of the application to be upgraded failing is sent to the manual detection terminal so that an operator can check the cause of the upgrade failure at the manual detection terminal.
[0124] Among them, the alarm information sent to the manual detection terminal may include the link where the upgrade failed and the problem occurred, that is, whether the attribute information of the buried point itself has changed, or the scene indicated by the scene information after the buried point is triggered has a problem. If the attribute information of the buried point has changed, it is necessary to report to the manual detection terminal the location of the buried point after the upgrade, the class to which it belongs, the method, and the specific code of the method, and give the specific changes of the buried point after the upgrade compared with the buried point before the upgrade, such as how much the position has moved forward or backward, and which lines of the specific code of the corresponding method have problems, etc.; if the scene information of the buried point has changed, it is necessary to send to the manual detection terminal the scene changes of the application scene triggered when the buried point after the upgrade is triggered, or the specific changes of the corresponding stack data, such as when the buried point after the upgrade is triggered, the corresponding application scene is delayed in display, and the data order in the stack sequence is changed, etc.
[0125] Here, the method of sending the warning information to the manual detection terminal may be email or instant messaging tools.
[0126] Here, after the upgrade fails, in addition to sending warning information to the manual detection terminal and manually intervening to troubleshoot, you can also insert troubleshooting data for some possible tracking problems when building the application to be upgraded. When pre-set tracking problems occur, call the troubleshooting data and solve the tracking problems directly during the test.
[0127] Furthermore, after step 304, the detection method also includes: for each post-upgrade buried point, if the attribute information of the post-upgrade buried point is inconsistent with the attribute information of the corresponding pre-upgrade buried point, or the scene information corresponding to the post-upgrade buried point is inconsistent with the scene information corresponding to the corresponding pre-upgrade buried point, data review is performed on the post-upgrade buried point; if the result of the data review shows that the buried point change of the post-upgrade buried point is less than the preset change threshold, it is determined that the upgrade of the application to be upgraded is successful.
[0128] In this step, for each post-upgrade tracking point, in the attribute information and scene information, the post-upgrade tracking point is consistent with the pre-upgrade tracking point in one dimension, and is inconsistent with the pre-upgrade tracking point in another dimension. Because the change may be caused by new functions after the upgrade, it is necessary to review the data of the post-upgrade tracking point for the inconsistent dimension, and reconfirm the change between the post-upgrade tracking point and the pre-upgrade tracking point in this dimension. If it is detected that the change of each post-upgrade tracking point compared with the pre-upgrade tracking point is less than the preset change threshold, then the application to be upgraded is also considered to have been successfully upgraded.
[0129] Among them, the content of data review will change accordingly according to the different dimensions of the review. For example, the main content of the data review on the tracking point attribute information is the changes in the tracking point location, tracking point type, tracking point method name and specific code of the tracking point method after the upgrade and before the upgrade; the direction of the data review on the tracking point scenario information is mainly to trigger the application scenario when the corresponding tracking point is upgraded and the changes in the stack data compared with the tracking point before the upgrade.
[0130] Furthermore, when there is inconsistency between the attribute information of the buried point after the upgrade and the attribute information of the corresponding buried point before the upgrade, the data of the buried point after the upgrade with inconsistent attribute information is reviewed through the following steps: based on the attribute information of the buried point after the upgrade with inconsistent attribute information and the attribute information of the corresponding buried point before the upgrade, the difference between the buried point position of the buried point after the upgrade and the buried point position of the corresponding buried point before the upgrade is detected; if the difference is less than the preset position threshold, and the buried point feature of the buried point after the upgrade is consistent with the buried point feature of the corresponding buried point before the upgrade, it is determined that the buried point change of the buried point after the upgrade is less than the preset change threshold.
[0131] In this step, the attribute information of the post-upgrade burial point with inconsistent attribute information is compared with the post-upgrade burial point position indicated in the attribute information of the pre-upgrade burial point, and the difference between the two is obtained. If the difference is less than the preset position threshold and the burial point feature is consistent with the burial point feature before the upgrade, it is determined that the burial point change after the upgrade is less than the preset change threshold.
[0132] Among them, when the buried point position is accurate to the code layer, it can be determined on which line of the code segment the buried point is. At this time, the difference between the buried point position after the upgrade and the buried point position before the upgrade is the difference in the number of code lines at the code layer. For example, the buried point after the upgrade is on the 200th line of the code segment, and the buried point before the upgrade is on the 160th line of the code segment, then the difference in the buried point position between the two is 40 lines.
[0133] Here, the setting of the preset position threshold can be determined based on the changes in the build data caused by the upgraded version. For example, at the code level, the number of lines of code for the new function is 10, and the code was added before the current monitoring tracking. Then, for the upgraded version, the tracking position of the upgraded tracking point should be 10 lines after the tracking position of the tracking point before the upgrade at the code level. Under normal circumstances, the tracking position difference of 10 lines is acceptable, so 10 can be a preset position threshold at this time. Therefore, there may be different preset position thresholds or the same preset position thresholds for different upgraded tracking points. The same preset position threshold can be set at the code level according to the value corresponding to the upgraded tracking point with the largest code number difference.
[0134] Here, in the above embodiment, the point attributes are considered to be the case where the point position after the upgrade has a deviation within the preset position threshold and the point features are consistent. In actual applications, the point position may also be considered to have a deviation within the preset position threshold and the point features are inconsistent. During manual investigation, for the case where the point features after the upgrade are inconsistent with those before the upgrade, it is possible to check whether there is an association between the class to which the point after the upgrade belongs and the class to which the point before the upgrade belongs (for example, they are parent and child classes of each other). There are differences in the specific codes of the point burying methods, but whether different codes can provide the same method, etc.
[0135] Furthermore, when the scene information corresponding to the post-upgrade buried point is inconsistent with the scene information corresponding to the corresponding pre-upgrade buried point, the data of the post-upgrade buried point with inconsistent scene information is reviewed through the following steps: based on the scene information of the post-upgrade buried point with inconsistent scene information and the scene information of the corresponding pre-upgrade buried point, detect whether the scene deviation between the application scene when the post-upgrade buried point is triggered and the application scene when the corresponding pre-upgrade buried point is triggered is less than a preset deviation threshold; if the scene deviation is less than the preset deviation threshold, and the stack data generated when the post-upgrade buried point is triggered is consistent with the stack data generated when the corresponding pre-upgrade buried point is triggered, determine that the buried point change of the post-upgrade buried point is less than the preset change threshold.
[0136] In this step, it is detected whether the scene information of the upgraded buried point after the upgrade indicated by the scene information of the inconsistent scene information indicates that the deviation between the application scene when the upgraded buried point is triggered after the upgrade and the application scene when the corresponding buried point before the upgrade is triggered is less than the preset deviation threshold; when it is determined that the scene deviation is less than the preset deviation threshold, and the stack data generated when the upgraded buried point is triggered is consistent with the stack data generated when the corresponding buried point before the upgrade is triggered, it is determined that the change of the buried point after the upgrade is less than the preset change threshold.
[0137] Among them, for the deviation of application scenarios, it can be compared from the switching time of application scenarios and the presentation effect of application scenario screen when the tracking point is triggered after the upgrade. For the switching time of application scenarios, when the tracking point is triggered after the upgrade, the processing time of the corresponding application scenario switching time may change according to the size of the installation package after the upgrade. There is a certain delay in background loading. The time for switching the application scenario after the upgrade is triggered may be slightly slower than the tracking point time before the upgrade. Within the acceptable range of delay, it can be considered that the scene deviation is less than the preset deviation threshold; for the presentation effect of the application scene screen, the presentation effect of the application scene when the tracking point is triggered after the upgrade may be improved compared with before the upgrade, such as changes in resolution. Within an acceptable range, it can also be considered that the scene deviation is less than the preset deviation threshold.
[0138] Here, for the same application scenario, when the tracking point is triggered, it must have the same stack data. When the stack data is the same and the scenario deviation is less than the preset deviation threshold, it is determined that the tracking point change after the upgrade is less than the preset change threshold.
[0139] The detection method provided in the embodiment of the present application obtains at least one pre-upgrade tracking point in the application to be upgraded, as well as the attribute information of each pre-upgrade tracking point and the scene information corresponding to each pre-upgrade tracking point; in the process of building the upgraded version of the application to be upgraded, scans the version build data of the application to be upgraded to obtain at least one post-upgrade tracking point and the attribute information of each post-upgrade tracking point; in the process of running the application to be upgraded after completing the upgrade version construction, obtains the scene information corresponding to each post-upgrade tracking point; matches the attribute information of each post-upgrade tracking point with the attribute information of the corresponding pre-upgrade tracking point, and matches the scene information corresponding to each post-upgrade tracking point with the scene information corresponding to the corresponding pre-upgrade tracking point; if the attribute information of each post-upgrade tracking point is consistent with the attribute information of the corresponding pre-upgrade tracking point, and the scene information corresponding to each post-upgrade tracking point is consistent with the scene information corresponding to the corresponding pre-upgrade tracking point, it is determined that the upgrade of the application to be upgraded is successful.
[0140] Compared with the prior art methods, the present application obtains at least one post-upgrade tracking point and the attribute information of each post-upgrade tracking point by scanning the version building data of the application to be upgraded during the process of building the upgraded version of the application to be upgraded, and the scene information corresponding to each post-upgrade tracking point during the test process, and matches and compares the attribute information and scene information of each post-upgrade tracking point with the acquired attribute information and scene information of the corresponding pre-upgrade tracking point, and determines whether the application to be upgraded is successfully upgraded based on the matching and comparison results. In this way, each tracking point can be monitored in real time during the construction and testing process of the upgraded version before release. Before the new version is released, the tracking points can be fully used to detect the application to be upgraded during the development and testing stage, and the tracking point problems can be fully discovered during the development and testing stage to improve the quality and utilization of the tracking points, which is conducive to improving the real-time performance, delivery timeliness and release efficiency of application detection, and helps to reduce time consumption.
[0141] Based on the same inventive concept, a detection device corresponding to the detection method is also provided in the embodiment of the present application. Since the principle of solving the problem by the device in the embodiment of the present application is similar to the above-mentioned detection method in the embodiment of the present application, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be repeated.
[0142] Reference Figure 4 , Figure 5 As shown, Figure 4 This is one of the structural schematic diagrams of a detection device provided in this application. Figure 5 This is a second structural diagram of a detection device provided in an embodiment of the present application, such as Figure 4 As shown, the detection device 400 includes:
[0143] The pre-upgrade embedding point information acquisition module 410 is used to obtain at least one pre-upgrade embedding point in the application to be upgraded, as well as attribute information of each pre-upgrade embedding point and scene information corresponding to each pre-upgrade embedding point.
[0144] The post-tracking point attribute acquisition module 420 is used to scan the version construction data of the application to be upgraded during the process of building an upgraded version of the application to be upgraded, and obtain at least one post-upgrade tracking point and attribute information of each post-upgrade tracking point.
[0145] The post-embedded point scenario acquisition module 430 is used to obtain the scenario information corresponding to each post-upgrade embedded point during the running test of the application to be upgraded after the upgraded version is built.
[0146] The upgrade determination module 440 is used to determine whether the application to be upgraded has been successfully upgraded based on the attribute information of each pre-upgrade buried point, the scene information corresponding to each pre-upgrade buried point, the attribute information of each post-upgrade buried point, and the scene information corresponding to each post-upgrade buried point.
[0147] Further, when the post-embedded point scene acquisition module 430 is used to obtain the scene information corresponding to each post-upgrade embedded point during the operation test after the upgraded version of the application to be upgraded is built, the post-embedded point scene acquisition module 430 is specifically used to:
[0148] During the running test after the upgraded version of the application to be upgraded is built, the application scenario where each post-upgrade tracking point is triggered is detected, and the stack data at the corresponding application scenario when each post-upgrade tracking point is triggered is collected;
[0149] Based on the generated stack data and the application scenario, determine the scenario information corresponding to each upgraded tracking point.
[0150] Further, when the upgrade determination module 440 is used to determine whether the application to be upgraded is successfully upgraded based on the attribute information of each pre-upgrade buried point, the scene information corresponding to each pre-upgrade buried point, the attribute information of each post-upgrade buried point, and the scene information corresponding to each post-upgrade buried point, the upgrade determination module 440 is specifically used to:
[0151] Match the attribute information of each post-upgrade buried point with the attribute information of the corresponding pre-upgrade buried point, and match the scene information corresponding to each post-upgrade buried point with the scene information corresponding to the corresponding pre-upgrade buried point;
[0152] If the attribute information of each post-upgrade buried point is consistent with the attribute information of the corresponding pre-upgrade buried point, and the scene information corresponding to each post-upgrade buried point is consistent with the scene information corresponding to the corresponding pre-upgrade buried point, it is determined that the application to be upgraded has been successfully upgraded.
[0153] Further, such as Figure 5 As shown, the detection device 400 further includes a failure determination module 450, and the failure determination module 450 is used to:
[0154] For each post-upgrade tracking point, if the attribute information of the post-upgrade tracking point is inconsistent with the attribute information of the corresponding pre-upgrade tracking point, and the scene information corresponding to the post-upgrade tracking point is inconsistent with the scene information corresponding to the corresponding pre-upgrade tracking point, it is determined that the upgrade of the application to be upgraded has failed.
[0155] Furthermore, the detection device 400 further includes a warning information sending module 460, and the warning information sending module 460 is used to:
[0156] The upgraded application to be upgraded is sent to the manual detection terminal, and an alarm message of upgrade failure is sent to the manual detection terminal.
[0157] Furthermore, the detection device 400 further includes a data review module 470, and the data review module 470 is used to:
[0158] For each post-upgrade tracking point, if the attribute information of the post-upgrade tracking point is inconsistent with the attribute information of the corresponding pre-upgrade tracking point, or the scene information corresponding to the post-upgrade tracking point is inconsistent with the scene information corresponding to the corresponding pre-upgrade tracking point, the data of the post-upgrade tracking point is reviewed;
[0159] If the result of the data review shows that the tracking point change after the upgrade is less than the preset change threshold, it is determined that the upgrade of the application to be upgraded is successful.
[0160] Further, when the attribute information of the post-upgrade tracking point is inconsistent with the attribute information of the corresponding pre-upgrade tracking point, the data review module 470 performs data review on the post-upgrade tracking point with inconsistent attribute information through the following steps:
[0161] Based on the attribute information of the post-upgrade burying point with inconsistent attribute information and the attribute information of the corresponding pre-upgrade burying point, detecting the difference between the burying point position of the post-upgrade burying point and the burying point position of the corresponding pre-upgrade burying point;
[0162] If the difference is smaller than the preset position threshold, and the burial point feature of the burial point after the upgrade is consistent with the burial point feature of the corresponding burial point before the upgrade, it is determined that the burial point change of the burial point after the upgrade is smaller than the preset change threshold.
[0163] Further, when the scene information corresponding to the post-upgrade tracking point is inconsistent with the scene information corresponding to the pre-upgrade tracking point, the data review module 470 performs data review on the post-upgrade tracking point with inconsistent scene information through the following steps:
[0164] Based on the scene information of the post-upgrade tracking point with inconsistent scene information and the scene information of the corresponding pre-upgrade tracking point, detect whether the scene deviation between the application scene when the post-upgrade tracking point is triggered and the application scene when the corresponding pre-upgrade tracking point is triggered is less than a preset deviation threshold;
[0165] If the scene deviation is less than the preset deviation threshold, and the stack data generated when the post-upgrade tracking point is triggered is consistent with the stack data generated when the corresponding pre-upgrade tracking point is triggered, it is determined that the tracking point change of the post-upgrade tracking point is less than the preset change threshold.
[0166] Furthermore, the attribute information includes a buried point location and buried point features, and the buried point features include at least one of a buried point type, a buried point method name, and a buried point method data.
[0167] Furthermore, the scenario information includes the application scenario in which the embedding point is triggered and the stack data generated when the embedding point is triggered.
[0168] The detection device provided in the embodiment of the present application obtains at least one pre-upgrade tracking point in the application to be upgraded, as well as the attribute information of each pre-upgrade tracking point and the scene information corresponding to each pre-upgrade tracking point; in the process of building an upgraded version of the application to be upgraded, scans the version build data of the application to be upgraded to obtain at least one post-upgrade tracking point and the attribute information of each post-upgrade tracking point; in the process of running the application to be upgraded after completing the upgrade version construction, obtains the scene information corresponding to each post-upgrade tracking point; based on the attribute information of each pre-upgrade tracking point, the scene information corresponding to each pre-upgrade tracking point, the attribute information of each post-upgrade tracking point and the scene information corresponding to each post-upgrade tracking point, determines whether the application to be upgraded is successfully upgraded.
[0169] Compared with the prior art methods, the present application obtains at least one post-upgrade tracking point and the attribute information of each post-upgrade tracking point by scanning the version building data of the application to be upgraded during the process of building the upgraded version of the application to be upgraded, and the scene information corresponding to each post-upgrade tracking point during the test process, and matches and compares the attribute information and scene information of each post-upgrade tracking point with the acquired attribute information and scene information of the corresponding pre-upgrade tracking point, and determines whether the application to be upgraded is successfully upgraded based on the matching and comparison results. In this way, each tracking point can be monitored in real time during the construction and testing process of the upgraded version before release. Before the new version is released, the tracking points can be fully used to detect the application to be upgraded during the development and testing stage, and the tracking point problems can be fully discovered during the development and testing stage to improve the quality and utilization of the tracking points, which is conducive to improving the real-time performance, delivery timeliness and release efficiency of application detection, and helps to reduce time consumption.
[0170] For descriptions of the processing flow of each module in the device and the interaction flow between each module, reference may be made to the relevant descriptions in the above method embodiment, which will not be described in detail here.
[0171] See also Figure 6 , Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Figure 6 As shown in , the electronic device 600 includes a processor 610 , a memory 620 and a bus 630 .
[0172] The memory 620 stores machine-readable instructions executable by the processor 610. When the electronic device 600 is running, the processor 610 communicates with the memory 620 via the bus 630. When the machine-readable instructions are executed by the processor 610, the above-mentioned Figure 2 as well as Figure 3The specific implementation of the steps of the detection method in the method embodiment shown can be found in the method embodiment, which will not be repeated here.
[0173] 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 computer program can execute the above-mentioned Figure 2 as well as Figure 3 The specific implementation of the steps of the detection method in the method embodiment shown can be found in the method embodiment, which will not be repeated here.
[0174] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0175] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, and the indirect coupling or communication connection of devices or units can be electrical, mechanical or other forms.
[0176] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0177] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
[0178] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present application can essentially be embodied in the form of a software product, or in other words, the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0179] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present application, which are used to illustrate the technical solutions of the present application, rather than to limit them. The protection scope of the present application is not limited thereto. Although the present application is described in detail with reference to the above-mentioned embodiments, ordinary technicians in the field should understand that any technician familiar with the technical field can still modify the technical solutions recorded in the above-mentioned embodiments within the technical scope disclosed in the present application, or can easily think of changes, or make equivalent replacements for some of the technical features therein; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.
Claims
1. A detection method, characterized in that: The detection method comprises: Obtain at least one pre-upgrade embedding point in the application to be upgraded, as well as attribute information of each pre-upgrade embedding point and scenario information corresponding to each pre-upgrade embedding point; In the process of building an upgraded version of the application to be upgraded, scanning the version building data of the application to be upgraded to obtain at least one post-upgrade tracking point and attribute information of each post-upgrade tracking point; During the running test after the upgraded version of the application to be upgraded is built, the scene information corresponding to each post-upgrade tracking point is obtained; Determine whether the application to be upgraded is successfully upgraded based on the attribute information of each pre-upgrade buried point, the scene information corresponding to each pre-upgrade buried point, the attribute information of each post-upgrade buried point, and the scene information corresponding to each post-upgrade buried point, wherein the attribute information includes the buried point location and the buried point feature, and the scene information includes the application scene in which the buried point is located when it is triggered and the stack data generated when the buried point is triggered; The determining whether the application to be upgraded is successfully upgraded based on the attribute information of each pre-upgrade buried point, the scene information corresponding to each pre-upgrade buried point, the attribute information of each post-upgrade buried point, and the scene information corresponding to each post-upgrade buried point includes: Match the attribute information of each post-upgrade buried point with the attribute information of the corresponding pre-upgrade buried point, and match the scene information corresponding to each post-upgrade buried point with the scene information corresponding to the corresponding pre-upgrade buried point to obtain a comparison result; Determine whether the application to be upgraded is successfully upgraded according to the comparison result.
2. The detection method according to claim 1, characterized in that: In the process of running the test after the upgraded version of the application to be upgraded is built, the scene information corresponding to each post-upgrade tracking point is obtained, including: During the running test after the upgraded version of the application to be upgraded is built, the application scenario where each post-upgrade tracking point is triggered is detected, and the stack data at the corresponding application scenario when each post-upgrade tracking point is triggered is collected; Based on the generated stack data and the application scenario, determine the scenario information corresponding to each upgraded tracking point.
3. The detection method according to claim 1, characterized in that: Determining whether the application to be upgraded is successfully upgraded according to the comparison result includes: If the attribute information of each post-upgrade buried point is consistent with the attribute information of the corresponding pre-upgrade buried point, and the scene information corresponding to each post-upgrade buried point is consistent with the scene information corresponding to the corresponding pre-upgrade buried point, it is determined that the application to be upgraded has been successfully upgraded.
4. The detection method according to claim 1, characterized in that: Determining whether the application to be upgraded is successfully upgraded according to the comparison result includes: For each post-upgrade tracking point, if the attribute information of the post-upgrade tracking point is inconsistent with the attribute information of the corresponding pre-upgrade tracking point, and the scene information corresponding to the post-upgrade tracking point is inconsistent with the scene information corresponding to the corresponding pre-upgrade tracking point, it is determined that the upgrade of the application to be upgraded has failed.
5. The detection method according to claim 4, characterized in that: After determining that the upgrade of the application to be upgraded fails, the detection method further includes: The upgraded application to be upgraded is sent to the manual detection terminal, and an alarm message of upgrade failure is sent to the manual detection terminal.
6. The detection method according to claim 1, characterized in that: Determining whether the application to be upgraded is successfully upgraded according to the comparison result includes: For each post-upgrade tracking point, if the attribute information of the post-upgrade tracking point is inconsistent with the attribute information of the corresponding pre-upgrade tracking point, or the scene information corresponding to the post-upgrade tracking point is inconsistent with the scene information corresponding to the corresponding pre-upgrade tracking point, the data of the post-upgrade tracking point is reviewed; If the result of the data review shows that the tracking point change after the upgrade is less than the preset change threshold, it is determined that the upgrade of the application to be upgraded is successful.
7. The detection method according to claim 6, characterized in that: When the attribute information of the post-upgrade tracking point is inconsistent with the attribute information of the corresponding pre-upgrade tracking point, the data of the post-upgrade tracking point with inconsistent attribute information is reviewed through the following steps: Based on the attribute information of the post-upgrade burying point with inconsistent attribute information and the attribute information of the corresponding pre-upgrade burying point, detecting the difference between the burying point position of the post-upgrade burying point and the burying point position of the corresponding pre-upgrade burying point; If the difference is smaller than the preset position threshold, and the burial point feature of the burial point after the upgrade is consistent with the burial point feature of the corresponding burial point before the upgrade, it is determined that the burial point change of the burial point after the upgrade is smaller than the preset change threshold.
8. The detection method according to claim 6, characterized in that: If the scene information corresponding to the post-upgrade tracking point is inconsistent with the scene information corresponding to the pre-upgrade tracking point, perform data review on the post-upgrade tracking point with inconsistent scene information by following the steps below: Based on the scene information of the post-upgrade tracking point with inconsistent scene information and the scene information of the corresponding pre-upgrade tracking point, detect whether the scene deviation between the application scene when the post-upgrade tracking point is triggered and the application scene when the corresponding pre-upgrade tracking point is triggered is less than a preset deviation threshold; If the scene deviation is less than the preset deviation threshold, and the stack data generated when the post-upgrade tracking point is triggered is consistent with the stack data generated when the corresponding pre-upgrade tracking point is triggered, it is determined that the tracking point change of the post-upgrade tracking point is less than the preset change threshold.
9. The detection method according to any one of claims 1 to 8, characterized in that: The burying point feature includes at least one of a burying point type, a burying point method name, and a burying point method data.
10. A detection device, characterized in that: The detection device comprises: A pre-upgrade embedding point information acquisition module is used to acquire at least one pre-upgrade embedding point in the application to be upgraded, as well as attribute information of each pre-upgrade embedding point and scenario information corresponding to each pre-upgrade embedding point; A post-tracking point attribute acquisition module is used to scan the version construction data of the application to be upgraded during the process of building an upgraded version of the application to be upgraded, and obtain at least one post-upgrade tracking point and attribute information of each post-upgrade tracking point; A post-buffering scene acquisition module is used to obtain scene information corresponding to each post-upgraded buried point during the running test after the upgraded version of the application to be upgraded is built; An upgrade determination module, for determining whether the application to be upgraded is successfully upgraded based on the attribute information of each pre-upgrade buried point, the scene information corresponding to each pre-upgrade buried point, the attribute information of each post-upgrade buried point, and the scene information corresponding to each post-upgrade buried point, wherein the attribute information includes the buried point location and the buried point feature, and the scene information includes the application scene in which the buried point is located when it is triggered and the stack data generated when the buried point is triggered; The upgrade determination module is specifically used for: Match the attribute information of each post-upgrade buried point with the attribute information of the corresponding pre-upgrade buried point, and match the scene information corresponding to each post-upgrade buried point with the scene information corresponding to the corresponding pre-upgrade buried point to obtain a comparison result; Determine whether the application to be upgraded is successfully upgraded according to the comparison result.
11. The detection device according to claim 10, characterized in that: When the post-embedded point scene acquisition module is used to obtain scene information corresponding to each post-upgrade embedded point during the operation test after the upgraded version of the application to be upgraded is built, the post-embedded point scene acquisition module is specifically used to: During the running test after the upgraded version of the application to be upgraded is built, the application scenario where each post-upgrade tracking point is triggered is detected, and the stack data at the corresponding application scenario when each post-upgrade tracking point is triggered is collected; Based on the generated stack data and the application scenario, determine the scenario information corresponding to each upgraded tracking point.
12. The detection device according to claim 10, characterized in that: When the upgrade determination module is used to determine whether the application to be upgraded is successfully upgraded according to the comparison result, the upgrade determination module is specifically used to: If the attribute information of each post-upgrade buried point is consistent with the attribute information of the corresponding pre-upgrade buried point, and the scene information corresponding to each post-upgrade buried point is consistent with the scene information corresponding to the corresponding pre-upgrade buried point, it is determined that the application to be upgraded has been successfully upgraded.
13. The detection device according to claim 10, characterized in that: When the upgrade determination module is used to determine whether the application to be upgraded is successfully upgraded according to the comparison result, the upgrade determination module is specifically used to: For each post-upgrade tracking point, if the attribute information of the post-upgrade tracking point is inconsistent with the attribute information of the corresponding pre-upgrade tracking point, and the scene information corresponding to the post-upgrade tracking point is inconsistent with the scene information corresponding to the corresponding pre-upgrade tracking point, it is determined that the upgrade of the application to be upgraded has failed.
14. The detection device according to claim 13, characterized in that: The detection device further includes a warning information sending module, and the warning information sending module is used to: The upgraded application to be upgraded is sent to the manual detection terminal, and an alarm message of upgrade failure is sent to the manual detection terminal.
15. The detection device according to claim 10, characterized in that: When the upgrade determination module is used to determine whether the application to be upgraded is successfully upgraded according to the comparison result, the upgrade determination module is specifically used to: For each post-upgrade tracking point, if the attribute information of the post-upgrade tracking point is inconsistent with the attribute information of the corresponding pre-upgrade tracking point, or the scene information corresponding to the post-upgrade tracking point is inconsistent with the scene information corresponding to the corresponding pre-upgrade tracking point, the data of the post-upgrade tracking point is reviewed; If the result of the data review shows that the tracking point change after the upgrade is less than the preset change threshold, it is determined that the upgrade of the application to be upgraded is successful.
16. The detection device according to claim 15, characterized in that: When the attribute information of the post-upgrade tracking point is inconsistent with the attribute information of the corresponding pre-upgrade tracking point, the data review module performs data review on the post-upgrade tracking point with inconsistent attribute information through the following steps: Based on the attribute information of the post-upgrade burying point with inconsistent attribute information and the attribute information of the corresponding pre-upgrade burying point, detecting the difference between the burying point position of the post-upgrade burying point and the burying point position of the corresponding pre-upgrade burying point; If the difference is smaller than the preset position threshold, and the burial point feature of the burial point after the upgrade is consistent with the burial point feature of the corresponding burial point before the upgrade, it is determined that the burial point change of the burial point after the upgrade is smaller than the preset change threshold.
17. The detection device according to claim 15, characterized in that: When the scene information corresponding to the post-upgrade tracking point is inconsistent with the scene information corresponding to the pre-upgrade tracking point, the data review module performs data review on the post-upgrade tracking point with inconsistent scene information through the following steps: Based on the scene information of the post-upgrade tracking point with inconsistent scene information and the scene information of the corresponding pre-upgrade tracking point, detect whether the scene deviation between the application scene when the post-upgrade tracking point is triggered and the application scene when the corresponding pre-upgrade tracking point is triggered is less than a preset deviation threshold; If the scene deviation is less than the preset deviation threshold, and the stack data generated when the post-upgrade tracking point is triggered is consistent with the stack data generated when the corresponding pre-upgrade tracking point is triggered, it is determined that the tracking point change of the post-upgrade tracking point is less than the preset change threshold.
18. The detection device according to any one of claims 10 to 17, characterized in that: The burying point feature includes at least one of a burying point type, a burying point method name, and a burying point method data.
19. An electronic device, characterized in that: include: A processor, a storage medium and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor communicates with the storage medium via the bus, and the processor executes the machine-readable instructions to perform the steps of the detection method as described in any one of claims 1 to 9.
20. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the detection method according to any one of claims 1 to 9 are executed.
