CN116467157A

CN116467157A - Application program testing method and device, computer equipment and storage medium

Info

Publication number: CN116467157A
Application number: CN202210033961.7A
Authority: CN
Inventors: 张志强; 郭润增; 王少鸣; 黎建忠
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2022-01-12
Filing date: 2022-01-12
Publication date: 2023-07-21

Abstract

The application program testing method, device, computer equipment and storage medium can be applied to the fields of cloud computing or intelligent transportation and the like and are used for solving the problem that the obtained application program testing result is low in accuracy and reliability. The method comprises the following steps: selecting an alternative initial state matched with the initial state to be tested from all the alternative test cases as a target initial state, and acquiring an alternative test case corresponding to the target initial state as a target test case; triggering an alternative event contained in the target test case aiming at the application program to be tested, and taking a display state presented by the display interface after triggering the target event as an ending state to be tested; and when the to-be-tested ending state is determined and is not matched with the alternative ending state contained in the target test case, an abnormal test result is generated, so that the accuracy and the reliability of the obtained application program test result are improved.

Description

Application program testing method and device, computer equipment and storage medium

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to an application program testing method, an application program testing device, a computer device, and a storage medium.

Background

With the continuous development of technology, various application programs can be developed to provide corresponding business services for different use scenarios. After the application program is developed, a plurality of rounds of tests are usually carried out before the application program is formally used on line, so that the normal and stable operation of the application program after the application program is on line is ensured.

In the traditional test process, only when the running result output by the application program is abnormal, recording abnormal prompt information in the test result; the abnormal running state of the application program in the test process can not trigger and record abnormal prompt information, so that the application program with the problem to be repaired can be caused, and a test result which characterizes that the application program can normally and stably run is obtained, so that the application program with the problem to be repaired is used on line in a formal way by mistake based on the wrong test result, and the problems that the application program cannot stably run, the application program fails to run on line and the like can be caused.

For example, if a cursor element which is not loaded successfully exists in a display interface associated with an application program, an abnormal operation state of the application program exists, but the abnormal operation state does not cause an abnormal operation result output by the application program, the application program can still operate normally, so that when the application program passes a test and is formally used online, a target object cannot determine a current input position through the display interface when inputting information to the display interface through a keyboard, the application program is easy to obtain wrong input information, and the application program cannot be used normally.

Therefore, in the related art, the accuracy and reliability of the application program test result obtained through the conventional test process are low.

Disclosure of Invention

The embodiment of the application program testing method, device, computer equipment and storage medium are provided to solve the problem that the obtained application program testing result is low in accuracy and reliability.

In a first aspect, an application testing method is provided, including:

in the running process of an application program to be tested, taking the display state currently presented by a display interface associated with the application program to be tested as an initial state to be tested;

selecting an alternative initial state matched with the initial state to be tested from all alternative test cases as a target initial state, and acquiring alternative test cases corresponding to the target initial state as target test cases, wherein each alternative test case comprises an alternative initial state, an alternative event and an alternative ending state corresponding to the application program to be tested;

triggering an alternative event contained in the target test case aiming at the application program to be tested, and taking a display state presented by the display interface after triggering the target event as an ending state to be tested;

And determining the ending state to be tested, and generating an abnormal test result representing that the program to be tested is abnormal when the ending state to be tested is not matched with the alternative ending state contained in the target test case.

In a second aspect, there is provided an application program testing apparatus comprising:

a first processing module: the method comprises the steps that in the running process of an application program to be tested, the display state currently presented by a display interface associated with the application program to be tested is used as an initial state to be tested;

the first processing module is further configured to: selecting an alternative initial state matched with the initial state to be tested from all alternative test cases as a target initial state, and acquiring alternative test cases corresponding to the target initial state as target test cases, wherein each alternative test case comprises an alternative initial state, an alternative event and an alternative ending state corresponding to the application program to be tested;

the first processing module is further configured to: triggering an alternative event contained in the target test case aiming at the application program to be tested, and taking a display state presented by the display interface after triggering the target event as an ending state to be tested;

And a second processing module: and the method is used for determining the ending state to be tested, and generating an abnormal test result representing that the program to be tested is abnormal when the ending state to be tested is not matched with the alternative ending state contained in the target test case.

Optionally, the first processing module is further configured to:

in the running process of an application program to be tested, taking the display state currently presented by a display interface associated with the application program to be tested as an alternative initial state;

when receiving a control instruction generated based on the display interface, triggering an alternative event corresponding to the control instruction by the application program to be tested;

taking the display state presented by the display interface after triggering the alternative event as an alternative ending state;

based on the alternative event, the alternative initial state, and the alternative end state, an alternative test case is generated for the alternative event.

Optionally, the application program to be tested has a corresponding view state relationship, and the view state relationship characterizes a logic relationship among display elements presented by the display interface in the running process of the application program to be tested;

the first processing module is specifically configured to:

After the alternative event triggering the target test case is acquired, a plurality of display elements to be tested are displayed on the display interface;

and taking the sub-relations corresponding to the display elements to be tested in the view state relation as the ending state to be tested.

Optionally, after the to-be-tested ending state characterization triggers an alternative event included in the target test case, the display interface presents a logic relationship among a plurality of to-be-tested display elements, and after the alternative ending state characterization included in the target test case executes a control operation generated through the display interface, the display interface presents a logic relationship among a plurality of target display elements;

the first processing module is specifically configured to:

determining the logic relation among the plurality of display elements to be tested, and generating the abnormal test result when the logic relation among the plurality of display elements to be tested is different from the logic relation among the plurality of target display elements;

and when the display elements to be tested exist and the target display elements corresponding to the same logic relationship are different, generating the abnormal test result.

Optionally, after triggering an alternative event included in the target test case, the target test case further includes a target interface snapshot corresponding to the display interface;

The second processing module is further configured to:

when the ending state to be tested is determined to be unmatched with the target ending state contained in the target test case, generating an abnormal test result representing that the program to be tested is abnormal, and then performing screen capturing processing on the display interface after triggering the target event to obtain an interface snapshot to be tested;

and in the display interface, presenting the interface snapshot to be tested, the target interface snapshot contained in the target test case and the abnormal test result.

Optionally, the second processing module is further configured to:

after the display state presented by the display interface after the alternative event contained in the target test case is triggered is used as the ending state to be tested, determining the ending state to be tested, and when the ending state to be tested is matched with the alternative ending state contained in the target test case, updating the initial state to be tested by taking the ending state to be tested as the display state currently presented by the display interface, and continuously reselecting the target test case from the alternative test cases to test.

In a third aspect, there is provided a computer program product comprising a computer program which, when executed by a processor, implements the method according to the first aspect.

In a fourth aspect, there is provided a computer device comprising:

a memory for storing program instructions;

and a processor for calling program instructions stored in the memory and executing the method according to the first aspect according to the obtained program instructions.

In a fifth aspect, there is provided a computer-readable storage medium storing computer-executable instructions for causing a computer to perform the method of the first aspect.

In the embodiment of the application, the alternative test case includes an alternative initial state, an alternative event and an alternative ending state of the application to be tested, and then the alternative event is relative to the display interface, not relative to the application to be tested itself. Therefore, in the running process of the application program to be tested, the application program to be tested can be tested through the state presented by the display interface associated with the application program to be tested. When the state presented by the display interface associated with the application program to be tested is not matched with the alternative ending state in the target test case, even if the application program to be tested can still normally run, an abnormal test result representing that the application program to be tested is abnormal can be generated, the obtained test result of the application program is improved, the accuracy and the reliability are improved, and the problems that the application program cannot stably run, the application program fails to run online and the like are avoided.

Drawings

Fig. 1 is an application scenario one of an application program testing method provided in an embodiment of the present application;

fig. 2 is a second application scenario of the application program testing method provided in the embodiment of the present application;

FIG. 3 is a flowchart illustrating a method for testing an application program according to an embodiment of the present disclosure;

FIG. 4a is a schematic diagram of an application testing method according to an embodiment of the present disclosure;

fig. 4b is a schematic diagram of a second principle of the application testing method according to the embodiment of the present application;

fig. 5a is a schematic diagram III of an application program testing method according to an embodiment of the present application;

fig. 5b is a schematic diagram of a method for testing an application according to an embodiment of the present application;

fig. 5c is a schematic diagram of an application program testing method according to an embodiment of the present application;

fig. 5d is a schematic diagram sixth of an application program testing method according to an embodiment of the present application;

fig. 5e is a schematic diagram seventh of an application program testing method according to an embodiment of the present application;

FIG. 5f is a schematic diagram eight of an application testing method according to an embodiment of the present disclosure;

fig. 6a is a schematic diagram nine of an application program testing method according to an embodiment of the present application;

Fig. 6b is a schematic diagram of an application program testing method according to an embodiment of the present application;

FIG. 6c is a schematic diagram eleven of an application testing method according to an embodiment of the present disclosure;

fig. 7a is a schematic diagram twelve of an application program testing method according to an embodiment of the present application;

FIG. 7b is a schematic diagram of a method for testing an application program according to an embodiment of the present disclosure;

FIG. 7c is a schematic diagram fourteen embodiments of an application testing method according to the present disclosure;

FIG. 8 is a schematic diagram of an application testing apparatus according to an embodiment of the present application;

fig. 9 is a schematic diagram of a second structure of the application testing apparatus according to the embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present application more clear, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application.

Some of the terms in the embodiments of the present application are explained below to facilitate understanding by those skilled in the art.

(1) Test cases:

the test case refers to executing a test task on an application program, and can embody a test scheme, a method, a technology and a strategy.

(2) State machine and state:

the state machine is a short term of finite state automaton, and is a mathematical model abstracted according to the operation rule of the application program. A state machine includes at least two states, a pre-event state triggered, and a post-event state triggered.

Encryption, decryption, signing, verifying signature, key agreement, etc.

With research and progress of cloud computing technology, the cloud computing technology is developed and applied in various fields, such as common smart home, smart wearable devices, virtual assistants, smart speakers, smart marketing, unmanned, autopilot, unmanned, robotic, smart medical, smart teaching, car networking, autopilot, smart transportation, etc., and it is believed that with the development of technology, the cloud computing technology will be applied in more fields and become more and more valuable.

The embodiment of the application relates to a cloud computing (cloud computing) technology, which is designed based on a cloud storage (cloud storage) technology.

Cloud computing is a computing model that distributes computing tasks over a large number of computer-made resource pools, enabling various application systems to acquire computing power, storage space, and information services as needed. The network that provides the resources is referred to as the "cloud". Resources in the cloud are infinitely expandable in the sense of users, and can be acquired at any time, used as needed, expanded at any time and paid for use as needed.

As a basic capability provider of cloud computing, a cloud computing resource pool (cloud platform for short, generally referred to as infrastructure as a service (Infrastructure as a Service, iaaS) platform) is established, in which multiple types of virtual resources are deployed for external clients to select for use.

According to the logic function division, a platform service (Platform as a Service, paaS) layer can be deployed on the IaaS layer, and a software service (Software as a Service, saaS) layer can be deployed on the PaaS layer, or the SaaS can be directly deployed on the IaaS layer. PaaS is a platform on which software runs, such as a database, web container, etc. SaaS is a wide variety of business software such as web portals, sms mass senders, etc. Generally, saaS and PaaS are upper layers relative to IaaS.

Cloud storage is a new concept which extends and develops in the concept of cloud computing, and a distributed cloud storage system (hereinafter referred to as a storage system for short) refers to a storage system which integrates a large number of storage devices (storage devices are also called storage nodes) of different types in a network through application software or application interfaces to cooperatively work and jointly provides data storage and service access functions for the outside through functions such as cluster application, grid technology, a distributed storage file system and the like.

At present, the storage method of the storage system is as follows: when creating logical volumes, each logical volume is allocated a physical storage space, which may be a disk composition of a certain storage device or of several storage devices. The client stores data on a certain logical volume, that is, the data is stored on a file system, the file system divides the data into a plurality of parts, each part is an object, the object not only contains the data but also contains additional information such as an Identity (ID) of the data, the file system writes each object into a physical storage space of the logical volume, and the file system records storage position information of each object, so that when the client requests to access the data, the file system can enable the client to access the data according to the storage position information of each object.

The process of allocating physical storage space for the logical volume by the storage system specifically includes: physical storage space is divided into stripes in advance according to the group of capacity measures for objects stored on a logical volume (which measures tend to have a large margin with respect to the capacity of the object actually to be stored) and redundant array of independent disks (Redundant Array of Independent Disk, RAID), and a logical volume can be understood as a stripe, whereby physical storage space is allocated to a logical volume.

It should be noted that, in the embodiments of the present application, related data such as content input by a user, screenshot obtained by screenshot, etc. when the embodiments of the present application are applied to specific products or technologies, user permission or consent needs to be obtained, and collection, use and processing of related data need to comply with related laws and regulations and standards of related countries and regions.

The application field of the application program testing method provided in the embodiment of the application is briefly described below.

For another example, please refer to fig. 1, especially for some applications running in internet of things (Internet of Things, ioT) terminal devices, the IoT terminal device includes a screen 101, a camera 102, a scan code component 103, a universal serial bus (Universal Serial Bus, USB) peripheral interface 104, and a Point of sale (POS) interface 105.

In the conventional testing process, the event is not triggered by the face information of the target object obtained through the camera 102, the two-dimensional code information provided by the target object obtained through the code scanning component 103, the input information provided by the user through the peripheral device obtained through the USB peripheral device interface 104, the transaction information provided by the target object obtained through the POS interface 105, and the like, so that when the problems to be repaired exist in the processes, the server still outputs a testing result representing the normal and stable operation of the application program.

In order to solve the problem of low accuracy and reliability of the obtained application program test result, the application program test method is provided. And in the running process of the application program to be tested, taking the display state currently presented by the display interface related to the application program to be tested as the initial state to be tested. Selecting an alternative initial state matched with an initial state to be tested from all the alternative test cases as a target initial state, and acquiring alternative test cases corresponding to the target initial state as target test cases, wherein each alternative test case comprises an alternative initial state, an alternative event and an alternative ending state corresponding to the application program to be tested. And aiming at the application program to be tested, triggering an alternative event contained in the target test case, and taking the display state presented by the display interface after the target event is triggered as the ending state to be tested. And determining the ending state to be tested, and generating an abnormal test result representing that the program to be tested is abnormal when the ending state to be tested is not matched with the alternative ending state contained in the target test case.

In the embodiment of the application, the alternative test case comprises an alternative initial state, an alternative event and an alternative ending state, and then the alternative event is relative to the display interface, not relative to the application to be tested. Therefore, in the running process of the application program to be tested, the application program to be tested can be tested through the state presented by the display interface associated with the application program to be tested. When the state presented by the display interface associated with the application program to be tested is not matched with the alternative ending state in the target test case, even if the application program to be tested can still normally run, an abnormal test result representing that the application program to be tested is abnormal can be generated, the obtained test result of the application program is improved, the accuracy and the reliability are improved, and the problems that the application program cannot stably run, the application program fails to run online and the like are avoided.

The application scenario of the application program testing method provided by the application program testing method is described below.

Please refer to fig. 2, which is a schematic diagram of an application scenario of the application program testing method provided in the present application. The application scene comprises a client 201 and a server 202. Communication may be between client 201 and server 202. The communication mode can be communication by adopting a wired communication technology, for example, communication is carried out through a connecting network wire or a serial port wire; the communication may also be performed by using a wireless communication technology, for example, a bluetooth or wireless fidelity (wireless fidelity, WIFI) technology, which is not particularly limited.

The client 201 generally refers to a device that can respond to an operation triggered by a target object, for example, a terminal device, a third party application that the terminal device can access, or a web page that the terminal device can access, or the like. Terminal devices include, but are not limited to, cell phones, computers, intelligent transportation devices, intelligent appliances, and the like. The server 202 generally refers to a device, such as a terminal device or a server, that can test an application. Servers include, but are not limited to, cloud servers, local servers, or associated third party servers, and the like. Both the client 201 and the server 202 may use cloud computing to reduce occupation of local computing resources; cloud storage may also be employed to reduce the occupation of local storage resources.

As an embodiment, the client 201 and the server 202 may be the same device, which is not limited in particular. In this embodiment, the description is given by taking the example that the client 201 and the server 202 are different devices respectively.

The following specifically describes an application program testing method provided in the embodiment of the present application, taking a server 202 as a main body and the server 202 as a server, based on fig. 2. Fig. 3 is a schematic flow chart of an application program testing method according to an embodiment of the present application.

S301, in the running process of the application program to be tested, taking the display state currently presented by the display interface related to the application program to be tested as the initial state to be tested.

Before testing the application program to be tested, the server can run the application program to be tested, so that a display interface associated with the application program to be tested can be presented in the client. In the running process of the application program to be tested, the server can take the display state currently presented by the display interface related to the application program to be tested as the initial state to be tested.

As one embodiment, the application to be tested has a corresponding view state relationship, and the view state relationship characterizes a logic relationship among display elements presented by the display interface in the running process of the application to be tested. Referring to fig. 4a, each display element presented by the display interface may include a typesetting, a layout, a background style, a text style, a color, an image, or a video presented in the display interface. Referring to fig. 4b, the logical relationship between the display elements may represent the vertical positional relationship of the display elements in the display interface, the stacking relationship of the display elements on the display interface, the inclusion relationship of the display elements on the display interface, the attachment relationship between the display elements, and so on. Wherein the sub-relationships of the shaded portion in fig. 4b correspond to the display elements of the shaded portion in fig. 4 a.

The view state relationship may be represented in a tree form, a list form, a knowledge graph form, or the like, which is not particularly limited. For example, the view state relationship may be that the UI is a view tree.

The server may use the sub-relationships corresponding to the display elements to be tested in the view state relationship as the initial state to be tested after obtaining the plurality of display elements to be tested currently presented by the display interface associated with the application program to be tested.

In one embodiment, the server obtains the sub-relationships corresponding to the plurality of display elements to be tested in the View state relationship, which may be implemented by calling a function, for example, the server calls window=activity.

S302, selecting an alternative initial state matched with an initial state to be tested from various alternative test cases as a target initial state, and acquiring an alternative test case corresponding to the target initial state as a target test case.

After obtaining the initial state to be tested, the server can select an initial state candidate matched with the initial state to be tested from all initial test cases candidate as a target initial state, and obtain the initial test cases candidate corresponding to the target initial state candidate as target test cases. Therefore, the server can automatically test the application program to be tested according to the current state of the display interface related to the application program to be tested.

The server may obtain each candidate test case in advance, where each candidate test case includes a corresponding candidate initial state, a candidate event, and a candidate end state of the application to be tested, for example, before the application to be tested triggers the corresponding candidate event, the candidate initial state corresponding to the display interface, and after the application to be tested triggers the candidate event, the candidate end state corresponding to the display interface. Therefore, when the server tests the application program to be tested, the server can complete the test of the application program to be tested based on each alternative test case.

The server may sequentially determine whether the initial state to be tested is the same as the candidate initial state included in each candidate test case, and if the initial state to be tested is determined to be the same as the candidate initial state, take the candidate initial state as a target initial state, and take the candidate test case corresponding to the candidate initial state as the target test case.

In the following description of the process of obtaining each candidate test case, the server may run the application program to be tested in advance, and obtain each candidate test case based on each control instruction generated by the tester aiming at the display interface in the process of using the application program to be tested through the display interface.

For example, please refer to fig. 5a, which is a schematic diagram of each alternative test case. Each alternative test case may be considered as a state machine that contains alternative events for 7 control instructions, i.e., 7 alternative test cases.

Referring to fig. 5b, the face payment client scans a shooting area through a camera, and when a face exists in the shooting area, the face payment client performs continuous shooting for multiple times, and the server can obtain multiple face images and select one face image from the multiple face images.

Referring to fig. 5c, the server selects a face image with the best image quality from the plurality of face images based on the plurality of face images, preferably the face image. When the server prefers the face image, if the optimization succeeds, the client displays the selected optimal face image in a designated area of the display interface, and the server continues to face recognition on the optimal face image.

Referring to fig. 5d, when the server performs face recognition on the optimal face image, if the recognition is successful, the client presents a prompt for successful recognition and a prompt for going into mobile phone number verification in the display interface.

Referring to fig. 5e, after the face recognition is successful, the client presents relevant display elements of mobile phone number verification in the display interface, the target object can input the mobile phone number through the display interface, and the server performs mobile phone number verification according to the received mobile phone number.

Referring to fig. 5f, when the server verifies the mobile phone number, if verification is successful, the server completes payment for the target object, and the client presents a payment completion prompt in the display interface, and may also present a payment result.

If the server does not select the optimal face image, namely the optimal face image fails or overtime, or the optimal face image fails or overtime in face recognition, or the mobile phone number fails in verification, a failure prompt can be presented in a display interface of the client, and whether the face image is acquired again through the camera is determined.

