Burial point verification method and device, computer equipment, readable storage medium and program product
By analyzing buried point test cases and simulating operations, and automatically grabbing and verifying buried point data, the problem of insufficient intelligence of buried point verification in the existing technology is solved, and efficient and accurate verification of buried point data is achieved.
Patent Information
- Application Number
- CN202411719979.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-11-28
- Publication Date
- 2025-03-18
AI Technical Summary
In the prior art, the intelligentity of buried point verification is poor, which makes it difficult to ensure the accuracy of data recording, and the verification process is cumbersome and time-consuming and cost-effective.
By analyzing the buried point test cases for the target application, obtaining the operation steps to be executed, simulating the user to automatically operate the target application, grab the actual buried point data, and analyzing and comparing the actual results with the expected results according to the preset rules to achieve automated verification.
It improves the intelligence of buried point verification, reduces the time and cost of manual verification, ensures the accuracy and consistency of buried point data, and reduces the regression cost.
Smart Images
Figure CN119645855A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of software testing technology, and in particular to a method, device, computer equipment, computer-readable storage medium and computer program product for checking embedded points. Background Art
[0002] Tracking is the process of collecting some information in a specific process of the application to track the use of the application and provide data support for further optimization of the product. When you want to track user behavior, observe page-related click data, or analyze the effect of an event, you need to track data in advance, and then collect the corresponding data through the pre-set data tracking points when the user uses the application.
[0003] At present, the application's tracking data has become an important basis for various industries to make market decisions and future development directions. The accuracy of the data affects whether the decision is correct and whether the direction of market analysis is correct. Therefore, application behavior analysis is becoming more and more important. How to ensure the accuracy of application behavior data records is attracting more and more attention.
[0004] Verifying tracking points can ensure the accuracy of the collected information. Currently, most of the tracking point verification of applications is semi-automatic. Either the tracking point is generated by the automated application, and then the tracking point results are manually verified. Manual verification is time-consuming and has a limited verification range. Or, the tracking point is only triggered, and the accuracy and consistency of the tracking point cannot be verified.
[0005] Therefore, in the related technology, there is a problem of poor intelligence of point verification. Summary of the invention
[0006] Based on this, it is necessary to provide a point-of-care verification method, device, computer equipment, computer-readable storage medium and computer program product that can improve the intelligence of point-of-care verification in response to the above-mentioned technical problems.
[0007] In a first aspect, the present application provides a method for burying point verification, comprising:
[0008] Parsing the tracking test cases for the target application to obtain the operation steps to be executed; the operation steps to be executed are used to simulate the user's automatic operation of the target application;
[0009] Capture actual buried point data corresponding to buried points in the target application; the actual buried point data is buried point data obtained by operating the target application through the operation steps;
[0010] Parse the actual buried point data according to the preset buried point data parsing rules to obtain the buried point actual result corresponding to the buried point test case;
[0011] The actual result of the buried point is compared with the expected result of the buried point corresponding to the buried point test case to obtain the buried point verification result corresponding to the buried point test case.
[0012] In one embodiment, parsing the actual buried point data according to a preset buried point data parsing rule to obtain the buried point actual result corresponding to the buried point test case includes:
[0013] Obtain the domain name of the burying point corresponding to the captured actual burying point data;
[0014] The captured actual burying point data is stored in a file matching the corresponding domain name, so as to parse different actual burying point data according to different domain names.
[0015] In one embodiment, before the step of parsing the tracking test case for the target application, the method further includes:
[0016] Obtaining an initial test case for the target application; the initial test case is a test case about business logic;
[0017] Parsing the initial test case according to a preset test system to generate the tracking test case for testing the tracking point;
[0018] The embedded point test case is stored in a target file; the target file uses an extensible markup language format to store content.
[0019] In one embodiment, comparing the actual result of the buried point with the expected result of the buried point corresponding to the buried point test case to obtain the buried point verification result corresponding to the buried point test case includes:
[0020] The actual result of the tracking point is stored in a JSON string;
[0021] Obtain the expected result of the tracking point defined by the tracking point test case in the target file;
[0022] Compare the expected result of the tracking point with the JSON string content of the actual result of the tracking point to obtain the tracking point verification result.
[0023] In one embodiment, the number of the embedded test cases is multiple, and the method further includes:
[0024] Obtaining the buried point verification result corresponding to each of the buried point test cases; the buried point verification result includes the buried point verification passing or the buried point verification failing;
[0025] Determine the first number of use cases and the second number of use cases according to the buried point verification results corresponding to each of the buried point test cases; the first number of use cases is the number of buried point test cases whose corresponding buried point verification results are passed by the buried point verification; the second number of use cases is the number of buried point test cases whose corresponding buried point verification results are failed by the buried point verification;
[0026] Generate an automated tracking test report based on the number of the first use cases and the number of the second use cases.
[0027] In one embodiment, the actual result of the buried point includes the actual result corresponding to each of the operation steps, the expected result of the buried point includes the expected result corresponding to each of the operation steps, and the actual result of the buried point is compared with the expected result of the buried point corresponding to the buried point test case to obtain the buried point verification result corresponding to the buried point test case, including:
[0028] Compare the actual result corresponding to the same operation step with the corresponding expected result to obtain the embedded point verification result corresponding to the embedded point test case.
[0029] In one embodiment, the capturing of actual tracking data corresponding to tracking points in the target application includes:
[0030] Dynamically obtain the IP address of the terminal device running the target application and each network card information of the terminal device;
[0031] According to the IP address and each of the network card information, obtain a data packet capturer on each network interface of the terminal device by opening a device method;
[0032] The actual buried point data is captured according to the data packet capturer.
[0033] In a second aspect, the present application also provides a buried point verification device, including:
[0034] A use case analysis unit, used to analyze the embedded test case for the target application to obtain the operation steps to be executed; the operation steps to be executed are used to simulate the user's automatic operation of the target application;
[0035] A capture unit, used to capture actual buried point data corresponding to buried points in the target application; the actual buried point data is the buried point data obtained by operating the target application through the operation steps;
[0036] A data analysis unit, used to analyze the actual buried point data according to a preset buried point data analysis rule to obtain the buried point actual result corresponding to the buried point test case;
[0037] The comparison unit is used to compare the actual result of the buried point with the expected result of the buried point corresponding to the buried point test case to obtain the buried point verification result corresponding to the buried point test case.
[0038] In a third aspect, the present application further provides a computer device, wherein the computer device comprises a memory and a processor, wherein the memory stores a computer program, and when the computer program is executed by the processor, the steps of the above method are implemented.
[0039] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program implements the steps of the above method when executed by a processor.
[0040] In a fifth aspect, the present application further provides a computer program product, wherein the computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the above method are implemented.
[0041] The above-mentioned buried point verification method, device, computer equipment, computer-readable storage medium and computer program product obtain the operation steps to be executed by parsing the buried point test case for the target application; the operation steps to be executed are used to simulate the user's automated operation of the target application; the actual buried point data corresponding to the buried points in the target application are captured; the actual buried point data is the buried point data obtained by operating the target application through the operation steps; the actual buried point data is parsed according to the preset buried point data parsing rules to obtain the actual buried point results corresponding to the buried point test case; the actual buried point results are compared with the expected buried point results corresponding to the buried point test case to obtain the buried point verification results corresponding to the buried point test case.
[0042] In this way, by parsing the tracking test case for the target application, the operation steps for simulating the user's automated operation of the target application are obtained, so that the actual tracking data corresponding to the tracking in the target application obtained by operating the target application through the operation steps can be captured, and the actual tracking result corresponding to the tracking test case is obtained by parsing the actual tracking data, so as to compare the actual tracking result with the expected tracking result corresponding to the tracking test case, and obtain the tracking verification result corresponding to the tracking test case, so as to realize the automated operation of the tracking in the application according to the tracking test case, and automatically verify the tracking result, so as to achieve the purpose of automated verification of the entire tracking link, improve the test work efficiency, reduce the threshold and cost of tracking test for testers, and thereby reduce the regression cost of tracking, ensure the quality of tracking data, and improve the intelligence of tracking verification. BRIEF DESCRIPTION OF THE DRAWINGS
[0043] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.
[0044] Figure 1 A schematic diagram of a flow chart of a method for checking buried points in an embodiment;
[0045] Figure 2 A system architecture diagram of a point-of-use verification system in an embodiment;
[0046] Figure 3 A flowchart of another method for checking buried points in an embodiment;
[0047] Figure 4 It is a flowchart of a method for checking buried points in another embodiment;
[0048] Figure 5 It is a structural block diagram of a buried point verification device in an embodiment;
[0049] Figure 6 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION
[0050] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.
[0051] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.
[0052] In one embodiment, Figure 1 As shown, a method for checking buried points is provided. This embodiment uses the method applied to a server as an example. The server can be implemented by an independent server or a server cluster composed of multiple servers. In this embodiment, the method includes the following steps:
[0053] Step S110, parsing the embedded test case for the target application to obtain the operation steps to be executed.
[0054] The operation steps to be executed are used to simulate the user's automated operation of the target application program.
[0055] Among them, the tracking test case is a test case used to test the tracking points in the target application.
[0056] In actual applications, the tracking test case can also be named as the tracking test case.
[0057] The target application may refer to the application to be tested.
[0058] The application program may be any front-end application in the prior art, such as an APP, a common web page, an H5 page, and the like.
[0059] In the specific implementation, the server can obtain the embedded test cases for the target application, and parse the embedded test cases to obtain the operation steps to be executed. These operation steps to be executed are operation steps that can be recognized by the target application, and the operation steps to be executed can be used to simulate the user's automated operation of the target application.
[0060] Step S120, capturing actual buried point data corresponding to the buried points in the target application.
[0061] The actual tracking data is the tracking data obtained by operating the target application through the operation steps.
[0062] Among them, in the process of operating the target application by parsing the operation steps obtained by the tracking test case, the tracking points in the target application can be triggered, so that the tracking points in the target application are triggered to execute the functional modules corresponding to the tracking points, so that the target application can send the tracking point data corresponding to the tracking point to the server through the terminal device where it is located, and the tracking point data corresponding to the tracking point is the actual tracking point data.
[0063] It is understandable that when the target application is operated through the operating steps, the target application will send a large amount of data to the server through the terminal device where it is located, including actual buried data, and the server needs to capture the actual buried data from the large amount of data sent by the terminal device.
[0064] Step S130, parse the actual buried point data according to the preset buried point data parsing rules to obtain the buried point actual result corresponding to the buried point test case.
[0065] Among them, the buried point data parsing rules are the rules used to parse the buried point data.
[0066] The actual result of the buried point is the analysis result obtained by analyzing the actual buried point data.
[0067] In a specific implementation, the server can parse the actual embedded point data according to the preset embedded point data parsing rules to obtain the actual embedded point results corresponding to the embedded point test case.
[0068] Step S140, compare the actual result of the buried point with the expected result of the buried point corresponding to the buried point test case, and obtain the buried point verification result corresponding to the buried point test case.
[0069] The expected result of the tracking point is the expected result pre-defined in the tracking point test case for the tracking point in the target application.
[0070] In the specific implementation, the server can compare the actual result of the tracking point with the expected result of the tracking point corresponding to the tracking point test case, and compare whether the actual result of the tracking point is consistent with the expected result of the tracking point, so as to obtain the tracking point verification result corresponding to the tracking point test case.
[0071] The result of the buried point verification can be either passed or failed.
[0072] In the above-mentioned buried point verification method, the operation steps to be executed are obtained by parsing the buried point test cases for the target application; the operation steps to be executed are used to simulate the user's automated operation of the target application; the actual buried point data corresponding to the buried points in the target application are captured; the actual buried point data is the buried point data obtained by operating the target application through the operation steps; the actual buried point data is parsed according to the preset buried point data parsing rules to obtain the actual buried point results corresponding to the buried point test cases; the actual buried point results are compared with the expected buried point results corresponding to the buried point test cases to obtain the buried point verification results corresponding to the buried point test cases.
[0073] In this way, by parsing the tracking test case for the target application, the operation steps for simulating the user's automated operation of the target application are obtained, so that the actual tracking data corresponding to the tracking in the target application obtained by operating the target application through the operation steps can be captured, and the actual tracking result corresponding to the tracking test case is obtained by parsing the actual tracking data, so as to compare the actual tracking result with the expected tracking result corresponding to the tracking test case, and obtain the tracking verification result corresponding to the tracking test case, so as to realize the automated operation of the tracking in the application according to the tracking test case, and automatically verify the tracking result, so as to achieve the purpose of automated verification of the entire tracking link, improve the test work efficiency, reduce the threshold and cost of tracking test for testers, and thereby reduce the regression cost of tracking, ensure the quality of tracking data, and improve the intelligence of tracking verification.
[0074] In one embodiment, the actual buried point data is parsed according to the preset buried point data parsing rules to obtain the actual buried point results corresponding to the buried point test case, including: obtaining the domain name of the buried point corresponding to the captured actual buried point data; storing the captured actual buried point data in a file matching the corresponding domain name, so as to parse different actual buried point data according to different domain names.
[0075] In the specific implementation, when the server parses the actual buried point data according to the preset buried point data parsing rules to obtain the actual buried point results corresponding to the buried point test case, the server can obtain the domain name of the buried point corresponding to the captured actual buried point data, and store the captured actual buried point data in a file matching the corresponding domain name, so as to parse different actual buried point data according to different domain names.
[0076] The technical solution of this embodiment is to obtain the domain name of the buried point corresponding to the captured actual buried point data; store the captured actual buried point data in a file matching the corresponding domain name, so as to parse different actual buried point data according to different domain names. In this way, by storing the captured actual buried point data in a file matching the domain name corresponding to the corresponding buried point, the captured actual buried point data is stored according to the domain name classification, which can facilitate the later management and maintenance of the buried point data, and the data of each domain name is concentrated together, and the search and editing efficiency is higher; at the same time, after the actual buried point data is classified according to the domain name, it can be more quickly parsed for the actual buried point data under a specific domain name, identify user behaviors and trends, and thus optimize more targetedly; further, each domain name independently stores the corresponding actual buried point data, which can reduce analysis errors caused by data confusion or duplicate data, thereby improving the reliability of the data.
[0077] In one embodiment, before the step of parsing the embedded point test case for the target application, the method also includes: obtaining an initial test case for the target application; parsing the initial test case according to a preset test system to generate an embedded point test case for testing the embedded point; and storing the embedded point test case in a target file.
[0078] Among them, the initial test case is a test case about business logic.
[0079] The target file stores content in the eXtensible Markup Language (XML) format.
[0080] The preset test system may be a test system selected by the user.
[0081] In a specific implementation, before parsing the tracking test case for the target application, the server can first obtain an initial test case for the target application, which is a test case about business logic. The initial test case can be parsed according to a preset test system to generate a tracking test case for testing tracking, so that the tracking test case is stored in a target file, and the target file uses an extensible markup language format to store content.
[0082] In actual applications, the initial test case can be a test case about business logic written by the user in a defined format on an HTML (HyperText Markup Language) page as the initial test case, so as to generate a test case for the test point by parsing the HTML page, and store the test case finally parsed in the target file. Exemplarily, the target file can be a test.xml file.
[0083] The technical solution of this embodiment, before the step of parsing the tracking test case for the target application, obtains the initial test case for the target application; the initial test case is a test case about the business logic; the initial test case is parsed according to the preset test system to generate a tracking test case for testing the tracking; the tracking test case is stored in the target file; the target file uses the extensible markup language format to store the content. In this way, by parsing the initial test case about the business logic into an extensible markup language file, the extensible markup language format is convenient for expanding the test case. When it is necessary to add a new test case or modify an existing test case, it can be simply modified in the extensible markup language file, which facilitates the version maintenance and management of the test case to improve the accuracy of the tracking data and the integrity of the test case.
[0084] In one embodiment, the actual result of the buried point is compared with the expected result of the buried point corresponding to the buried point test case to obtain the buried point verification result corresponding to the buried point test case, including: storing the actual result of the buried point in a JSON string; obtaining the expected result of the buried point defined in the buried point test case in the target file; comparing the expected result of the buried point with the JSON string content of the actual result of the buried point to obtain the buried point verification result.
[0085] Among them, JSON (JavaScript Object Notation) is a lightweight data interaction format.
[0086] In the specific implementation, when the server compares the actual result of the tracking point with the expected result of the tracking point corresponding to the tracking point test case to obtain the tracking point verification result corresponding to the tracking point test case, the server can store the parsed actual result of the tracking point in a JSON string, obtain the expected result of the tracking point defined for the tracking point in the tracking point test case in the parsed test.xml file (target file), compare the expected result of the tracking point with the JSON string content of the actual result of the tracking point, and obtain the tracking point verification result.
[0087] Among them, during the comparison process, comparison methods such as regular matching, parameterization, or constant verification can be used. If the JSON string content of the actual result of the buried point is inconsistent with the corresponding expected result of the buried point, the buried point verification fails. If the JSON string content of the actual result of the buried point is consistent with the corresponding expected result of the buried point, the buried point verification passes.
[0088] In some of the embodiments, a burying point whose JSON string content of the actual result is inconsistent with the corresponding expected result of the burying point can be identified as a test failure, and a burying point whose JSON string content of the actual result is consistent with the corresponding expected result of the burying point can be identified as a test pass.
[0089] In some of the embodiments, the actual result of the buried point includes the actual result corresponding to each operation step, the expected result of the buried point includes the expected result corresponding to each operation step, the actual result of the buried point is compared with the expected result of the buried point corresponding to the buried point test case, and the buried point verification result corresponding to the buried point test case is obtained, including: comparing the actual result corresponding to the same operation step with the corresponding expected result, and obtaining the buried point verification result corresponding to the buried point test case.
[0090] In the specific implementation, the actual results of the tracking point include the actual results corresponding to each operation step, and the expected results of the tracking point include the expected results corresponding to each operation step. When the server compares the actual results of the tracking point with the expected results of the tracking point corresponding to the tracking point test case to obtain the tracking point verification results corresponding to the tracking point test case, the server can compare the actual results corresponding to the same operation step with the corresponding expected results to obtain the tracking point verification results corresponding to the tracking point test case.
[0091] Specifically, as mentioned above, in the process of operating the target application by parsing the operation steps obtained from the buried point test case, the buried points in the target application can be triggered, and the execution of each operation step can trigger the buried point, so that the target application can send the buried point data corresponding to the buried point to the server through the terminal device where it is located. In this way, the actual buried point data captured by the server also includes the buried point data corresponding to the buried point triggered by each operation step. Therefore, in the process of parsing the actual buried point data according to the preset buried point data parsing rules to obtain the actual buried point results corresponding to the buried point test case, the actual results corresponding to the buried points triggered by each operation step can be parsed.
[0092] Correspondingly, the expected results related to the tracking points triggered by each operation step are defined in the tracking point test case, that is, the expected results of the tracking points corresponding to the tracking point test case include the expected results corresponding to the tracking points triggered by each operation step. By comparing the actual results corresponding to the same operation step with the corresponding expected results, it is possible to identify whether each tracking point in the target application has passed the test, and obtain the tracking point verification results corresponding to the tracking point test case based on whether each tracking point in the target application has passed the test.
[0093] In the technical solution of this embodiment, the actual result of the buried point includes the actual result corresponding to each operation step, and the expected result of the buried point includes the expected result corresponding to each operation step. By comparing the actual result corresponding to the same operation step with the corresponding expected result, the buried point verification result corresponding to the buried point test case is obtained. In this way, the expected result of the buried point includes the expected result corresponding to each operation step, which can ensure that the actual result generated by each operation step is triggered with a standard control; by comparing the actual result obtained by parsing the buried point data captured by each operation step with the corresponding expected result, the accuracy and consistency of the buried point verification are achieved, and the consistency of the buried point test case and the actual buried point data generated is guaranteed.
[0094] In one embodiment, there are multiple buried point test cases, and the method also includes: obtaining the buried point verification result corresponding to each buried point test case; the buried point verification result includes the buried point verification passed or the buried point verification failed; according to the buried point verification results corresponding to each buried point test case, determining the first case number and the second case number; according to the first case number and the second case number, generating an automated buried point test report.
[0095] Among them, the automated tracking test report is a test report used to record the execution results of all tracking test cases.
[0096] Among them, the automated tracking test report can be a test report in HTML format.
[0097] Among them, the first number of use cases is the number of buried point test cases whose corresponding buried point verification results pass the buried point verification.
[0098] Among them, the second number of use cases is the number of buried point test cases whose corresponding buried point verification results are failed buried point verification.
[0099] Among them, the buried point verification result corresponding to the buried point test case can be determined according to the test result of the buried point tested by the buried point test case.
[0100] For example, a tracking point test case can test multiple tracking points. Among the tracking points tested by the tracking point test case, if the corresponding test result is that the number of tracking points that passed the test meets the preset threshold, then the tracking point verification result corresponding to the tracking point test case is that the tracking point verification passed; if the corresponding test result is that the number of tracking points that passed the test does not meet the preset threshold, then the tracking point verification result corresponding to the tracking point test case is that the tracking point verification failed.
[0101] In the specific implementation, there are multiple tracking test cases, and the server can obtain the tracking verification results corresponding to each tracking test case; the tracking verification results include the tracking verification passed or the tracking verification failed; according to the tracking verification results corresponding to each tracking test case, the number of first test cases and the number of second test cases are determined; according to the number of first test cases and the number of second test cases, an automated tracking test report is generated.
[0102] Furthermore, at least one type of data includes the quantity data of the automated tracking test report (the number of first use cases, the number of second use cases, and the total number of use cases), the tracking verification results corresponding to each tracking test case, and the test results corresponding to each tracking point tested by each tracking test case.
[0103] According to the technical solution of this embodiment, there are multiple buried point test cases, and the buried point verification results corresponding to each buried point test case are obtained; the buried point verification results include buried point verification passed or buried point verification failed; according to the buried point verification results corresponding to each buried point test case, the first number of cases and the second number of cases are determined; the first number of cases is the number of buried point test cases whose corresponding buried point verification results are buried point verification passed; the second number of cases is the number of buried point test cases whose corresponding buried point verification results are buried point verification failed; according to the first number of cases and the second number of cases, an automated buried point test report is generated.
[0104] In this way, by generating an automated test report based on the tracking verification results of each tracking test case, the user can clearly and accurately understand the verification results of each tracking test case through the automated test report to improve the target application.
[0105] In practical applications, the server may be deployed with a point-of-use verification system, and the steps of the above-mentioned point-of-use verification method are performed by the point-of-use verification system. For the convenience of understanding by those skilled in the art, take the target application as an APP as an example, Figure 2 A system architecture diagram of a buried point verification system is provided. Figure 2 As shown, the burying point verification system mainly includes: a burying point use case management module 210, a burying point use case analysis and execution use case module 220, a burying point data capture and analysis module 230, and a burying point verification module 240.
[0106] The tracking test case management module 210 is mainly used to manage the tracking test cases and the expected results of each test case (tracking expected results).
[0107] Tracking test case analysis and execution module 220: mainly parses the tracking test cases recorded by the open source testing framework (for example, fitnesse) into operation steps that can be recognized by the APP, and then executes the tracking test cases through the open source automated testing framework (for example, selenium);
[0108] The tracking data capture and analysis module 230 captures the tracking data generated by the executed tracking test cases and analyzes the actual results of the tracking;
[0109] The tracking point verification module 240: compares and verifies the expected results in the tracking point test case with the actual results of the analyzed tracking point to obtain the accuracy of the tracking point verification.
[0110] Figure 3 A flowchart of a method for performing a point-of-care verification system is provided. Figure 3 As shown, the buried point verification method includes the following steps:
[0111] 1. Construction of the tracking test case platform: The test framework is installed, configured and started. The initial test cases about the business logic are described on the HTML page. The test framework will parse the initial test cases transmitted by the HTML page according to the selected test system. The test system will generate tracking test cases by parsing the HTML page, and store the final parsed tracking test cases in the target file that uses the Extensible Markup Language format to store content.
[0112] 2. Operate the APP according to the embedded test cases and execute the embedded test cases: mainly through the embedded test cases generated in step 1, read the target file of the generated embedded test cases, and then parse them into the operation steps of the automated testing framework. Through the automated testing framework, simulate the real user to automatically operate the APP to trigger the sending of embedded tests. Each embedded test case is executed independently to ensure the independence of the case.
[0113] 3. Implementation of the packet capture program: Dynamically obtain the IP address of the terminal device running the target application, as well as the information of each network card of the terminal device; based on the IP address and the information of each network card, obtain the data packet capturer on each network interface of the terminal device by opening the device method; and capture the actual buried data based on the data packet capturer.
[0114] In actual applications, it is mainly implemented through a middleware that can monitor the current network situation (for example, jpcap). First, the IP address of the terminal device running the target application is dynamically obtained, and then the information of each network card of the terminal device corresponding to the IP address is obtained. The data packet capturer (for example, JpcapCaptor object) on each network interface is obtained by opening the device (openDevice) method. This method can be used to capture packets, and then packet capture is started. After the actual embedded point data corresponding to the embedded point in the target application is captured, the captured actual embedded point data is parsed according to the domain name of the embedded point and stored in the file of the corresponding domain name, which is convenient for parsing different actual embedded point data according to different domain names. The actual embedded point data corresponding to each embedded point test case is stored in a embedded point file (the file content must be cleared before each embedded point test case is executed), ensuring that the actual embedded point data is generated when each embedded point test case is executed, thereby ensuring the accuracy of the embedded point data.
[0115] 4. Tracking accuracy check: parse the actual tracking data captured, store the actual tracking results obtained by parsing into a JSON string, and compare the expected results defined in the tracking test cases in the target file (including regular matching, parameterization, or constant verification, etc.) with the JSON string content of the actual tracking data parsed by the packet capture. If it is different from the expected result, the tracking check fails. If the expected result is consistent with the JSON string content of the actual tracking data, the tracking check passes.
[0116] 5. Finally, the execution results of all the test cases are encapsulated into an HTML test report. According to step 4, the number of test cases that passed and failed the test is recorded to generate an automated test report.
[0117] In this way, this method includes the writing and saving of tracking point use cases, and can parse the tracking point test cases into operation steps that can be recognized by the APP and the expected results of each operation step, then operate the APP according to the operation steps to generate actual tracking point data, and then capture the actual tracking point data, and then parse the actual tracking point data into actual tracking point results for storage, compare and verify the expected tracking point results in the tracking point test case with the parsed actual tracking point results, identify the tracking points with inconsistent verification as test failures, and verify the tracking points with consistent verification as test passes, thereby realizing the technical effect of automatically operating the tracking points according to the APP tracking point test cases and automatically verifying the tracking point results, achieving the purpose of automatic verification of the entire tracking point link, improving the work efficiency of the tracking point test, reducing the regression cost of the tracking point, and ensuring the quality of the tracking point data.
[0118] It solves the problem of time-consuming manual verification of APP tracking points, insufficient verification, and inability to ensure the accuracy of tracking point data. It can not only increase the accuracy of tracking point data, but also improve testing efficiency, reduce the threshold and cost of tracking point testing for testers, and provide more accurate guarantees for big data analysis and market decision-making, so that data analysis and market decisions have data to rely on.
[0119] At the same time, the related technology does not implement the management of tracking test cases, and cannot ensure the consistency between the tracking test cases and the actual tracking data generated. The present application manages the tracking test cases through a testing framework, verifies the actual results and expected results recorded in each operation step, combines use case management with use case execution, and ensures that the execution results of the use cases are well-documented. In addition, the use cases are clear, ensuring the consistency between the tracking test cases and the actual tracking data generated.
[0120] In summary, this method achieves fully automated verification from use case management to tracking triggering to the final tracking verification, effectively improving the intelligence of tracking verification.
[0121] In another embodiment, Figure 4 As shown, a method for checking the buried points is provided, and the method is applied to a server as an example for explanation, including the following steps:
[0122] Step S402: obtaining an initial test case for the target application.
[0123] Step S404, parse the initial test case according to the preset test system, and generate a tracking test case for testing tracking.
[0124] Step S406, storing the embedded test case in the target file.
[0125] Step S408, parsing the tracking test case for the target application to obtain the operation steps to be executed.
[0126] Step S410, capturing actual buried point data corresponding to buried points in the target application.
[0127] Step S412, parse the actual buried point data according to the preset buried point data parsing rules to obtain the buried point actual result corresponding to the buried point test case.
[0128] Step S414, compare the actual result of the buried point with the expected result of the buried point corresponding to the buried point test case, and obtain the buried point verification result corresponding to the buried point test case.
[0129] Step S416, determining the number of first test cases and the number of second test cases according to the test case verification results corresponding to each test case.
[0130] Step S418, generating an automated tracking test report based on the first number of use cases and the second number of use cases.
[0131] It should be noted that the specific limitations of the above steps can refer to the specific limitations of a buried point verification method above.
[0132] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.
[0133] Based on the same inventive concept, the embodiment of the present application also provides a point-of-sale verification device for implementing the point-of-sale verification method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more embodiments of the point-of-sale verification device provided below can refer to the limitations of the point-of-sale verification method above, and will not be repeated here.
[0134] In an exemplary embodiment, Figure 5As shown, a point-of-use verification device is provided, including: a use case analysis unit 510, a capture unit 520, a data analysis unit 530 and a comparison unit 540, wherein:
[0135] The use case analysis unit 510 is used to analyze the embedded test cases for the target application to obtain the operation steps to be executed; the operation steps to be executed are used to simulate the user's automated operation of the target application.
[0136] The capture unit 520 is used to capture the actual buried point data corresponding to the buried points in the target application; the actual buried point data is the buried point data obtained by operating the target application through the operation steps.
[0137] The data analysis unit 530 is used to analyze the actual buried point data according to the preset buried point data analysis rules to obtain the buried point actual result corresponding to the buried point test case.
[0138] The comparison unit 540 is used to compare the actual result of the buried point with the expected result of the buried point corresponding to the buried point test case to obtain the buried point verification result corresponding to the buried point test case.
[0139] In one of the embodiments, the data parsing unit 530 is specifically used to obtain the domain name of the burial point corresponding to the captured actual burial point data; store the captured actual burial point data in a file matching the corresponding domain name, so as to parse different actual burial point data according to different domain names.
[0140] In one of the embodiments, the device also includes: a use case acquisition unit, used to acquire an initial test case for the target application; the initial test case is a test case about business logic; the initial test case is parsed according to a preset test system to generate the embedded point test case for testing the embedded point; the embedded point test case is stored in a target file; the target file uses an extensible markup language format to store content.
[0141] In one of the embodiments, the comparison unit 540 is specifically used to store the actual result of the burying point in a JSON string; obtain the expected result of the burying point defined by the burying point test case in the target file; compare the expected result of the burying point with the JSON string content of the actual result of the burying point to obtain the burying point verification result.
[0142] In one of the embodiments, the actual result of the buried point includes the actual result corresponding to each of the operation steps, and the expected result of the buried point includes the expected result corresponding to each of the operation steps. The comparison unit 540 is specifically used to compare the actual result corresponding to the same operation step with the corresponding expected result to obtain the buried point verification result corresponding to the buried point test case.
[0143] In one of the embodiments, there are multiple buried point test cases, and the device further includes: a report generation unit, used to obtain a buried point verification result corresponding to each of the buried point test cases; the buried point verification result includes a buried point verification pass or a buried point verification fail; according to the buried point verification result corresponding to each of the buried point test cases, the first number of cases and the second number of cases are determined; the first number of cases is the number of buried point test cases whose corresponding buried point verification results are buried point verification pass; the second number of cases is the number of buried point test cases whose corresponding buried point verification results are buried point verification fail; according to the first number of cases and the second number of cases, an automated buried point test report is generated.
[0144] Each unit in the above-mentioned buried point verification device can be implemented in whole or in part by software, hardware and their combination. Each of the above-mentioned units can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the corresponding operations of each of the above-mentioned units.
[0145] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Figure 6 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. Among them, the processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store buried point test case data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a buried point verification method is implemented.
[0146] Those skilled in the art will understand that Figure 6The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.
[0147] In one embodiment, a computer device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above method embodiments when executing the computer program.
[0148] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.
[0149] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.
[0150] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.
[0151] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.
[0152] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.
[0153] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.
Claims
1. A method for burying point verification, characterized in that: The method comprises: Parsing the tracking test cases for the target application to obtain the operation steps to be executed; the operation steps to be executed are used to simulate the user's automatic operation of the target application; Capture actual buried point data corresponding to buried points in the target application; the actual buried point data is buried point data obtained by operating the target application through the operation steps; Parse the actual buried point data according to the preset buried point data parsing rules to obtain the buried point actual result corresponding to the buried point test case; The actual result of the buried point is compared with the expected result of the buried point corresponding to the buried point test case to obtain the buried point verification result corresponding to the buried point test case.
2. The method according to claim 1, characterized in that The step of parsing the actual buried point data according to the preset buried point data parsing rules to obtain the buried point actual result corresponding to the buried point test case includes: Obtain the domain name of the burying point corresponding to the captured actual burying point data; The captured actual burying point data is stored in a file matching the corresponding domain name, so as to parse different actual burying point data according to different domain names.
3. The method according to claim 1, characterized in that Before the step of parsing the tracking test case for the target application, the method further includes: Obtaining an initial test case for the target application; the initial test case is a test case about business logic; Parsing the initial test case according to a preset test system to generate the tracking test case for testing the tracking point; The embedded point test case is stored in a target file; the target file uses an extensible markup language format to store content.
4. The method according to claim 3, characterized in that The step of comparing the actual result of the buried point with the expected result of the buried point corresponding to the buried point test case to obtain the buried point verification result corresponding to the buried point test case includes: The actual result of the tracking point is stored in a JSON string; Obtain the expected result of the tracking point defined by the tracking point test case in the target file; Compare the expected result of the tracking point with the JSON string content of the actual result of the tracking point to obtain the tracking point verification result.
5. The method according to claim 1, characterized in that The actual result of the buried point includes the actual result corresponding to each of the operation steps, the expected result of the buried point includes the expected result corresponding to each of the operation steps, and the buried point actual result is compared with the expected result of the buried point corresponding to the buried point test case to obtain the buried point verification result corresponding to the buried point test case, including: Compare the actual result corresponding to the same operation step with the corresponding expected result to obtain the embedded point verification result corresponding to the embedded point test case.
6. The method according to claim 1, characterized in that The number of the embedded test cases is multiple, and the method further includes: Obtaining the buried point verification result corresponding to each buried point test case; the buried point verification result includes the buried point verification passing or the buried point verification failing; Determine the first number of use cases and the second number of use cases according to the buried point verification results corresponding to each of the buried point test cases; the first number of use cases is the number of buried point test cases whose corresponding buried point verification results are passed by the buried point verification; the second number of use cases is the number of buried point test cases whose corresponding buried point verification results are failed by the buried point verification; Generate an automated tracking test report based on the number of the first use cases and the number of the second use cases.
7. A buried point verification device, characterized in that: The device comprises: A use case analysis unit, used to analyze the embedded test case for the target application to obtain the operation steps to be executed; the operation steps to be executed are used to simulate the user's automatic operation of the target application; A capture unit, used to capture actual buried point data corresponding to buried points in the target application; the actual buried point data is the buried point data obtained by operating the target application through the operation steps; A data analysis unit, used to analyze the actual buried point data according to a preset buried point data analysis rule to obtain the buried point actual result corresponding to the buried point test case; The comparison unit is used to compare the actual result of the buried point with the expected result of the buried point corresponding to the buried point test case to obtain the buried point verification result corresponding to the buried point test case.
8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.
10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.