A page jump test method and apparatus

Abstract

The present invention provides a page jump test method and device. The method comprises the following steps: refreshing an access interface of a server and capturing a client request sent by a client to be tested to the server via the access interface; sending the client request to the server and receiving a first page jump path sent by the server via the access interface; tampering with the first page jump path to obtain a second page jump path pre-set with a target page; sending the second page jump path to the client to be tested, causing the client to jump to a page to be verified based on the second page jump path; comparing the target page with the page to be verified to obtain a page jump test result, and returning to the step of refreshing the server access interface until a preset stop condition is met. This method eliminates the need for testers to perform page jump tests for each scenario, thereby improving test efficiency and accuracy.

Description

Technical Field

[0001] The present invention relates to the technical field of software testing, and in particular to a page jump testing method and device. Background Art

[0002] The schema protocol in Android is a page jump protocol that allows you to control app page jumps. To ensure the normal operation of the app, you need to verify that the app can jump to different types of pages.

[0003] The current method for testing app page jumps is for testers to click the app's page jump button to test whether the jumps to different types of pages in different scenarios are normal. However, when testing a large number of pages, testers need to spend a lot of time to conduct page jump tests, and manual testing is prone to omissions, resulting in low test efficiency and low test accuracy. Summary of the Invention

[0004] In view of this, an embodiment of the present invention provides a page jump testing method and device to solve the problems of low testing efficiency and low testing accuracy in the existing method of testing APP page jumps.

[0005] To achieve the above objectives, the embodiments of the present invention provide the following technical solutions:

[0006] A first aspect of an embodiment of the present invention discloses a page jump testing method, the method comprising:

[0007] Refreshing the access interface of the server and capturing the client request sent by the client to be tested to the server through the access interface;

[0008] Sending the client request to the server, and receiving a first page jump path sent by the server through the access interface;

[0009] Tampering with the first page jump path to obtain a second page jump path with a target page preset;

[0010] Sending the second page jump path to the client to be tested, so that the client to be tested jumps to the page to be verified based on the second page jump path;

[0011] The target page and the page to be verified are compared to obtain a page jump test result, and the process returns to the step of refreshing the access interface of the server until a preset stop condition is met.

[0012] Preferably, sending the second page jump path to the client to be tested, so that the client to be tested jumps to the page to be verified based on the second page jump path, includes:

[0013] Sending the second page jump path to the client to be tested, so that the client to be tested loads and displays a target button corresponding to the second page jump path;

[0014] The detection tool is called to trigger the target button, so that the client to be tested jumps to the page to be verified based on the second page jump path.

[0015] Preferably, sending the client request to the server and receiving the first page jump path sent by the server through the access interface includes:

[0016] Obtaining the first URL requested by the client, and sending the client request to the server;

[0017] Obtain the pending page jump protocol issued by the server, and obtain the second URL of the pending page jump protocol;

[0018] Determine whether the first URL and the second URL match;

[0019] If the first URL and the second URL match, it is determined that the page jump protocol to be processed is the first page jump path sent by the server through the access interface.

[0020] Preferably, after determining whether the first URL and the second URL match, the method further includes:

[0021] If the first URL and the second URL do not match, the page jump protocol to be processed is sent to the client to be tested, and the process returns to the step of obtaining the page jump protocol to be processed issued by the server.

[0022] Preferably, the client to be tested is an Android client; the first page jump path and the second page jump path are schema jump paths.

[0023] A second aspect of an embodiment of the present invention discloses a page jump testing device, the device comprising:

[0024] a processing unit, configured to refresh the access interface of the server and capture the client request sent by the client to be tested to the server through the access interface;

[0025] A first communication unit is configured to send the client request to the server and receive a first page jump path sent by the server through the access interface;

[0026] a tampering unit, configured to tamper with the first page jump path to obtain a second page jump path with a target page preset;

[0027] A second communication unit is configured to send the second page jump path to the client to be tested, so that the client to be tested jumps to the page to be verified based on the second page jump path;

[0028] The comparison unit is used to compare the target page with the page to be verified to obtain a page jump test result, and return to execute the processing unit until a preset stop condition is met.

[0029] Preferably, the second communication unit is specifically used to: send the second page jump path to the client to be tested, so that the client to be tested loads and displays the target button corresponding to the second page jump path; call the detection tool to trigger the target button, so that the client to be tested jumps to the page to be verified based on the second page jump path.

[0030] Preferably, the first communication unit includes:

[0031] A communication module, configured to obtain a first URL requested by the client and send the client request to the server;

[0032] An acquisition module, configured to receive the pending page jump protocol issued by the server and acquire a second URL of the pending page jump protocol;

