CN112148618A - Buried point testing method and buried point testing platform - Google Patents

Buried point testing method and buried point testing platform Download PDF

Info

Publication number
CN112148618A
CN112148618A CN202011079986.8A CN202011079986A CN112148618A CN 112148618 A CN112148618 A CN 112148618A CN 202011079986 A CN202011079986 A CN 202011079986A CN 112148618 A CN112148618 A CN 112148618A
Authority
CN
China
Prior art keywords
buried point
data
buried
tested
detected
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202011079986.8A
Other languages
Chinese (zh)
Inventor
赵志忠
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Dajia Internet Information Technology Co Ltd
Original Assignee
Beijing Dajia Internet Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Dajia Internet Information Technology Co Ltd filed Critical Beijing Dajia Internet Information Technology Co Ltd
Priority to CN202011079986.8A priority Critical patent/CN112148618A/en
Publication of CN112148618A publication Critical patent/CN112148618A/en
Pending legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3672Test management
    • G06F11/3688Test management for test execution, e.g. scheduling of test suites
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3672Test management
    • G06F11/3692Test management for test results analysis

Abstract

The disclosure provides a buried point testing method and a buried point testing platform. The buried point testing method can comprise the following steps executed by a buried point testing platform: creating a buried point table in a database; acquiring a buried point file to be detected comprising data of the buried point to be detected; the method comprises the steps that data of buried points to be detected in a buried point file to be detected are configured into a buried point table to update the buried point table; acquiring actual buried point data corresponding to a buried point in a target application; and determining effective buried points in the updated buried point table by comparing the actual buried point data with the data of the buried points to be detected in the updated buried point table.

Description

Buried point testing method and buried point testing platform
Technical Field
The disclosure relates to the field of computer software testing, in particular to a buried point testing method and a buried point testing platform.
Background
The data burying point enables related personnel such as products or operation and the like to perform customized statistics on more complex user data according to specific requirements. For example, when a user wants to track the behavior of the user, observe click data related to a page, or analyze the effect of an event activity, data embedding needs to be performed in advance, and then corresponding data is collected through the preset data embedding points when the user uses an application program to perform analysis and research.
However, due to the large number of buried points, a tester needs to frequently grab a buried point report request and check and analyze whether buried point data is normally reported field by field, which not only consumes time and labor, but also has low test efficiency.
Disclosure of Invention
The disclosure provides a buried point testing method, a buried point testing device and a buried point testing platform, which are used for at least solving the problem of low testing efficiency caused by the fact that testing personnel need to frequently check and analyze buried point data in the prior art.
According to a first aspect of the embodiments of the present disclosure, there is provided a buried point testing method, which may include the following steps: establishing a buried point table in a database of a buried point test platform; acquiring a buried point file to be detected comprising data of the buried point to be detected; the method comprises the steps that data of buried points to be detected in a buried point file to be detected are configured into a buried point table to update the buried point table; acquiring actual buried point data corresponding to a buried point in a target application; and comparing the actual buried point data with the data of the buried point to be detected in the updated buried point table to determine the effective buried point in the updated buried point table.
Optionally, each piece of to-be-tested buried point data in the to-be-tested buried point file may include at least one of an operating system type, occurrence time, identification information, function description, identification information, application version, and data generation time. Optionally, the actual buried point data may be uploaded to the buried point test platform via an upload interface of the target application, wherein the upload interface of the target application is modified to be an interface of the buried point test platform.
Optionally, the step of determining the effective buried point in the updated buried point table by comparing the actual buried point data with the data of the buried point to be measured in the updated buried point table may include: searching whether the buried point data to be detected with the identification information exists in the updated buried point table based on the identification information in the actual buried point data; determining a valid buried point in the buried point table based on the lookup result.
Optionally, the step of determining a valid buried point in the buried point table based on the search result may include: setting the test state of the buried point data to be tested to be effective under the condition that the buried point data to be tested with the same identification information as the actual buried point data exists in the buried point table; and under the condition that the data of the buried point to be tested with the same identification information as the actual buried point data does not exist in the buried point table, setting the test state of the data of the buried point to be tested as failure.
Optionally, the buried point testing method further includes: and screening effective data of the buried points to be tested and invalid data of the buried points to be tested corresponding to the target application from the buried point table based on the test state of the data of the buried points to be tested to generate a buried point test result, and displaying the buried point test result to a user.
According to a second aspect of the embodiments of the present disclosure, there is provided a buried point test platform, which may include: the interface is used for receiving actual buried point data corresponding to a buried point in a target application and a to-be-detected buried point file comprising to-be-detected buried point data; the database is used for creating a buried point table and configuring the buried point data to be detected in the buried point file to be detected into the buried point table to update the buried point table; and the processor is used for comparing the actual buried point data with the buried point data to be tested in the updated buried point table to determine the effective buried point in the updated buried point table.
Optionally, the interface may include a network interface and a user interface, where the network interface may receive actual buried point data corresponding to a buried point in the target application, and the user interface may receive a to-be-detected buried point file including the to-be-detected buried point data.
Optionally, each piece of to-be-tested buried point data in the to-be-tested buried point file may include at least one of an operating system type, occurrence time, identification information, function description, identification information, application version, and data generation time.
Optionally, the actual buried point data may be uploaded to the buried point test platform via an upload interface of the target application, wherein the upload interface of the target application is modified to be an interface of the buried point test platform.
Optionally, the processor may be configured to look up whether the data of the buried point to be tested with the identification information exists in the updated buried point table based on the identification information in the actual buried point data; and determining a valid buried point in the buried point table based on the lookup result.
Optionally, the processor may be configured to set the test state of the piece of buried point data to be tested to be valid in a case where buried point data to be tested having the same identification information as actual buried point data exists in the buried point table; and under the condition that the data of the buried point to be tested with the same identification information as the actual buried point data does not exist in the buried point table, setting the test state of the data of the buried point to be tested as failure.
Optionally, the processor may be configured to screen out valid buried point data to be tested and invalid buried point data to be tested corresponding to the target application from the buried point table based on the test state, the application version and the operating system type of the buried point data to be tested, so as to generate a buried point test result.
Optionally, the buried point test platform may include a display for displaying the buried point test result to a user.
According to a third aspect of the embodiments of the present disclosure, there is provided a buried point testing device, which may include: the data acquisition module is used for acquiring a to-be-detected buried point file comprising to-be-detected buried point data and actual buried point data corresponding to the buried point in the target application; and the data processing module is used for creating a buried point table in the database, configuring the data of the buried point to be detected in the file of the buried point to be detected into the buried point table to update the buried point table and determining the effective buried point in the updated buried point table by comparing the actual buried point data with the data of the buried point to be detected in the updated buried point table.
Optionally, each piece of to-be-tested buried point data in the to-be-tested buried point file may include at least one of an operating system type, occurrence time, identification information, function description, identification information, application version, and data generation time.
Optionally, the data processing module may search whether the data of the buried point to be detected with the identification information exists in the updated buried point table based on the identification information in the actual buried point data; and determining a valid buried point in the buried point table based on the lookup result.
Optionally, the data processing module may set the test state of the to-be-tested buried point data to be valid when the to-be-tested buried point data having the same identification information as the actual buried point data exists in the buried point table; and under the condition that the data of the buried point to be tested with the same identification information as the actual buried point data does not exist in the buried point table, setting the test state of the data of the buried point to be tested as failure.
Optionally, the data processing module may screen out valid buried point data to be tested and invalid buried point data to be tested corresponding to the target application from the buried point table based on the test state, the application version and the operating system type of the buried point data to be tested, so as to generate a buried point test result.
Optionally, the buried point testing device may include a display module, configured to display the generated buried point testing result to a user.
According to a fourth aspect of embodiments of the present disclosure, there is provided an electronic apparatus, which may include: at least one processor; at least one memory storing computer executable instructions, wherein the computer executable instructions, when executed by the at least one processor, cause the at least one processor to perform a buried point testing method as described above.
According to a fifth aspect of embodiments of the present disclosure, there is provided a computer readable storage medium storing instructions that, when executed by at least one processor, cause the at least one processor to perform a buried point testing method as described above.
According to a sixth aspect of embodiments of the present disclosure, there is provided a computer program product, instructions of which are executed by at least one processor in an electronic device to perform the buried point testing method as described above.
The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:
the embedded point data is directly obtained by changing an interface for uploading the embedded point data of the target application into an interface of the embedded point test platform, and the test state of the embedded point data to be tested in the embedded point file to be tested is determined by searching the identification information which is the same as the embedded point data in the database table without the need of checking and analyzing the embedded point data by a tester, so that the working pressure of the tester is reduced, the invalid embedded point can be accurately checked, and the test efficiency is greatly improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the disclosure and are not to be construed as limiting the disclosure.
FIG. 1 is a diagram of an application environment for testing a buried site provided in accordance with an embodiment of the present disclosure;
FIG. 2 is a flow chart of a buried point testing method according to an embodiment of the present disclosure;
FIG. 3 is a block diagram of a buried site test platform according to an embodiment of the present disclosure;
FIG. 4 is a schematic diagram of a buried site test platform interface according to an embodiment of the present disclosure;
FIG. 5 is a schematic flow chart for testing a buried site according to an embodiment of the present disclosure;
FIG. 6 is a block diagram of a buried site testing apparatus according to an embodiment of the present disclosure;
FIG. 7 is a block diagram of a buried site testing apparatus according to an embodiment of the present disclosure;
fig. 8 is a block diagram of an electronic device according to an embodiment of the disclosure.
Throughout the drawings, it should be noted that the same reference numerals are used to designate the same or similar elements, features and structures.
Detailed Description
The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of the embodiments of the disclosure as defined by the claims and their equivalents. Various specific details are included to aid understanding, but these are to be considered exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and constructions are omitted for clarity and conciseness.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the disclosure described herein are capable of operation in sequences other than those illustrated or otherwise described herein. The embodiments described in the following examples do not represent all embodiments consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
In this case, the expression "at least one of the items" in the present disclosure means a case where three types of parallel expressions "any one of the items", "a combination of any plural ones of the items", and "the entirety of the items" are included. For example, "include at least one of a and B" includes the following three cases in parallel: (1) comprises A; (2) comprises B; (3) including a and B. For another example, "at least one of the first step and the second step is performed", which means that the following three cases are juxtaposed: (1) executing the step one; (2) executing the step two; (3) and executing the step one and the step two.
The test application embedding point is a test technology that a tester operates a functional module in a target application by simulating a user and then checks whether the user operation is accurately recorded to the back end. By applying the buried point test, it is possible to analyze which function of the application is popular and which function is used less, thereby improving the function of the application.
For a test application embedded point, the embedded point is generally realized by a third-party tool to capture packets, and each embedded point needs to clear the packet capturing information generated last time when the embedded point is tested. However, tens of buried points are usually required to be tested each time, the operation is complicated, the time consumption is long, the efficiency is low, errors are easy to occur through manual observation, the testing quality is influenced, and economic losses are caused.
In the present disclosure, manual inspection is replaced by an automated technique, errors caused by operators are avoided, and efficiency of buried point testing is improved by a sophisticated automation system.
Hereinafter, according to various embodiments of the present disclosure, a method, an apparatus, and a system of the present disclosure will be described in detail with reference to the accompanying drawings.
FIG. 1 is a diagram of an application environment for testing a buried site provided in accordance with an embodiment of the present disclosure.
Referring to fig. 1, the application environment 100 includes a terminal 110 and a buried point test platform 120.
The terminal 110 is a terminal where a user is located, and the terminal 110 may be at least one of a smart phone, a tablet computer, a portable computer, a desktop computer, and the like. Although the embodiment shows only two terminals 110 for illustration, those skilled in the art will know that the number of the terminals may be one or more than two. The number of terminals and the type of the device are not limited in any way in the embodiments of the present disclosure.
The terminal 110 may be installed with a target application for providing the buried point data to the buried point test platform 120, and the target application may be a multimedia application, a social application, an information application, or the like. The buried point is preset in the target application. The embedded point is that some program codes are added into application project codes, and different functional operations use respective identifications to collect and count browsing data, access data and application use conditions of a user in an application, so that user interaction behaviors are analyzed to help products and operation to perform subsequent optimization. The essential technology of the embedded point is to monitor events in the running process of the application, judge and capture the events needing attention when the events occur, then obtain necessary context information, and finally send the information to a back end, such as the embedded point test platform 120.
According to the embodiment of the present disclosure, the embedded point data uploading interface of the target application may be modified to the interface of the embedded point test platform 120 in advance, so that after the embedded point in the target application is triggered to execute the functional module corresponding to the embedded point, the target application may directly send the embedded point data of the embedded point to the embedded point test platform 120. For example, the terminal 110 may be a terminal used by a user, an account of the user is registered in a target application running in the terminal 110, the user clicks a button on a home page interface of the target application, such as a garment, a fruit, an electrical appliance, and the like, and after the corresponding button is clicked, the terminal records the user operation and reports to the buried point test platform 120.
As an example, the buried point data upload interface of the target application may be changed by changing the item code of the target application. For example, before the project code of the target application is packaged by using the Jenkins persistent integration system, a tester may first write a script code for modifying the interface, and then configure the written script code into the Jenkins persistent integration system for compiling the target application. After the tester triggers and packages the data, the written script code can modify the original interface for uploading the buried point data in the target application into the interface of the buried point test platform 120, and then the packing process is performed. For example, a script for changing an interface can be written in python language. After packaging is successful, the tester may install the installation package of the target application to the terminal 110. The generated buried point data may then be directly reported to the buried point test platform 120 when the page function of the target application is clicked. Here, Jenkins is an open source software project, is a continuous integration tool developed based on Java, is used for monitoring continuous and repeated work, and aims to provide an open and easy-to-use software platform, so that continuous integration of software becomes possible. However, the above examples are merely exemplary, and the present disclosure is not limited to the packaging system or programming language described above.
The terminal 110 may be connected to the buried point test platform 120 through a wireless network, so that data interaction between the terminal 110 and the buried point test platform 120 is possible. For example, the network may comprise a Local Area Network (LAN), a Wide Area Network (WAN), a wireless link, an intranet, the Internet, a combination thereof, or the like. In addition, the terminal 110 may also be connected to the buried point test platform 120 through a wired network for data interaction. When data interaction is performed between the terminal 110 and the buried point test platform 120 by using a wired network, an interface for uploading buried point data by a target application may not be modified. In the present disclosure, the operation of modifying the interface for uploading buried point data by the target application is mainly directed to the process of data transmission using the wireless network.
The buried point test platform 120 may be a server for analyzing the received buried point data. For example, the buried site testing platform 120 may include an interface 121, a database 122, a display 124, and a processor 123, among other things. The above examples are merely exemplary and may further include, for example, a memory, a server, etc., to which the present disclosure is not limited. The buried point test platform 120 is configured to receive buried point data, analyze the buried point data, compare the buried point data with the buried point test data, and determine valid buried points and invalid buried points according to the comparison result. Here, the buried point test data may be from a buried point test file provided by an application product manager. The buried site test platform 120 of the present disclosure will be described in detail below with reference to fig. 3.
In the embodiment of the present disclosure, the buried point data may be sent to the buried point testing platform 120 in real time, or may be stored on the terminal 110 for a period of time and then sent to the buried point testing platform 120. For example, the function of sending the buried point data is executed by the function module corresponding to the buried point, and after the function module obtains the buried point data, the buried point data is sent to the buried point test platform in real time, so as to avoid that the buried point data is stored on the terminal to affect the performance of the target application and even the terminal 110.
In the above embodiment, the triggering operation for triggering the function module corresponding to the embedded point may be a manual operation, or may be generated by a simulation test tool.
Fig. 2 is a flow chart of a buried point testing method according to an embodiment of the present disclosure. According to the buried point testing method disclosed by the embodiment of the disclosure, the testing can be performed before the target application is on line, however, even after the target application is on line, the target application can be continuously tested by adopting the buried point testing method.
Referring to fig. 2, in step S201, a buried point table is created in a database.
As an example, a Mysql database may be used to create the buried point table. For example, a buried point table buried _ table may be created using the Mysql database. However, the present disclosure is not limited to the above database.
When creating the buried point table, each field in the buried point table may be the same as the list name of the file of the buried point to be tested provided by the previous product manager. The fields of the buried point list may be an operating system type, occurrence time, identification information, function description, identification information, application version, data generation time, and the like, respectively. However, the above field setting is only exemplary, and different elements may be set according to a file of a buried point under test actually provided from a tester as well as a product manager, and the present disclosure is not limited thereto.
In step S202, a buried point file to be measured including data of the buried point to be measured is acquired. Here, the file of the buried point to be detected may be provided by a product manager of the target application, the format of the file of the buried point to be detected may be an Excel list, each row of the Excel list represents one piece of data of the buried point to be detected, and each piece of data of the buried point to be detected may include at least one of an operating system type, occurrence time, identification information, function description, identification information, application version, and data generation time. For example, the contents of the part of the file of the buried point to be measured can be shown in table 1 below.
TABLE 1
The elements and order in table 1 are exemplary only, and the disclosure is not limited thereto.
In step S203, the buried point data to be measured in the buried point file to be measured is configured in the buried point table to update the buried point table. Each analyzed element (such as the type of an operating system, the occurrence time, the identification information, the function description, the identification information, the application version, the data generation time and the like in the embedded point) in each piece of embedded point data to be detected can be stored under a corresponding field in the embedded point table of the database by analyzing the embedded point file to be detected. For example, the buried point file buried.xls given by the product manager may be parsed into a buried point table buried _ table stored in the Mysql database. At this time, the buried point table buried _ table already contains all the buried point information to be currently tested.
In step S204, actual buried point data corresponding to a buried point in the target application is acquired. The essential technology of the embedded point is to monitor events in the running process of the application, judge and capture the events needing attention when the events occur, then obtain necessary context information, and finally send the information to the embedded point test platform 120.
As an example, the buried point is set in the target application, and an interface for uploading buried point data of the target application is set as the above-described interface of the buried point test platform. And executing a corresponding function module of the buried point through triggering operation, and sending the actual buried point data to the buried point test platform. Here, the trigger operation refers to an operation of the user on the interface in the target application, for example, clicking a certain button or a page turning operation up or down, or the like. By uploading information about user operations to the buried point test platform, it is possible to analyze which function of the target application is popular and which function is less used, thereby improving the function of the target application.
According to the embodiment of the present disclosure, the embedded point data uploading interface of the target application may be modified to the interface of the embedded point test platform 120 in advance, so that after the embedded point in the target application is triggered to execute the functional module corresponding to the embedded point, the target application may directly send the embedded point data of the embedded point to the embedded point test platform 120. For example, a user clicks a button such as a garment, a fruit, an electrical appliance, etc. on a home page interface of a target application, and after the corresponding button is clicked, the terminal records the user's operation and reports to the target application back end.
Since the buried point test platform receives buried point data from a plurality of terminals, the plurality of terminals are generally connected to the buried point test platform via a wireless network. Therefore, when the terminal is connected to the buried point test platform via the wireless network, the interface for uploading the buried point data to the target application on the terminal may be modified to the interface of the buried point test platform, so that the target application may directly send the buried point data of the buried point to the buried point test platform 120 after the buried point in the target application is triggered to execute the functional module corresponding to the buried point. It should be noted that, here, the interface of the buried point test platform may be a wireless network interface, and may also be an interface including a wireless network interface.
According to the embodiment of the disclosure, the buried point data uploading interface of the target application can be changed by changing the project code of the target application. For example, before the project code of the target application is packaged by using the Jenkins persistent integration system, a tester may first write a script code for modifying the interface, and then configure the written script code into the Jenkins persistent integration system for compiling the target application. After the tester triggers and packages the data, the written script code can modify the original interface for uploading the buried point data in the target application into the interface of the buried point test platform 120, and then the packing process is performed. For example, a script for changing an interface can be written in python language. After packaging is successful, the tester may install the installation package of the target application to the terminal 110. The generated buried point data may then be directly reported to the buried point test platform 120 when the page function of the target application is clicked. Here, Jenkins is an open source software project, is a continuous integration tool developed based on Java, is used for monitoring continuous and repeated work, and aims to provide an open and easy-to-use software platform, so that continuous integration of software becomes possible. However, the above examples are merely exemplary, and the present disclosure is not limited to the packaging system or programming language described above.
By modifying the interface of the uploading embedded point in the target application project code into the interface of the embedded point test platform, the embedded point data of the target application can be uploaded to the embedded point test platform under the condition of keeping the original logic of the target application.
In step S205, a valid buried point in the updated buried point table is determined by comparing the actual buried point data with the data of the buried point to be measured in the updated buried point table.
Specifically, whether the data of the buried point to be detected with the same identification information exists or not can be searched from the updated buried point table based on the identification information in the actual buried point data. And setting the test state of the buried point data to be tested to be valid under the condition that the buried point data to be tested with the identification information same as the actual buried point data exists in the buried point table, and setting the test state of the buried point data to be tested to be invalid under the condition that the buried point data to be tested with the identification information same as the actual buried point data does not exist in the buried point table. And screening effective buried point data to be tested and invalid buried point data to be tested corresponding to the target application from the buried point table based on the test state of the buried point data to be tested so as to generate a buried point test result.
As an example, the obtained actual buried point data may be parsed first to obtain an application version number, a system version (such as iOS/Android), identification information, a generation time, and the like in the buried point. Here, the identification information may be provided by a product manager, and different functions of the target application correspond to different identification information. Then, by using the identification information of the buried point, a search query is performed in the buried point table buried _ table in the Mysql database, and a piece of data to be tested which is the same as the identification information in the actual buried point data may be found, at this time, the buried point may be determined to be an effective buried point, and the test state of the buried point may be changed to pass by using, for example, an sql statement. By analogy, all the buried points to be tested can update the test state of each piece of buried point data to be tested in the buried point table buried _ table in such a way.
In addition, after the buried point test results are generated, the buried point test results can be presented to the user. Optionally, the user may access the URL of the buried point test platform through the browser of the terminal to view the buried point test result. Optionally, the generated buried point test results may be exported for downloading and viewing by the user.
According to the embodiment of the disclosure, the embedded point information of the target application is automatically uploaded to the embedded point testing platform, and the embedded point testing platform automatically completes comparison between actual embedded point data and embedded point data to be tested, so that the time cost for testing the embedded point of the target application is saved by more than half, errors caused by careless operation of workers are avoided, and the testing efficiency is improved to more than 95%.
Fig. 3 is a block diagram of a buried point test platform according to an embodiment of the present disclosure. According to the disclosed embodiment, the buried point test platform 120 may allow a target application in a terminal to be tested to upload buried point data to the buried point test platform 120, may allow a tester to import a buried point file to be tested provided by a product manager to the buried point test platform 120, and may have a function of viewing a buried point table in a browser and supporting screening of data according to a version number of the target application, or the like.
Referring to fig. 3, the buried point test platform 120 may include an interface 121, a database 122, a processor 123, and a display 124. In various embodiments, some modules in the buried site test platform 120 may be omitted, or additional modules may also be included. Furthermore, modules/elements according to various embodiments of the present disclosure may be combined to form a single entity, and thus the functions of the respective modules/elements may be equivalently performed prior to the combination.
The interface 121 may receive actual buried point data corresponding to a buried point in a target application. In the present disclosure, actual buried point data is uploaded to a buried point test platform via an upload interface of a target application, wherein the upload interface of the target application is modified to an interface of the buried point test platform. For example, before the App project code to be tested is packaged by a Jenkins continuous integration system, a preprogrammed python script buried.py can be configured in the Jenkins integration system for compiling the App project, wherein the python script can modify an interface of an uploading buried point in the App project code into an interface of the buried point testing platform 120, so that the embedded point of the App is uploaded to the buried point testing platform under the condition of keeping the logic of the original App project. After the testers trigger the package, the script buried.py can revise the original interface of uploading buried points in the App project into the interface of the buried point test platform, and then the Jenkins integrated system packages. After successful packaging, the tester can install the installation package into the terminal and click the App page function, so that the terminal reports the generated buried points to the buried point test platform 120.
According to an embodiment of the present disclosure, the interface 121 may include a wireless network interface, and after the interface for uploading the buried point data on the terminal is modified to the interface 121, the buried point test platform 120 may directly receive the buried point data from the outside via the interface 121. In addition, the interface 121 may further include, for example, an input/output interface, and a user may import the file of the buried point to be tested through the input/output interface of the interface 121. Alternatively, the interface 121 may be a network interface, and the actual buried point data corresponding to the buried point in the target application and the buried point file to be tested including the data of the buried point to be tested may be received via the interface 121. However, the above examples are merely illustrative and not limited thereto.
The buried point table may be updated by creating the buried point table using the database 122 and configuring the buried point data to be tested in the buried point file to the buried point table. For example, a Mysql database may be used to create the buried point table. For example, a buried point table buried _ table may be created using the Mysql database. The fields of the buried point table can be set according to each element in the buried point data to be detected in the buried point file to be detected. Each piece of buried point data to be tested in the buried point file to be tested may include at least one of an operating system type, occurrence time, identification information, function description, identification information, application version, and data generation time. For example, the buried point file to be tested, buried. xls, provided by the product manager can be parsed and stored in the buried point table, buried _ table, in the Mysql database.
The processor 123 may determine the valid buried points in the updated buried point table by comparing the actual buried point data with the data of the buried points to be measured in the updated buried point table.
The processor 123 may look up whether there is data of buried points to be measured having the same identification information from the updated buried point table based on the identification information in the actual buried point data, and determine a valid buried point in the buried point table based on the result of the look-up.
The processor 123 may set the test state of the piece of buried point data to be tested to be valid in a case where buried point data to be tested having identification information identical to actual buried point data exists in the buried point table, and the processor 123 may set the test state of the piece of buried point data to be invalid in a case where buried point data to be tested having identification information identical to actual buried point data does not exist in the buried point table.
The processor 123 may screen out valid buried point data to be tested and invalid buried point data to be tested corresponding to the target application from the buried point table based on the test state, application version, and operating system type of the buried point data to be tested, so as to generate a buried point test result.
Display 124 may display the buried site test results to a user.
In addition, the buried point test platform 120 may further include a user interface (not shown), through which a user may select, for example, a corresponding target application version and a terminal system in the buried point table to screen out all buried point data to be tested that are tested on the terminal.
According to the embodiment of the disclosure, the back end of the embedded point test platform 120 may be implemented by using a SpringBoot framework in Java language, the data persistence layer may be implemented by using a Mybatis framework, and the database may be implemented by using a Mysql database. The front end page of the buried site test platform 120 may be implemented using at least one of BootStrap, jQuery, Css3, Html5, and the like. In addition, the Python language can be used to combine with the back-end flush framework to write the interface with the same function. However, the above examples are merely exemplary, and the present disclosure is not limited thereto.
FIG. 4 is a schematic diagram of a buried site test platform interface according to an embodiment of the present disclosure.
Referring to fig. 4, the buried point test platform interface may include a user login box, a buried point file import box to be tested, a buried point test result generation button, and a buried point table display area.
After the buried point test platform is opened, a tester can log in the buried point test platform by inputting user information. The testing personnel can upload the to-be-tested embedded point file provided by the product manager to the embedded point testing platform through the to-be-tested embedded point file import frame, and after the to-be-tested embedded point file is successfully uploaded, the to-be-tested embedded point file which is just uploaded can be refreshed in the embedded point table display area. For example, the file of the buried points to be tested provided by the product manager may be an Excel table as shown in table 1, and after the file is uploaded successfully, the data of the buried points to be tested in the Excel table may be configured into the database buried point table one by one to update the buried point table.
And then, a tester can operate the target application on the terminal, so that the buried point test platform receives buried point data corresponding to buried points in the target application, the buried point test platform can analyze the buried point data, and the buried point data to be tested with the same identification information as the buried point data is searched in the buried point table according to the identification information in the buried point data. When a piece of buried point data to be tested with the same identification information is found, the purchase order test platform can set the test state of the piece of buried point data to be tested to be a passing state. By analogy, all the buried points to be tested update the test state of each buried point in the buried point table in such a way.
After all the buried points are tested, the tester may operate the buried point table in the buried point table display area, for example, the corresponding target application version or/and the terminal system may be selected on the page of the buried point table to screen out the buried point data in which all the tests of the tester on the terminal are in the pass state from the buried point table.
Alternatively, the tester may derive the final buried point test result by clicking on the buried point test result generation button.
However, the above-described platform interface is merely exemplary, and the platform interface may further include graphics, text, icons, videos, and any combination thereof associated with the buried point, and the disclosure is not limited thereto.
The display used to display the platform interface may be a touch screen display, such that the display may have the ability to capture touch signals on or over the surface of the display. The touch signal can be input to a processor as a control signal for processing. At this point, the display may also be used to provide virtual buttons and/or a virtual keyboard, also referred to as soft buttons and/or a soft keyboard.
In some embodiments, the display may be one, disposed on the front panel of the buried site test platform; in other embodiments, the number of the displays may be at least two, and the displays are respectively arranged on the front panel of the buried point testing platform and are electrically connected with the buried point testing platform. The Display 702 can be made of LCD (Liquid Crystal Display), OLED (Organic Light-Emitting Diode), and the like. However, the above examples are merely exemplary, and the present disclosure is not limited thereto.
FIG. 5 is a schematic flow chart for testing a buried site according to an embodiment of the present disclosure.
For the establishment of the buried point test platform 505, the tester 501 may use a SpringBoot framework in Java language to build the back end of the buried point test platform 120, use Mybatis to build a data persistence layer, and use the Mysql database 506. Tester 501 may implement the front end of buried site test platform 120 using at least one of BootStrap, jQuery, Css3, Html5, etc.
The tester 501 may create a buried point table buried _ table using the Mysql database 506. The fields in the buried point table buried _ table may be the same as the column name of the buried point file to be tested buried.xls 508 provided by the previous product manager. Fig. 5 shows that database 506 is contained inside buried site testing platform 505, and database 506 may also be external to the buried site testing platform. When database 506 is external to the buried site test platform, it may be connected to the buried site test platform via a wired or wireless network for data interaction.
The tester 501 can develop an upload function/interface on the buried point test platform 505, upload the buried point file to be tested, buried.xls 508, provided by the product manager, to the back end of the buried point test platform 505, and analyze and store the buried _ table in the Mysql database 506. At this time, the buried _ table already contains all the buried point information to be tested this time. In addition, the Python language can be used to combine with the back-end flush framework to write the interface with the same function. Here, the interface for uploading the file of the buried point to be tested may be an input/output interface. As an example, the tester 501 may log in the buried point test platform 505 and upload the buried point file to be tested buried.xls 508 provided by the product manager to the buried point test platform 505. After successful upload, the buried point information just uploaded can be refreshed in the buried _ table in the Mysql database 506. Alternatively, the tester 501 may also upload the file of the buried point to be tested using a network interface described below.
The tester 501 can write a python script buried.py, and the function of the tester is to modify an interface for uploading data of the embedded points in the App project codes into a network interface of the embedded point test platform 505, and to upload the data of the embedded points of the App to the embedded point test platform 505 under the condition of keeping the original code logic.
Before App project codes are packaged by Jenkins integrated system 502, tester 501 configures the script buried.py into Jenkins integrated system 502 which compiles App projects. Thus, after the tester 501 triggers and packs, the script buried.py modifies the original interface of uploading buried point data in the App project into a network interface of a buried point test platform, and then the Jenkins integrated system 502 packs the codes of the App project. After the package is successful, the tester 501 installs the installation package of the App to the terminal 503, and clicks the App page function and reports the generated data of the embedded point to the embedded point test platform 505. Here, the buried point information may be transmitted via the wireless network 504.
After receiving the embedded point data, the embedded point test platform 505 may analyze an App version number, a terminal system (e.g., iOS or Android), identification key information (which may be provided by a product manager, and sets different keys for operating different functions of the App), generation time, and the like in the embedded point data. Next, the buried point test platform 505 uses the identification key information of the buried point data to perform query in the buried _ table of the Mysql database 506, and at this time, if a piece of buried point data with the same identification key information is found, the test state of the buried point data may be changed to the passing state by using the sql statement. By analogy, all the buried points to be tested update the test state of each buried point in the buried _ table in this way.
Finally, tester 501 may view the buried point table page on display 507. According to embodiments of the present disclosure, display 507 may be a touch display screen, such that the display may have the ability to acquire touch signals on or over the surface of the display. The touch signal can be input to a processor as a control signal for processing. The tester 501 can select the corresponding App version and terminal system in the embedded point table through the display 507, and screen out all the embedded point data to be tested whose test state on the terminal is pass.
Referring to fig. 6, fig. 6 is a schematic structural diagram of a buried point testing device in a hardware operating environment according to an embodiment of the present disclosure.
As shown in fig. 6, the buried site testing apparatus 600 may include: a processing component 601, a communication bus 602, a network interface 603, an input-output interface 604, a memory 605, and a power component 606. Wherein a communication bus 602 is used to enable the connection communication between these components. The input output interface 604 may include a video display (such as a liquid crystal display) and a user interaction interface (such as a keyboard, mouse, touch input device, etc.), and optionally the input output interface 604 may also include a standard wired interface, a wireless interface. The network interface 603 may optionally include a standard wired interface, a wireless interface (e.g., a wireless fidelity interface). The memory 605 may be a high speed random access memory or a stable non-volatile memory. The memory 605 may alternatively be a storage device separate from the processing component 601 described previously.
Those skilled in the art will appreciate that the configuration shown in fig. 1 does not constitute a limitation of the buried site testing apparatus 600, and may include more or fewer components than those shown, or some components in combination, or a different arrangement of components.
As shown in fig. 6, the memory 605, which is a storage medium, may include therein an operating system, a data storage module, a network communication module, a user interface module, a client-side embedded point test program, and a database.
In the buried-point test apparatus 600 shown in fig. 6, the network interface 603 is mainly used for data communication with an external apparatus/terminal; the input/output interface 604 is mainly used for data interaction with a user; the processing component 601 and the memory 605 in the buried point testing apparatus 600 may be disposed in the buried point testing apparatus 600, and the buried point testing apparatus 600 calls the buried point testing program stored in the memory 605 through the processing component 601 to execute the buried point testing method provided by the embodiment of the present disclosure.
The processing component 601 may include at least one processor, and the memory 605 has stored therein a set of computer executable instructions that, when executed by the at least one processor, perform a method of buried point testing in accordance with an embodiment of the present disclosure.
The buried point testing apparatus 600 may receive actual buried point data corresponding to a buried point in a target application from an external apparatus (such as a terminal in which the target application is installed) via the network interface 603. According to the embodiment of the disclosure, in order to improve the efficiency of acquiring the buried point data, an interface for uploading the buried point data by the target application may be modified to be the network interface 603 of the buried point test equipment, so that the actual buried point data is directly uploaded to the buried point test equipment.
The buried site testing apparatus 600 may receive user input via the input-output interface 604. For example, the user may import a file of burial points to be tested including data of the burial points to be tested into the burial point testing apparatus 600 via the input-output interface 604.
The processing component 601 may build the buried point table using the database in the memory 605 and configure the buried point data to be tested in the buried point file to the buried point table to refresh the buried point table. Each piece of buried point data to be tested in the buried point file to be tested may include at least one of an operating system type, occurrence time, identification information, function description, identification information, application version, and data generation time. When the buried point table is established, each field in the buried point table may correspond to each element in the buried point data to be measured.
The processing component 601 may determine valid buried points in the updated buried point table by comparing the actual buried point data with the data of the buried points to be tested in the updated buried point table.
The processing component 601 may look up whether there is data of buried points to be tested having the same identification information from the updated buried point table based on the identification information in the actual buried point data, and determine a valid buried point in the buried point table based on the result of the look-up.
In the case where buried point data to be tested having the same identification information as the actual buried point data exists in the buried point table, the processing component 601 may set the test state of the piece of buried point data to be tested to valid/pass.
In the case where there is no data of buried point to be tested having the same identification information as the actual data of buried point in the buried point table, the processing component 601 may set the test state of the piece of data of buried point to be tested to be invalid.
The processing component 601 may screen out valid buried point data to be tested and invalid buried point data to be tested corresponding to the target application from the buried point table based on the test state of the buried point data to be tested, the application version and the operating system type input by the user, to generate a buried point test result.
When generating a test result, a user can enter the page of the buried point table through the input/output interface, and select an application version, an operating system type and the like which are required to be checked, so that all buried point data to be tested at the terminal are obtained. The buried point testing device 600 may display the buried point test results to a user via a display for viewing by the user.
The user can also access the URL of the buried point testing equipment through the browser of the terminal to check the buried point testing result.
As an example, the buried site testing apparatus 600 may be a PC computer, tablet device, personal digital assistant, smartphone, or other device capable of executing the set of instructions described above. Here, the buried point test apparatus 600 is not necessarily a single electronic device, but may be any combination of devices or circuits capable of executing the above-described instructions (or instruction sets) alone or in combination. The buried site test device 600 may also be part of an integrated control system or system manager, or may be configured as a portable electronic device that interfaces with local or remote (e.g., via wireless transmission).
In the buried site test apparatus 600, the processing component 601 may include a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a programmable logic device, a dedicated processor system, a microcontroller, or a microprocessor. By way of example and not limitation, processing component 601 may also include an analog processor, a digital processor, a microprocessor, a multi-core processor, a processor array, a network processor, and the like.
The processing component 601 may execute instructions or code stored in a memory, where the memory may also store data. Instructions and data may also be sent and received over a network via the network interface 603, where the network interface 603 may employ any known transmission protocol.
The memory 605 may be integral to the processor, e.g., with RAM or flash memory disposed within an integrated circuit microprocessor or the like. Further, the memory 605 may comprise a stand-alone device, such as an external disk drive, storage array, or any other storage device that may be used by a database system. The memory and the processor may be operatively coupled or may communicate with each other, such as through an I/O port, a network connection, etc., so that the processor can read files stored in the memory.
FIG. 7 is a block diagram of a buried point testing device according to an embodiment of the present disclosure.
Referring to fig. 7, a buried site testing apparatus 700 may include a data acquisition module 701 and a data processing module 702. Each module in the buried site testing apparatus 700 may be implemented by one or more modules, and names of the corresponding modules may vary according to types of the modules. In various embodiments, some modules in the buried site testing device 700 may be omitted, or additional modules may also be included. Furthermore, modules/elements according to various embodiments of the present disclosure may be combined to form a single entity, and thus the functions of the respective modules/elements may be equivalently performed prior to the combination.
The data obtaining module 701 may obtain a file of buried points to be detected including the data of the buried points to be detected and actual buried point data corresponding to the buried points in the target application.
The data processing module 702 may create a buried point table in the database, configure the buried point data to be tested in the buried point file to the buried point table to update the buried point table and determine the valid buried points in the updated buried point table by comparing the actual buried point data with the buried point data to be tested in the updated buried point table.
In one possible implementation manner, each piece of buried point data to be tested in the buried point file to be tested may include at least one of an operating system type, occurrence time, identification information, function description, identification information, application version, and data generation time.
In one possible implementation, the data processing module 702 may look up whether there is data of buried points to be measured with the same identification information from the updated buried point table based on the identification information in the actual buried point data, and determine an effective buried point in the buried point table based on the lookup result.
In one possible implementation manner, in the case that the buried point data to be tested having the same identification information as the actual buried point data exists in the buried point table, the data processing module 702 may set the test state of the piece of buried point data to be tested to be valid. In the case where there is no data of buried point to be tested having the same identification information as the actual data of buried point in the buried point table, the data processing module 702 may set the test state of the piece of data of buried point to be tested to be invalid.
In one possible implementation, the data processing module 702 may screen out valid buried point data to be tested and invalid buried point data to be tested corresponding to the target application from the buried point table based on the test state, application version and operating system type of the buried point data to be tested, so as to generate a buried point test result.
In one possible implementation, the buried point testing apparatus 700 may include a display module (not shown) for displaying the generated buried point testing result to a user.
The video transcoding device of this embodiment uses the modules to implement video transcoding according to the same principle and technical effect as those of the related method embodiments, and reference may be made to the description of the related method embodiments in detail, which is not repeated herein.
According to an embodiment of the present disclosure, an electronic device may be provided. Fig. 8 is a block diagram of an electronic device 800 including at least one memory 802 and at least one processor 801, the at least one memory 802 having stored therein a set of computer-executable instructions that, when executed by the at least one processor 801, perform a method of buried point testing according to an embodiment of the disclosure, according to an embodiment of the disclosure.
The memory 802 may be integrated with the processor 801, for example, with RAM or flash memory disposed within an integrated circuit microprocessor or the like. Further, the memory 802 may comprise a stand-alone device, such as an external disk drive, storage array, or other storage device that any database system may use. The memory and the processor may be operatively coupled or may communicate with each other, such as through an I/O port, a network connection, etc., so that the processor can read files stored in the memory.
Further, the electronic device 800 may also include a video display (such as a liquid crystal display) and a user interaction interface (such as a keyboard, mouse, touch input device, etc.). All components of the electronic device 800 may be connected to each other via a bus and/or a network.
According to an embodiment of the present disclosure, there may also be provided a computer readable storage medium storing instructions, wherein the instructions, when executed by at least one processor, cause the at least one processor to perform a buried point testing method according to the present disclosure. Examples of the computer-readable storage medium herein include: read-only memory (ROM), random-access programmable read-only memory (PROM), electrically erasable programmable read-only memory (EEPROM), random-access memory (RAM), dynamic random-access memory (DRAM), static random-access memory (SRAM), flash memory, non-volatile memory, CD-ROM, CD-R, CD + R, CD-RW, CD + RW, DVD-ROM, DVD-R, DVD + R, DVD-RW, DVD + RW, DVD-RAM, BD-ROM, BD-R, BD-R LTH, BD-RE, Blu-ray or optical disk memory, Hard Disk Drive (HDD), solid-state disk (SSD), card-type memory (such as a multimedia card, a Secure Digital (SD) card or an extreme digital (XD) card), magnetic tape, a floppy disk, a magneto-optical data storage device, an optical data storage device, a magnetic tape, a magneto-optical, Hard disk, solid state disk, and any other device configured to store and provide a computer program and any associated data, data files, and data structures to a processor or computer in a non-transitory manner such that the processor or computer can execute the computer program. The computer program in the computer-readable storage medium described above can be run in an environment deployed in a computer apparatus, such as a client, a host, a proxy device, a server, and so on, and further, in one example, the computer program and any associated data, data files, and data structures are distributed across a networked computer system such that the computer program and any associated data, data files, and data structures are stored, accessed, and executed in a distributed fashion by one or more processors or computers.
According to an embodiment of the present disclosure, there may also be provided a computer program product, in which instructions may be executed by a processor of a computer device to perform the above-mentioned buried point testing method.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims (10)

1. A buried point testing method is characterized by comprising the following steps:
establishing a buried point table in a database of a buried point test platform;
acquiring a buried point file to be detected comprising data of the buried point to be detected;
the method comprises the steps that data of buried points to be detected in a buried point file to be detected are configured into a buried point table to update the buried point table;
acquiring actual buried point data corresponding to a buried point in a target application;
and comparing the actual buried point data with the data of the buried point to be detected in the updated buried point table to determine the effective buried point in the updated buried point table.
2. The method of claim 1, wherein each piece of buried point data to be tested in the buried point file to be tested comprises at least one of an operating system type, an occurrence time, identification information, a function description, identification information, an application version, and a data generation time.
3. The buried point testing method of claim 1, wherein the actual buried point data is uploaded to the buried point testing platform via an uploading interface of the target application,
wherein the uploading interface of the target application is modified to be the interface of the buried point test platform.
4. The buried point testing method of claim 1, wherein the step of determining valid buried points in the updated buried point table by comparing actual buried point data with buried point data to be tested in the updated buried point table comprises:
searching whether the buried point data to be detected with the identification information exists in the updated buried point table based on the identification information in the actual buried point data;
determining a valid buried point in the buried point table based on the lookup result.
5. The method of claim 4, wherein the step of determining valid burial points in the buried point table based on the search result comprises:
setting the test state of the buried point data to be tested to be effective under the condition that the buried point data to be tested with the same identification information as the actual buried point data exists in the buried point table;
and under the condition that the data of the buried point to be tested with the same identification information as the actual buried point data does not exist in the buried point table, setting the test state of the data of the buried point to be tested as failure.
6. The buried site testing method of claim 5, further comprising:
screening effective buried point data to be tested and invalid buried point data to be tested corresponding to the target application from the buried point table based on the test state of the buried point data to be tested so as to generate a buried point test result;
and displaying the buried point test result to a user.
7. The utility model provides a bury some test platform which characterized in that, bury some test platform includes:
the interface is used for receiving actual buried point data corresponding to a buried point in a target application and a to-be-detected buried point file comprising to-be-detected buried point data;
the database is used for creating a buried point table and configuring the buried point data to be detected in the buried point file to be detected into the buried point table to update the buried point table;
and the processor is used for comparing the actual buried point data with the buried point data to be detected in the updated buried point table to determine the effective buried point in the updated buried point table.
8. The utility model provides a bury some testing arrangement which characterized in that bury some testing arrangement includes:
the data acquisition module is used for acquiring a to-be-detected buried point file comprising to-be-detected buried point data and actual buried point data corresponding to the buried point in the target application;
and the data processing module is used for creating a buried point table in the database, configuring the data of the buried point to be detected in the file of the buried point to be detected into the buried point table to update the buried point table and determining the effective buried point in the updated buried point table by comparing the actual buried point data with the data of the buried point to be detected in the updated buried point table.
9. An electronic device, characterized in that the electronic device comprises:
at least one processor;
at least one memory storing computer executable instructions,
wherein the computer executable instructions, when executed by the at least one processor, cause the at least one processor to perform the buried point testing method of any one of claims 1 to 6.
10. A computer readable storage medium storing instructions which, when executed by at least one processor, cause the at least one processor to perform a buried point testing method as claimed in any one of claims 1 to 6.
CN202011079986.8A 2020-10-10 2020-10-10 Buried point testing method and buried point testing platform Pending CN112148618A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011079986.8A CN112148618A (en) 2020-10-10 2020-10-10 Buried point testing method and buried point testing platform

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011079986.8A CN112148618A (en) 2020-10-10 2020-10-10 Buried point testing method and buried point testing platform

