CN103353858A - Automatic testing method and device based on action touch simulation - Google Patents

Abstract

The present invention provides an automatic test method and device based on motion touch simulation. After generating touch events conforming to the test state and combining them into a touch event sequence of touch actions, the touch event sequence is sent to the event forwarding object of the system under test. The event forwarding object forwards the touch events in the sequence. The method and device provided by the invention can execute the Monkey test without being connected to a PC, saving resources; in addition, the dependence on the Instruments tool memory is eliminated, and the test quality is improved.

Description

An automated testing method and device based on motion touch simulation

【Technical field】

The invention relates to the technical field of computer testing, in particular to an automatic testing method and device based on motion touch simulation.

【Background technique】

The Monkey test uses the Monkey program to simulate user operations such as clicking on the screen, sliding, and pressing keys to stress test the programs on the device. At present, the Monkey automated testing of iOS products needs to connect to the Instruments tool on the PC side (Mac machine), and then start the javascript script to execute the Monkey automated testing. This approach has the following drawbacks:

1) The Monkey test must be connected to a Mac machine, which takes up additional resources.

2) The memory requirements for the Instruments tool are high. If the memory is insufficient, the Monkey test may stop, and the test quality cannot be guaranteed.

【Content of invention】

In view of this, the present invention provides an automatic test method and device based on motion touch simulation, so as to save resources and improve test quality.

The specific technical scheme is as follows:

An automated testing method based on motion touch simulation, the method comprising:

S1. Generate a touch event conforming to the test state and combine it into a touch event sequence of a touch action;

S2. Send the touch event sequence to the event forwarding object of the system under test, and the event forwarding object forwards the touch events in the sequence.

According to a preferred embodiment of the present invention, the step S1 specifically includes:

S11. Obtain touch action information from the test case;

S12. Calculate the touch trajectory according to the acquired touch action information;

S13. According to the direction of the touch action, insert a touch event corresponding to the touch action type at the corresponding position in the touch track every preset time interval to obtain a touch event sequence.

According to a preferred embodiment of the present invention, the touch action information is described by a multivariate parameter set, and the multivariate parameter set includes: the position, speed, acceleration, duration and number of clicks of the start point and the end point.

According to a preferred embodiment of the present invention, if the type of the touch action is N-point touch, the touch action information is described using N multivariate parameter groups, and N touch trajectories are obtained in the step S12. There are N coordinate points at the insertion position of each touch event in S13, where N is a positive integer.

According to a preferred embodiment of the present invention, when inserting a touch event corresponding to the type of touch action at this position, a touch event in a pressed state is inserted at the start point, a touch event in a pop-up state is inserted at the end point, and a touch event in a pop-up state is inserted at the start point. Insert the touch event of the moving state at each position between and the end point.

According to a preferred embodiment of the present invention, if the system under test is an ISO system, the touch event is UIEvent, the event forwarding object is UIApplication, and the UIApplication distributes the UIEvent in the UIEvent sequence to the target view;

If the system under test is an Android system, then the touch event is a MotionEvent, and the event forwarding object is an Instrumentation, and the Instrumentation forwards the MotionEvent in the MotionEvent sequence to the Android system for the Android system to broadcast to the monitoring Application .

An automatic testing device based on motion touch simulation, the device comprising:

An event generation unit, configured to generate a touch event conforming to the test state and combine it into a touch event sequence of a touch action;

The event sending unit is configured to send the touch event sequence to the event forwarding object of the system under test, and the event forwarding object forwards the touch events in the sequence.

According to a preferred embodiment of the present invention, the event generating unit specifically includes:

The information acquisition subunit is used to acquire touch action information from the test case;

A trajectory calculation subunit, configured to calculate a touch trajectory according to the touch action information;

The event insertion subunit is configured to insert a touch event corresponding to the type of touch action at the corresponding position in the touch track at preset time intervals according to the direction of the touch action, to obtain a sequence of touch events.

According to a preferred embodiment of the present invention, the touch action information is described by a multivariate parameter set, and the multivariate parameter set includes: the position, speed, acceleration, duration and number of clicks of the start point and the end point.

According to a preferred embodiment of the present invention, if the type of the touch action is N-point touch, the touch action information is described using N multivariate parameter groups, the trajectory calculation subunit obtains N touch trajectories, and the event insertion When the subunit inserts a touch event, there are N coordinate points at the insertion position of each touch event, where N is a positive integer.