[0033] The judgment module is used to judge whether the first url and the second url match; if the first url and the second url match, determine that the page jump protocol to be processed is the first page jump path sent by the server through the access interface.

[0034] Preferably, the judgment module is further configured to: if the first URL and the second URL do not match, send the page jump protocol to be processed to the client to be tested, and return to execute the acquisition module.

[0035] Preferably, the client to be tested is an Android client; the first page jump path and the second page jump path are schema jump paths.

[0036] Based on the above-mentioned embodiment of the present invention, a page jump test method and device are provided. The method is as follows: refreshing the access interface of the server, and capturing the client request sent by the client to be tested to the server through the access interface; sending the client request to the server, and receiving the first page jump path sent by the server through the access interface; tampering with the first page jump path to obtain a second page jump path with a target page pre-set; sending the second page jump path to the client to be tested, so that the client to be tested jumps to the page to be verified based on the second page jump path; comparing the target page and the page to be verified to obtain the page jump test result, and returning to the step of refreshing the access interface of the server until the preset stop condition is met. In this solution, the client request is captured and sent to the server, and the first page jump path sent by the server is received. The first page jump path is tampered with to obtain the second page jump path with the target page set. The second page jump path is sent to the client to be tested to make it jump to the page to be verified. The page jump test result is obtained by comparing the target page and the page to be verified. There is no need for the tester to perform page jump tests for each scenario, which improves test efficiency and test accuracy. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are merely embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0038] Figure 1 A flow chart of a page jump testing method provided by an embodiment of the present invention;

[0039] Figure 2 A flowchart of receiving a first page jump path provided by an embodiment of the present invention;

[0040] Figure 3 A structural block diagram of a page jump test device provided by an embodiment of the present invention;

[0041] Figure 4 This is another structural block diagram of a page jump testing device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0042] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.

[0043] In this application, the terms "comprises," "comprising," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not preclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.

[0044] As can be seen from the background technology, when testing APP page jumps, the tester usually clicks the page jump button of the APP to test whether the jumps of different types of pages in different scenarios are normal. When testing a large number of pages, the tester needs to spend a lot of time to perform page jump tests, and manual testing is prone to omissions, resulting in low test efficiency and low test accuracy.

[0045] Therefore, an embodiment of the present invention provides a page jump test method and device, which captures a client request and sends it to a server, and receives a first page jump path sent by the server. The first page jump path is tampered with to obtain a second page jump path with a target page. The second page jump path is sent to the client to be tested so that it jumps to the page to be verified. By comparing the target page and the page to be verified to obtain the page jump test result, it is no longer necessary for the tester to perform page jump tests for each scenario, thereby improving test efficiency and test accuracy.

[0046] It should be noted that the schema protocol is a page jump protocol (also called an intra-page jump protocol). By customizing the schema protocol, you can jump to various pages in the APP. The format example of the schema protocol is "xl: / / goods:8888 / goodsDetail?goodsId=10011002", where "xl" represents the schema protocol name, "goods" represents the passed parameters, and "8888" represents the path port number. The schema protocol can be used to jump to different types of pages. For example: the client jumps to the corresponding page according to the jump path sent by the server (implemented through the schema protocol); for example: a button is displayed on the H5 page, and the button is configured with a corresponding jump path. Clicking the button displayed on the H5 page can jump to the corresponding page.

[0047] The following describes a page jump test method in detail through various embodiments.

[0048] See also Figure 1 , shows a flow chart of a page jump test method provided by an embodiment of the present invention, the page jump test method comprising:

[0049] Step S101: Refresh the access interface of the server and capture the client request sent by the client to be tested to the server through the access interface.

[0050] It should be noted that the access interface is a uniform resource locator (URL) interface; the client accesses the server through the access interface, and the server sends the return content containing the page jump path to the client through the access interface. The return content can be the content of a specified field (for example, the content of the res field, which is json data); the client implements page jump through the page jump path sent by the server; in the process of page jump testing on the client, it is necessary to refresh the access interface to obtain different page jump paths, and use the different page jump paths obtained to test page jumps in different scenarios; specifically, during the test, the client needs to refresh the access interface to obtain a new page jump path before each page jump.

[0051] In the specific implementation of step S101, the interface access function (such as the http interface access function) of the client to be tested is triggered; the access interface of the server is refreshed, and the client request sent by the client to be tested to the server through the access interface (the refreshed interface) is captured (or intercepted).

[0052] That is, after refreshing the access interface of the server, the client to be tested sends a client request to the server through the access interface, and the client request is captured at this time. Specifically, the client request sent by the client to be tested is captured by the proxy server (based on the secondary development of mitmproxy proxy), wherein the client to be tested is pre-bound to the proxy server host.

[0053] It should be noted that the client request is a URL request; mitmproxy is a Python open source proxy framework.

[0054] In some embodiments, the client to be tested is an Android client.

[0055] Step S102: Send the client request to the server, and receive the first page jump path sent by the server through the access interface.

[0056] In the specific implementation of step S102, the captured client request is sent to the server, and the return content sent by the server is received. The return content can be stored in a text file; from the return content sent by the server, the first page jump path sent by the server through the access interface (the interface refreshed in step S101) is determined.

[0057] After receiving the first page jump path, the first page jump path is parameterized.

[0058] It should be noted that in actual situations, the server will send multiple return contents to the client to be tested through multiple interfaces; when determining the first page jump path, it is necessary to use the first URL requested by the client to match the URL of each return content to determine the return content sent by the server through the access interface (the interface refreshed in step S101), thereby obtaining the first page jump path.

[0059] In some embodiments, the first page jump path is a schema jump path, and the first page jump path is the schema field value.

[0060] Step S103: tampering with the first page jump path to obtain a second page jump path with a target page preset.

[0061] In the process of implementing step S103, in order to test page jumps in different scenarios, the first page jump path needs to be tampered with to obtain a second page jump path with a target page pre-set. The second page jump path is the tampered first page jump path, wherein the target page is the expected page after the page jump is performed based on the second page jump path.

[0062] That is to say, by tampering with the first page jump path, different schema jump situations are tested, for example: testing the jump to the play page (the target page is the play page at this time), testing the jump to the H5 page (the target page is the H5 page at this time).

[0063] In a specific implementation, the first page jump path can be tampered with through "flow.response.set_text(json.dumps(res))", where "res" is the returned content, which includes the first page jump path.

[0064] In some embodiments, the second page jump path is a schema jump path.

[0065] Step S104: sending the second page jump path to the client to be tested, so that the client to be tested jumps to the page to be verified based on the second page jump path.

[0066] In the specific implementation of step S104, the second page jump path is sent to the client under test, causing the client under test to load and display a target button corresponding to the second page jump path. The detection tool is called to trigger the target button (or click the target button) so that the client under test jumps to the page to be verified based on the second page jump path.

[0067] That is to say, after the second page jump path is sent to the client to be tested, the client to be tested loads and displays the target button corresponding to the second page jump path on the specified page (such as the home page), and triggers the target button on the specified page through the detection tool; after triggering the target button, the client to be tested jumps to the page to be verified based on the second page jump path.

[0068] It should be noted that the detection tool triggers the target button through a pre-packaged application programming interface (API), and the input parameter of the API is the second page jump path.

[0069] In some embodiments, the detection tool can be a UI automation tool implemented by writing scripts based on Appium.

[0070] Step S105: Compare the target page and the page to be verified to obtain a page jump test result, and return to step S101 until a preset stop condition is met.

[0071] As can be seen from the above content, the second page jump path is pre-set with a target page. In the specific implementation of step S105, after the client to be tested jumps to the page to be verified based on the second page jump path, the target page and the page to be verified are compared to obtain the page jump test result.

[0072] Specifically, if the target page and the page to be verified are the same, the page jump test result indicates that the page jump test of the client to be tested is accurate, that is, the client to be tested successfully jumps to the target page based on the second page jump path; if the target page and the page to be verified are different, the page jump test result indicates that the page jump test of the client to be tested is inaccurate, that is, the client to be tested did not successfully jump to the target page based on the second page jump path.

[0073] In some embodiments, after comparing the target page and the page to be verified to obtain the page jump test result, the client to be tested is controlled to return to the specified page; and step S101 is returned to continue the next scenario or next type of page jump test until a preset stop condition is met.

[0074] It should be noted that the preset stop condition may be receiving a test stop instruction; the preset stop condition may also be completing execution of all preset scenarios or types of page jump tests; the specific content of the preset stop condition is not limited in the embodiment of the present invention.

[0075] In an embodiment of the present invention, a client request is captured and sent to a server, which receives a first page jump path sent by the server. The first page jump path is tampered with to obtain a second page jump path having a target page. The second page jump path is sent to the client under test to cause it to jump to the page to be verified. By comparing the target page with the page to be verified, a page jump test result is obtained, eliminating the need for testers to perform page jump tests for each scenario, thereby improving test efficiency and accuracy.

[0076] The above embodiments of the present invention Figure 1 The process of receiving the first page jump path involved in step S102 is shown in FIG. Figure 2 , shows a flow chart of receiving a first page jump path provided by an embodiment of the present invention, including the following steps:

[0077] Step S201: Obtain the first URL requested by the client and send the client request to the server.

[0078] In the specific implementation of step S201, the first url requested by the client is obtained; specifically, the first url requested by the client is obtained based on the return class "Response()", for example: the first url is obtained using the method of "curl=flow.request.url".

[0079] Step S202: Obtain the page jump protocol to be processed sent by the server, and obtain the second URL of the page jump protocol to be processed.

[0080] It should be noted that in actual situations, the server will send multiple return contents to the client under test through multiple interfaces; at this time, obtain the pending page jump protocol contained in the return content sent by the server through any interface; and obtain the second URL of the pending page jump protocol.

[0081] Step S203: Determine whether the first URL and the second URL match. If the first URL and the second URL match, execute step S204; if the first URL and the second URL do not match, execute step S205.

[0082] In the specific implementation of step S203, whether the first URL and the second URL match is determined; specifically, whether the first URL and the second URL match is determined by "re.search(url, curl)! = None". In "re.search(url, curl)! = None", "url" is the second URL and "curl" is the first URL.

[0083] If the result of "re.search(url,curl)!=None" is "None", it means that the first url and the second url do not match, and step S205 is executed; if the result of "re.search(url,curl)!=None" is not "None", it means that the first url and the second url match (or the match is successful), and step S204 is executed.

[0084] Step S204: Determine that the page jump protocol to be processed is the first page jump path sent by the server through the access interface.

[0085] In the specific implementation of step S204, if the first URL and the second URL match, it is determined that the page jump protocol to be processed is the first page jump path sent by the server through the access interface.

[0086] Step S205: Send the page jump protocol to be processed to the client to be tested, and return to step S202.

[0087] In the process of implementing step S205, if the first URL and the second URL do not match, the page jump protocol to be processed is sent to the client to be tested, so that the client to be tested processes the page jump protocol to be processed according to the established processing flow; return to execute step S202, obtain a new page jump protocol to be processed, and again determine whether the second URL of the new page jump protocol to be processed matches the first URL.

[0088] Corresponding to the page jump test method provided by the above embodiment of the present invention, see Figure 3, an embodiment of the present invention also provides a structural block diagram of a page jump test device, the page jump test device includes: a processing unit 301, a first communication unit 302, a tampering unit 303, a second communication unit 304 and a comparison unit 305;

[0089] The processing unit 301 is configured to refresh the access interface of the server and capture the client request sent by the client to be tested to the server through the access interface.

[0090] The first communication unit 302 is configured to send the client request to the server and receive a first page jump path sent by the server through an access interface.

[0091] The tampering unit 303 is configured to tamper with the first page jump path to obtain a second page jump path with a target page preset.

[0092] The second communication unit 304 is configured to send the second page jump path to the client to be tested, so that the client to be tested jumps to the page to be verified based on the second page jump path.

[0093] In a specific implementation, the second communication unit 304 is specifically used to: send the second page jump path to the client to be tested, so that the client to be tested loads and displays the target button corresponding to the second page jump path; call the detection tool to trigger the target button, so that the client to be tested jumps to the page to be verified based on the second page jump path.

[0094] In some embodiments, the client to be tested is an Android client; the first page jump path and the second page jump path are schema jump paths.

[0095] The comparison unit 305 is used to compare the target page with the page to be verified to obtain a page jump test result, and returns to the execution processing unit 301 until a preset stop condition is met.

[0096] In an embodiment of the present invention, a client request is captured and sent to a server, which receives a first page jump path sent by the server. The first page jump path is tampered with to obtain a second page jump path having a target page. The second page jump path is sent to the client under test to cause it to jump to the page to be verified. By comparing the target page with the page to be verified, a page jump test result is obtained, eliminating the need for testers to perform page jump tests for each scenario, thereby improving test efficiency and accuracy.

[0097] Preferably, combined Figure 3 , see Figure 4, shows another structural block diagram of a page jump test device provided by an embodiment of the present invention, the first communication unit 302 includes: a communication module 3021, an acquisition module 3022 and a judgment module 3023;

[0098] The communication module 3021 is used to obtain the first URL requested by the client and send the client request to the server.

[0099] The acquisition module 3022 is used to obtain the page jump protocol to be processed sent by the server and obtain the second URL of the page jump protocol to be processed;

[0100] The judgment module 3023 is used to judge whether the first URL and the second URL match; if the first URL and the second URL match, it is determined that the page jump protocol to be processed is the first page jump path sent by the server through the access interface.

