CN111382071A - User behavior data testing method and system - Google Patents
User behavior data testing method and system Download PDFInfo
- Publication number
- CN111382071A CN111382071A CN202010140712.9A CN202010140712A CN111382071A CN 111382071 A CN111382071 A CN 111382071A CN 202010140712 A CN202010140712 A CN 202010140712A CN 111382071 A CN111382071 A CN 111382071A
- Authority
- CN
- China
- Prior art keywords
- behavior data
- user
- customer behavior
- request
- fields
- 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
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The embodiment of the invention provides a method and a system for testing user behavior data, wherein the method comprises the following steps: when a product is tested, acquiring customer behavior data uploaded by a client; analyzing the structure of the customer behavior data to obtain all fields of the customer behavior data; judging whether all the fields conform to preset fields or not to obtain a judgment result; if all the fields conform to preset fields, matching the customer behavior data to corresponding preset test cases; according to the method provided by the invention, when testing the new function embedded point, a tester does not need to wait for the research and development personnel to test after the function is realized, so that the new function testing efficiency is improved, the accuracy of embedded point reporting is ensured, the testing manpower is reduced, and the comprehensive testing is ensured.
Description
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to a user behavior data testing method and system.
Background
The App (application program) generally clicks various behaviors of the user while providing good use experience for the user, and reports the behaviors to the server, so that the user behaviors are analyzed, and product functions are optimized and iterated better.
The current report form of the buried point data is generally a structured json (JavaScript object notation, JS, object notation)) body, and reports to the server through an interface, and the server receives and stores the data, and sends the data to a plurality of bins for sorting and analysis.
Because the reporting of the embedded point is a thing which is executed by a program in a background silently and cannot be seen visually, the currently adopted testing mode can only trigger a reporting scene manually, and the comparison of each field value through a packet capturing tool (charles) is not in accordance with expectations.
However, in order to ensure the accuracy of the report of the embedded point, a large amount of testing manpower needs to be consumed, and with continuous iteration of functions, more and more fields and scenes need to be concerned by testing personnel, so that missing testing is easy to occur.
Therefore, how to provide a user data testing scheme can reduce testing labor and ensure comprehensive testing while ensuring accuracy of reporting a buried point, and is a technical problem to be solved urgently by technical personnel in the field.
Disclosure of Invention
Therefore, the embodiment of the invention provides a user behavior data testing method and system, which can reduce testing manpower and ensure comprehensive testing while ensuring accuracy of reporting of a buried point.
In order to achieve the above object, the embodiments of the present invention provide the following technical solutions:
in a first aspect, an embodiment of the present invention provides a user behavior data testing method, including:
when a product is tested, acquiring customer behavior data uploaded by a client;
analyzing the structure of the customer behavior data to obtain all fields of the customer behavior data;
judging whether all the fields conform to preset fields or not to obtain a judgment result;
if all the fields conform to preset fields, matching the customer behavior data to corresponding preset test cases;
and verifying whether the customer behavior meets the expectation or not according to the preset test case to obtain a test result.
Preferably, the setting process of the preset test case is as follows:
after the requirement of the product is determined, generating a corresponding preset test case according to the requirement;
recording the preset test case into a test background;
and when the product is tested, the preset test case is synchronously used for testing the customer behavior data.
Preferably, the obtaining of the customer behavior data uploaded by the client includes:
receiving client behavior data sent by a preset position of a client;
writing the customer behavior data into a kafka queue according to behavior types;
and receiving the client behavior data in the kafka queue through a monitoring script.
Preferably, the verifying whether the customer behavior meets the expectation according to the preset test case includes:
judging whether the field key is completely matched with the key value;
or verifying whether the key value has a numerical value when the field key exists;
or to verify whether the value contains multiple values when the field key exists.
Preferably, the method further comprises the following steps:
receiving a modification request, a copy request, a deletion request or a reset request of a user;
responding to a modification request of a user, and modifying the test result of the customer behavior data;
responding to a replication request of a user, and replicating the test result of the customer behavior data;
responding to a deletion request of a user, and deleting the test result of the customer behavior data;
and responding to a reset request of a user, and resetting the test result of the customer behavior data.
In a second aspect, an embodiment of the present invention provides a user behavior data testing system, including:
the data acquisition module is used for simultaneously acquiring the customer behavior data uploaded by the client during product testing;
the field analysis module is used for analyzing the structure of the customer behavior data to obtain all fields of the customer behavior data;
the field judgment module is used for judging whether all the fields accord with preset fields or not to obtain a judgment result;
the test matching module is used for matching the customer behavior data to a corresponding preset test case if all the fields conform to preset fields;
and the matching verification module is used for verifying whether the customer behavior meets the expectation or not according to the preset test case to obtain a test result.
Preferably, the data acquisition module includes:
the data receiving unit is used for receiving the client behavior data sent by the preset position of the client;
the queue classification unit is used for writing the customer behavior data into a kafka queue according to behavior types;
and the monitoring receiving unit is used for receiving the client behavior data in the kafka queue through a monitoring script.
Preferably, the method further comprises the following steps:
the request receiving module is used for receiving a modification request, a copying request, a deleting request or a resetting request of a user;
the modification execution module is used for responding to a modification request of a user and modifying the test result of the customer behavior data;
the replication execution module is used for responding to a replication request of a user and replicating the test result of the client behavior data;
the deletion execution module is used for responding to a deletion request of a user and deleting the test result of the client behavior data;
and the resetting execution module is used for responding to a resetting request of a user and resetting the test result of the customer behavior data.
In a third aspect, an embodiment of the present invention provides a user behavior data testing device, including:
a memory for storing a computer program;
a processor configured to implement the steps of the user behavior data testing method according to any one of the first aspect above when executing the computer program.
In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when being executed by a processor, the computer program implements the steps of the user behavior data testing method according to any one of the first aspect.
The embodiment of the invention provides a user behavior data testing method, which comprises the following steps: when a product is tested, acquiring customer behavior data uploaded by a client; analyzing the structure of the customer behavior data to obtain all fields of the customer behavior data; judging whether all the fields conform to preset fields or not to obtain a judgment result; if all the fields conform to preset fields, matching the customer behavior data to corresponding preset test cases; according to the method provided by the invention, when testing a new function embedded point, a tester does not need to wait for the research and development personnel to test after the function is realized, when the requirement is confirmed, the requirement is converted into a test case according to the requirement and is input into an embedded point monitoring platform, after the research and development personnel carry out test, a program automatically helps to verify the embedded point data and output the test result while verifying the product function, so that the test efficiency of the new function is improved, the test labor is reduced while the accuracy of the embedded point reporting is ensured, and the comprehensive test is ensured.
The method and the system for testing the user behavior data provided by the embodiment of the invention have the same beneficial effects, and are not repeated herein.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below. It should be apparent that the drawings in the following description are merely exemplary, and that other embodiments can be derived from the drawings provided by those of ordinary skill in the art without inventive effort.
The structures, ratios, sizes, and the like shown in the present specification are only used for matching with the contents disclosed in the specification, so as to be understood and read by those skilled in the art, and are not used to limit the conditions that the present invention can be implemented, so that the present invention has no technical significance, and any structural modifications, changes in the ratio relationship, or adjustments of the sizes, without affecting the effects and the achievable by the present invention, should still fall within the range that the technical contents disclosed in the present invention can cover.
Fig. 1 is a flowchart of a user behavior data testing method according to an embodiment of the present invention;
fig. 2 is a flow chart illustrating setting of a test case of a user behavior data testing method according to an embodiment of the present invention;
fig. 3 is a data acquisition flowchart of a user behavior data testing method according to an embodiment of the present invention;
fig. 4 is a flowchart illustrating a test result operation of a method for testing user behavior data according to an embodiment of the present invention;
FIG. 5 is a flowchart illustrating a method for testing user behavior data according to an embodiment of the present invention;
fig. 6 is a schematic composition diagram of a user behavior data testing system according to an embodiment of the present invention;
fig. 7 is a schematic diagram illustrating a data acquisition module of a user behavior data testing system according to an embodiment of the present invention;
fig. 8 is an expanded composition diagram of a user behavior data testing system according to an embodiment of the present invention;
FIG. 9 is a schematic structural diagram of a user behavior data testing apparatus according to an embodiment of the present invention;
fig. 10 is a schematic structural diagram of a computer-readable storage medium according to an embodiment of the present invention.
Detailed Description
The present invention is described in terms of particular embodiments, other advantages and features of the invention will become apparent to those skilled in the art from the following disclosure, and it is to be understood that the described embodiments are merely exemplary of the invention and that it is not intended to limit the invention to the particular embodiments disclosed. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 1, fig. 2, fig. 3, fig. 4, and fig. 5, fig. 1 is a flowchart of a user behavior data testing method according to an embodiment of the present invention; fig. 2 is a flow chart illustrating setting of a test case of a user behavior data testing method according to an embodiment of the present invention; fig. 3 is a data acquisition flowchart of a user behavior data testing method according to an embodiment of the present invention; fig. 4 is a flowchart illustrating a test result operation of a method for testing user behavior data according to an embodiment of the present invention; fig. 5 is a practical flowchart of a user behavior data testing method according to an embodiment of the present invention.
In a specific implementation manner of the present invention, an embodiment of the present invention provides a user behavior data testing method, including:
step S11: when a product is tested, acquiring customer behavior data uploaded by a client;
in the embodiment of the invention, the client behavior data uploaded by the client side needs to be acquired first. When the product is developed, test cases corresponding to the dotting customer behavior data can be synchronously generated according to requirements. Therefore, the client behavior data on the client can be acquired while the product functions are tested, and the subsequent synchronous test can be performed.
Step S12: analyzing the structure of the customer behavior data to obtain all fields of the customer behavior data;
specifically, after the client behavior data is obtained, the client behavior data generally includes a mouse click behavior (click), a web page view behavior (view), and a page exposure behavior (pv), and may also include other behavior data, and at this time, the client behavior data may be analyzed to obtain all fields of the behavior data, that is, the KEY.
Step S13: judging whether all the fields conform to preset fields or not to obtain a judgment result;
after the fields of the customer behavior data are obtained, the fields can be judged according to the fields and preset fields, whether the fields conform to some preset fields or not is checked, and therefore the customer behavior data can be classified, and the judged classification result is obtained.
Step S14: if all the fields conform to preset fields, matching the customer behavior data to corresponding preset test cases;
at this time, matching of the corresponding preset test case can be performed according to the data type corresponding to the client behavior data obtained by judgment, for example, a corresponding first test case can be performed on the client behavior of clicking a mouse; the behavior of the client viewing the behavior (view) of the webpage corresponds to a second test case; the client behavior of the page exposure behavior (pv) corresponds to a third test case; the test cases are set with expected data structures and expected data values, namely key and value, which should be possessed by the client behavior data.
Step S15: and verifying whether the customer behavior meets the expectation or not according to the preset test case to obtain a test result.
Therefore, the client behaviors can be verified according to the preset test case to obtain a final result, and whether the reported client behavior data are normal or not can be known. If the customer behavior is verified to be in accordance with the expectation according to the preset test case, the customer behavior data is normal, and the product test is passed; and if the customer behavior is not in accordance with the preset test case verification, the customer behavior data is normal, and the product test is failed.
Further, the setting process of the preset test case is as follows:
step S21: after the requirement of the product is determined, generating a corresponding preset test case according to the requirement;
step S22: recording the preset test case into a test background;
step S23: and when the product is tested, the preset test case is synchronously used for testing the customer behavior data.
That is to say, when testing new function and burying a point, the tester need not to wait for the research and development personnel function to realize and then test, after the demand is confirmed, the demand is converted into the test case according to the demand and is input into a buried point monitoring platform, after the research and development is carried out and tested, when verifying the product function, the program automatically helps to verify the buried point data, the test result is output, and the test efficiency of the new function is improved.
Specifically, in practice, in order to obtain the customer behavior data uploaded by the client, the following steps may be performed:
step S31: receiving client behavior data sent by a preset position of a client;
step S32: writing the customer behavior data into a kafka queue according to behavior types;
step S33: and receiving the client behavior data in the kafka queue through a monitoring script.
That is to say, because the buried point verification program is continuously verified, when the tester performs function regression, the relevant buried points are automatically verified by the program, and the efficiency of buried point regression testing is improved.
Specifically, when verifying whether the customer behavior is expected according to the preset test case, whether the field key is completely matched with the key value can be judged; or verifying whether the key value has a numerical value when the field key exists; or to verify whether the value contains multiple values when the field key exists. Of course, other types of preset test cases are also possible, and the verification process can be set according to actual situations.
On the basis of the above embodiment, in this embodiment, a series of operations may be further performed on the test result, specifically, the following steps may be performed:
step S41: receiving a modification request, a copy request, a deletion request or a reset request of a user;
step S42: responding to a modification request of a user, and modifying the test result of the customer behavior data;
step S43: responding to a replication request of a user, and replicating the test result of the customer behavior data;
step S44: responding to a deletion request of a user, and deleting the test result of the customer behavior data;
step S45: and responding to a reset request of a user, and resetting the test result of the customer behavior data.
In practice, buttons such as modification, copy, deletion, reset and the like can be arranged after corresponding customer behavior data entries, so that the staff can operate the corresponding customer behavior data entries conveniently.
The embodiment of the invention provides a user behavior data testing method, which comprises the following steps: when a product is tested, acquiring customer behavior data uploaded by a client; analyzing the structure of the customer behavior data to obtain all fields of the customer behavior data; judging whether all the fields conform to preset fields or not to obtain a judgment result; if all the fields conform to preset fields, matching the customer behavior data to corresponding preset test cases; according to the method provided by the invention, when testing a new function embedded point, a tester does not need to wait for the research and development personnel to test after the function is realized, when the requirement is confirmed, the requirement is converted into a test case according to the requirement and is input into an embedded point monitoring platform, after the research and development of the new function embedded point is tested, a program automatically helps to verify the embedded point data and output the test result, because the embedded point verification program is continuously verified, when the tester performs function regression, the relevant embedded point can be automatically verified by the program, the embedded point regression test efficiency is improved, after the embedded point test is input by a sample, the program can verify each field and value, the artificial error risk is reduced, the test quality is improved, and the new function test efficiency is improved, the accuracy of reporting the buried points can be guaranteed, meanwhile, the testing manpower is reduced, and comprehensive testing is guaranteed.
Referring to fig. 6, 7 and 8, fig. 6 is a schematic diagram illustrating a user behavior data testing system according to an embodiment of the present invention; fig. 7 is a schematic diagram illustrating a data acquisition module of a user behavior data testing system according to an embodiment of the present invention; fig. 8 is an expanded composition schematic diagram of a user behavior data testing system according to an embodiment of the present invention.
In another specific embodiment of the present invention, an embodiment of the present invention provides a user behavior data testing system 600, including:
the data acquisition module 610 is used for acquiring customer behavior data uploaded by a client side when product testing is performed;
a field analyzing module 620, configured to analyze a structure of the customer behavior data to obtain all fields of the customer behavior data;
a field judging module 630, configured to judge whether all the fields conform to preset fields, so as to obtain a judgment result;
the test matching module 640 is configured to match the customer behavior data to a corresponding preset test case if all the fields conform to preset fields;
and the matching verification module 650 is configured to verify whether the behavior of the client meets expectations according to the preset test case, so as to obtain a test result.
Preferably, the data acquisition module 610 includes:
the data receiving unit 611 is configured to receive client behavior data sent from a preset location of the client;
a queue classification unit 612, configured to write the customer behavior data into a kafka queue according to a behavior type;
a listening receiving unit 613, configured to receive, through a listening script, the client behavior data in the kafka queue.
Preferably, the method further comprises the following steps:
a request receiving module 660, configured to receive a modification request, a copy request, a deletion request, or a reset request of a user;
a modification executing module 670, configured to modify the test result of the customer behavior data in response to a modification request from a user;
the replication execution module 680 is configured to respond to a replication request of a user, and replicate the test result of the client behavior data;
a deletion executing module 690, configured to respond to a deletion request from a user, and delete the test result of the customer behavior data;
a reset execution module 6100, configured to reset the test result of the customer behavior data in response to a reset request from a user.
Referring to fig. 9 and 10, fig. 9 is a schematic structural diagram of a user behavior data testing apparatus according to an embodiment of the present invention; fig. 10 is a schematic structural diagram of a computer-readable storage medium according to an embodiment of the present invention.
An embodiment of the present invention provides a user behavior data testing apparatus 900, including:
a memory 910 for storing a computer program;
a processor 920, configured to implement the steps of any one of the user behavior data testing methods according to the first aspect when executing the computer program. Stored in a space in the memory 910 for storage of program code, which when executed by the processor 920 performs any of the methods in embodiments of the invention.
An embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements the steps of any of the user behavior data testing methods according to any of the above embodiments.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described apparatuses, devices and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus, device and method may be implemented in other manners. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, a division of a unit is merely a logical division, and an actual implementation may have another division, for example, a plurality of units or components may be combined or integrated into another apparatus, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
Units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a function calling device, or a network device) to execute all or part of the steps of the method of the embodiments of the present application.
Although the invention has been described in detail above with reference to a general description and specific examples, it will be apparent to one skilled in the art that modifications or improvements may be made thereto based on the invention. Accordingly, such modifications and improvements are intended to be within the scope of the invention as claimed.
Claims (10)
1. A user behavior data testing method is characterized by comprising the following steps:
when a product is tested, acquiring customer behavior data uploaded by a client;
analyzing the structure of the customer behavior data to obtain all fields of the customer behavior data;
judging whether all the fields conform to preset fields or not to obtain a judgment result;
if all the fields conform to preset fields, matching the customer behavior data to corresponding preset test cases;
and verifying whether the customer behavior meets the expectation or not according to the preset test case to obtain a test result.
2. The user behavior data testing method of claim 1,
the setting process of the preset test case is as follows:
after the requirement of the product is determined, generating a corresponding preset test case according to the requirement;
recording the preset test case into a test background;
and when the product is tested, the preset test case is synchronously used for testing the customer behavior data.
3. The user behavior data testing method of claim 1,
the acquiring of the customer behavior data uploaded by the client comprises the following steps:
receiving client behavior data sent by a preset position of a client;
writing the customer behavior data into a kafka queue according to behavior types;
and receiving the client behavior data in the kafka queue through a monitoring script.
4. The user behavior data testing method of claim 1,
the verifying whether the customer behavior meets the expectation according to the preset test case comprises the following steps:
judging whether the field key is completely matched with the key value;
or verifying whether the key value has a numerical value when the field key exists;
or to verify whether the value contains multiple values when the field key exists.
5. The user behavior data testing method according to any one of claims 1 to 4, further comprising:
receiving a modification request, a copy request, a deletion request or a reset request of a user;
responding to a modification request of a user, and modifying the test result of the customer behavior data;
responding to a replication request of a user, and replicating the test result of the customer behavior data;
responding to a deletion request of a user, and deleting the test result of the customer behavior data;
and responding to a reset request of a user, and resetting the test result of the customer behavior data.
6. A user behavior data testing system, comprising:
the data acquisition module is used for simultaneously acquiring the customer behavior data uploaded by the client during product testing;
the field analysis module is used for analyzing the structure of the customer behavior data to obtain all fields of the customer behavior data;
the field judgment module is used for judging whether all the fields accord with preset fields or not to obtain a judgment result;
the test matching module is used for matching the customer behavior data to a corresponding preset test case if all the fields conform to preset fields;
and the matching verification module is used for verifying whether the customer behavior meets the expectation or not according to the preset test case to obtain a test result.
7. The user behavior data testing system of claim 6,
the data acquisition module comprises:
the data receiving unit is used for receiving the client behavior data sent by the preset position of the client;
the queue classification unit is used for writing the customer behavior data into a kafka queue according to behavior types;
and the monitoring receiving unit is used for receiving the client behavior data in the kafka queue through a monitoring script.
8. The user behavior data testing system of claim 6, further comprising:
the request receiving module is used for receiving a modification request, a copying request, a deleting request or a resetting request of a user;
the modification execution module is used for responding to a modification request of a user and modifying the test result of the customer behavior data;
the replication execution module is used for responding to a replication request of a user and replicating the test result of the client behavior data;
the deletion execution module is used for responding to a deletion request of a user and deleting the test result of the client behavior data;
and the resetting execution module is used for responding to a resetting request of a user and resetting the test result of the customer behavior data.
9. A user behavior data testing device, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the user behavioural data testing method as claimed in any one of claims 1 to 5 when executing said computer program.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the user behavior data testing method according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010140712.9A CN111382071A (en) | 2020-03-03 | 2020-03-03 | User behavior data testing method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010140712.9A CN111382071A (en) | 2020-03-03 | 2020-03-03 | User behavior data testing method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111382071A true CN111382071A (en) | 2020-07-07 |
Family
ID=71219741
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010140712.9A Pending CN111382071A (en) | 2020-03-03 | 2020-03-03 | User behavior data testing method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111382071A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113626239A (en) * | 2021-07-27 | 2021-11-09 | 福建天泉教育科技有限公司 | Function verification method and terminal |
| CN117724986A (en) * | 2024-02-08 | 2024-03-19 | 云账户技术(天津)有限公司 | Method and device for automatically operating kafka in use case execution |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160342501A1 (en) * | 2015-05-18 | 2016-11-24 | Hcl Technologies Limited | Accelerating Automated Testing |
| CN109960651A (en) * | 2019-02-13 | 2019-07-02 | 北京达佳互联信息技术有限公司 | Bury a test method, system, device and computer readable storage medium |
| CN110221945A (en) * | 2019-06-12 | 2019-09-10 | 深圳市网心科技有限公司 | Automated testing method, device, terminal and storage medium based on secure authentication |
| CN110362480A (en) * | 2019-06-19 | 2019-10-22 | 平安普惠企业管理有限公司 | Client buries a test method, device, equipment and storage medium |
-
2020
- 2020-03-03 CN CN202010140712.9A patent/CN111382071A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160342501A1 (en) * | 2015-05-18 | 2016-11-24 | Hcl Technologies Limited | Accelerating Automated Testing |
| CN109960651A (en) * | 2019-02-13 | 2019-07-02 | 北京达佳互联信息技术有限公司 | Bury a test method, system, device and computer readable storage medium |
| CN110221945A (en) * | 2019-06-12 | 2019-09-10 | 深圳市网心科技有限公司 | Automated testing method, device, terminal and storage medium based on secure authentication |
| CN110362480A (en) * | 2019-06-19 | 2019-10-22 | 平安普惠企业管理有限公司 | Client buries a test method, device, equipment and storage medium |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113626239A (en) * | 2021-07-27 | 2021-11-09 | 福建天泉教育科技有限公司 | Function verification method and terminal |
| CN117724986A (en) * | 2024-02-08 | 2024-03-19 | 云账户技术(天津)有限公司 | Method and device for automatically operating kafka in use case execution |
| CN117724986B (en) * | 2024-02-08 | 2024-05-07 | 云账户技术(天津)有限公司 | Method and device for automatically operating kafka in use case execution |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2572294B1 (en) | System and method for sql performance assurance services | |
| CN111290956B (en) | Brain graph-based test method and device, electronic equipment and storage medium | |
| US20150095892A1 (en) | Systems and methods for evaluating a change pertaining to a service or machine | |
| CN108509344B (en) | Daily cutting batch test method, equipment and readable storage medium | |
| WO2018184361A1 (en) | Application test method, server, terminal, and storage media | |
| CN103246606A (en) | Method and system for testing performances of ESB (enterprises service bus) platform | |
| CN105204986A (en) | Automated product testing method, server and mobile equipment | |
| CN113434396A (en) | Interface test method, device, equipment, storage medium and program product | |
| CN111382071A (en) | User behavior data testing method and system | |
| CN114546738A (en) | Server general test method, system, terminal and storage medium | |
| Srikanth et al. | Regression testing in software as a service: An industrial case study | |
| US20130290938A1 (en) | Testing applications | |
| CN113360376A (en) | Buried point testing method and device | |
| EP3734460B1 (en) | Probabilistic software testing via dynamic graphs | |
| CN111737143B (en) | Method and system for troubleshooting AB test of webpage | |
| CN117493188A (en) | Interface testing method and device, electronic equipment and storage medium | |
| CN107678965A (en) | It is automatically integrating method of testing and system, service terminal, memory | |
| CN114564387A (en) | Scene type automatic testing method and system for OpenStack cloud platform | |
| CN110795330A (en) | Monkey pressure testing method and device | |
| CN114676066A (en) | Security testing method and device for target application, electronic equipment and storage medium | |
| CN112346994B (en) | Test information association method, device, computer equipment and storage medium | |
| US20160132424A1 (en) | Simulating sensors | |
| CN114020642A (en) | Big data task testing method and device, storage medium and electronic equipment | |
| CN115129575A (en) | Code coverage result generation method and device | |
| CN113220586A (en) | Automatic interface pressure test execution method, device and system |
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 |