According to a preferred embodiment of the present invention, when the event insertion subunit inserts a touch event corresponding to the touch action type at this position, a touch event in a pressed state is inserted at the start point position, and a touch event in a pop-up state is inserted at the end point position. Touch events, insert moving state touch events at each position between the start point and the end point.

According to a preferred embodiment of the present invention, if the system under test is an ISO system, the touch event is UIEvent, the event forwarding object is UIApplication, and the UIApplication distributes the UIEvent in the UIEvent sequence to the target view;

If the system under test is an Android system, then the touch event is a MotionEvent, and the event forwarding object is an Instrumentation, and the Instrumentation forwards the MotionEvent in the MotionEvent sequence to the Android system for the Android system to broadcast to the monitoring Application .

It can be seen from the above technical solutions that the method and device provided by the present invention can execute the Monkey test without connecting to the PC, which saves resources; in addition, it gets rid of the dependence on the Instruments tool memory and improves the test quality.

【Description of drawings】

FIG. 1 is a flowchart of an automated testing method provided by Embodiment 1 of the present invention;

FIG. 2 is a schematic diagram of a touch track and a UIEvent for sliding provided by Embodiment 1 of the present invention;

FIG. 3 is a schematic diagram of a touch track and a UIEvent for two-finger squeeze provided by Embodiment 1 of the present invention;

FIG. 4 is a structural diagram of an automated testing device provided by Embodiment 2 of the present invention.

【Detailed ways】

In order to make the object, technical solution and advantages of the present invention clearer, the present invention will be described in detail below in conjunction with the accompanying drawings and specific embodiments.

Since the basic process of Monkey automated testing is to randomly call the function interface related to screen processing to trigger various screen touch actions to simulate the user's screen touch behavior, and the screen touch action of iOS is essentially composed of UIEvent (user interface event), That is, a touch action corresponds to a UIEvent sequence. When the user touches the screen, iOS generates the corresponding UIEvent; then the UIAplication (user interface application) object distributes the received UIEvent sequence; finally, the distributed target view performs touch logic processing on the UIEvent. Based on the above principles, the core idea of the present invention is to combine the UIEvents conforming to the test state into a UIEvent sequence of touch actions, send the UIEvent sequence to the UIAplication object, and the UIAplication object performs distribution processing. The method provided by the present invention is described in detail below through examples.

Embodiment one,

Fig. 1 is a flow chart of the method provided by Embodiment 1 of the present invention. In this embodiment, based on the case (test case) provided by the user, the user's test behavior is simulated for automated testing. As shown in Fig. 1, the method includes the following steps:

Step 101: Obtain touch action information from the case.

The case usually contains information such as the object to be tested, the test environment, etc. Since the test in the embodiment of the present invention is a Monkey test, the case also contains touch action information, which is the subsequent touch action that needs to be simulated. In view of the touch Actions may include multiple types, such as click, slide, multi-touch, etc., but for event types, there are mainly two dimensions. The first dimension is the number of clicks, that is, click, double-click, multi-touch, etc. Click, etc., the second dimension is the number of touch points, that is, single point, two points, multi-point, etc. Here, each type of touch action can be described by a multivariate parameter set. The multivariate parameter group includes: the position of the start point and the end point, velocity, acceleration, duration and number of clicks. Here are a few examples:

Suppose you want to test to click on the screen coordinates (100,100) for 1.5s, then the touch action information contained in the case can be the following multivariate parameter group:

<(100,100),(100,100),0,0,1.5,1>

Suppose you want to test sliding from screen coordinates (100,100) to (150,200) for 2 seconds, and the sliding speed is 10m/s, then the touch action information contained in the case can be the following multivariate parameter group:

<(100,100), (150,200), 10, 0, 2, 1>

For multi-touch, suppose you want to test two-finger squeeze, from screen coordinates (100,100) and (180,100) to screen coordinates (140,120) and (160,120), there will be two motion tracks, then the touch action contained in the case The information can be two multivariate parameter groups as follows:

<(100,100),(140,120),10,0,2,1>

<(180,100), (160,120), 10, 0, 2, 1>

Step 102: Calculate the touch track according to the acquired touch action information, insert a UIEvent corresponding to the touch action type at the corresponding position in the touch track every preset time interval according to the touch action direction, and obtain a UIEvent sequence.

其中，Y为动作结束点的位置，X为动作起始点的位置，

为速度向量，为加速度向量，t为时间。When calculating the touch trajectory, the traditional mathematical method is used, namely