Publications (1)

Publication Number Publication Date
CN112148618A true CN112148618A (en) 2020-12-29

Family

ID=73952956

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011079986.8A Pending CN112148618A (en) 2020-10-10 2020-10-10 Buried point testing method and buried point testing platform

Country Status (1)

Country Link
CN (1) CN112148618A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112988532A (en) * 2021-01-27 2021-06-18 腾讯科技(深圳)有限公司 Reporting method and device of embedded point event, server and storage medium

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112988532A (en) * 2021-01-27 2021-06-18 腾讯科技(深圳)有限公司 Reporting method and device of embedded point event, server and storage medium

Similar Documents

Publication Publication Date Title
CN107908541B (en) Interface testing method and device, computer equipment and storage medium
AU2017258963B2 (en) Simultaneous multi-platform testing
US10990512B2 (en) User interface test coverage
TWI533123B (en) Method and system for automated test and result comparison
US9411782B2 (en) Real time web development testing and reporting system
EP3301580A1 (en) System for automatically generating test data for testing applications
US9846636B1 (en) Client-side event logging for heterogeneous client environments
CN104156224B (en) A kind of software building continuous integrating method and system
CN102272757A (en) Method for server-side logging of client browser state through markup language
CN105868096B (en) For showing the method, device and equipment of web page test result in a browser
CN107480053B (en) Software test data generation method and device
US9317398B1 (en) Vendor and version independent browser driver
Hallé et al. Testing web applications through layout constraints
US11436133B2 (en) Comparable user interface object identifications
CN112148618A (en) Buried point testing method and buried point testing platform
Holl et al. Mobile application quality assurance
RU2611961C2 (en) Method and system of regression testing of web page functionality, machine-readable data storage media
CN111897723A (en) Method and device for testing application
US9430361B1 (en) Transition testing model for heterogeneous client environments
Ricca et al. Three open problems in the context of e2e web testing and a vision: Neonate
WO2020096665A2 (en) System error detection
CN113535567A (en) Software testing method, device, equipment and medium
EP3333712A2 (en) Simultaneous multi-platform testing
Li et al. Modeling web application for cross-browser compatibility testing
US10097565B1 (en) Managing browser security in a testing context

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination