CN111459774A - Method, device and equipment for acquiring flow of application program and storage medium - Google Patents
Method, device and equipment for acquiring flow of application program and storage medium Download PDFInfo
- Publication number
- CN111459774A CN111459774A CN201910054892.6A CN201910054892A CN111459774A CN 111459774 A CN111459774 A CN 111459774A CN 201910054892 A CN201910054892 A CN 201910054892A CN 111459774 A CN111459774 A CN 111459774A
- Authority
- CN
- China
- Prior art keywords
- behavior
- current interface
- executing
- operation behavior
- information
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3438—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment monitoring of user actions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
- G06F3/04817—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance using icons
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/04—Processing captured monitoring data, e.g. for logfile generation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
- H04L47/2475—Traffic characterised by specific attributes, e.g. priority or QoS for supporting traffic characterised by the type of applications
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Human Computer Interaction (AREA)
- Signal Processing (AREA)
- Quality & Reliability (AREA)
- Data Mining & Analysis (AREA)
- Computer Hardware Design (AREA)
- Stored Programmes (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the application discloses a method, a device, equipment and a storage medium for acquiring the flow of an application program, wherein the method comprises the following steps: calling an automatic script corresponding to the current interface according to the operation behavior identifier on the current interface of the application program; executing the automation script to generate flow information by executing the operation behavior to be detected in the packaging operation behavior group; and identifying the flow information and outputting the identified flow information.
Description
Technical Field
The embodiment of the application relates to the field of service support based on computer information technology, and relates to but is not limited to a method, a device, equipment and a storage medium for acquiring the flow of an application program.
Background
Currently, with the rapid development of mobile internet, in order to meet the needs of users, Applications (APPs) with various functions are developed. The demand of operators for APP traffic analysis in wireless networks is also more and more urgent, and it is necessary to parse and identify traffic data packets in a pipe, so the position of Deep Packet Inspection (DPI) technology is gradually increasing in operators, where the pipe is an entity for carrying traffic. DPI is a flow monitoring and control technology based on an application layer, and obtains valuable information by reading binary original code stream data of a flow data packet to perform parsing, such as: application service identification, network flow control, etc.
In order to enable traffic identification functionality in DPI devices, a large amount of traffic data with application classes (hereinafter simply referred to as "tags") is required, such as: a traffic data packet of a WeChat APP, a traffic data packet of a mobile business hall APP, and the like. To generate these tagged traffic data, methods are currently in common use that: manual packet grabbing, compiling automatic script packet grabbing for each application, and the like. However, since the automation scripts need to be written for each application, the complexity of writing the scripts is increased, and the scripts need to be modified when the applications are changed, which increases the difficulty and labor cost of designing the scripts.
Disclosure of Invention
In view of the above, embodiments of the present application provide a method, an apparatus, a device, and a storage medium for acquiring traffic of an application program to solve at least one problem in the prior art.
The technical scheme of the embodiment of the application is realized as follows:
in a first aspect, an embodiment of the present application provides a method for acquiring a flow of an application program, where the method includes: calling an automatic script corresponding to a current interface according to an operation behavior identifier on the current interface of an application program; executing the automation script to generate flow information by executing the operation behavior to be detected in the packaging operation behavior group; and identifying the flow information and outputting the identified flow information.
In a second aspect, an embodiment of the present application provides an apparatus for acquiring traffic of an application, where the apparatus includes: the calling unit is configured to call the automatic script corresponding to the current interface according to the operation behavior identifier on the current interface of the application program; the execution unit is configured to execute the automation script so as to generate flow information by executing the operation behavior to be detected in the packaged operation behavior group; and the identification unit is configured to identify the traffic information and output the identified traffic information.
In a third aspect, an embodiment of the present application provides an apparatus for acquiring traffic of an application, where the apparatus at least includes: a processor and a storage medium configured to store executable instructions, wherein: the processor is configured to execute stored executable instructions configured to perform the method for acquiring traffic of an application program provided by the above-mentioned embodiments.
In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, where computer-executable instructions are stored in the computer-readable storage medium, and the computer-executable instructions are configured to execute the method for acquiring traffic of an application program provided in the foregoing embodiment.
In the embodiment of the application, through calling and executing the preset automatic script, flow information is generated through the to-be-detected behaviors in the to-be-detected behavior group, the flow information is identified, the flow grabbing and label automatic generation of the APPs can be realized, the special script is no longer compiled for each APP, the basic actions of the human operation mobile phone are abstracted, a series of complex actions are combined, and the deep traversal of each control in the APPs is completed.
Drawings
Fig. 1 is a first flowchart illustrating a method for acquiring traffic of an application according to an embodiment of the present application;
FIG. 2 is a block diagram of an automated click process provided by an embodiment of the present application;
fig. 3 is a second flowchart illustrating a method for acquiring traffic of an application according to an embodiment of the present application;
fig. 4 is a schematic source code diagram of an acquisition control according to an embodiment of the present application;
FIG. 5 is a schematic interface diagram of a consent regulation status provided by an embodiment of the present application;
fig. 6A is a first schematic interface diagram of a closed window state according to an embodiment of the present disclosure;
fig. 6B is a second schematic interface diagram of a closed window state according to the present embodiment;
FIG. 7 is a schematic diagram of an interface of a verification code login status provided in an embodiment of the present application;
fig. 8 is a schematic interface diagram of an account password login state according to an embodiment of the present disclosure;
FIG. 9A is a first schematic view of an interface illustrating a welcome window status according to an embodiment of the present application;
fig. 9B is a second interface schematic diagram of a welcome window status provided by the present application;
fig. 9C is a third schematic interface diagram of a welcome window status provided by the embodiment of the present application;
fig. 10 is a schematic structural diagram of an apparatus for acquiring traffic of an application according to an embodiment of the present application;
fig. 11 is a schematic structural diagram of an apparatus for acquiring traffic of an application according to an embodiment of the present application.
Detailed Description
In the related art, the APP flow data with the tag can be acquired manually or mechanically. Wherein, the manual mode is: and manually installing an APP, clicking, monitoring flow, grabbing a packet, and finally manually marking. However, with the rapid development of mobile internet, the number of APP applications grows at an explosive rate, and the version iteration update rate is also very rapid. The new APP can not be manually captured to acquire data, and an automatic test script can not be compiled for each version update. A more versatile automated test tool solution is available. Taking an Android system as an example, currently, a mainstream Android test frame includes APPium, uiautomation, Robotium and Monkey, an Android platform has a plurality of automatic test tools, and testers can perform behavior operation on APP by compiling test case scripts.
Different automatic test scripts are compiled aiming at different APPs, although all operations in the APPs can be accurately and completely executed, due to the occurrence of massive applications and the updating of a plurality of versions of the APPs, the compiled scripts are invalid and need to be revised again, and a large amount of labor cost is increased by adding the scripts. And mining APP service identification rules or models requires a large amount of flow data to enable the identification effect to be better, if the automatic script compiling efficiency is insufficient, subsequent mining on the flow data can be caused, especially the scheme of machine learning is used, mass data are required to be trained, and the user cannot always invest in manual work to compile scripts.
Aiming at the defects of the related technology, a more randomized solution is adopted in the embodiment of the application, a corresponding automatic script is not required to be written for each APP, a large amount of abstract human-like behaviors are packaged, interface information on the terminal is used as input, corresponding behaviors are generated and fed back to the terminal, the behavior operation is carried out, and the behavior operation is continuously and repeatedly carried out to approach the effect of manual clicking.
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, specific technical solutions of the present invention will be described in further detail below with reference to the accompanying drawings in the embodiments of the present application. The following examples are intended to illustrate the present application but are not intended to limit the scope of the present application.
The embodiment of the present application provides a method for acquiring traffic of an application, where the method is applied to an apparatus for acquiring traffic of an application, where the apparatus may be an electronic apparatus such as a mobile phone, a desktop computer, a tablet computer, a server cluster, and the like, and functions implemented by the method may be implemented by a processor in the apparatus calling a program code, where the program code may be stored in a computer storage medium.
Fig. 1 is a first schematic flow chart of a method for acquiring traffic of an application program according to an embodiment of the present application, as shown in fig. 1, the method includes:
and step S11, the flow acquiring device calls an automation script corresponding to the current interface according to the operation behavior identification on the current interface of the application program.
Here, the operation behavior identifier is used to identify a corresponding control, and may be an icon or a text displayed on the interface. In the embodiment of the application, if the terminal is provided with the application program, the corresponding application program can be started and operated through a trigger instruction input by a user, the interface corresponding to the application program is entered, and the automatic script corresponding to the current interface can be called through the operation behavior identifier on the current interface of the application program. In the embodiment of the application, a universal automation script is preset, and the corresponding automation script can be called through all control information on the corresponding interface.
And step S12, the traffic acquiring device executes the automation script to generate traffic information by executing the operation behavior to be detected in the packaged operation behavior group.
In the process of designing the script, the operation behaviors to be detected, which can be executed on the interfaces of most application programs at present, can be obtained, the operation behaviors are packaged to form a corresponding packaged operation behavior group, and the automatic script corresponding to the interface is designed according to the packaged operation behavior group, wherein the packaged operation behavior group can comprise various human-simulated operation behaviors to be detected. Correspondingly, when the automation script is executed on the terminal, the operation behavior to be detected in the encapsulation operation behavior group can be executed, and flow information is generated. For example, if the current behavior is in the sliding welcome window state, the behavior to be detected in the packaged operation behavior group includes a click behavior and a sliding behavior, and when the script is executed, the terminal may automatically execute the click behavior and the sliding behavior to generate a corresponding flow, and as for the click times and the sliding range, both may be preset, and are not specifically limited herein.
Step S13, the traffic acquiring device identifies the traffic information and outputs the identified traffic information.
Here, after the traffic information is generated through the corresponding operation behavior in the process of executing the automation script, the traffic information may be identified so as to further process the identified traffic information through the deep packet inspection technology.
In other embodiments, identifying the traffic information and outputting the identified traffic information includes: and acquiring the flow information generated by the current interface, identifying the flow information according to the type of the application program, and outputting the identified flow information.
Here, the traffic information may be identified by the type of the application program, for example, if the traffic information is generated by performing a corresponding operation behavior on a certain interface in the wechat program, the traffic information is identified as the traffic information generated by the wechat program.
In the embodiment of the application, the flow information of the APP is generated by using a large number of random simulated user operation behaviors, and each control function of the APP is tested.
The embodiment of the application also provides a method for acquiring the flow of another application program, which comprises the following steps:
step S101, classifying, by a traffic acquisition device, an operation behavior to be detected according to a type of the operation behavior to be detected, where the operation behavior to be detected is an operation behavior that can be executed on an interface of each application program, and the operation behavior to be detected includes: click behavior, swipe behavior, or edit behavior.
Here, it is possible to analyze the operation behaviors that can be executed in most application programs at present by observation, and determine a relatively general operation behavior to be detected, such as a click behavior, a sliding behavior, an editing behavior, or the like. In the embodiment of the application, the operation behaviors to be detected can be classified according to the types of the operation behaviors to be detected through the current relatively universal combination, for example, by taking a sliding window state as an example, the clicking behaviors and the sliding behaviors can be executed on most of interfaces in the sliding window state, and then the clicking behaviors and the sliding behaviors can be classified into one class so as to be convenient for subsequent encapsulation and form a corresponding encapsulation operation behavior group.
Step S102, the traffic obtaining device packages the different types of operation behaviors to be detected respectively to obtain each interface package operation behavior group of each application program.
Based on step S101, if the clicking behavior and the sliding behavior can be executed on most of the interfaces in the sliding window state on the user interface, the clicking behavior and the sliding behavior can be classified into one type, and the clicking behavior and the sliding behavior are encapsulated to form an encapsulation operation behavior group corresponding to the sliding window state.
And step S103, the flow acquisition equipment determines the automation script of the corresponding interface according to the packaging operation behavior group.
Here, the traffic obtaining device may determine the automation script corresponding to the interface according to the package operation behavior group, and when the automation script is executed on the corresponding interface on the terminal, the operation behavior to be detected in the package operation behavior group may be automatically executed. Or taking the sliding window state as an example, when the automation script is executed, the terminal may automatically execute the click behavior and the sliding behavior in the package operation behavior group.
Through the steps S101 to S103, the generated flow is closer to the real flow generated by the user through abstract user behavior and a large amount of randomization operations. The method breaks away from the unique identification and traversal mode of the query control, and uses a scheme of classifying according to an input interface and automatically distributing the automatic script, so that the whole automatic clicking device has higher universality.
And step S104, the flow acquisition equipment calls an automatic script corresponding to the current interface according to the operation behavior identification on the current interface of the application program.
Step S105, the traffic obtaining device executes the automation script to generate traffic information by executing the operation to be detected in the package operation behavior group.
And step S106, the flow obtaining equipment identifies the flow information and outputs the identified flow information.
The embodiment of the application also provides a method for acquiring the flow of another application program, which comprises the following steps:
step S201, determining, by the traffic obtaining device, an instantiation object of a current interface according to an operation behavior identifier on the current interface of an application program.
Here, the operation behavior identifier is used to identify a corresponding control, and may be an icon or a text displayed on the interface, and all instantiated objects (controls) on the current interface may be determined according to the operation behavior identifier.
Step S202, the flow obtaining device calls an automation script corresponding to the current interface according to the attribute information of the instantiation object.
Here, if each interface of the application is regarded as an Activity, and the attribute information of all the controls on the Activity is set in the xml layout file of the Activity, the terminal may obtain the attribute information of all the controls on the Activity according to the operation behavior identifier, instead of separately searching the attribute information of each control according to the unique identifier information of each control, where Activity is one of the most basic modules in the Android system, and in an Android-based program, Activity generally represents a screen of a terminal screen, i.e., one interface, and in each Activity, a corresponding control may be set.
Through the steps S201 to S202, the step of "the terminal calls the automation script corresponding to the current interface according to the operation behavior identifier on the current interface of the application program" is executed, and the terminal can obtain the attribute information of all the controls on the interface according to the operation behavior identifier without respectively searching the attribute information of each control according to the unique identifier information of each control, so that the universality of the automation script can be realized.
Step S203, the traffic acquiring device executes the automation script to generate traffic information by executing the operation to be detected in the package operation behavior group.
Step S204, the traffic obtaining device identifies the traffic information and outputs the identified traffic information.
The embodiment of the application also provides a method for acquiring the flow of another application program, which comprises the following steps:
step S31, the flow obtaining device determines an instantiation object of the current interface according to the operation behavior identifier.
Step S32, if the current interface has no instantiation objects capable of performing editing activities and the number of instantiation objects capable of performing click activities does not exceed a first threshold, the flow acquiring device invokes an automation script corresponding to the current interface.
If the current interface has no instantiation objects capable of executing editing behaviors, the number of the instantiation objects capable of executing clicking behaviors does not exceed a first threshold value, and the characters on the current interface meet preset conditions, determining that the current interface is in a first state, and calling an automation script corresponding to the first state. For example, if the current interface has no instantiation objects capable of performing editing behaviors, the number of instantiation objects capable of performing clicking behaviors does not exceed a first threshold, and words such as "policy", "term", "agreement" and the like exist on the current interface, it is determined that the current interface is in the agreement term window state, and an automation script corresponding to the agreement term window state may be called.
If the current interface has no instantiation objects capable of executing editing behaviors, the number of the instantiation objects capable of executing clicking behaviors does not exceed a first threshold value, and no text information exists on the current interface, determining that the current interface is in a second state, and calling an automation script corresponding to the second state. The second state may be a window closing state, and correspondingly, an automation script corresponding to the window closing state is called.
Step S33, the traffic acquiring device executes the automation script to generate traffic information corresponding to the click behavior by executing the click behavior.
Based on the step S32, if the automation script corresponding to the agreement clause window status is called, when the automation script is executed, the click behavior in the package operation behavior group may be executed to generate the flow information corresponding to the click behavior.
Through the steps of S32 and S33, the state of the current interface of the application program can be determined according to the current state of the terminal, the corresponding automation script is called, and the humanoid operation behavior in the package operation behavior group is executed, so that the flow information close to reality can be obtained, and the labor cost can be reduced.
Step S34, the traffic acquiring device identifies the traffic information and outputs the identified traffic information.
The embodiment of the application also provides a method for acquiring the flow of another application program, which comprises the following steps:
step S401, the flow obtaining device determines an instantiation object of the current interface according to the operation behavior identifier.
Step S402, if the number of instantiation objects capable of executing editing behaviors of the current interface does not exceed a second threshold value and text information included in the instantiation objects meets a first preset condition, the flow acquisition device calls an automation script corresponding to the current interface.
Here, if the number of instantiated objects capable of executing editing activities of the current interface does not exceed a second threshold and text information included in the instantiated objects meets a preset condition, determining that the current interface is in a third state, and calling an automation script corresponding to the third state. For example, if the number of the editable controls of the current interface does not exceed the second threshold value, and a word like "login" or the like exists, it is determined that the current interface is in the login state. The login state can be divided into an account password login state and a verification code login state, and if the characters of 'mobile phone' and 'password' exist in the editable control, the login state is set as the account password login state; if the word of 'mobile phone' and 'verification code' exists in the editable control and the terminal is a mobile phone real machine (capable of receiving the verification code), the editable control is set to be in a verification code login state.
Step S403, the traffic obtaining device executes the automation script to generate traffic information corresponding to the editing behavior by executing the editing behavior.
Based on the step S402, if the automation script corresponding to the login status is called, when the automation script is executed, the editing behavior in the package operation behavior group may be executed to generate the traffic information corresponding to the editing behavior.
Through the steps S402 and S403, the state of the current interface of the application program can be determined according to the current state of the terminal, the corresponding automation script is called, and the human-like operation behavior in the package operation behavior group is executed, so that the flow information close to reality can be obtained, and the labor cost can be reduced.
Step S404, the traffic obtaining device identifies the traffic information and outputs the identified traffic information.
The embodiment of the application also provides a method for acquiring the flow of another application program, which comprises the following steps:
step S501, the flow obtaining device determines an instantiation object of the current interface according to the operation behavior identifier.
Step S502, if the number of times that the current interface can execute the click behavior does not exceed a third threshold value and the current interface comprises an instantiation object capable of executing the sliding behavior, the flow acquisition device calls an automation script corresponding to the current interface.
Here, if the current interface does not exceed a third threshold and includes an instantiation object capable of performing a sliding behavior, it is determined that the current interface is in a fourth state, and an automation script corresponding to the fourth state is called, where the fourth state may be a welcome sliding window state.
Step S503, the flow acquiring device executes the automation script to generate flow information corresponding to the click behavior and the sliding behavior by executing the click behavior and the sliding behavior.
Based on the step S502, if the automation script corresponding to the welcome sliding window state is called, when the automation script is executed, the sliding behavior in the package operation behavior group may be executed to generate the traffic information corresponding to the sliding behavior.
Through the steps S502 and S503, the state of the current interface of the application program can be determined according to the current state of the terminal, the corresponding automation script is called, the human-like operation behaviors in the package operation behavior group are executed, the flow information close to the reality can be obtained, and the labor cost can be reduced.
Step S504, the traffic obtaining device identifies the traffic information and outputs the identified traffic information.
In the embodiment of the application, information of a terminal interface is first obtained, that is, information of an instantiated object on the terminal interface is obtained, taking a terminal based on an Android system as an example, if the instantiated object is a control, a corresponding space can be determined from a control layout file (that is, an xml structure file), for example, a clickable control, a slidable control, and the like. Then analyzing the acquired information and storing the information into a user-defined Activity; and analyzing the control distribution in the Activity to obtain a current optimal behavior, calling an automatic script corresponding to the optimal behavior, returning the automatic script of the behavior to the terminal to complete the script operation, wherein the optimal behavior refers to the behavior generating flow, the Activity is one of the most basic modules in an Android system, in an Android-based program, the Activity generally represents a screen of a terminal screen, namely an interface, and in each Activity, a corresponding control can be set.
In the embodiment of the application, the method for analyzing the APP interface controls in the terminal does not involve analyzing which controls corresponding to the unique identifiers are clicked, so that the method has better universality. At present, the updating of the APP is very fast, but the types of the User Interface (UI) designs of the APP are different, the UI designs can be completely classified through the distribution of controls, and corresponding automatic scripts are generated according to the distribution of different controls.
Fig. 2 is a structural block diagram of an automated click process provided in an embodiment of the present application, and as shown in fig. 2, a control layout of each interface in an APP installed on an existing terminal 21 may be analyzed by observation, and a corresponding behavior set is generated according to characteristics of the control layout, where the behavior set 22 includes: the method comprises the following steps of ordinary behavior, random behavior, registration behavior, welcome page sliding, notification window closing, rule agreeing window, account number and password login behavior, verification code login behavior and the like. Corresponding automation scripts 23 are generated from the various behaviors in the behavior collection, each automation script corresponding to each type of behavior. When determining that the terminal has the APP to be detected, the corresponding automatic script can be called by analyzing the layout information on the current interface of the APP, and the automatic script is executed on the terminal.
In the embodiment of the application, a plurality of categories such as common click, sliding, text input, registration and login are abstracted from a behavior set. Empirically, most operational behaviors include: registering login operation, wherein each APP is basically completed by inputting a mobile phone number, a password or a verification code; characters are filled in the text box control; the pop-up window needs to be closed normally; basic click behavior. The behaviors can be abstracted and packaged and applied to different APPs.
Fig. 3 is a second flowchart of a method for acquiring traffic of an application program according to an embodiment of the present application, where as shown in fig. 3, the method includes:
step S301, the flow acquisition device starts an automatic click function according to a trigger instruction input by a user.
Step S302, the flow acquiring device starts an APP to be clicked.
Step S303, the flow acquiring device judges whether the current interface of the terminal belongs to the APP to be clicked.
If the current interface of the terminal belongs to the APP to be clicked, executing the step S304; and if the current interface of the terminal does not belong to the APP to be clicked, returning to execute the step S303.
Step S304, the flow acquiring device analyzes the instantiation object of the current interface.
Here, the instantiation object may be a control distributed on the current interface of the terminal.
Step S305, the flow acquiring device analyzes control distribution.
Step S306, the traffic acquiring device determines whether the control cannot be identified on the current interface.
If the control cannot be recognized, a random behavior is set, and step S311 is performed. If the control can be recognized, step S307 is performed.
Step S307, the traffic acquiring device determines whether the current interface has a pop-up window.
If there is a pop-up window, a processing window behavior is set, and step S311 is performed. If there is no pop-up window, step S308 is performed.
Step S308, the traffic acquiring device determines whether the current interface is a login page.
If the current interface is a login page, it is set to process the login behavior, and step S311 is performed. If not, step S309 is performed.
In step S309, the traffic acquiring device determines whether the current interface is a welcome page.
If the current interface is a welcome page, it is set to process welcome behavior, and step S311 is performed. If not, step S310 is performed.
Step S310, the traffic acquiring device sets the operation behavior executed by the current page setting as a normal behavior.
Step S311, the flow acquiring device invokes a corresponding automation script.
In step S312, the flow acquiring device executes the automation script. If the APP dodges and retreats, the APP can be restarted by the flow acquiring equipment, and behavior operation is continued.
In the embodiment of the application, the test can be performed under the UIAutomator frame, and since the UIAutomator frame includes a Device object, the object can acquire various useful information of the current interface of the terminal, including: the clickable control information, the slidable control information, the editable control information and the like, such as the number and distribution of the clickable controls, the slidable controls and the editable controls, can be used as the subsequent division state. The dump _ hierarchy () method may directly obtain xml information of Activity of the current APP interface, and fig. 4 shows a source code for obtaining xml information of a corresponding control, for example.
In the embodiment of the application, after the Activity of the APP is digitized, according to the UI design of most of the current applications, the Activities can be subjected to state classification in a manual rule mode, and are divided into a plurality of categories, and corresponding action automation scripts are obtained respectively. Such as random behavior, processing window behavior, login behavior, sliding welcome window behavior, and normal behavior. The detailed information of each behavior is as follows:
(1) random behavior: if the Activity object is resolved incorrectly, or no clickable, slideable, and editable control is found, then a random behavior state is set.
(2) Agreement terms window action: if the number of editable objects does not exceed the threshold Th1 and the characters of policy, clause and agreement exist in xml, the Activity object is set to be in the state of agreement. As shown in fig. 5, if the text portion in the bullet box 501 on the interface includes "clause", it can be determined that the interface is in the state of agreement regulation.
(3) A window closing behavior: if the editable objects do not exist in the Activity objects and the number of the clickable objects does not exceed the threshold Th1, the text typeface of each button in the notification window is checked, and if the typeface does not exist in the maintained list of clickable words, the state of closing the window is set. As shown in fig. 6A and 6B, there are no editable objects and the number of clickable objects in fig. 6A is 2, and the popup frame 601a does not include the words "policy", "term", and "agreement", so that it can be determined that the interface is in a closed window state; in fig. 6B, there are no editable objects and the number of clickable objects is 1, and the words "policy", "term" and "agreement" are not included in the pop-up box 601B, it can be determined that the interface is in a closed window state.
(4) Login behavior: if the number of editable controls in the Activity object does not exceed the threshold Th2 and similar characters such as "login" exist, the Activity object is set to be in a login behavior state. The login behavior state is divided into an account password login state and an authentication code login state: if the words of "mobile phone" and "password" exist in the editable control, the editable control is set to be in the account password login state, as shown in fig. 7, the interface 701 includes the words of "mobile phone" and "password", which are in the account password login state; if the word of 'mobile phone' and 'verification code' exists in the editable control and the terminal is a mobile phone real machine (capable of receiving the verification code), the editable control is set to be in a verification code login state. As shown in fig. 8, the interface 801 includes words of "mobile phone" and "verification code" as the login status of the account password.
(5) Sliding welcome window behavior: if the number of clicks in the Activity object in the APP does not exceed the threshold Th3, the number of clickable controls does not exceed the threshold Th4, and a slidable control exists, the Activity object is set to be in a welcome window processing state, as shown in fig. 9A, 9B, and 9C, the interface in fig. 9A includes a slidable control 901 a; the interface in fig. 9B includes a slider control 901B; the interface of fig. 9C includes a clickable control slider control 901C, and the interface of fig. 9A, 9B, and 9C is determined to be in the process welcome window state.
(6) General behavior: and if the judgment conditions are not met, setting the state to be in a common behavior state.
In the embodiment of the application, the automatic clicking system calls the corresponding automatic script according to the set state and feeds the corresponding automatic script back to the terminal for execution. According to the scheme, the basic behavior actions of the user are abstracted to form the behavior groups of each state, so that each interface of each application can obtain corresponding behaviors, and the flow is continuously and circularly generated until the termination condition is met. The behavior scheme corresponding to each state is as follows:
(1) random behavior: generating a random number, and performing a sliding action from a random coordinate point (x1, y1) on the screen to a random point (x2, y2) if the random number is greater than a threshold Th 5; otherwise, randomly clicking a point (x3, y3) on the terminal screen. And after the random behavior is finished, generating a random number, and returning to the previous interface if the random number is greater than a threshold Th6 to prevent the random number from entering an excessively deep APP interface and not returning to the main page. If the APP is in a stuck state at the moment, the current interface can be quitted through the operation of sliding or clicking on the current page.
(2) Agreement terms window action: looking at the text typeface of each button in the notification window, if the typeface belongs to an already maintained list of words that represent "consent", it is retained. And randomly clicking one button in the reserved clickable buttons.
(3) A window closing behavior: and looking at the text typeface of each button in the notification window, and filtering out the text typeface if the typeface does not exist in a maintained list of clickable words. And randomly clicking one button for the rest clickable buttons.
(4) Login behavior: the login behavior is divided into common account password login and verification code login.
A) And account password login: and pre-storing login information including a registered mobile phone number and a login password. Filling in the corresponding input text box, and clicking a 'login' button.
B) And (3) logging in the verification code: if the mobile phone can receive the short message, the function is started. The automatic script automatically fills in the mobile phone number and clicks the button for obtaining the verification code. And the automatic script can execute the circulation of preset times, search the character information on the notification interface, inquire the corresponding verification code information through a preset rule, and automatically input the verification code information into a text box to finish the login operation of the verification code. For example, a loop is executed three times at the same time, character strings in a mobile phone notification bar are searched, a required 4-8-bit verification code is searched in a regularized matching mode and is filled in an input box of the verification code, and the verification code login operation is completed.
(5) Sliding welcome window behavior: most welcome pages slide horizontally to the far right and then click the "enter" button. The universal script is also completed using this flow.
(6) General behavior: the following behavior was randomly selected.
A) If a slideable control is present, there is a certain probability that a horizontal or vertical sliding action is performed.
B) If an editable control exists, the characters are randomly filled in the input box with a certain probability. And clicking if the words are 'sending' or 'searching'.
C) And if the controls can be clicked, randomly selecting one to click. Here, it is determined whether the characters of the clicked control are in the blacklist characters, such as "exit", "update", "download", and the like, without clicking.
In the embodiment of the application, an automatic script does not need to be compiled for each APP, only one set of universal script needs to be maintained, the requirement can be met, behavior operation of a large number of APPs in the market is completed, and a large number of pieces of tagged flow information are generated. Aiming at an input interface of a terminal, an optimal automatic script can be configured for the current interface through an analysis and analysis mode in the embodiment of the application, the automatic script is divided into a plurality of types, the functions comprise common clicking, registration and login, pop-up window closing and the like, and a large number of UI design interfaces of the current APP can be covered.
Based on the foregoing embodiments, the embodiments of the present application provide an apparatus for acquiring traffic of an application, where each unit included in the apparatus may be implemented by a processor in a device for acquiring traffic of an application; of course, may be implemented by logic circuits; in implementation, the processor may be a Central Processing Unit (CPU), a Microprocessor (MPU), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), or the like.
Fig. 10 is a schematic structural diagram of an apparatus for acquiring a flow rate of an application according to an embodiment of the present application, where the apparatus 1000 includes:
the calling unit 1001 is configured to call an automation script corresponding to a current interface according to an operation behavior identifier on the current interface of an application program;
an execution unit 1002 configured to execute the automation script to generate flow information by executing an operation to be detected in the packaged operation behavior group;
an identifying unit 1003 configured to identify the traffic information and output the identified traffic information.
In other embodiments, the apparatus further comprises: the classification unit is configured to classify the operation behavior to be detected according to the type of the operation behavior to be detected, where the operation behavior to be detected is an operation behavior that can be executed on an interface of each application program, and includes: click behavior, slide behavior, or edit behavior; the packaging unit is configured to package different types of operation behaviors to be detected respectively to obtain each interface packaging operation behavior group of each application program; and the determining unit is configured to determine the automation script of the corresponding interface according to the packaging operation behavior group.
In other embodiments, the invoking unit is further configured to: determining an instantiation object of the current interface according to the operation behavior identifier; and calling an automation script corresponding to the current interface according to the attribute information of the instantiation object.
In other embodiments, the identification unit is further configured to: and acquiring the flow information generated by the current interface, identifying the flow information according to the type of the application program, and outputting the identified flow information.
In other embodiments, the invoking unit is further configured to: if the current interface has no instantiation objects capable of executing editing behaviors and the number of the instantiation objects capable of executing clicking behaviors does not exceed a first threshold value, calling an automation script corresponding to the current interface;
correspondingly, the execution unit is further configured to: and executing the automatic script to generate flow information corresponding to the click behavior by executing the click behavior.
In other embodiments, the invoking unit is further configured to: if the number of the instantiation objects capable of executing the editing behaviors of the current interface does not exceed a second threshold value and the text information included by the instantiation objects meets a first preset condition, calling an automation script corresponding to the current interface;
correspondingly, the execution unit is further configured to: and executing the automation script to generate flow information corresponding to the editing behavior by executing the editing behavior.
In other embodiments, the invoking unit is further configured to: if the number of times that the current interface can execute the click behavior does not exceed a third threshold value and the current interface comprises an instantiation object capable of executing the sliding behavior, calling an automation script corresponding to the current interface;
correspondingly, the execution unit is further configured to: and executing the automatic script to generate flow information corresponding to the click behavior and the sliding behavior by executing the click behavior and the sliding behavior.
In the embodiment of the present application, if the method for acquiring the traffic of the application program is implemented in the form of a software functional module and is sold or used as a standalone product, the method may also be stored in a computer-readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a server to execute all or part of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read Only Memory (ROM), a magnetic disk, or an optical disk. Thus, embodiments of the present application are not limited to any specific combination of hardware and software.
Correspondingly, the embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the steps in the method for acquiring the traffic of the application program provided in the above embodiment.
Here, it should be noted that: the above description of the storage medium and device embodiments is similar to the description of the method embodiments above, with similar advantageous effects as the method embodiments. For technical details not disclosed in the embodiments of the storage medium and apparatus of the present application, reference is made to the description of the embodiments of the method of the present application for understanding.
It should be noted that fig. 11 is a schematic structural diagram of an apparatus for acquiring traffic of an application program according to an embodiment of the present application, and as shown in fig. 11, the apparatus 1100 at least includes: a processor 1101, a communication interface 1102, and a memory 1103, wherein:
the processor 1101 generally controls the overall operation of the device 1100.
The communication interface 1102 may enable the device to communicate with other devices over a network.
The memory 1103 is configured to store instructions and applications executable by the processor 1101, and may also buffer data (e.g., image data, audio data, voice communication data, and video communication data) to be processed or already processed by the processor 1101 and modules in the device 1100, and may be implemented by a flash memory (F L ASH) or a Random Access Memory (RAM).
Of course, the apparatus in the embodiment of the present application may have other similar protocol interaction implementation cases, and those skilled in the art can make various corresponding changes and modifications according to the embodiment of the present application without departing from the spirit and the spirit of the present application, but these corresponding changes and modifications should fall within the scope of the claims appended to the method of the present application.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of a hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, 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 specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present application. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application. The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described device embodiments are merely illustrative, for example, the division of the modules is only one logical functional division, and there may be other division ways in actual implementation, such as: multiple modules or components may be combined, or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the coupling, direct coupling or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection between the devices or modules may be electrical, mechanical or other.
The modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical modules; the network module can be located in one place or distributed on a plurality of network modules; some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
The above description is only for the embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. A method for acquiring traffic of an application program, the method comprising:
calling an automatic script corresponding to a current interface according to an operation behavior identifier on the current interface of an application program;
executing the automation script to generate flow information by executing the operation behavior to be detected in the packaging operation behavior group;
and identifying the flow information and outputting the identified flow information.
2. The method of claim 1, further comprising:
classifying the operation behaviors to be detected according to the types of the operation behaviors to be detected, wherein the operation behaviors to be detected are operation behaviors which can be executed on interfaces of all application programs, and the method comprises the following steps: click behavior, slide behavior, or edit behavior;
respectively encapsulating different types of operation behaviors to be detected to obtain each interface encapsulation operation behavior group of each application program;
and determining an automation script of the corresponding interface according to the packaging operation behavior group.
3. The method of claim 1, wherein invoking the automation script corresponding to the current interface according to the operation behavior identifier on the current interface of the application program comprises:
determining an instantiation object of a current interface according to an operation behavior identifier on the current interface of an application program;
and calling an automation script corresponding to the current interface according to the attribute information of the instantiation object.
4. The method of claim 1, wherein identifying the traffic information and outputting the identified traffic information comprises:
and acquiring the flow information generated by the current interface, identifying the flow information according to the type of the application program, and outputting the identified flow information.
5. The method of claim 3, wherein the invoking an automation script corresponding to the current interface according to the attribute information of the instantiation object comprises: if the current interface has no instantiation objects capable of executing editing behaviors and the number of the instantiation objects capable of executing clicking behaviors does not exceed a first threshold value, calling an automation script corresponding to the current interface;
correspondingly, executing the automation script to generate flow information by executing the operation behavior to be detected in the packaged operation behavior group, including: and executing the automatic script to generate flow information corresponding to the click behavior by executing the click behavior.
6. The method of claim 3, wherein the invoking an automation script corresponding to the current interface according to the attribute information of the instantiation object comprises: if the number of the instantiation objects capable of executing the editing behaviors of the current interface does not exceed a second threshold value and the text information included by the instantiation objects meets a first preset condition, calling an automation script corresponding to the current interface;
correspondingly, executing the automation script to generate flow information by executing the operation behavior to be detected in the packaged operation behavior group, including: and executing the automation script to generate flow information corresponding to the editing behavior by executing the editing behavior.
7. The method of claim 3, wherein the invoking an automation script corresponding to the current interface according to the attribute information of the instantiation object comprises: if the number of times that the current interface can execute the click behavior does not exceed a third threshold value and the current interface comprises an instantiation object capable of executing the sliding behavior, calling an automation script corresponding to the current interface;
correspondingly, executing the automation script to generate flow information by executing the operation behavior to be detected in the packaged operation behavior group, including: and executing the automatic script to generate flow information corresponding to the click behavior and the sliding behavior by executing the click behavior and the sliding behavior.
8. An apparatus for acquiring traffic of an application, the apparatus comprising:
the calling unit is configured to call the automatic script corresponding to the current interface according to the operation behavior identifier on the current interface of the application program;
the execution unit is configured to execute the automation script so as to generate flow information by executing the operation behavior to be detected in the packaged operation behavior group;
and the identification unit is configured to identify the traffic information and output the identified traffic information.
9. An apparatus for acquiring traffic of an application, the apparatus comprising at least: a processor and a storage medium configured to store executable instructions, wherein:
the processor is configured to execute stored executable instructions configured to perform the method of obtaining traffic of an application program as provided in any of the preceding claims 1 to 7.
10. A computer-readable storage medium, wherein computer-executable instructions are stored in the computer-readable storage medium, and the computer-executable instructions are configured to execute the method for acquiring the traffic of the application program provided in any one of the above claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910054892.6A CN111459774B (en) | 2019-01-21 | 2019-01-21 | Method, device, equipment and storage medium for acquiring flow of application program |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910054892.6A CN111459774B (en) | 2019-01-21 | 2019-01-21 | Method, device, equipment and storage medium for acquiring flow of application program |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111459774A true CN111459774A (en) | 2020-07-28 |
| CN111459774B CN111459774B (en) | 2023-05-12 |
Family
ID=71682137
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910054892.6A Active CN111459774B (en) | 2019-01-21 | 2019-01-21 | Method, device, equipment and storage medium for acquiring flow of application program |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111459774B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114025333A (en) * | 2021-11-01 | 2022-02-08 | 中国电信股份有限公司甘肃分公司 | Flow configuration method, device and storage medium |
| CN114051061A (en) * | 2021-11-09 | 2022-02-15 | 武汉虹旭信息技术有限责任公司 | Internet application protocol analysis method and system |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104978266A (en) * | 2014-04-11 | 2015-10-14 | 腾讯科技（深圳）有限公司 | Application test method and device |
| CN105553772A (en) * | 2015-12-18 | 2016-05-04 | 小米科技有限责任公司 | Flow monitoring method and device |
| WO2016146004A1 (en) * | 2015-03-19 | 2016-09-22 | 阿里巴巴集团控股有限公司 | Information lookup and identification method and device |
| US20160308749A1 (en) * | 2015-04-17 | 2016-10-20 | Somansa Co., Ltd. | Test automation system and method for detecting change in signature of internet application traffic protocol |
| US20170060368A1 (en) * | 2015-09-02 | 2017-03-02 | International Business Machines Corporation | Computer-vision based execution of graphical user interface (gui) application actions |
| CN106649103A (en) * | 2016-11-25 | 2017-05-10 | 深圳大学 | Android application program automatically black box testing method and system |
| CN107707369A (en) * | 2017-09-30 | 2018-02-16 | 广东欧珀移动通信有限公司 | The method and apparatus of flow order management, computer equipment, readable storage medium storing program for executing |
| JP2018527668A (en) * | 2015-07-27 | 2018-09-20 | アリババ グループ ホウルディング リミテッド | Method and system for limiting data traffic |
-
2019
- 2019-01-21 CN CN201910054892.6A patent/CN111459774B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104978266A (en) * | 2014-04-11 | 2015-10-14 | 腾讯科技（深圳）有限公司 | Application test method and device |
| WO2016146004A1 (en) * | 2015-03-19 | 2016-09-22 | 阿里巴巴集团控股有限公司 | Information lookup and identification method and device |
| US20160308749A1 (en) * | 2015-04-17 | 2016-10-20 | Somansa Co., Ltd. | Test automation system and method for detecting change in signature of internet application traffic protocol |
| JP2018527668A (en) * | 2015-07-27 | 2018-09-20 | アリババ グループ ホウルディング リミテッド | Method and system for limiting data traffic |
| US20170060368A1 (en) * | 2015-09-02 | 2017-03-02 | International Business Machines Corporation | Computer-vision based execution of graphical user interface (gui) application actions |
| CN105553772A (en) * | 2015-12-18 | 2016-05-04 | 小米科技有限责任公司 | Flow monitoring method and device |
| CN106649103A (en) * | 2016-11-25 | 2017-05-10 | 深圳大学 | Android application program automatically black box testing method and system |
| CN107707369A (en) * | 2017-09-30 | 2018-02-16 | 广东欧珀移动通信有限公司 | The method and apparatus of flow order management, computer equipment, readable storage medium storing program for executing |
Non-Patent Citations (2)
| Title |
|---|
| 张胜桥;尹青;常瑞;朱晓东;: "基于APK的Android应用程序GUI遍历自动化方法" * |
| 郑宇;白凡凡;: "Android多媒体通信终端自动化测试工具设计与实现" * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114025333A (en) * | 2021-11-01 | 2022-02-08 | 中国电信股份有限公司甘肃分公司 | Flow configuration method, device and storage medium |
| CN114051061A (en) * | 2021-11-09 | 2022-02-15 | 武汉虹旭信息技术有限责任公司 | Internet application protocol analysis method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111459774B (en) | 2023-05-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108334781B (en) | Virus detection method, device, computer readable storage medium and computer equipment | |
| CN110737899B (en) | Intelligent contract security vulnerability detection method based on machine learning | |
| CN105094783B (en) | method and device for testing stability of android application | |
| CN109995601B (en) | Network traffic identification method and device | |
| CN107315810B (en) | Internet of things equipment behavior portrait method | |
| CN107480053B (en) | Software test data generation method and device | |
| US9720687B2 (en) | Validating and maintaining respective validation status of software applications and manufacturing systems and processes | |
| CN108845930B (en) | Interface operation test method and device, storage medium and electronic device | |
| CN109479061A (en) | Compliance violates detection | |
| CN106776338B (en) | Test method, test device and server | |
| CN109508298B (en) | Graphical script test method and system | |
| CN110941467A (en) | Data processing method, device and system | |
| CN107894889A (en) | Bury point methods, equipment and computer-readable recording medium | |
| CN103839005A (en) | Malware detection method and malware detection system of mobile operating system | |
| CN105357204B (en) | Method and device for generating terminal identification information | |
| CN110162457A (en) | Test method, device, equipment and the storage medium of user interface | |
| CN110381026B (en) | Business service packaging and accessing system, method and device for rich client | |
| CN105653946A (en) | Android malicious behavior detection system based on combined event behavior triggering and detection method of Android malicious behavior detection system | |
| CN113778864A (en) | Test case generation method and device, electronic equipment and storage medium | |
| CN109902487B (en) | Android application malicious property detection method based on application behaviors | |
| CN111459774B (en) | Method, device, equipment and storage medium for acquiring flow of application program | |
| CN115757100A (en) | Automated testing framework facing user interface, method, equipment and medium | |
| CN108334441A (en) | A kind of automated testing method and system of Software Development Kit | |
| CN110888628A (en) | Method, device, equipment and storage medium for generating control tool | |
| CN108090355B (en) | APK automatic triggering tool |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |