CN111444085A - Test method, test device and related equipment - Google Patents
Test method, test device and related equipment Download PDFInfo
- Publication number
- CN111444085A CN111444085A CN202010127200.9A CN202010127200A CN111444085A CN 111444085 A CN111444085 A CN 111444085A CN 202010127200 A CN202010127200 A CN 202010127200A CN 111444085 A CN111444085 A CN 111444085A
- Authority
- CN
- China
- Prior art keywords
- buried point
- point
- matching
- test
- preset
- 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
- 238000012360 testing method Methods 0.000 title claims abstract description 274
- 238000010998 test method Methods 0.000 title claims abstract description 8
- 238000000034 method Methods 0.000 claims abstract description 30
- 238000004590 computer program Methods 0.000 claims description 12
- 230000006870 function Effects 0.000 description 24
- 238000010586 diagram Methods 0.000 description 18
- 239000008186 active pharmaceutical agent Substances 0.000 description 9
- 238000007689 inspection Methods 0.000 description 7
- 238000012545 processing Methods 0.000 description 7
- 230000005540 biological transmission Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 4
- 230000000903 blocking effect Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 239000002699 waste material Substances 0.000 description 3
- 239000000835 fiber Substances 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000001902 propagating effect Effects 0.000 description 2
- 238000012827 research and development Methods 0.000 description 2
- RYGMFSIKBFXOCR-UHFFFAOYSA-N Copper Chemical compound [Cu] RYGMFSIKBFXOCR-UHFFFAOYSA-N 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 229910052802 copper Inorganic materials 0.000 description 1
- 239000010949 copper Substances 0.000 description 1
- 238000013480 data collection Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000007943 implant Substances 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 239000003826 tablet Substances 0.000 description 1
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
-
- 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/3692—Test management for test results analysis
Abstract
The embodiment of the disclosure discloses a test method, a test device and related equipment, wherein the method comprises the following steps: the method comprises the steps that a test platform obtains a buried point file and a preset test case; the buried point file comprises buried point data corresponding to the buried points, and the buried points are arranged in the application to be tested; presetting a test case for testing buried point data; and the test platform matches the buried point data with a preset test case to obtain a matching result. Thus, the application program to be tested can be tested more effectively.
Description
Technical Field
The present disclosure relates to the field of computers, and in particular, to a test method, device and related apparatus.
Background
With the gradual development of computer technology, more and more APP products are oriented to users. Experience is better when making the user use the APP product, and the performance of APP product is better, and the developer of APP product can test the APP. In order to test whether each function of the APP product can normally operate, research and development personnel generally select a function to be tested of the APP to perform point burying. However, in the prior art, the buried point test needs to upload the buried point data to the test platform one by one, which is time-consuming.
Disclosure of Invention
The disclosed embodiments provide a testing technique.
In a first aspect, a testing method is disclosed, the method comprising: the method comprises the steps that a test platform obtains a buried point file and a preset test case; the buried point file comprises buried point data acquired at a buried point of an application to be tested; the preset test case is used for testing the data of the buried point; and the test platform matches the buried point data with the preset test case to obtain a matching result.
In one possible implementation, the buried point data is stored in a cache of the electronic device in which the application to be tested is installed; the buried point file is generated from all buried point data in the electronic device.
In a possible implementation manner, after the embedded point file is uploaded to the test platform by the electronic device, the embedded point file in the electronic device is deleted.
In a possible implementation manner, the buried point file uploaded by the client is regenerated by storing a buried point data line in the electronic device where the client is located into a cache. When the electronic equipment runs the APP, the log information of the APP can be automatically stored in the cache. And generating a buried point file from the buried point data in the cache and storing the buried point file into a memory of the electronic equipment. And uploading the buried point file to a test platform. Therefore, the uploading of only one data through the API can be avoided, and the time waste can be avoided. And the uploaded buried point data is not comprehensive.
In a possible implementation manner, a blocking API call switch is arranged in the electronic device equipped with the client, and after the switch is turned on, the embedded data generated by the APP to be tested is stored in a cache of the electronic device. And after the switch is closed, the data of the buried point generated by the APP to be tested is uploaded to the test platform through the API.
In a possible implementation manner, after the buried point file is generated, the electronic device may delete the buried point data in the cache after receiving the user operation. In this way, the cache may be released.
In one possible implementation manner, the buried point data includes a plurality of buried point check points and actual test results corresponding to the plurality of buried point check points;
the preset test case comprises a plurality of preset check points and expected test results corresponding to the preset check points.
In a possible implementation manner, the matching, by the test platform, the buried point data and the preset test case to obtain a matching result includes:
and inquiring a preset check point corresponding to each embedded point check point in a plurality of preset check points, and matching an expected test result of the preset check point corresponding to each embedded point check point with an actual test result corresponding to each embedded point check point to obtain a matching result.
In one possible implementation manner, querying a preset check point corresponding to each embedded point check point in a plurality of preset check points, and matching an expected test result of the preset check point corresponding to each embedded point check point with an actual test result corresponding to each embedded point check point to obtain a matching result includes: and matching the first actual test result with the first expected test result by using a regular matching algorithm to obtain a matching result.
In one possible implementation, matching the first actual test result with the first expected test result by using a regular matching algorithm to obtain a matching result includes: and matching the fields in the first actual test result with the fields in the first expected test result one by one to obtain a matching result. Thus, the matching result is more accurate.
In a possible implementation manner, the querying, in a plurality of preset check points, a preset check point corresponding to each buried point check point, and matching an expected test result of the preset check point corresponding to each buried point check point with an actual test result corresponding to each buried point check point to obtain a matching result includes: and matching the first actual test result with the first expected test result by using a fuzzy matching algorithm to obtain a matching result.
In one possible implementation, matching the first actual test result with the first expected test result by using a fuzzy matching algorithm to obtain a matching result includes: and matching the key fields in the first actual test result with the fields in the first expected test result to obtain a matching result. In this way, matching time is saved.
In a second aspect, a test apparatus is disclosed, comprising:
the acquisition unit is used for acquiring the embedded point file and a preset test case; the buried point file comprises buried point data acquired at a buried point of an application to be tested; the preset test case is used for testing the data of the buried point;
and the matching unit is used for matching the buried point data with the preset test case and obtaining a matching result.
In one possible implementation, the buried point data is stored in a cache of the electronic device in which the application to be tested is installed; the buried point file is generated from all buried point data in the electronic device.
In one possible implementation, the buried point file is uploaded to the test platform by the electronic device.
In a possible implementation manner, the buried point file uploaded by the client is regenerated by storing a buried point data line in the electronic device where the client is located into a cache. When the electronic equipment runs the APP, the log information of the APP can be automatically stored in the cache. And generating a buried point file from the buried point data in the cache and storing the buried point file into a memory of the electronic equipment. And uploading the buried point file to a test platform. Therefore, the uploading of only one data through the API can be avoided, and the time waste can be avoided. And the uploaded buried point data is not comprehensive.
In a possible implementation manner, a blocking API call switch is arranged in the electronic device equipped with the client, and after the switch is turned on, the embedded data generated by the APP to be tested is stored in a cache of the electronic device. And after the switch is closed, the data of the buried point generated by the APP to be tested is uploaded to the test platform through the API.
In a possible implementation manner, after the buried point file is generated, the electronic device may delete the buried point data in the cache after receiving the user operation. In this way, the cache may be released.
In one possible implementation manner, the buried point data includes a plurality of buried point check points and actual test results corresponding to the plurality of buried point check points;
the preset test case comprises a plurality of preset buried point check points and expected test results corresponding to the preset buried point check points.
In a possible implementation manner, the matching unit is configured to:
and inquiring a preset check point corresponding to each embedded point check point in a plurality of preset check points, and matching an expected test result of the preset check point corresponding to each embedded point check point with an actual test result corresponding to each embedded point check point to obtain a matching result.
In a possible implementation manner, the matching unit is configured to:
and matching the first actual test result with the first expected test result by using a regular matching algorithm to obtain a test result.
In a possible implementation manner, the matching unit is configured to:
and matching the fields in the first actual test result with the fields in the first expected test result one by one to obtain a test result.
In a possible implementation manner, the matching unit is configured to:
and matching the first actual test result with the first expected test result by using a fuzzy matching algorithm to obtain a test result.
In a possible implementation manner, the matching unit is configured to:
and matching the key fields in the first actual test result with the fields in the first expected test result to obtain a test result.
In a third aspect, a testing device is disclosed, comprising a processor and a memory, wherein the memory is configured to store computer program code, and the processor is configured to invoke the computer program code to perform a method as in the first aspect or any possible implementation manner of the first aspect.
In the embodiment of the disclosure, a buried point file and a preset test case can be obtained; the buried point file comprises buried point data acquired at a buried point of an application to be tested; the preset test case is used for testing the data of the buried point; and the test platform matches the buried point data with the preset test case to obtain a matching result. Therefore, the test platform can obtain the test result of the application program to be tested by matching the buried point data with the preset test case. Moreover, the test platform is matched with the embedded point data in the whole embedded point file, so that the application program to be tested can be effectively tested.
Drawings
In order to more clearly illustrate the embodiments of the present disclosure 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.
Wherein:
FIG. 1 is a schematic diagram of an architecture of a test system provided by an embodiment of the present disclosure;
FIG. 2 is a schematic flow chart of a testing method provided by an embodiment of the present disclosure;
FIG. 3 is a schematic diagram of an interface for adding a preset test case according to an embodiment of the present disclosure;
FIG. 4 is a schematic diagram of a test results interface provided by embodiments of the present disclosure;
FIG. 5 is a schematic structural diagram of a testing apparatus provided in an embodiment of the present disclosure;
fig. 6 is a schematic structural diagram of a test apparatus provided in an embodiment of the present disclosure.
Detailed Description
Technical solutions in the embodiments of the present disclosure will be clearly described below with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are only some embodiments of the present disclosure, but not all embodiments.
It is also to be understood that the terminology used in the description of the disclosure herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure.
It should be further understood that the term "and/or" as used in this disclosure and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
In a specific implementation, the technical solution described in the embodiments of the present disclosure may be implemented by a terminal device or a server or a system with a test function, such as a mobile phone, a desktop computer, a laptop computer, and a wearable device, which is not limited herein. For ease of understanding, the subject of execution of the test method is hereinafter referred to as the test apparatus.
The embodiment of the disclosure provides a test method, which includes: the method comprises the steps that a test platform obtains a buried point file and a preset test case; the buried point file comprises buried point data acquired at a buried point of an application to be tested; presetting a test case for testing buried point data; and the test platform matches the buried point data with a preset test case to obtain a matching result.
Some concepts to which the disclosure relates are explained below.
(1) Buried point
The buried point is a term of data collection, and refers to a tester implanting code at each function in the APP to obtain data about some specific user behavior of the function. For example, the APP login function implants a code to obtain whether the account entered by the user can be successfully logged in. Or, for example, count the number of clicks a user clicks on the "buy" button in a page. The buried point code for counting the number of clicks of the "buy" button in one page can be as follows:
HashMap<String,String>map＝new HashMap<String,String>()；
map.put("type","book")；
map.put("quantity","3")；
MobclickAgent.onEvent(mContext,"purchase",map)；
the embedded point codes of different APP functions may be different, and the specific embedded point code is not limited herein.
(2) Buried point data
The data obtained after the code is embedded at each function in the APP is called buried point data. The buried point data may include a buried point inspection point and actual test results corresponding to the buried point inspection point. For example, the buried point data acquired at the APP login function may be a login account, a login result corresponding to the login account, and the like. Then, at this time, the buried point check point may be a login account, and the actual test result may be a login result corresponding to the login account, that is, a login success or a login failure.
The disclosed embodiments also provide a corresponding testing device, a computer readable storage medium and a computer program product. Each of which is described in detail below.
First, a test system to which the embodiments of the present disclosure are applicable is described below. Referring to fig. 1, fig. 1 is a schematic structural diagram of an example application system of the technical solution provided in the embodiment of the present disclosure. As shown in fig. 1, the test system may include one or more servers and a plurality of terminal devices, wherein:
the server and the terminal device can communicate through the internet. Specifically, the terminal device installed with the application to be tested sends the embedded point file to the test server through a network or an interface. Here, the user is a tester, and a buried point is set in the application to be tested. The test server obtains the embedded point file uploaded by the terminal equipment and the preset test case uploaded or input by the tester. And the test server matches the obtained embedded point file with the pre-test case to obtain a matching result. Further, the test server may send the matching result to a mailbox of a corresponding tester, so that the tester can view the test result.
The server can include, but is not limited to, a background server, a component server, a test system server, and the like, and the server receives the embedded point file sent by the terminal device. The terminal device may be installed and run with an associated Client (Client) (e.g., a test Client, etc.). A Client (Client) refers to a program that corresponds to a server and provides a local service to a user. Here, the local service may include, but is not limited to: generating a buried point file from the buried point data generated by the application to be tested, providing an interface for uploading the buried point file, and the like.
Specifically, the client may include: locally running applications, functions running on a Web browser (also known as Web apps), and the like. For the client, a corresponding server program needs to be operated on the server to set a buried point in the application to be tested, the buried point data generated by the application to be tested after the buried point is set is generated into a buried point file, and an interface for uploading the buried point file is provided.
The terminal device in the embodiments of the present disclosure may include, but is not limited to, any electronic product based on an intelligent operating system, which may perform human-computer interaction with a user through an input device such as a keyboard, a virtual keyboard, a touch pad, a touch screen, and a voice control device, such as a smart phone, a tablet computer, a personal computer, and the like. The smart operating system includes, but is not limited to, any operating system that enriches device functionality by providing various mobile applications to the mobile device, such as Android (Android), iOSTMWindows Phone, etc.
It should be noted that the architecture of the test system applied in the embodiment of the present disclosure is not limited to the example shown in fig. 1.
The following describes a test method provided by an embodiment of the present disclosure with reference to fig. 2.
S101, a testing platform obtains a buried point file and a preset testing case; the buried point file comprises buried point data acquired at a buried point of an application to be tested; the preset test case is used for testing the buried point data.
The testing platform firstly obtains embedded point data and a preset testing case of an application program to be tested, wherein the embedded point data can be log data generated by a certain function of APP after the embedded point is operated. For example, to test the login function of an APP, a site is buried at the login function of the APP. After the data is buried, the electronic device stores log information (e.g., information about login time, login account, whether login is successful, etc.) of the user logging in the APP for multiple times in a cache to form data buried in the data. The preset test case may be manually input into the test platform by a developer, or may be originally reserved in the test platform. The preset test case is used for testing the application program to be tested after the point is buried. For example, if a login function of an application to be tested is tested, a point needs to be buried in the login function to obtain login data of a user, where the buried point data may be an actual login time, a login account, and whether the login is successful. The preset test case may be N preset login accounts, and the login of the N login accounts is successful or failed.
In one possible implementation, the buried point data is stored in a cache of the electronic device in which the application to be tested is installed; the buried point file is generated from all buried point data in the electronic device.
In one possible implementation, the buried point file is uploaded to the test platform by the electronic device.
In a possible implementation manner, the buried point file uploaded by the client is regenerated by storing a buried point data line in the electronic device where the client is located into a cache. When the electronic equipment runs the APP, the log information of the APP can be automatically stored in the cache. And generating a buried point file from the buried point data in the cache and storing the buried point file into a memory of the electronic equipment. And uploading the buried point file to a test platform. Therefore, the uploading of only one data through the API can be avoided, and the time waste can be avoided. And the uploaded buried point data is not comprehensive.
In a possible implementation manner, a blocking API call switch is arranged in the electronic device equipped with the client, and after the switch is turned on, the embedded data generated by the APP to be tested is stored in a cache of the electronic device. And after the switch is closed, the data of the buried point generated by the APP to be tested is uploaded to the test platform through the API.
In a possible implementation manner, after the buried point file is generated, the electronic device may delete the buried point data in the cache after receiving the user operation. In this way, the cache may be released.
In one possible implementation manner, the buried point data includes a plurality of buried point check points and actual test results corresponding to the plurality of buried point check points; the preset test case comprises a plurality of preset check points and expected test results corresponding to the preset check points. For example, if the buried point data is the login accounts inputted by a plurality of actual users and the login results of the login accounts. The buried point check point may be login accounts input by a plurality of users, and the actual test result is a login result corresponding to the login accounts input by the user. Correspondingly, the preset test case comprises a plurality of preset login accounts and login results corresponding to the preset login accounts. The preset check point may be a preset login account, and the expected test result may be a login result corresponding to a plurality of preset login accounts.
S102, the test platform matches the buried point data with the preset test case to obtain a matching result.
After the test platform obtains the buried point data and the preset test case, research and development personnel click a start button or input a start command, and the test platform starts to match the buried point data and the preset test case. For example, a login function of an application to be tested is still tested. The buried point data is the actual user login account number, and login success or failure. The preset test cases are N preset login accounts, and the login of the N login accounts is successful or failed. If the buried point check point in the buried point data is the login account number "0100", the actual test result is that the login is successful. When the test platform performs matching, it is compared whether an expected test result corresponding to the preset check point login account number "0100" in the preset test case is consistent with an actual test result, that is, whether the preset check point login account number "0100" is also successful in login. In one possible implementation, an interface for adding test cases in the test platform may be as shown in fig. 3. The test platform may provide a button (shown as a "new test case" button in fig. 3) for the developer to add a preset test case. The test platform may also display the ID, creator, etc. of the preset test case.
In a possible implementation manner, the matching, by the test platform, the buried point data and the preset test case to obtain a matching result includes: and inquiring a preset check point corresponding to each embedded point check point in a plurality of preset check points, and matching an expected test result of the preset check point corresponding to each embedded point check point with an actual test result corresponding to each embedded point check point to obtain a matching result.
Optionally, the test platform may query a preset check point corresponding to the buried point check point through a field of the buried point check point. It can be understood that, if the field in the predetermined check point is the same as the field in the buried point check point, the predetermined check point is the predetermined check point corresponding to the buried point check point.
Optionally, the test platform may query a preset check point corresponding to the buried point check point by using the ID of the buried point check point. It can be understood that, if the ID of the predetermined inspection point is the same as or corresponds to the ID of the buried point inspection point, the predetermined inspection point is the predetermined inspection point corresponding to the buried point inspection point. Here, the test platform may also query the preset check point corresponding to the buried point check point by the name, number, and the like of the buried point check point.
Inquiring a preset check point corresponding to each embedded point check point in a plurality of preset check points, matching an expected test result of the preset check point corresponding to each embedded point check point with an actual test result corresponding to each embedded point check point and obtaining a matching result, wherein the method comprises the following steps: and matching the first actual test result with the first expected test result by using a regular matching algorithm to obtain a matching result.
In one possible implementation, matching the first actual test result with the first expected test result by using a regular matching algorithm to obtain a test result includes: and matching the fields in the first actual test result with the fields in the first expected test result one by one to obtain a test result. For example, the buried point file has 3 fields, i.e., a field 1 "abcde", a field 2 "1 abcd", and a field 3 "2 disc". Then all three fields have fields in the test case to match. Thus, the matching result is more accurate.
In a possible implementation manner, the querying, in a plurality of preset check points, a preset check point corresponding to each buried point check point, and matching an expected test result of the preset check point corresponding to each buried point check point with an actual test result corresponding to each buried point check point to obtain a matching result includes: and matching the first actual test result with the first expected test result by using a fuzzy matching algorithm to obtain a matching result.
In one possible implementation, matching the first actual test result with the first expected test result by using a fuzzy matching algorithm and returning a test result includes: and matching the key fields in the first actual test result with the fields in the first expected test result to obtain a test result. For example, the buried point file has 3 fields, where the field 1 "abcde", the field 2 "1 abcd", and the field 3 "2 disc" assume that the field 2 is a key field, and only the field 2 is selected to match the field in the test case. In this way, matching time is saved.
In one possible implementation, the matching result may be "match", "NO match" or "YES", "NO", or other prompt words. Here, the content of the specific prompt text is not limited.
In one possible implementation, the matching result is shown in fig. 4. The default test case execution fails or succeeds. And executing some test cases which fail to be executed, executing time, embedding point description and the like.
In the embodiment of the disclosure, a buried point file and a preset test case can be obtained; the buried point file comprises buried point data acquired at a buried point of an application to be tested; the preset test case is used for testing the data of the buried point; and the test platform matches the buried point data with the preset test case to obtain a matching result. Therefore, the test platform can obtain the test result of the application program to be tested by matching the buried point data with the preset test case. Moreover, the test platform is matched with the embedded point data in the whole embedded point file, so that the application program to be tested can be effectively tested.
In order to better implement the above-mentioned scheme of the embodiments of the present disclosure, the present disclosure also provides a testing apparatus, which is described in detail below with reference to the accompanying drawings:
as shown in fig. 3, a schematic structural diagram of a testing apparatus provided in an embodiment of the present disclosure, the testing apparatus may include: an obtaining unit 101, and a matching unit 102, wherein,
the acquiring unit 101 is used for acquiring a buried point file and a preset test case; the buried point file comprises buried point data acquired at a buried point of an application to be tested; the preset test case is used for testing the data of the buried point;
and the matching unit 102 is configured to match the buried point data with the preset test case and obtain a matching result.
In a possible implementation manner, the matching unit 102 is configured to:
and inquiring a preset check point corresponding to each embedded point check point in a plurality of preset check points, and matching an expected test result of the preset check point corresponding to each embedded point check point with an actual test result corresponding to each embedded point check point to obtain a matching result.
In a possible implementation manner, the matching unit 102 is configured to:
and matching the first actual test result with the first expected test result by using a regular matching algorithm to obtain a matching result.
In a possible implementation manner, the matching unit 102 is configured to:
and matching the first actual test result with the first expected test result by using a fuzzy matching algorithm to obtain a matching result.
In a possible implementation manner, the matching unit 102 is configured to:
and matching the fields in the first actual test result with the fields in the first expected test result one by one to obtain a test result.
In a possible implementation manner, the matching unit 102 is configured to:
and matching the key fields in the first actual test result with the fields in the first expected test result to obtain a test result.
In the embodiment of the disclosure, a buried point file and a preset test case can be obtained; the buried point file comprises buried point data acquired at a buried point of an application to be tested; the preset test case is used for testing the data of the buried point; and the test platform matches the buried point data with the preset test case to obtain a matching result. Therefore, the test platform can obtain the test result of the application program to be tested by matching the buried point data with the preset test case. Moreover, the test platform is matched with the embedded point data in the whole embedded point file, so that the application program to be tested can be effectively tested.
It should be noted that the data sending-out device 10 in the embodiment of the present disclosure is the testing device in the embodiment of fig. 2, and functions of each unit in the testing device 10 may refer to a specific implementation manner of the embodiment of fig. 2 in each method embodiment, which is not described herein again.
In order to better implement the above scheme of the embodiments of the present disclosure, the present disclosure also provides a testing apparatus, which is described in detail below with reference to the accompanying drawings:
as shown in fig. 4, which is a schematic structural diagram of the test device provided by the embodiment of the present disclosure, the test device 110 may include a processor 1101, an input unit 1102, an output unit 1103, a memory 1104, a communication unit 1105 and a bus 1106, and the processor 1101, the input unit 1102, the output unit 1103, the memory 1104 and the communication unit 1105 may be connected to each other through the bus 1106. The memory 1104 may be a high-speed RAM memory or a non-volatile memory (e.g., at least one disk memory). The memory 1104 may optionally be at least one memory system located remotely from the processor 1101. The memory 1104 is used for storing application program codes, which may include an operating system, a network communication module, a user interface module, and a test program, and the communication unit 1105 is used for information interaction with external units; the processor 1101 is configured to call the program code, and perform the following steps:
the processor 1101 obtains a buried point file and a preset test case; the buried point file comprises buried point data acquired at a buried point of an application to be tested; the preset test case is used for testing the data of the buried point;
the processor 1101 matches the buried point data with the preset test case and obtains a matching result.
The processor 1101 queries a preset check point corresponding to each embedded point check point from a plurality of preset check points, matches an expected test result of the preset check point corresponding to each embedded point check point with an actual test result corresponding to each embedded point check point, and obtains a matching result.
The processor 1101 matches the first actual test result with the first expected test result by using a regular matching algorithm to obtain a matching result.
The processor 1101 matches the first actual test result with the first expected test result by using a fuzzy matching algorithm and obtains a matching result.
The processor 1101 matches the fields in the first actual test result with the fields in the first expected test result one by one to obtain a test result.
In the embodiment of the disclosure, a buried point file and a preset test case can be obtained; the embedded point file comprises embedded point data obtained after embedding points are set for the application to be tested; the preset test case is used for testing the data of the buried point; and the test platform matches the buried point data with the preset test case to obtain a matching result. Therefore, the test platform can obtain the test result of the application program to be tested by matching the buried point data with the preset test case. Moreover, the test platform is matched with the embedded point data in the whole embedded point file, so that the application program to be tested can be effectively tested.
It should be noted that the test device 110 in the embodiment of the present disclosure is the test device in the embodiment of fig. 2, and specific reference may be specifically made to the specific implementation manner of the embodiment of fig. 2 in each method embodiment described above, which is not described herein again.
The embodiment of the present invention further provides a computer-readable storage medium, where the computer-readable storage medium may store a program, and when the program is executed, the program includes some or all of the steps of any one of the method embodiments described above.
Embodiments of the present invention also provide a computer program, where the computer program includes instructions that, when executed by a computer, enable the computer to perform some or all of the steps of any of the text-to-document methods.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The storage medium may be a usb disk, a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.
The present disclosure may be systems, methods, and/or computer program products. The computer program product may include a computer-readable storage medium having computer-readable program instructions embodied thereon for causing a processor to implement various aspects of the present disclosure.
The computer readable storage medium may be a tangible device that can hold and store the instructions for use by the instruction execution device. The computer readable storage medium may be, for example, but not limited to, an electronic memory device, a magnetic memory device, an optical memory device, an electromagnetic memory device, a semiconductor memory device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a Static Random Access Memory (SRAM), a portable compact disc read-only memory (CD-ROM), a Digital Versatile Disc (DVD), a memory stick, a floppy disk, a mechanical coding device, such as punch cards or in-groove projection structures having instructions stored thereon, and any suitable combination of the foregoing. Computer-readable storage media as used herein is not to be construed as transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission medium (e.g., optical pulses through a fiber optic cable), or electrical signals transmitted through electrical wires.
The computer-readable program instructions described herein may be downloaded to the respective computing/processing apparatus from a computer-readable storage medium, or to an external computer or external storage device via a network, such as the internet, a local area network, a wide area network, and/or a wireless network. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. The network adapter card or network interface in each computing/processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium in the respective computing/processing device.
Computer program instructions for carrying out operations of the present disclosure may be assembler instructions, Instruction Set Architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source or object code written in any combination of one or more programming languages, including AN object oriented programming language such as Smalltalk, C + +, or the like, as well as conventional procedural programming languages, such as the "C" language or similar programming languages.
Various aspects of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.
These computer-readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer-readable program instructions may also be stored in a computer-readable storage medium that can direct a computer, programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer-readable medium storing the instructions comprises an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer, other programmable apparatus or other devices implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The disclosure of the present invention is not intended to be limited to the particular embodiments disclosed, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A method of testing, comprising:
the method comprises the steps that a test platform obtains a buried point file and a preset test case; the buried point file comprises buried point data acquired at a buried point of an application to be tested; the preset test case is used for testing the data of the buried point;
and matching the buried point data with the preset test case to obtain a matching result.
2. The method of claim 1, wherein the buried point data is stored in a cache of an electronic device in which the application to be tested is installed; the buried point file is generated from all buried point data in the electronic device.
3. The method of claim 2, wherein the embedded point file in the electronic device is deleted after the embedded point file is uploaded to the test platform by the electronic device.
4. The method of claim 1,
the buried point data comprises a plurality of buried point check points and actual test results corresponding to the plurality of buried point check points;
the preset test case comprises a plurality of preset check points and expected test results corresponding to the preset check points.
5. The method of claim 4, wherein the matching the buried point data with the preset test case and obtaining a matching result comprises:
and inquiring a preset check point corresponding to each embedded point check point in a plurality of preset check points, and matching an expected test result of the preset check point corresponding to each embedded point check point with an actual test result corresponding to each embedded point check point to obtain a matching result.
6. The method of claim 5, wherein querying a predetermined checkpoint corresponding to each of the plurality of predetermined checkpoints, matching expected test results of the predetermined checkpoint corresponding to each of the plurality of buried point checkpoints with actual test results corresponding to each of the plurality of buried point checkpoints and obtaining a matching result comprises:
and matching the first actual test result with the first expected test result by using a regular matching algorithm to obtain a matching result.
7. The method of claim 5, wherein querying a predetermined checkpoint corresponding to each of the plurality of predetermined checkpoints, matching expected test results of the predetermined checkpoint corresponding to each of the plurality of buried point checkpoints with actual test results corresponding to each of the plurality of buried point checkpoints and obtaining a matching result comprises:
and matching the first actual test result with the first expected test result by using a fuzzy matching algorithm to obtain a matching result.
8. A testing apparatus, characterized in that it comprises means for performing the method according to any one of claims 1-7.
9. A test device comprising a processor, an input device, an output device and a memory, the processor, the input device, the output device and the memory being interconnected, wherein the memory is configured to store application program code and the processor is configured to invoke the program code to perform the method of any of claims 1-7.
10. A computer-readable storage medium, characterized in that the computer storage medium stores a computer program comprising program instructions that, when executed by a processor, cause the processor to perform the method according to any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010127200.9A CN111444085A (en) | 2020-02-27 | 2020-02-27 | Test method, test device and related equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010127200.9A CN111444085A (en) | 2020-02-27 | 2020-02-27 | Test method, test device and related equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111444085A true CN111444085A (en) | 2020-07-24 |
Family
ID=71655754
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010127200.9A Pending CN111444085A (en) | 2020-02-27 | 2020-02-27 | Test method, test device and related equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111444085A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111813693A (en) * | 2020-07-31 | 2020-10-23 | 南方科技大学 | Software compatibility detection method, intelligent terminal and storage medium |
| CN112148618A (en) * | 2020-10-10 | 2020-12-29 | 北京达佳互联信息技术有限公司 | Buried point testing method and buried point testing platform |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160140032A1 (en) * | 2014-11-19 | 2016-05-19 | International Business Machines Corporation | Correlating test results variations with business requirements |
| CN107562598A (en) * | 2017-08-03 | 2018-01-09 | 合肥美的智能科技有限公司 | Processing method, device, computer installation, server and readable storage medium storing program for executing |
| CN108319552A (en) * | 2018-02-07 | 2018-07-24 | 优信数享（北京）信息技术有限公司 | One kind burying a test method, apparatus and system |
| CN109960651A (en) * | 2019-02-13 | 2019-07-02 | 北京达佳互联信息技术有限公司 | Bury a test method, system, device and computer readable storage medium |
| CN110362480A (en) * | 2019-06-19 | 2019-10-22 | 平安普惠企业管理有限公司 | Client buries a test method, device, equipment and storage medium |
-
2020
- 2020-02-27 CN CN202010127200.9A patent/CN111444085A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160140032A1 (en) * | 2014-11-19 | 2016-05-19 | International Business Machines Corporation | Correlating test results variations with business requirements |
| CN107562598A (en) * | 2017-08-03 | 2018-01-09 | 合肥美的智能科技有限公司 | Processing method, device, computer installation, server and readable storage medium storing program for executing |
| CN108319552A (en) * | 2018-02-07 | 2018-07-24 | 优信数享（北京）信息技术有限公司 | One kind burying a test method, apparatus and system |
| CN109960651A (en) * | 2019-02-13 | 2019-07-02 | 北京达佳互联信息技术有限公司 | Bury a test method, system, device and computer readable storage medium |
| 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 |
|---|---|---|---|---|
| CN111813693A (en) * | 2020-07-31 | 2020-10-23 | 南方科技大学 | Software compatibility detection method, intelligent terminal and storage medium |
| CN111813693B (en) * | 2020-07-31 | 2023-06-06 | 南方科技大学 | Software compatibility detection method, intelligent terminal and storage medium |
| CN112148618A (en) * | 2020-10-10 | 2020-12-29 | 北京达佳互联信息技术有限公司 | Buried point testing method and buried point testing platform |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107992308B (en) | Plug-in management method for android terminal application program | |
| CN109684188B (en) | Test method and device | |
| US20160179800A1 (en) | Revision management | |
| CN111708557B (en) | Method, device and storage medium for updating configuration file | |
| CN112685029A (en) | Visual template generation method, device, equipment and storage medium | |
| US20190042552A1 (en) | Identifying and mapping emojis | |
| CN111444085A (en) | Test method, test device and related equipment | |
| CN109783355A (en) | Page elements acquisition methods, system, computer equipment and readable storage medium storing program for executing | |
| CN112631924A (en) | Automatic testing method and device, computer equipment and storage medium | |
| CN113536174A (en) | Interface loading method, device and equipment | |
| CN104021039A (en) | Calling method for APP and browser | |
| CN111124291B (en) | Data storage processing method and device of distributed storage system and electronic equipment | |
| CN110457085B (en) | File processing method and device, terminal equipment and computer readable medium | |
| CN111435328B (en) | Application testing method and device, electronic equipment and readable storage medium | |
| US10311138B2 (en) | Preventing partial change set deployments in content management systems | |
| CN110554892A (en) | Information acquisition method and device | |
| CN114091909A (en) | Collaborative development method, system, device and electronic equipment | |
| CN111176718A (en) | Script online method and device, storage medium and electronic equipment | |
| CN105160247A (en) | Method for identifying hijacked browser | |
| CN111858158A (en) | Data processing method and device and electronic equipment | |
| CN111162960A (en) | Method and server for starting debugging panel | |
| CN111176982A (en) | Test interface generation method and device | |
| US9473440B1 (en) | Hyperlink validation | |
| CN113656044B (en) | Android installation package compression method and device, computer equipment and storage medium | |
| CN110781188B (en) | Form information processing method and device, electronic equipment and storage medium |
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 |