Detection Method, Device, Storage Medium and Equipment for Mobile Application

Abstract

The present application discloses a detection method, device, storage medium and equipment for a mobile application. The method is as follows: after receiving a detection instruction sent by a user, a preset automated testing tool is called to trigger the terminal to start the mobile application; the terminal is controlled to bind the network node address of the server, so that the mobile application sends network requests corresponding to each UI scene to the server according to each pre-configured UI scene; for each UI scene, when all network requests corresponding to the UI scene meet the preset conditions, the UI scene is marked as a legal UI scene; based on the legal UI scenes, a detection report is generated and sent to the user. This method can detect each UI scene in the mobile application without manual operation of the mobile application and without spending labor costs to check the network requests under each UI scene. Compared with the prior art, the detection efficiency of the mobile application is significantly improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular, to a detection method, device, storage medium, and equipment for mobile applications. Background Art

[0002] After a mobile application is launched, due to security or regulatory reasons, it is necessary to detect whether the UI scenarios of the mobile application are legal.

[0003] The existing detection method is as follows: manually operate the mobile application to trigger all network requests in each UI scenario, and determine whether the UI scenario is legal by checking each network request. However, the number of UI scenarios provided by the mobile application is large, and the number of network requests in each UI scenario is also large. Limited by labor costs, the detection efficiency of the existing detection method is relatively low.

[0004] Therefore, how to improve the detection efficiency of mobile applications has become an urgent problem to be solved in this field. Summary of the Invention

[0005] This application provides a detection method, device, storage medium, and equipment for mobile applications, aiming to improve the detection efficiency of mobile applications.

[0006] To achieve the above object, this application provides the following technical solutions:

[0007] A detection method for mobile applications includes:

[0008] After receiving a detection instruction sent by a user, call a preset automated testing tool to trigger the terminal to start a pre-installed mobile application;

[0009] Control the terminal to bind to the network node address of the server, so that the mobile application sends network requests corresponding to each UI scenario to the server according to the pre-configured UI scenarios; the network request includes at least a network address and body information;

[0010] For each UI scenario, when all network requests corresponding to the UI scenario meet the preset conditions, mark the UI scenario as a legal UI scenario; where the preset conditions are: the network address does not contain any illegal domain names in the preset illegal domain name list, and the body information does not contain any sensitive characters in the preset sensitive character list;

[0011] Generate a detection report based on the legal UI scenarios, and send the detection report to the user.

[0012] Optionally, controlling the network node address of the terminal to bind to the server, so that the mobile application sends network requests corresponding to each UI scenario to the server according to the pre-configured UI scenarios, includes:

[0013] Pre-delete the network requests in the preset real-time request collection table;

[0014] Control the network node address of the terminal to bind to the server, so that the mobile application sends network requests corresponding to each UI scenario to the server according to the pre-configured UI scenarios;

[0015] For each UI scenario, call the preset open-source network proxy tool to save all the network requests sent by the mobile application in the UI scenario to the real-time request collection table.

[0016] Optionally, in the case that all the network requests corresponding to the UI scenario meet the preset conditions, marking the UI scenario as a legal UI scenario, includes:

[0017] In the case that all the network requests corresponding to the UI scenario meet the preset conditions, obtain the scenario expected request list of the UI scenario from the preset database; the scenario expected request list includes multiple sample network requests;

[0018] In the case that all the network requests corresponding to the UI scenario are the same as all the sample network requests of the UI, mark the UI scenario as a legal UI scenario.

[0019] Optionally, it further includes:

[0020] In the case that not all the network requests corresponding to the UI scenario meet the preset conditions, mark the UI scenario as an illegal UI scenario.

[0021] Optionally, it further includes:

[0022] In the case that not all the network requests corresponding to the UI scenario are the same as all the sample network requests of the UI, mark the UI scenario as an illegal UI scenario.

[0023] Optionally, in the case that all the network requests corresponding to the UI scenario are the same as all the sample network requests of the UI, marking the UI scenario as a legal UI scenario, includes:

[0024] In the case that all the network requests corresponding to the UI scenario are the same as all the sample network requests of the UI, determine whether the types of all the network requests corresponding to the UI scenario are all hypertext transfer security protocol requests;

[0025] When the types of all network requests corresponding to the UI scenario are all Hypertext Transfer Security Protocol requests, the UI scenario is identified as a legal UI scenario.

[0026] Optionally, it further includes:

[0027] When the types of all network requests corresponding to the UI scenario are not all Hypertext Transfer Security Protocol requests, the UI scenario is identified as an illegal UI scenario.

[0028] A detection device for a mobile application, including:

[0029] A startup unit, configured to, after receiving a detection instruction sent by a user, call a preset automated testing tool to trigger the terminal to start a pre-installed mobile application;

[0030] A control unit, configured to control the network node address of the terminal to be bound to the server, so that the mobile application sends network requests corresponding to each UI scenario to the server according to each pre-configured UI scenario; the network request at least includes a network address and body information;

[0031] An identification unit, configured to, for each UI scenario, when all network requests corresponding to the UI scenario meet preset conditions, identify the UI scenario as a legal UI scenario; wherein, the preset conditions are: the network address does not include any illegal domain name in a preset illegal domain name list, and the body information does not include any sensitive character in a preset sensitive character list;

[0032] A generation unit, configured to generate a detection report based on the legal UI scenario and send the detection report to the user.

[0033] A computer-readable storage medium, the computer-readable storage medium includes a stored program, wherein the program executes the detection method of the mobile application.

[0034] A detection device for a mobile application, including: a processor, a memory, and a bus; the processor is connected to the memory through the bus;

[0035] The memory is used to store a program, and the processor is used to run the program, wherein the program, when running, executes the detection method of the mobile application.

[0036] The technical solution provided by this application, after receiving a detection instruction sent by a user, calls a preset automated testing tool to trigger the terminal to start a pre-installed mobile application. The control terminal binds the network node address of the server, so that the mobile application sends network requests corresponding to each UI scenario to the server according to the pre-configured UI scenarios. The network requests at least include a network address and body information. For each UI scenario, when all network requests corresponding to the UI scenario meet the preset conditions, the UI scenario is marked as a legal UI scenario. Among them, the preset conditions are: the network address does not contain any illegal domain names in the preset illegal domain name list, and the body information does not contain any sensitive characters in the preset sensitive character list. Based on the legal UI scenarios, a detection report is generated and sent to the user. Using the solution shown in this application, it is not necessary to manually operate the mobile application, nor is it necessary to spend human costs to check the network requests under each UI scenario, so as to realize the detection of each UI scenario in the mobile application. Compared with the prior art, the detection efficiency of the mobile application is significantly improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0038] Figure 1a It is a schematic flowchart of a method for detecting a mobile application provided by an embodiment of the present application;

[0039] Figure 1b It is a schematic flowchart of a method for detecting a mobile application provided by an embodiment of the present application;

[0040] Figure 2 It is a schematic flowchart of another method for detecting a mobile application provided by an embodiment of the present application;

[0041] Figure 3 It is a schematic architecture diagram of a device for detecting a mobile application provided by an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0042] The following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some embodiments of the present application, rather than all embodiments. Based on the embodiments of the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0043] As Figure 1a and Figure 1b shown, the following is a schematic flowchart of a detection method for a mobile application provided by an embodiment of the present application, including the following steps:

[0044] S101: After receiving a detection instruction sent by a user, call a preset automated testing tool to trigger the terminal to start a pre-installed mobile application.

[0045] Among them, the preset automated testing tools include but are not limited to: Appium, Calabash, Robotium, Frank, and UIAutomator, etc. In the embodiment of the present application, triggering the terminal to start a pre-installed application is merely to play back a pre-recorded use case. The specific implementation principles of the recording and playback of the use case are common knowledge familiar to those skilled in the art and will not be elaborated here.

[0046] S102: Delete the network requests in the preset real-time request collection table.

[0047] Among them, in order to prevent obtaining invalid network requests from the real-time request collection table subsequently, therefore, it is necessary to clear the network requests in the real-time request collection table in advance.

[0048] S103: Control the terminal to bind the network node (host) address of the server, so that the mobile application sends network requests corresponding to each UI scenario to the server according to the pre-configured UI scenarios.

[0049] Among them, the so-called UI scenario is used to indicate the page access scenario, that is, to access the page using the mobile application. The number of network requests corresponding to each UI scenario can be one or more.