Among them, Y is the position of the end point of the action, X is the position of the starting point of the action,

is the velocity vector, is the acceleration vector, and t is the time.

When inserting a UIEvent, three factors are mainly required, one is the position of the insertion point, the other is the type of touch action, and the third is the action state. Since the insertion of the UIEvent is inserted at a preset time interval, the position of the inserted time point in the touch track can be determined (that is, substituted into the above formula of the touch track). The type of touch action has been described above and is mainly reflected in two dimensions: the number of clicks and the number of touch points. The number of clicks can be directly obtained from the multivariate parameter group in the case, and the number of touch points corresponds to the number of multivariate parameter groups in the case. Action states mainly include three types: pressed state, moving state and popping state. When inserting a UIEvent, the action state at the starting point is the pressed state, the action state at the end point is the pop-up state, and the action state of each insertion point between the starting point and the end point in the touch track is the moving state.

The following are examples of sliding and two-finger squeeze respectively:

Sliding action: From the case, it can be learned that the touch action to test sliding from point A to point B is to be tested. After calculating the touch track according to the touch action information in the case, insert it in the touch track at a fixed time interval of 0.05s in chronological order UIEvent, specifically: calculate the position of the insertion point at every 0.05s time point, that is, determine the position of each time point in the touch track at 0, 0.05s, 0.1s, 0.15s and so on, according to the touch action in the case The information shows that the action type is single-click (the number of clicks is 1, and the action track is also 1). Insert a single-click UIEvent in the pressed state at point A, and insert a single-click popup at point B. Insert the UIEvent in the starting state, and insert the UIEvent in the single-click moving state at each insertion point between A and B, so as to obtain a sequence of UIEvents arranged in chronological order. In this sequence, the position of the i-th UIEvent (x _i , y _i )for:

$<span\; class="notranslate">\; (</span>{\mathrm{<span\; class="notranslate">\; x</span>}}_{\mathrm{<span\; class="notranslate">\; i</span>}}<span\; class="notranslate">\; ,</span>{\mathrm{<span\; class="notranslate">\; the\; y</span>}}_{\mathrm{<span\; class="notranslate">\; i</span>}}<span\; class="notranslate">\; )</span><span\; class="notranslate">\; =</span><span\; class="notranslate">\; (</span>{\mathrm{<span\; class="notranslate">\; x</span>}}_{\mathrm{<span\; class="notranslate">\; 0</span>}}<span\; class="notranslate">\; ,</span>{\mathrm{<span\; class="notranslate">\; the\; y</span>}}_{\mathrm{<span\; class="notranslate">\; 0</span>}}<span\; class="notranslate">\; )</span><span\; class="notranslate">\; +</span>\stackrel{<span\; class="notranslate">\; \&Right\; Arrow;</span>}{\mathrm{<span\; class="notranslate">\; v</span>}}<span\; class="notranslate">\; *</span><span\; class="notranslate">\; (</span>\mathrm{<span\; class="notranslate">\; i</span>}<span\; class="notranslate">\; -</span>\mathrm{<span\; class="notranslate">\; 1</span>}<span\; class="notranslate">\; )</span>\mathrm{<span\; class="notranslate">\; \&Delta;t</span>}<span\; class="notranslate">\; ,</span>$

Wherein (x ₀ , y ₀ ) is the coordinate of the starting point A of the action, Δt is the time interval for inserting the UIEvent, and the schematic diagram of the generated UIEvent is shown in FIG. 2 .

Two-finger squeeze action:

It can be known from the case that there are two sets of multivariate parameter groups to test the two-finger squeeze action. Therefore, the touch trajectories are calculated for the two sets of multivariate parameter groups, and two touch trajectories are obtained. As shown in Figure 3, two The touch tracks are from A1 to B1 and from A2 to B2 respectively. Insert UIEvent in the touch track at a fixed time interval of 0.05s in chronological order, that is, determine the position of each time point in the touch track at 0, 0.05s, 0.1s, 0.15s and so on, according to the touch action information in the case It can be seen that its action type belongs to multi-click (the number of clicks is 1, and the action track is also 2). Each UIEvent corresponds to two insertion point positions. Insert a UIEvent in the state of double-click pressing at A1 and A2, and insert a UIEvent in the pressed state at B1. Insert a UIEvent in the double-click pop-up state at point B2, and insert a UIEvent in the double-click moving state at each insertion point in the middle. In order to get the UIEvent sequence arranged in chronological order. The positions (x1 _i , y1 _i ) and (x2 _i , y2 _i ) of the i-th UIEvent in the sequence are:

$<span\; class="notranslate">\; (</span>{\mathrm{<span\; class="notranslate">\; x</span>}\mathrm{<span\; class="notranslate">\; 1</span>}}_{\mathrm{<span\; class="notranslate">\; i</span>}}<span\; class="notranslate">\; ,</span>{\mathrm{<span\; class="notranslate">\; the\; y</span>}\mathrm{<span\; class="notranslate">\; 1</span>}}_{\mathrm{<span\; class="notranslate">\; i</span>}}<span\; class="notranslate">\; )</span><span\; class="notranslate">\; =</span><span\; class="notranslate">\; (</span>{\mathrm{<span\; class="notranslate">\; x</span>}\mathrm{<span\; class="notranslate">\; 1</span>}}_{\mathrm{<span\; class="notranslate">\; 0</span>}}<span\; class="notranslate">\; ,</span>{\mathrm{<span\; class="notranslate">\; the\; <figure-callout\; id="1"\; label="y"\; filenames="HDA00003309450000021.png"\; state="\{\{state\}\}">y</figure-callout></span>}\mathrm{<span\; class="notranslate">\; 1</span>}}_{\mathrm{<span\; class="notranslate">\; 0</span>}}<span\; class="notranslate">\; )</span><span\; class="notranslate">\; +</span>{\stackrel{<span\; class="notranslate">\; \&Right\; Arrow;</span>}{\mathrm{<span\; class="notranslate">\; v</span>}}}_{\mathrm{<span\; class="notranslate">\; 1</span>}}<span\; class="notranslate">\; *</span><span\; class="notranslate">\; (</span>\mathrm{<span\; class="notranslate">\; i</span>}<span\; class="notranslate">\; -</span>\mathrm{<span\; class="notranslate">\; 1</span>}<span\; class="notranslate">\; )</span>\mathrm{<span\; class="notranslate">\; \&Delta;t</span>}$

$<span\; class="notranslate">\; (</span>{\mathrm{<span\; class="notranslate">\; x</span>}\mathrm{<span\; class="notranslate">\; 2</span>}}_{\mathrm{<span\; class="notranslate">\; i</span>}}<span\; class="notranslate">\; ,</span>{\mathrm{<span\; class="notranslate">\; the\; y</span>}\mathrm{<span\; class="notranslate">\; 2</span>}}_{\mathrm{<span\; class="notranslate">\; i</span>}}<span\; class="notranslate">\; )</span><span\; class="notranslate">\; =</span><span\; class="notranslate">\; (</span>{\mathrm{<span\; class="notranslate">\; x</span>}\mathrm{<span\; class="notranslate">\; 2</span>}}_{\mathrm{<span\; class="notranslate">\; 0</span>}}<span\; class="notranslate">\; ,</span>{\mathrm{<span\; class="notranslate">\; the\; y</span>}\mathrm{<span\; class="notranslate">\; 2</span>}}_{\mathrm{<span\; class="notranslate">\; 0</span>}}<span\; class="notranslate">\; )</span><span\; class="notranslate">\; +</span>{\stackrel{<span\; class="notranslate">\; \&Right\; Arrow;</span>}{\mathrm{<span\; class="notranslate">\; v</span>}}}_{\mathrm{<span\; class="notranslate">\; 2</span>}}<span\; class="notranslate">\; *</span><span\; class="notranslate">\; (</span>\mathrm{<span\; class="notranslate">\; i</span>}<span\; class="notranslate">\; -</span>\mathrm{<span\; class="notranslate">\; 1</span>}<span\; class="notranslate">\; )</span>\mathrm{<span\; class="notranslate">\; \&Delta;t</span>}$

为从A1到B1对应的速度向量，

为从A2到B2对应的速度向量，Δt为插入UIEvent的时间间隔。(x1 ₀ ,y1 ₀ ) is the coordinate of A1, (x2 ₀ ,y2 ₀ ) is the coordinate of A2,

is the velocity vector corresponding to from A1 to B1,

is the corresponding velocity vector from A2 to B2, and Δt is the time interval for inserting UIEvent.

In the embodiment of the present invention, different click times and touch point numbers can be combined to simulate different touch actions, and different cases can also be combined, that is, UIEvent sequences obtained from different cases are combined to simulate more complex actions.

Step 103: Send the UIEvent sequence to the UIAplication object, and the UIAplication object performs distribution processing.

The above-mentioned embodiments of the present invention are all described using the ISO system as an example. In view of the fact that the above-mentioned method of generating touch events has nothing to do with the platform, the method provided by the present invention can also be applied to other systems such as android, except that touch events in the android system are not UIEvent is MotionEvent. The generated MotionEvent sequence is not sent to UIAplication object, but to Instrumentation. Instrumentation forwards the MotionEvent sequence to the Android system, and the Android system provides it to the listening Application (application) through system broadcast. It is not necessary to repeat them one by one for other systems here.

The above is a detailed description of the method provided by the present invention, and the automated testing device provided by the present invention will be described in detail below through the second embodiment.

Embodiment two,

FIG. 4 is a structural diagram of a device provided by Embodiment 2 of the present invention. As shown in FIG. 4 , the device mainly includes an event generating unit 00 and an event sending unit 10 .

The event generation unit 00 is responsible for generating touch events conforming to the test state and combining them into a touch event sequence of touch actions.

The event sending unit 10 is responsible for sending the touch event sequence to the event forwarding object of the system under test, and the event forwarding object forwards the touch events in the sequence.

The device provided by the present invention can be used in tested systems such as ISO system, Android system, etc. Specifically, if the tested system is an ISO system, the touch event is UIEvent, the event forwarding object is UIApplication, and UIApplication converts the UIEvent in the UIEvent sequence Distributed to the target view. If the system under test is an Android system, the touch event is a MotionEvent, and the event forwarding object is an Instrumentation. The Instrumentation forwards the MotionEvent in the MotionEvent sequence to the Android system for the Android system to broadcast to the listening Application. In the subsequent description of this embodiment, only the iSO system is used as an example for description.

Usually, automated testing is performed on a case-by-case basis. In this case, the event generation unit 00 may specifically include: an information acquisition subunit 01 , a trajectory calculation subunit 02 , and an event insertion subunit 03 .

The case usually contains information such as the object to be tested and the test environment. Since the test in the embodiment of the present invention is a Monkey test, the case also contains touch action information. First, the information acquisition subunit 01 acquires touch action information from the case. In view of the fact that touch actions may include multiple types, such as click, slide, multi-touch, etc., but for event types, there are mainly two dimensions. The first dimension is the number of clicks, that is, click, double-click , multi-click, etc., the second dimension is the number of touch points, that is, single point, two points, multi-point, etc. Here, each type of touch action can be described using a multivariate parameter group. Specifically, the multivariate parameter group can include: the position, speed, acceleration, duration, and number of clicks of the start point and end point. The specific examples will not be described here. , see Embodiment 1.

其中，Y为动作结束点的位置，X为动作起始点的位置，

为速度向量，

为加速度向量，t为时间。Then the trajectory calculation subunit 02 calculates the touch trajectory according to the touch action information. When calculating the touch trajectory, it adopts a traditional mathematical method, that is,

Among them, Y is the position of the end point of the action, X is the position of the starting point of the action,

is the velocity vector,

is the acceleration vector, and t is the time.

Finally, the event insertion subunit 03 inserts a UIEvent corresponding to the touch action type at the corresponding position in the touch track every preset time interval according to the touch action direction, and obtains a UIEvent sequence. When inserting a UIEvent, three factors are mainly required, one is the insertion point position, the other is the event type, and the third is the action state. Since the insertion of the UIEvent is inserted at a preset time interval, the position of the inserted time point in the touch track can be determined (that is, substituted into the above formula of the touch track). The event type has been described above and is mainly reflected in two dimensions: the number of clicks and the number of touch points. The number of clicks can be directly obtained from the multivariate parameter group in the case, and the number of touch points corresponds to the number of multivariate parameter groups in the case. Action states mainly include three types: pressed state, moving state and popping state. When inserting a UIEvent, the action state at the starting point is the pressed state, the action state at the end point is the pop-up state, and the action state of each insertion point between the starting point and the end point in the touch track is the moving state.

If the touch action type is N-point touch, the touch action information is described by N multivariate parameter groups, the trajectory calculation subunit 02 obtains N touch trajectories, and when the event insertion subunit 03 inserts a UIEvent, the inserted position of each UIEvent exists N coordinate points, N is a positive integer.

No specific examples are listed here, and reference may be made to the description in Embodiment 1 of the above-mentioned method.