If it is determined that the face image is re-acquired through the camera, the display interface is re-presented as the interface shown in fig. 5b, and the face image is re-acquired. If the target object cancels the acquisition of the face image or the verification of the mobile phone number, the payment failure aiming at the target object is presented in the display interface.

The acquisition process of each alternative test case is similar, and the embodiment of the application is introduced by taking the acquisition process of one alternative test case as an example.

And the server takes the display state currently presented by the display interface associated with the application program to be tested as an alternative initial state in the running process of the application program to be tested. And triggering an alternative event corresponding to the control instruction by the application program to be tested when receiving the control instruction generated based on the display interface.

The control instruction may be a control instruction generated when the target object uses the application program to be tested through the display interface. For example, when the client scans the shooting area through the camera, the target object places the face in the shooting area by facing the display interface to generate shooting, and the camera shoots the shooting area for a plurality of times to obtain a plurality of face images. For another example, after the mobile phone number input by the target object is obtained, a mobile phone number verification instruction is generated, and the obtained mobile phone number is verified.

The control instruction may also be generated based on the obtained alternative end state, for example, after a plurality of face images are obtained, a preference instruction is generated to select a face image with the best image quality from the plurality of face images. For another example, after the optimal face image is obtained, a mobile phone number obtaining instruction is generated to obtain information input by the target object through the display interface. For another example, when the mobile phone number verification is successful, a payment instruction is generated to complete the payment.

The server may take the display state presented by the display interface after triggering the alternative event as an alternative ending state. The server may generate alternative test cases for the alternative events based on the alternative events, the alternative initial state, and the alternative end state.

When the alternative ending state is obtained, the server can update the original control instruction based on the control instruction generated by the alternative ending state, update the alternative initial state based on the alternative ending state, and continue to generate other alternative test cases.

As an embodiment, when the server obtains the alternative initial state, the server may perform screen capturing processing on the display interface to obtain an interface snapshot corresponding to the alternative initial state, when the server obtains the alternative end state, may perform screen capturing processing on the display interface to obtain an interface snapshot corresponding to the alternative end state, and store the obtained interface snapshot into the alternative test case, thereby intuitively displaying the alternative initial state and the alternative end state through the interface snapshot.

S303, aiming at the application program to be tested, triggering an alternative event contained in the target test case, and taking the display state presented by the display interface after triggering the target event as the ending state to be tested.

After determining the target test case, the server can trigger an alternative event contained in the target test case aiming at the application program to be tested, and the display state presented by the display interface after the alternative event is triggered is used as the ending state to be tested. In order to facilitate differentiation, the embodiment of the application uses the candidate event contained in the target test case as a target event and uses the candidate ending state contained in the target test case as a target ending state.

After the server can acquire the trigger target event, the display interface presents a plurality of display elements to be tested, and the sub-relations corresponding to the plurality of display elements to be tested in the view state relation are used as the ending state to be tested. For example, please continue to refer to fig. 4a and 4b, the text of the shaded portion in fig. 4a may be regarded as a display element to be tested, and then the display element to be tested may correspond to the sub-relationship of the shaded portion in fig. 4 b; alternatively, the characters and the character positions of the shaded portion in fig. 4a, etc. may be regarded as a plurality of display elements to be tested, and then the plurality of display elements to be tested may correspond to the sub-relationship from the fourth row to the row in which the shaded portion is located in fig. 4 b; alternatively, the characters in the shaded portion in fig. 4a, a line of characters below the shaded portion, the character position, the character pattern, etc. may be regarded as a plurality of display elements to be tested, and then the plurality of display elements to be tested may correspond to the sub-relationships shown in the fourth line to the ninth line in fig. 4 b; alternatively, all elements in fig. 4a may be regarded as a plurality of display elements to be tested, and then the plurality of display elements to be tested may correspond to the sub-relationships shown in the first to last rows (not shown in fig. 4 b) in fig. 4b, and so on.

As an embodiment, the plurality of display elements to be tested presented by the display interface may be different display elements to be tested from each display element to be tested presented by the display interface before the triggering of the target event; or each display element to be tested presented on the display interface after triggering the target event, and the like, and the method is not particularly limited.

For example, the display state of the display interface related to the application program to be tested is the display state of the camera for scanning the shooting area, and then, from all the candidate test cases, the target test case corresponding to the state of the camera for scanning the shooting area is selected, the target event 'shooting' contained in the target test case is triggered for the application program to be tested, the shooting area is continuously shot for multiple times, a plurality of images are obtained, and the display state of the display interface after the triggering of the target event is used as the ending state to be tested.

S304, determining the ending state to be tested, and generating an abnormal test result representing that the program to be tested is abnormal when the ending state to be tested is not matched with the target ending state contained in the target test case.

After obtaining the ending state to be tested, the server can determine whether the ending state to be tested is matched with the target ending state contained in the target test case, if so, the server can generate an abnormal test result representing that the program to be tested is abnormal. The abnormal test result may include an initial state to be tested, an end state to be tested, a target event, a target test case, and prompt information for indicating that the test program has an abnormality.

If the to-be-tested ending state is determined to be matched with the target ending state contained in the target test case, the server can update the initial state to be tested by taking the to-be-tested ending state as the display state currently presented by the display interface, and the target test case is continuously selected from all the candidate test cases again for testing, so that an automatic test process is realized.

As an embodiment, after the end state of the test indicates the triggering target event, the logic relationship among the plurality of display elements to be tested presented by the display interface, after the end state of the test indicates the execution of the control instruction corresponding to the target event, the server may determine whether the logic relationship among the plurality of display elements to be tested is the same as the logic relationship among the plurality of display elements to be tested, and if not, generate the abnormal test result.

For example, please refer to fig. 6a (1), which shows a plurality of target display elements presented by the interface and a logic relationship between the plurality of target display elements, i.e. a target ending state included in the target test case, after the control instruction corresponding to the target event is executed by the application program to be tested. Referring to fig. 6a (2), after triggering a target event for an application to be tested, a plurality of display elements to be tested presented on a display interface and a logic relationship between the plurality of display elements to be tested, i.e. an end state to be tested, are displayed.

In the logic relationship corresponding to the target ending state, "four digits after requesting to input the bound mobile phone number" the same level logic relationship also comprises "no trace for safe input" and "ImageView [285, 243] [515, 437]", while in the logic relationship corresponding to the test ending state, "four digits after requesting to input the bound mobile phone number" the same level logic relationship does not contain other contents. That is, the server may generate an abnormal test result if the logical relationship between the plurality of display elements to be tested is not the same as the logical relationship between the plurality of target display elements.

The server can also determine whether the display elements to be tested exist, the target display elements corresponding to the same logic relationship are different, and if the display elements to be tested exist, the target display elements corresponding to the same logic relationship are different, an abnormal test result is generated.

For example, referring to fig. 6b (1), after the control instruction corresponding to the target event is executed for the application program to be tested, a plurality of target display elements presented by the interface and a logic relationship between the plurality of target display elements, that is, a target end state included in the target test case, are displayed. Referring to fig. 6b (2), after the application to be tested triggers the target event, the display interface presents a plurality of display elements to be tested and a logic relationship between the plurality of display elements to be tested, i.e. an end state to be tested.

In the same logic relationship, the target ending state corresponds to "please input four digits after the bound mobile phone number", the ending state to be tested corresponds to "this is a section of wrong prompt document", that is, there are display elements to be tested, and the target display elements corresponding to the same logic relationship are different, so that an abnormal test result is generated.

If the logic relationship among the plurality of display elements to be tested is determined to be the same as the logic relationship among the plurality of target display elements, the display elements to be tested do not exist, and the target display elements corresponding to the same logic relationship are different, the server can update the initial state to be tested by taking the ending state to be tested as the display state currently presented by the display interface, and the target test cases are continuously selected again from the candidate test cases for testing.

As an embodiment, if the target test case further includes a target interface snapshot corresponding to the display interface after the target event is triggered, the server may take the display state of the display interface after the target event is triggered as the to-be-tested end state, and then perform screen capturing processing on the display interface after the target event is triggered to obtain the to-be-tested interface snapshot. In the display interface, the interface snapshot to be tested, the target interface snapshot contained in the target test case and the abnormal test result are presented, so that the abnormal test result can be intuitively displayed, and a tester can quickly repair the abnormality.

For example, referring to fig. 6c, in the display interface, a target interface snapshot and an interface snapshot to be tested included in the target test case may be presented, and an abnormal position represented by the abnormal test result may be marked by adding a shadow. The abnormal position in the interface snapshot to be tested is the area where the error prompting document is located, so that the area where the four digits after the bound mobile phone number is requested to be input in the target interface snapshot is located, and the area where the error prompting document is located in the interface snapshot to be tested are marked by using shadows.

The following describes an example of an application program testing method provided in the embodiment of the present application by taking a face payment process in an application program to be tested as an example.

Referring to fig. 7a, a client obtains each candidate test case corresponding to an application program to be tested in advance, uploads the candidate test cases to a test case archiving server, and when the application program to be tested is tested, the server may download a target test case from the test case archiving server based on a current state of a display interface of the client in a running process of the application program to be tested, and obtain an ending state to be tested by triggering a target event of the application program to be tested. By matching the ending state to be tested with the target ending state contained in the target test case, generating an abnormal test result when the ending state is not matched with the target ending state; and when the test result is matched, the ending state to be tested is used as the initial state to be tested, and the target test case is continuously downloaded from the test case archiving server for testing until an abnormal test result is obtained or all the candidate test cases corresponding to the application program to be tested are tested.

In the process of acquiring the candidate test case, please refer to fig. 7b, in the state of acquiring the preferred face image, based on the control instruction of face recognition, a face recognition event is triggered, based on the face recognition event, interaction is performed with the server through the internet, the face recognition action is executed for the preferred face image, and the associated display element is presented in the display interface. When the face recognition action is executed, the server obtains the state of the preferred face image through the Hook event and converts the state into the state of successful face recognition, failed face recognition or overtime. Thus, an alternative test case may be generated based on the status of the obtained preferred face image, the status of the face recognition success, the face recognition failure or timeout, and the face recognition event. And continuing to generate corresponding instructions through the Hook event in the states of successful face recognition, failed face recognition or overtime, triggering corresponding events and generating other alternative test cases.

Based on the process of testing the application program to be tested by each alternative test case, the state before the state transition, the state after the state transition and the event corresponding to the state transition can be recorded through a preset monitoring interface during the state transition.

The monitoring interface may be an onTransition () function that is called by the method shown in table 1 to monitor the state transitions generated by the event.

TABLE 1

Referring to fig. 7c, in a state that the preferred face image is obtained, a target test case is selected from the candidate test cases by interacting with Mock, a face recognition event included in the target test case is triggered by Hook, a face recognition action is performed on the preferred face image based on the face recognition event, and associated display elements are presented in a display interface. When the face recognition action is executed, the server obtains the state of the preferred face image through the Hook event and converts the state into the state of successful face recognition, failed face recognition or overtime. Therefore, the state of the obtained preferred face image can be compared and converted into the state of successful face recognition, failure face recognition or overtime, whether the state is matched with the target ending state contained in the target test case or not, and an abnormal test result representing that the program to be tested is abnormal is generated when the state is not matched with the target ending state.

Based on the same inventive concept, the embodiment of the application program testing device can realize the functions corresponding to the application program testing method. Referring to fig. 8, the apparatus includes a first processing module 801 and a second processing module 802, wherein:

first processing module 801: the method comprises the steps that in the running process of an application program to be tested, the display state of a display interface related to the application program to be tested, which is currently presented, is used as an initial state to be tested;

the first processing module 801 is further configured to: selecting a target test case corresponding to a target initial state matched with an initial state to be tested from various alternative test cases, wherein each alternative test case comprises an alternative initial state corresponding to a display interface before an application program to be tested triggers a corresponding alternative event and an alternative ending state corresponding to the display interface after the application program to be tested triggers the alternative event;

the first processing module 801 is further configured to: triggering a target event contained in a target test case aiming at an application program to be tested, and taking a display state presented by a display interface after triggering the target event as an ending state to be tested;

the second processing module 802: and the method is used for determining the ending state to be tested, and generating an abnormal test result representing that the program to be tested is abnormal when the ending state to be tested is not matched with the target ending state contained in the target test case.

In one possible embodiment, the first processing module 801 is further configured to:

in the running process of the application program to be tested, taking the display state currently presented by the display interface associated with the application program to be tested as an alternative initial state;

when receiving a control instruction generated based on a display interface, triggering an alternative event corresponding to the control instruction by an application program to be tested;

In one possible embodiment, the application to be tested has a corresponding view state relationship, and the view state relationship characterizes a logic relationship among display elements presented by the display interface in the running process of the application to be tested;

the first processing module 801 is specifically configured to:

after a trigger target event is acquired, a plurality of display elements to be tested are displayed on a display interface;

In one possible embodiment, after the end state to be tested represents the triggering target event, displaying the logic relationship among the plurality of display elements to be tested presented by the interface, and after the end state to be tested represents the control operation generated by the display interface, displaying the logic relationship among the plurality of target display elements presented by the interface;

The first processing module 801 is specifically configured to:

determining a logic relationship among a plurality of display elements to be tested, and generating an abnormal test result when the logic relationship among the plurality of display elements to be tested is different from the logic relationship among the plurality of target display elements;

and determining that the display elements to be tested exist, and generating an abnormal test result when the display elements to be tested are different from the target display elements corresponding to the same logic relationship.

In one possible embodiment, the target test case further includes displaying a target interface snapshot corresponding to the interface after triggering the target event;

the second processing module 802 is further configured to:

when the ending state to be tested is determined and is not matched with the target ending state contained in the target test case, generating an abnormal test result representing that the program to be tested is abnormal, and then performing screen capturing processing on the display interface after triggering the target event to obtain an interface snapshot to be tested;

and presenting the interface snapshot to be tested, the target interface snapshot contained in the target test case and the abnormal test result in the display interface.

In one possible embodiment, the second processing module 802 is further configured to:

and after the display state presented by the display interface after the trigger target event is used as the ending state to be tested, determining the ending state to be tested, and when the ending state to be tested is matched with the ending state of the target contained in the target test case, updating the initial state to be tested by taking the ending state to be tested as the display state currently presented by the display interface, and continuously reselecting the target test case from all the candidate test cases to test.

Referring to fig. 9, the application program testing apparatus may be run on a computer device 900, and a current version and a historical version of a data storage program and application software corresponding to the data storage program may be installed on the computer device 900, where the computer device 900 includes a processor 980 and a memory 920. In some embodiments, the computer device 900 may include a display unit 940, the display unit 940 including a display panel 941 for displaying an interface or the like for interactive operation by a user.

In one possible embodiment, the display panel 941 may be configured in the form of a liquid crystal display (Liquid Crystal Display, LCD) or an Organic Light-Emitting Diode (OLED) or the like.

The processor 980 is configured to read the computer program and then perform a method defined by the computer program, for example, the processor 980 reads a data storage program or a file, etc., so that the data storage program is executed on the computer device 900 and a corresponding interface is displayed on the display unit 940. Processor 980 may include one or more general-purpose processors and may also include one or more DSPs (Digital Signal Processor, digital signal processors) for performing associated operations to implement the techniques provided by the embodiments of the present application.

Memory 920 generally includes memory and external storage, and memory may be Random Access Memory (RAM), read Only Memory (ROM), CACHE memory (CACHE), and the like. The external memory can be a hard disk, an optical disk, a USB disk, a floppy disk, a tape drive, etc. The memory 920 is used to store computer programs including application programs corresponding to respective clients, etc., and other data, which may include data generated after the operating system or application programs are executed, including system data (e.g., configuration parameters of the operating system) and user data. In the embodiment of the present application, the program instructions are stored in the memory 920, and the processor 980 executes the program instructions in the memory 920, implementing any of the methods discussed in the previous figures.