[0050] It should be noted that the network request includes user agent information, network address, body information, request method, and the scenario id of the UI scenario to which the network request belongs. In practical applications, the user agent information includes the device information of the terminal, and this device information can be used to indicate the source of the network request. The request methods include but are not limited to: get method and post method.

[0051] Generally speaking, the server shown in the embodiment of the present application adopts the Django architecture. Therefore, based on the data collection characteristics of the Django architecture, only by controlling the terminal to bind the network node address of the server, the mobile application can send network requests to the server according to the UI scenario to realize the access of the functional page.

[0052] S104: For each UI scenario, call a preset open-source network proxy tool to save all the network requests sent by the mobile application in the UI scenario to the real-time request collection table.

[0053] Among them, the preset open-source network proxy tools include, but are not limited to, the mitmproxy tool in the Python language.

[0054] It should be noted that the user agent information, network address, body information, request method, and scenario ID of the network request are all stored in the respective fields of the real-time request collection table in the form of key-value pairs, and each field includes a url field, a body field, a platform field, a method field, and an id field.

[0055] Generally speaking, the value corresponding to the url field as the key is used to record the network address, the value corresponding to the body field as the key is used to record the body information, the value corresponding to the platform field as the key is used to record the user agent information, the value corresponding to the method field as the key is used to record the request method, and the value corresponding to the id field as the key is used to record the scenario ID.

[0056] Specifically, the real-time request collection table shown in the embodiments of the present application can be seen in Table 1 shown below.

[0057] Table 1

[0058] url body platform method id https: / / nuc.api.com Support=101001 null get 1

[0059] The content shown in Table 1 above is only for illustrative purposes.

[0060] S105: Determine whether all network requests recorded in the real-time request collection table corresponding to the UI scenario meet the preset conditions.

[0061] If all network requests recorded in the real-time request collection table corresponding to the UI scenario meet the preset conditions, then execute S106; otherwise, execute S110.

[0062] Among them, the preset conditions are: the network address does not contain any illegal domain names in the preset illegal domain name list, and the body information does not contain any sensitive characters in the preset sensitive character list.

[0063] S106: Obtain the scenario expected request list of the UI scenario from the preset database.

[0064] Among them, the preset database includes the scenario expected request lists of each UI scenario, and each scenario expected request list includes multiple sample network requests.

[0065] S107: Determine whether all network requests recorded in the real-time request collection table corresponding to the UI scenario are the same as all sample network requests of the UI scenario.

[0066] If all the network requests corresponding to the UI scenario recorded in the real-time request collection table are the same as all the sample network requests of the UI scenario, then execute S108; otherwise, execute S110.

[0067] S108: Determine whether the types of all the network requests corresponding to the UI scenario recorded in the real-time request collection table are all Hyper Text Transfer Protocol over Secure Socket Layer (HTTPS) requests.

[0068] If the types of all the network requests corresponding to the UI scenario recorded in the real-time request collection table are all HTTPS requests, then execute S109; otherwise, execute S110.

[0069] S109: Determine that the UI scenario does not contain illegal network requests, mark the UI scenario as a legal UI scenario, and delete all the network requests corresponding to the UI scenario from the real-time request collection table.

[0070] After executing S109, continue to execute S111.

[0071] S110: Determine that the UI scenario contains illegal network requests, mark the UI scenario as an illegal UI scenario, and delete all the network requests corresponding to the UI scenario from the real-time request collection table.

[0072] After executing S110, continue to execute S111.

[0073] S111: Generate a detection report based on the legal UI scenario and the illegal UI scenario, and send the detection report to the user.

[0074] In summary, by using the solution shown in this embodiment, it is possible to detect each UI scenario in the mobile application without manual operation of the mobile application and without spending human costs to check the network requests under each UI scenario. Compared with the prior art, the detection efficiency of the mobile application is significantly improved.

[0075] It should be noted that S109 mentioned in the above embodiment is an optional implementation manner of the detection method for the mobile application claimed in the application. In addition, S110 mentioned in the above embodiment is also an optional implementation manner of the detection method for the mobile application claimed in this application. Therefore, the process mentioned in the above embodiment can be summarized as Figure 2 the method shown.

[0076] As Figure 2As shown in the figure, it is a schematic flowchart of another detection method for mobile applications provided by an embodiment of the present application, including the following steps:

[0077] S201: After receiving a detection instruction sent by a user, call a preset automated testing tool to trigger the terminal to start a pre-installed mobile application.

[0078] S202: Control the terminal to bind to the network node address of the server, so that the mobile application sends a network request corresponding to each UI scene to the server according to each pre-configured UI scene.

[0079] Among them, the network request includes at least a network address and body information.

[0080] S203: For each UI scene, when all network requests corresponding to the UI scene meet the preset conditions, mark the UI scene as a legal UI scene.

[0081] Among them, the preset conditions are: the network address does not contain any illegal domain names in the preset illegal domain name list, and the body information does not contain any sensitive characters in the preset sensitive character list.

[0082] S204: Generate a detection report based on the legal UI scenes and send the detection report to the user.

[0083] In summary, using the solution shown in this embodiment, it is not necessary to manually operate the mobile application, nor is it necessary to spend labor costs to check the network requests under each UI scene, so as to realize the detection of each UI scene in the mobile application. Compared with the prior art, the detection efficiency of the mobile application is significantly improved.

[0084] Corresponding to the detection method for mobile applications provided by the above embodiment of the present application, the embodiment of the present application also provides a detection device for mobile applications.

[0085] As Figure 3 shown, it is a schematic architecture diagram of a detection device for mobile applications provided by an embodiment of the present application, including:

[0086] A startup unit 100, configured to call a preset automated testing tool after receiving a detection instruction sent by a user, and trigger the terminal to start a pre-installed mobile application.

[0087] A control unit 200, configured to control the terminal to bind to the network node address of the server, so that the mobile application sends a network request corresponding to each UI scene to the server according to each pre-configured UI scene; the network request includes at least a network address and body information.

[0088] Optionally, the control unit 200 is specifically configured to: pre-delete network requests in a preset real-time request collection table; control the terminal to bind the network node address of the server, so that the mobile application sends network requests corresponding to each UI scenario to the server according to each pre-configured UI scenario; for each UI scenario, call a preset open-source network proxy tool to save all network requests sent by the mobile application in the UI scenario to the real-time request collection table.

[0089] The identification unit 300 is used to, for each UI scenario, when all network requests corresponding to the UI scenario meet the preset conditions, identify the UI scenario as a legal UI scenario; wherein, the preset conditions are: the network address does not contain any illegal domain name in the preset illegal domain name list, and the main body information does not contain any sensitive character in the preset sensitive character list.

[0090] Optionally, the identification unit 300 is specifically configured to: when all network requests corresponding to the UI scenario meet the preset conditions, obtain the scenario expected request list of the UI scenario from the preset database; the scenario expected request list includes multiple sample network requests; when all network requests corresponding to the UI scenario are the same as all sample network requests of the UI, identify the UI scenario as a legal UI scenario.

[0091] The identification unit 300 is further used to: when all network requests corresponding to the UI scenario do not all meet the preset conditions, identify the UI scenario as an illegal UI scenario.

[0092] The identification unit 300 is further used to: when all network requests corresponding to the UI scenario are not all the same as all sample network requests of the UI, identify the UI scenario as an illegal UI scenario.

[0093] The identification unit 300 is specifically configured to: when all network requests corresponding to the UI scenario are the same as all sample network requests of the UI, determine whether the types of all network requests corresponding to the UI scenario are all Hypertext Transfer Security Protocol requests; when the types of all network requests corresponding to the UI scenario are all Hypertext Transfer Security Protocol requests, identify the UI scenario as a legal UI scenario.

[0094] The identification unit 300 is further used to: when the types of all network requests corresponding to the UI scenario are not all Hypertext Transfer Security Protocol requests, identify the UI scenario as an illegal UI scenario.

[0095] The generation unit 400 is used to generate a detection report based on the legal UI scenario and send the detection report to the user.

[0096] In summary, by using the solution shown in this embodiment, it is not necessary to manually operate the mobile application, nor is it necessary to spend labor costs to check the network requests in each UI scenario, and the detection of each UI scenario in the mobile application can be realized. Compared with the prior art, the detection efficiency of the mobile application is significantly improved.

[0097] The present application also provides a computer-readable storage medium, which includes a stored program. Among them, the program executes the detection method of the mobile application provided by the present application.

[0098] The present application also provides a detection device for a mobile application, including: a processor, a memory, and a bus. The processor is connected to the memory through the bus. The memory is used to store the program, and the processor is used to run the program. Among them, when the program runs, it executes the detection method of the mobile application provided by the present application, including the following steps:

[0099] After receiving the detection instruction sent by the user, call the preset automated testing tool to trigger the terminal to start the pre-installed mobile application;

[0100] Control the terminal to bind the network node address of the server, so that the mobile application sends network requests corresponding to each UI scenario to the server according to the pre-configured UI scenarios; the network request includes at least a network address and main body information;

[0101] For each UI scenario, when all network requests corresponding to the UI scenario meet the preset conditions, mark the UI scenario as a legal UI scenario; where the preset conditions are: the network address does not contain any illegal domain name in the preset illegal domain name list, and the main body information does not contain any sensitive character in the preset sensitive character list;

[0102] Generate a detection report based on the legal UI scenarios and send the detection report to the user.

[0103] Specifically, on the basis of the above embodiment, the controlling the terminal to bind the network node address of the server, so that the mobile application sends network requests corresponding to each UI scenario to the server includes:

[0104] Pre-delete the network requests in the preset real-time request collection table;

[0105] Control the terminal to bind the network node address of the server, so that the mobile application sends network requests corresponding to each UI scenario to the server according to the pre-configured UI scenarios;

[0106] For each of the UI scenarios, call a preset open-source network proxy tool to save all network requests sent by the mobile application in the UI scenario to the real-time request collection table.

[0107] Specifically, based on the above embodiments, when all network requests corresponding to the UI scenario meet the preset conditions, marking the UI scenario as a legal UI scenario includes:

[0108] When all network requests corresponding to the UI scenario meet the preset conditions, obtain the scenario expected request list of the UI scenario from a preset database; the scenario expected request list includes multiple sample network requests;

[0109] When all network requests corresponding to the UI scenario are the same as all sample network requests of the UI, mark the UI scenario as a legal UI scenario.

[0110] Specifically, based on the above embodiments, it further includes:

[0111] When not all network requests corresponding to the UI scenario meet the preset conditions, mark the UI scenario as an illegal UI scenario.

[0112] Specifically, based on the above embodiments, it further includes:

[0113] When not all network requests corresponding to the UI scenario are the same as all sample network requests of the UI, mark the UI scenario as an illegal UI scenario.

[0114] Specifically, based on the above embodiments, when all network requests corresponding to the UI scenario are the same as all sample network requests of the UI, marking the UI scenario as a legal UI scenario includes:

[0115] When all network requests corresponding to the UI scenario are the same as all sample network requests of the UI, determine whether the types of all network requests corresponding to the UI scenario are all Hypertext Transfer Security Protocol requests;

[0116] When the types of all network requests corresponding to the UI scenario are all the Hypertext Transfer Security Protocol requests, mark the UI scenario as a legal UI scenario.

[0117] Specifically, based on the above embodiments, it further includes:

[0118] When not all types of network requests corresponding to the UI scenario are Hypertext Transfer Security Protocol requests, the UI scenario is identified as an illegal UI scenario.