[0101] Preferably, the judgment module 3023 is further configured to: if the first URL and the second URL do not match, send the page jump protocol to be processed to the client to be tested, and return to execute the acquisition module 3022.

[0102] In summary, an embodiment of the present invention provides a page jump test method and device, which captures a client request and sends it to a server, and receives a first page jump path sent by the server. The first page jump path is tampered with to obtain a second page jump path with a target page. The second page jump path is sent to the client to be tested so that it jumps to the page to be verified. By comparing the target page and the page to be verified to obtain the page jump test result, it is no longer necessary for the tester to perform page jump tests on each scenario, thereby improving test efficiency and test accuracy.

[0103] Each embodiment in this specification is described in a progressive manner. The same or similar parts between the embodiments can be referred to each other. Each embodiment focuses on the differences from other embodiments. In particular, for system or system embodiments, since they are basically similar to method embodiments, the description is relatively simple. For relevant parts, refer to the partial description of the method embodiment. The system and system embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. A person of ordinary skill in the art can understand and implement it without expending creative work.

[0104] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the above description has generally described the components and steps of each example according to their functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present invention.

[0105] The above description of the disclosed embodiments is intended to enable one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be readily apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the scope of the present invention. Therefore, the present invention is not limited to the embodiments shown herein, but is intended to conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A page jump test method, characterized in that: The method comprises: Refreshing the access interface of the server and capturing the client request sent by the client to be tested to the server through the access interface; Sending the client request to the server, and receiving a first page jump path sent by the server through the access interface; Tampering with the first page jump path to obtain a second page jump path with a target page preset; Sending the second page jump path to the client to be tested, so that the client to be tested jumps to the page to be verified based on the second page jump path; Comparing the target page with the page to be verified to obtain a page jump test result, and returning to the step of refreshing the access interface of the server until a preset stop condition is met; Sending the client request to the server, and receiving a first page jump path sent by the server through the access interface, includes: Obtaining the first URL requested by the client, and sending the client request to the server; Obtain the pending page jump protocol issued by the server, and obtain the second URL of the pending page jump protocol; Determine whether the first URL and the second URL match; If the first URL and the second URL match, it is determined that the page jump protocol to be processed is the first page jump path sent by the server through the access interface.

2. The method according to claim 1, characterized in that Sending the second page jump path to the client to be tested, so that the client to be tested jumps to the page to be verified based on the second page jump path, includes: Sending the second page jump path to the client to be tested, so that the client to be tested loads and displays a target button corresponding to the second page jump path; The detection tool is called to trigger the target button, so that the client to be tested jumps to the page to be verified based on the second page jump path.

3. The method according to claim 1, characterized in that After determining whether the first URL and the second URL match, the method further includes: If the first URL and the second URL do not match, the page jump protocol to be processed is sent to the client to be tested, and the process returns to the step of obtaining the page jump protocol to be processed issued by the server.

4. The method according to any one of claims 1 to 3, characterized in that The client to be tested is an Android client; the first page jump path and the second page jump path are schema jump paths.

5. A page jump testing device, characterized in that: The device comprises: A processing unit, configured to refresh the access interface of the server and capture the client request sent by the client to be tested to the server through the access interface; A first communication unit is configured to send the client request to the server and receive a first page jump path sent by the server through the access interface; a tampering unit, configured to tamper with the first page jump path to obtain a second page jump path with a target page preset; A second communication unit is configured to send the second page jump path to the client to be tested, so that the client to be tested jumps to the page to be verified based on the second page jump path; a comparison unit, configured to compare the target page with the page to be verified to obtain a page jump test result, and return to execute the processing unit until a preset stop condition is met; The first communication unit includes: A communication module, configured to obtain a first URL requested by the client and send the client request to the server; An acquisition module, configured to acquire the pending page jump protocol issued by the server, and acquire a second URL of the pending page jump protocol; The judgment module is used to judge whether the first url and the second url match; if the first url and the second url match, determine that the page jump protocol to be processed is the first page jump path sent by the server through the access interface.

6. The device according to claim 5, characterized in that The second communication unit is specifically used to: send the second page jump path to the client under test, so that the client under test loads and displays the target button corresponding to the second page jump path; call the detection tool to trigger the target button, so that the client under test jumps to the page to be verified based on the second page jump path.

7. The device according to claim 5, characterized in that The judgment module is further configured to: if the first URL and the second URL do not match, send the page jump protocol to be processed to the client to be tested, and return to execute the acquisition module.

8. The device according to any one of claims 5-6, characterized in that The client to be tested is an Android client; the first page jump path and the second page jump path are schema jump paths.

Images