The above-described display unit 940 is used to receive input digital information, character information, or touch operation/noncontact gestures, and to generate signal inputs related to user settings and function controls of the computer device 900, and the like. Specifically, in the embodiment of the present application, the display unit 940 may include a display panel 941. The display panel 941, such as a touch screen, may collect touch operations thereon or thereabout by a user (e.g., operations of the user on the display panel 941 or on the display panel 941 using any suitable object or accessory such as a finger, a stylus, etc.), and drive the corresponding connection device according to a predetermined program.

In one possible embodiment, the display panel 941 may include two parts, a touch detection device and a touch controller. The touch detection device detects the touch azimuth of a player, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device and converts it into touch point coordinates, which are then sent to the processor 980, and can receive commands from the processor 980 and execute them.

The display panel 941 may be implemented by various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the display unit 940, in some embodiments, the computer device 900 may also include an input unit 930, and the input unit 930 may include an image input device 931 and other input devices 932, which may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, mouse, joystick, etc.

In addition to the above, computer device 900 may also include a power supply 990 for powering other modules, audio circuitry 960, near field communication module 970, and RF circuitry 910. The computer device 900 may also include one or more sensors 950, such as acceleration sensors, light sensors, pressure sensors, and the like. Audio circuitry 960 may include, among other things, a speaker 961 and a microphone 962, for example, where the computer device 900 may collect a user's voice via the microphone 962, perform a corresponding operation, etc.

The number of processors 980 may be one or more, and the processors 980 and memory 920 may be coupled or may be relatively independent.

As an example, the processor 980 in fig. 9 may be used to implement the functionality of the first processing module 801 and the second processing module 802 as in fig. 8.

As an example, the processor 980 in fig. 9 may be used to implement the functions associated with the servers or terminal devices discussed above.

Those of ordinary skill in the art will appreciate that: all or part of the steps for implementing the above method embodiments may be implemented by hardware associated with program instructions, where the foregoing program may be stored in a computer readable storage medium, and when executed, the program performs steps including the above method embodiments; and the aforementioned storage medium includes: a mobile storage device, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk or an optical disk, or the like, which can store program codes.

Alternatively, the above-described integrated units of the present invention may be stored in a computer-readable storage medium if implemented in the form of software functional modules and sold or used as separate products. Based on such understanding, the technical solutions of the embodiments of the present invention may be embodied in essence or in a part contributing to the prior art in the form of a software product, for example, by a computer program product stored in a storage medium, comprising several instructions for causing a computer device to execute all or part of the methods described in the embodiments of the present invention. And the aforementioned storage medium includes: a removable storage device, ROM, RAM, magnetic or optical disk, or other medium capable of storing program code.

It will be apparent to those skilled in the art that various modifications and variations can be made in the present application without departing from the spirit or scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims and the equivalents thereof, the present application is intended to cover such modifications and variations.

Claims

1. An application testing method, comprising:

2. The method of claim 1, wherein the alternative test cases are obtained by:

3. The method according to claim 1, wherein the application to be tested has a corresponding view state relationship, the view state relationship representing a logical relationship between display elements presented by the display interface during the running process of the application to be tested;

Triggering an alternative event contained in the target test case aiming at the application program to be tested, and taking a display state presented by the display interface after triggering the target event as an ending state to be tested, wherein the method comprises the following steps:

4. The method of claim 1, wherein the end-of-test state characterization triggers a logical relationship between a plurality of display elements to be tested presented by the display interface after an alternative event included in the target test case, and wherein the end-of-test state characterization includes a logical relationship between a plurality of target display elements presented by the display interface after a control operation generated by the display interface is performed;

determining that the ending state to be tested is not matched with the alternative ending state contained in the target test case, and generating an abnormal test result representing that the program to be tested is abnormal, wherein the abnormal test result comprises at least one of the following steps:

5. The method according to any one of claims 1 to 4, wherein the target test case further includes a target interface snapshot corresponding to the display interface after triggering an alternative event included in the target test case;

when the ending state to be tested is determined to be unmatched with the alternative ending state contained in the target test case, generating an abnormal test result representing that the program to be tested is abnormal, and further comprising:

performing screen capturing processing on the display interface after triggering the target event to obtain an interface snapshot to be tested;

6. The method according to any one of claims 1 to 4, wherein, after the candidate event included in the target test case is triggered, the display state presented by the display interface is taken as the to-be-tested end state, further comprising:

And when the to-be-tested ending state is determined and matched with the alternative ending state contained in the target test case, the to-be-tested ending state is used as the display state currently presented by the display interface, the initial state to be tested is updated, and the target test case is continuously selected from the alternative test cases again for testing.

7. An application testing apparatus, comprising:

8. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any one of claims 1 to 6.

9. A computer device, comprising:

a memory for storing program instructions;

a processor for invoking program instructions stored in said memory and for performing the method according to any of claims 1-6 in accordance with the obtained program instructions.

10. A computer-readable storage medium storing computer-executable instructions for causing a computer to perform the method of any one of claims 1 to 6.