[0119] If the functions described in the method embodiments of this application are implemented in the form of software function units and sold or used as independent products, they can be stored in a storage medium readable by a computing device. Based on this understanding, the part of this application that contributes to the prior art or part of this technical solution can be embodied in the form of a software product. The software product is stored in a storage medium and includes several instructions for causing a computing device (which may be a personal computer, a server, a mobile computing device, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The foregoing storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memories, random access memories, magnetic disks, or optical discs that can store program codes.

[0120] The various embodiments in this specification are described in a progressive manner. The key point of each embodiment is to illustrate the differences from other embodiments. The same or similar parts among the various embodiments can be referred to each other.

[0121] The above description of the disclosed embodiments enables those skilled in the art to implement or use this application. Various modifications to these embodiments will be obvious to those skilled in the art. The general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application will not be limited to the embodiments shown herein, but rather will be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A detection method for a mobile application, characterized in that, Including: After receiving a detection instruction sent by a user, call a preset automated testing tool to trigger the terminal to start a pre-installed mobile application; Control the terminal to bind to the network node address of the server, so that the mobile application sends network requests corresponding to each UI scenario to the server according to the pre-configured UI scenarios; the network requests include user agent information, network address, body information, request method, and the scenario id of the UI scenario to which the network request belongs; For each UI scenario, when all network requests corresponding to the UI scenario meet the preset conditions, mark the UI scenario as a legal UI scenario; wherein, the preset conditions are: the network address does not contain any illegal domain names in the preset illegal domain name list, and the body information does not contain any sensitive characters in the preset sensitive character list; Generate a detection report based on the legal UI scenarios and send the detection report to the user; Wherein, the step of marking the UI scenario as a legal UI scenario when all network requests corresponding to the UI scenario meet the preset conditions includes: When all network requests corresponding to the UI scenario meet the preset conditions, obtain the scenario expected request list of the UI scenario from a preset database; the scenario expected request list includes multiple sample network requests; When all network requests corresponding to the UI scenario are the same as all sample network requests of the UI, mark the UI scenario as a legal UI scenario.

2. The method according to claim 1, wherein The step of controlling the terminal to bind to the network node address of the server, so that the mobile application sends network requests corresponding to each UI scenario to the server according to the pre-configured UI scenarios includes: Delete the network requests in the preset real-time request collection table in advance; Control the terminal to bind to the network node address of the server, so that the mobile application sends network requests corresponding to each UI scenario to the server according to the pre-configured UI scenarios; For each UI scenario, call a preset open-source network proxy tool to save all network requests sent by the mobile application in the UI scenario to the real-time request collection table.

3. The method according to claim 1, wherein Also including: When not all network requests corresponding to the UI scenario meet the preset conditions, mark the UI scenario as an illegal UI scenario.

4. The method according to claim 1, characterized in that Also including: When not all network requests corresponding to the UI scenario are the same as all sample network requests of the UI, mark the UI scenario as an illegal UI scenario.

5. The method according to claim 1, wherein The step of marking the UI scenario as a legal UI scenario when all network requests corresponding to the UI scenario are the same as all sample network requests of the UI includes: When all network requests corresponding to the UI scenario are the same as all sample network requests of the UI, determine whether the types of all network requests corresponding to the UI scenario are all hypertext transfer security protocol requests; When the types of all network requests corresponding to the UI scenario are all Hypertext Transfer Security Protocol requests, the UI scenario is identified as a legal UI scenario.

6. The method according to claim 5, wherein It further includes: When the types of all network requests corresponding to the UI scenario are not all Hypertext Transfer Security Protocol requests, the UI scenario is identified as an illegal UI scenario.

7. A detection device for a mobile application, characterized in that, It includes: A startup unit, configured to, after receiving a detection instruction sent by a user, call a preset automated testing tool to trigger the terminal to start a pre-installed mobile application; A control unit, configured to control the network node address of the terminal to be bound to a server, so that the mobile application sends network requests corresponding to each UI scenario to the server according to each pre-configured UI scenario; the network requests include user agent information, network address, body information, request method, and the scenario id of the UI scenario to which the network request belongs; An identification unit, configured to, for each UI scenario, when all network requests corresponding to the UI scenario meet preset conditions, identify the UI scenario as a legal UI scenario; wherein, the preset conditions are: the network address does not contain any illegal domain name in a preset illegal domain name list, and the body information does not contain any sensitive character in a preset sensitive character list; A generation unit, configured to generate a detection report based on the legal UI scenario and send the detection report to the user; Among them, when all network requests corresponding to the UI scenario meet preset conditions, the identification unit identifies the UI scenario as a legal UI scenario, including: When all network requests corresponding to the UI scenario meet preset conditions, obtain a scenario expected request list of the UI scenario from a preset database; the scenario expected request list includes multiple sample network requests; When all network requests corresponding to the UI scenario are the same as all sample network requests of the UI, the UI scenario is identified as a legal UI scenario.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein the program executes the detection method of the mobile application according to any one of claims 1-6.

9. A detection device for a mobile application, characterized in that, It includes: A processor, a memory, and a bus; The processor is connected to the memory through the bus; The memory is used to store a program, and the processor is used to run the program, wherein when the program runs, it executes the detection method of the mobile application according to any one of claims 1-6.

Images