In the several embodiments provided by the present invention, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division, and there may be other division methods in actual implementation.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware, or in the form of hardware plus software functional units.

The above-mentioned integrated units implemented in the form of software functional units may be stored in a computer-readable storage medium. The above-mentioned software functional units are stored in a storage medium, including several instructions to enable a computer device (which may be a personal computer, server, or network device, etc.) or a processor (processor) to execute the methods described in various embodiments of the present invention. partial steps. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program codes. .

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included in the present invention. within the scope of protection.

Claims (12)

1. One kind based on the action touch simulation automated testing method, it is characterized in that the method comprises:

   S1, generation meet the touch event of test mode and are combined into the touch event sequence of touch action;

   S2, the touch event sequence is sent to the event forwarding object of tested system, by the event forwarding object touch event in the sequence is transmitted.
2. 2. method according to claim 1 is characterized in that, described step S1 specifically comprises:

   S11, from test case, obtain touch action information;

   The touch action information calculations touch track that S12, basis are obtained;

   S13, according to the touch action direction, correspondence position in touch track inserts the touch event corresponding with the touch action type of this position every the Preset Time interval, obtains the touch event sequence.
3. 3. method according to claim 2 is characterized in that, described touch action information adopts the multiple parameters group to be described, and described multiple parameters group comprises: the position of starting point and end point, speed, acceleration, duration and number of clicks.
4. 4. method according to claim 3, it is characterized in that, if being the N point, described touch action type touches, then described touch action information adopts N multiple parameters group to be described, in described step S12, obtain N bar touch track, there be N coordinate points in the position that each touch event inserts in described step S13, and N is positive integer.
5. 5. method according to claim 2, it is characterized in that, when inserting the touch event corresponding with the touch action type of this position, insert the touch event of down state in initial point position, insert the touch event of the state of upspringing in the end point position, the touch event of mobile status is inserted in each position between starting point and end point.
6. 6. according to claim 1 to the described method of 5 arbitrary claims, it is characterized in that, if described tested system is the iSO system, then described touch event is UIEvent, described event forwarding object is UIApplication, and described UIApplication is distributed to target view with the UIEvent in the UIEvent sequence;

   If described tested system is the Android system, then described touch event is MotionEvent, described event forwarding object is Instrumentation, described Instrumentation is transmitted to the Android system with the MotionEvent in the MotionEvent sequence, is broadcast to the Application of monitoring for the Android service system.
7. One kind based on the action touch simulation automatic test device, it is characterized in that this device comprises:

   The event generation unit is used for generating the touch event sequence that meets the touch event of test mode and be combined into touch action;

   The event transmitting element for the event forwarding object that described touch event sequence is sent to tested system, is transmitted the touch event in the sequence by the event forwarding object.
8. 8. device according to claim 7 is characterized in that, described event generation unit specifically comprises:

   The acquisition of information subelement is used for obtaining touch action information from test case;

   The track computation subunit is used for according to described touch action information calculations touch track;

   Event intron unit is used for according to the touch action direction, and correspondence position in touch track inserts the touch event corresponding with the touch action type of this position every the Preset Time interval, obtains the touch event sequence.
9. 9. device according to claim 8 is characterized in that, described touch action information adopts the multiple parameters group to be described, and described multiple parameters group comprises: the position of starting point and end point, speed, acceleration, duration and number of clicks.
10. 10. device according to claim 9, it is characterized in that, if being the N point, described touch action type touches, then described touch action information adopts N multiple parameters group to be described, described track computation subunit obtains N bar touch track, described event intron unit is when inserting touch event, and there be N coordinate points in the position that each touch event inserts, and N is positive integer.
11. 11. device according to claim 8, it is characterized in that, described event intron unit is when inserting the touch event corresponding with the touch action type of this position, insert the touch event of down state in initial point position, insert the touch event of the state of upspringing in the end point position, the touch event of mobile status is inserted in each position between starting point and end point.
12. 12. according to claim 7 to the described device of 11 arbitrary claims, it is characterized in that, if described tested system is the iSO system, then described touch event is UIEvent, described event forwarding object is UIApplication, and described UIApplication is distributed to target view with the UIEvent in the UIEvent sequence;

    If described tested system is the Android system, then described touch event is MotionEvent, described event forwarding object is Instrumentation, described Instrumentation is transmitted to the Android system with the MotionEvent in the MotionEvent sequence, is broadcast to the Application of monitoring for the Android service system.

Images