CN116401173A - Test case generation method and device, medium and electronic equipment - Google Patents

Abstract

The disclosure relates to a test case generation method, a test case generation device, a test case generation medium and an electronic device. The method comprises the following steps: displaying a test scene configuration interface aiming at an application program to be tested, and determining a target test scene configured aiming at the application program to be tested; the configuration interface supports a target test scene for executing selection operation on the interface to configure the coverage required by the test; invoking a test map which is generated in advance for an application program to be tested, and generating a corresponding test case based on a target test scene; the test map is a scene relation knowledge graph constructed by clustering information obtained by performing scene clustering on page information of the application program to be tested. Therefore, a user can configure a target test scene required to be covered by the test by clicking the scene on the test scene configuration interface, the test is convenient and quick, then the test case can be automatically generated according to the test map, the test case does not need to be manually written, the complexity of obtaining the test case is reduced, and the generation efficiency of the test case and the test efficiency of the application program are improved.

Description

Test case generation method, device, medium and electronic equipment

technical field

The present disclosure relates to the field of computer technology, and in particular, to a test case generation method, device, medium and electronic equipment.

Background technique

As the functions of the terminal equipment continue to increase, more and more application programs are applied on the terminal equipment. In the development stage of the application program, in order to test whether the function of the application program is normal and whether the expected effect can be achieved, the developer needs to test the developed application program before the application program goes online. In addition, after a new version of the application program is released, a functional test is also required for the application program of the new version. At this stage, when testing applications, it is usually necessary to manually write test cases, resulting in high complexity, time-consuming test cases, and low user experience.

Contents of the invention

This Summary is provided to introduce a simplified form of concepts that are described in detail later in the Detailed Description. This summary of the invention is not intended to identify key features or essential features of the claimed technical solution, nor is it intended to be used to limit the scope of the claimed technical solution.

In a first aspect, the present disclosure provides a test case generation method, including:

Displaying the test scenario configuration interface for the application to be tested, determining the target test scenario configured for the application to be tested; the test scenario configuration interface supports performing selection operations on the interface to configure the target test that the test needs to cover Scenes;

Invoking the pre-generated test map for the application under test, generating a corresponding test case based on the target test scenario, the test case is used to test the application under test; wherein, the test map is for The scene relationship knowledge graph constructed by the clustering information obtained from the scene clustering of the page information of the application to be tested, the nodes in the scene relationship knowledge graph are used to represent the scene abstracted from the page, and the edges connected by the nodes are used to represent Controls, actions and jump information supported by the node.

In a second aspect, the present disclosure provides a test case generation device, including:

A determination module, configured to display a test scenario configuration interface for the application to be tested, and determine a target test scenario configured for the application to be tested; the test scenario configuration interface supports performing selection operations on the interface to configure the coverage required for the test The target test scenario of ;

A generating module, configured to invoke a pre-generated test map for the application under test, and generate a corresponding test case based on the target test scenario, the test case is used to test the application under test; wherein, the The test map is a scene relationship knowledge graph constructed from the clustering information obtained by performing scene clustering on the page information of the application to be tested. The nodes in the scene relationship knowledge graph are used to represent the scenes abstracted from the page, and the nodes are connected The edges of are used to represent the controls, actions and jump information supported by the node.

In a third aspect, the present disclosure provides a computer-readable medium on which a computer program is stored, and when the program is executed by a processing device, the steps of the test case generation method provided in the first aspect of the present disclosure are implemented.

In a fourth aspect, the present disclosure provides an electronic device, including:

a storage device on which a computer program is stored;

A processing device configured to execute the computer program in the storage device to implement the steps of the method for generating test cases provided in the first aspect of the present disclosure.

In the above technical solution, firstly, a test scenario configuration interface for the application to be tested is displayed, and a target test scenario configured for the application to be tested is determined, wherein the test scenario configuration interface supports performing a selection operation on the interface to configure the required test scenario for the test. Covered target test scenarios; then, call the pre-generated test map for the application under test, and generate corresponding test cases based on the target test scenarios. In this way, the user only needs to click the scene on the test scene configuration interface to configure the target test scene to be covered by the test, which is convenient and fast. After that, the test case can be automatically generated based on the target test scene according to the pre-generated test map , instead of manually writing test cases, thereby reducing the complexity of obtaining test cases, thereby improving the efficiency of test case generation and application testing, and improving user experience.

Other features and advantages of the present disclosure will be described in detail in the detailed description that follows.

Description of drawings

The above and other features, advantages and aspects of the various embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic and that elements and elements are not necessarily drawn to scale. In the attached picture:

Fig. 1 shows the steps of a test case generation method according to an exemplary embodiment.

Fig. 2 is a schematic diagram showing jump information between pages in an application program to be tested and trigger conditions for page jumps according to an exemplary embodiment.

Fig. 3 is a schematic diagram of a test map constructed according to Fig. 2 according to an exemplary embodiment.

Fig. 4 is a schematic diagram of a test case according to an exemplary embodiment.

Fig. 5 is a block diagram of a device for generating test cases according to an exemplary embodiment.

Fig. 6 is a schematic structural diagram of an electronic device according to an exemplary embodiment.

Detailed ways

Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the drawings, it should be understood that the disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein; A more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for exemplary purposes only, and are not intended to limit the protection scope of the present disclosure.

It should be understood that the various steps described in the method implementations of the present disclosure may be executed in different orders, and/or executed in parallel. Additionally, method embodiments may include additional steps and/or omit performing illustrated steps. The scope of the present disclosure is not limited in this respect.

As used herein, the term "comprise" and its variations are open-ended, ie "including but not limited to". The term "based on" is "based at least in part on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one further embodiment"; the term "some embodiments" means "at least some embodiments." Relevant definitions of other terms will be given in the description below.

It should be noted that concepts such as "first" and "second" mentioned in this disclosure are only used to distinguish different devices, modules or units, and are not used to limit the sequence of functions performed by these devices, modules or units or interdependence.

It should be noted that the modifications of "one" and "multiple" mentioned in the present disclosure are illustrative and not restrictive, and those skilled in the art should understand that unless the context clearly indicates otherwise, it should be understood as "one or more" multiple".

The names of messages or information exchanged between multiple devices in the embodiments of the present disclosure are used for illustrative purposes only, and are not used to limit the scope of these messages or information.

It can be understood that before using the technical solutions disclosed in the embodiments of the present disclosure, the user should be informed of the type, scope of use, and use scenarios of the personal information involved in the present disclosure in an appropriate manner in accordance with relevant laws and regulations, and the authorization of the user should be obtained. .

For example, in response to receiving the user's active request, send prompt information to the user to clearly remind the user that the requested operation will require the acquisition and use of the user's personal information. Thus, the user can independently choose whether to provide personal information to software or hardware such as electronic devices, application programs, servers, or storage media that perform the operations of the technical solution of the present disclosure according to the prompt information.

As an optional but non-limiting implementation, in response to receiving the active request of the user, the way of sending the prompt information to the user may be, for example, a pop-up window, and the prompt information may be presented in text in the pop-up window. In addition, the pop-up window may also carry a selection control for the user to choose "agree" or "disagree" to provide personal information to the electronic device.

It can be understood that the above process of notifying and obtaining user authorization is only illustrative and does not limit the implementation of the present disclosure. Other methods that meet relevant laws and regulations may also be applied to the implementation of the present disclosure.

At the same time, it can be understood that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of data) should comply with the requirements of corresponding laws and regulations and relevant regulations.

Fig. 1 shows the steps of a test case generation method according to an exemplary embodiment. As shown in FIG. 1 , the method may include the following S101-S104.

In S101, a test scenario configuration interface for the application to be tested is displayed, and a target test scenario configured for the application to be tested is determined.

In this disclosure, the test scenario configuration interface supports performing selection operations on the interface to configure the target test scenario that the test needs to cover, that is, the user can configure the target test that the test needs to cover by clicking the scene on the test scenario configuration interface Scenes.

In S102, the pre-generated test map for the application program to be tested is invoked, and corresponding test cases are generated based on the target test scenario.

In this disclosure, test cases are used to test the application under test. The test map is a scene relational knowledge map constructed from the clustering information obtained by scene clustering of the page information of the application to be tested. The nodes in the scene relational knowledge map are used to represent the scene abstracted from the page, and the edges connected by the nodes are used to represent Controls, actions and jump information supported by the node.

The application under test usually includes many application functions. For example, a video application will include multiple functional modules such as login, video recording, video editing, dubbing, chat, etc., and each function will be reflected in each page of the application under test , that is, the scene of each page, or it can also be said to be the characteristics of each page. In order to implement a comprehensive test of the application under test, it is necessary to determine the scene of each page in the application under test, that is, it is necessary to abstract the clustering of pages in the application under test into multiple scenarios.

Jump information between scenes refers to a scene jump relationship that can jump from one scene to another scene, for example, jumping from scene A to scene B is a scene jump relationship. The jump information between scenes may include a one-way jump relationship and a two-way jump relationship. Among them, when two scenes can jump to each other, it is determined that there is a two-way jump relationship between the two scenes, and when two scenes can only jump from one scene to another scene, it is determined that the two scenes There is a one-way jump relationship between them.

The scene of the page of the application to be tested is usually provided with several controls (ie, jump controls) for implementing scene jumps, which are used to control the application to be tested to jump from one scene to another. By applying a corresponding action (that is, a jump action, such as a click action, a long press action, etc.) on the jump control in a scene or at any position in the scene, it is possible to jump from this scene to another scene.

In the above technical solution, firstly, a test scenario configuration interface for the application to be tested is displayed, and a target test scenario configured for the application to be tested is determined, wherein the test scenario configuration interface supports performing a selection operation on the interface to configure the required test scenario for the test. Covered target test scenarios; then, call the pre-generated test map for the application under test, and generate corresponding test cases based on the target test scenarios. In this way, the user only needs to click the scene on the test scene configuration interface to configure the target test scene to be covered by the test, which is convenient and fast. After that, the test case can be automatically generated based on the target test scene according to the pre-generated test map , instead of manually writing test cases, thereby reducing the complexity of obtaining test cases, thereby improving the efficiency of test case generation and application testing, and improving user experience.

The method of generating the above test map will be described in detail below. Specifically, it can be achieved through the following steps [1] to [3]:

Step [1]: traverse the Extensible Markup Language (XML) information of the pages in the application to be tested, and perform scene clustering on the Extensible Markup Language information of all pages to obtain multiple scenes.

In the present disclosure, the XML information of the page may include information such as arrangement, style, and name of each control in the page. It should be noted that the specific implementation of traversing the XML information of the pages in the application program under test, and performing scene clustering on the XML information of all pages to obtain multiple scenes is well known to those skilled in the art, and will not be repeated here.

Step [2]: According to the scene abstracted into each page and the historical test data related to the application to be tested, the edge relationship is abstracted to obtain the edge relationship between multiple scenes.

In the present disclosure, the edge relationship includes jump information between scenes and attribute information of the edge relationship, wherein the attribute information of the edge relationship may include a trigger condition for jumping to a scene where the edge relationship exists.

Wherein, the triggering condition of the scene jump includes a jump control and a jump action, that is, by applying a corresponding jump action (for example, a click action, a long press action, etc.) Scene jumps to another scene.

Step [3]: Generate a test map according to the edge relationship between multiple scenes.

Among them, in the test map, the nodes in the edge relationship are used to represent the scenes abstracted from the page, and the edges connected by nodes are used to represent the controls, actions and jump information supported by the nodes.

The following describes in detail the specific implementation manner of abstracting the edge relationship according to the scene abstracted from each page and the historical test data related to the application program to be tested in the above step [2]. Specifically, it can be realized through the following steps [21] to [23]:

Step [21]: According to the historical test data related to the application to be tested, determine the jump information between the pages of the application to be tested and the triggering conditions for page jumps.

In the present disclosure, each page of the application program to be tested is usually provided with several controls for realizing page jumps (ie, jump controls), which are used to control the application program to be tested to jump from one page to another. The jump information between pages refers to a page jump relationship that can jump from one page to another page, for example, page a jumps to page b is a page jump relationship. The jump information between pages may include a one-way jump relationship and a two-way jump relationship. Wherein, when two pages can jump to each other, it is determined that there is a bidirectional jump relationship between the two pages; There is a one-way jump relationship between them.

Exemplarily, as shown in FIG. 2 , the application program to be tested includes seven pages, namely page a1 , page a2 , page b, page c1 , page c2 , page d, and page e. Among them: there is a two-way jump relationship between page a1 and page a2, and the trigger condition for realizing the mutual jump between page a1 and page a2 includes a sliding action, wherein the jump control is empty; there is a single link between page a2 and page c1 To the jump relationship, the trigger conditions for realizing the jump from page a2 to page c1 include the control a21 in page a2 (not shown in Figure 2) and the click action, that is, by clicking the control a21 in page a2, the page a2 is realized Jump to page c1; there is a one-way jump relationship between page a2 and page c2, and the trigger conditions to realize the jump from page a2 to page c2 include the control a21 in page a2 and the long-press action, that is, by long-pressing page a2 The control a21 in the page realizes the jump from page a2 to page c2; there is a one-way jump relationship between page a1 and page b, and the trigger condition for realizing the jump from page a1 to page b includes the control a11 in page a1 (Figure 2 not shown in ) and click actions, that is, by clicking the control a11 in page a1, the jump from page a1 to page b is realized; there is a one-way jump relationship between page b and page d, and page b to page The triggering conditions for the d jump include the control b1 (not shown in Figure 2) and the click action in page b, that is, by clicking the control b1 in page b, the jump from page b to page d is realized; page d and There is a one-way jump relationship between pages e, and the trigger conditions for realizing the jump from page d to page e include the control d1 (not shown in Figure 2) in page d and the click action, that is, by clicking the Control d1 realizes the jump from page d to page e.

Step [22]: According to the jump information between the pages of the application program to be tested and the scenes abstracted from each page, determine the jump information between multiple scenes.

Specifically, for each page pair that has a jump relationship in the application program to be tested, the jump information between the page pair can be determined as the jump information between the scene pair corresponding to the page pair.

For example, as shown in Figure 2, there is a two-way jump relationship between page a1 and page a2, the scenes of page a1 and page a2 are both scene A, and the scene pair corresponding to page a1-a2 is scene A-A, therefore, scene A itself has a one-way jump relationship.

As another example, as shown in Figure 2, there is a one-way jump relationship from page a2 to page c1 between the page pair a2-c1, the scene of page a2 is scene A, the scene of page c1 is scene C, and the scene of page c1 is scene C. The pair a2-c1 corresponds to the scene pair A-C, therefore, there is a relationship between scene A and scene C that jumps from scene A to scene C.

Step [23]: Determine the triggering conditions for scene jumping according to the triggering conditions for page jumping and the scenes abstracted from each page.

Specifically, for each page pair that has a jump relationship in the application to be tested, the trigger condition for realizing the jump between the page pair can be determined as realizing the jump between the scene pairs corresponding to the page pair Turn trigger conditions.

For example, as shown in Figure 2, there is a two-way jump relationship between page a1 and page a2, and the trigger condition for realizing the mutual jump between page a1 and page a2 includes a sliding action, and the scenes of page a1 and page a2 are both scenes A, the page pair a1-a2 corresponds to the scene pair A-A, therefore, the trigger condition for realizing the jump from scene A to itself includes a sliding action, wherein the jump control is empty.

As another example, as shown in Figure 2, there is a one-way jump relationship from page a2 to page c1 between the page pair a2-c1, and the trigger condition for realizing the jump from page a2 to page c1 includes the Control a21 and click action, the scene of page a2 is scene A, the scene of page c1 is scene C, and the scene pair A-C corresponding to page pair a2-c1, therefore, the triggering conditions to realize the jump from scene A to scene C include page a2 Control a21 in and click action.

The specific implementation of determining the jump information between pages of the application to be tested and the triggering conditions for page jumps according to the historical test data related to the application to be tested in the above step [21] will be described in detail below. Specifically, it can be realized through the following steps [211] and steps [212]:

Step [211]: Obtain the random test data of the preset test tool for the application to be tested as historical test data related to the application to be tested.

Step [212]: According to the historical test data, determine the jump information between the pages of the application to be tested and the triggering conditions of the page jump.

In the present disclosure, the preset testing tool is used to perform multiple random tests on the application program to be tested to obtain random test data as historical test data related to the application program to be tested. In each random test, you can first start the application to be tested, and when the application to be tested is running, click the jump control in each page of the application to be tested to control the continuous jump of the page, thereby obtaining the application to be tested Jump information between different pages in , and trigger conditions for page jumps.

Wherein, the above-mentioned preset testing tool may be a testing installation package, for example, a Fastbot client.

The specific implementation manner of generating the test map according to the edge relationship between multiple scenes in the above step [3] will be described in detail below. Specifically, each scene in multiple scenes can be used as a node, and the scene nodes with edge relationship can be connected with directed line segments to represent the jump relationship between the two, where the starting point of the directed line segment is jump The scene node before the transfer (i.e. the source scene), the end point of the directed line segment is the scene node after the jump (i.e. the target scene), and the attribute information of the edge relationship is marked on the directed line segment, so as to obtain the application program under test Corresponding test map. Wherein, the target scene can be understood as a scene to be jumped to based on a jump action in the source scene.

Exemplarily, according to the jump information between pages shown in FIG. 2 and the triggering conditions of page jumps, the test map corresponding to the application program to be tested is constructed as shown in FIG. 3 .

In addition, in order to make the test map cover more scenarios and improve the integrity of the test map, so as to realize the comprehensive test of the application program under test as much as possible, the above test map can be updated with the update of the test data.

The specific implementation manner of determining the target test scenario configured for the application program under test in the above S101 will be described in detail below.

Specifically, in response to receiving a sequential selection operation for the scenarios to be tested in the test scenario configuration interface, the scenarios to be tested sequentially selected by the selection operation may be determined as target test scenarios.

In the present disclosure, the above-mentioned selection operation can be triggered in various ways. In one embodiment, a pre-generated test map for the application to be tested is displayed in the test scene configuration interface. In the displayed test map, select the scenarios that need to participate in the test (that is, the scenarios to be tested) in sequence, so as to realize the sequential selection of the scenarios to be tested, and configure the target test scenarios that the test needs to cover.

In another embodiment, all the scene nodes in the pre-generated test map for the application to be tested are first displayed in the test scene configuration interface, and then based on the scene selected by the user, the scene selected by the user is displayed according to the test map The downstream adjacent scene of the selected scene is for the user to further select, and then, based on the scene re-selected by the user, according to the test map, the downstream adjacent scene of the re-selected scene is displayed in the test scene configuration interface for the user to further select, and so on. , until the selection termination condition is satisfied. Specifically, before the above step of determining the scene to be tested sequentially selected by the selection operation as the target test scene, the above S101 may further include the following steps (1) to (4).

Step (1): In response to receiving a selection operation for the scene to be tested in the test scene configuration interface, acquire adjacent downstream scenes of the scene to be tested in the test map.

Wherein, the scene to be tested is initially the main page of the application program to be tested. All scene nodes in the test map are displayed in the test scene configuration interface, so that the user can select the scene to be tested by clicking.

The adjacent downstream scene of the scene to be tested is the target scene in the test map that has a jump relationship with the scene to be tested.

For example, as shown in FIG. 3 , the scene to be tested is scene A, and the adjacent downstream scenes of scene A include: scene C, scene A, and scene B.

For another example, as shown in FIG. 3 , the scene to be tested is scene B, and the adjacent downstream scene of scene B includes scene D.

Step (2): Determine whether the selection termination condition is satisfied.

In the present disclosure, if an instruction indicating termination of selection is received or the adjacent downstream scene of the scene to be tested is empty (that is, there is no adjacent downstream scene of the scene to be tested), it is determined that the selection termination condition is satisfied. If the instruction for indicating selection termination is not received and the adjacent downstream scene of the scene to be tested is not empty, it is determined that the selection termination condition is not satisfied.

If the selection termination condition is not satisfied, then perform the following steps (3) and (4), after that, return to the above step of obtaining the adjacent downstream scene of the scene to be tested in the test map, that is, return to the above step (1); if satisfied If the termination condition is selected, the above-mentioned steps of determining the scene to be tested successively selected by the selection operation as the target test scene are executed.

Step (3): Display adjacent downstream scenarios in the test scenario configuration interface.

Step (4): In response to receiving a selection operation for any adjacent downstream scene, update the scene to be tested to the selected adjacent downstream scene.

The specific implementation manner of generating a corresponding test case based on the target test scenario based on the pre-generated test map of the application program to be tested by calling in the above S102 will be described in detail below. Specifically, it can be realized through various implementation modes. In one implementation mode, firstly, each scene to be tested in the target test scene is sequentially connected according to the selected sequence to obtain the test path; then, according to the test map to obtain the attribute information of each edge in the test path; next, add the attribute information of each edge in the test path to the edge in the test path to obtain a test case.

In another embodiment, the path where the target test scene is located may be extracted from the test map as a test case. Wherein, the directional relationship of the path where the target test scene is located is determined based on the order in which each scene to be tested in the target test scene is selected.

Exemplarily, the test map is shown in Figure 3, and the target test scenarios configured by the user for the application to be tested include scenario A, scenario B, scenario D, and scenario E, and the order in which they are selected is scenario A, scenario B, scenario D. Scenario E, the test path is scenario A→scene B→scene D→scene E, and the test example is shown in Figure 4 (the jump control is not shown).

The test cases generated by the above two implementation methods are all structured, which is convenient for persistent storage, and the maintainability of the test cases is greatly enhanced. In addition, test cases include test paths, which can track the progress of test case coverage in real time, facilitate access to multiple assertion capabilities, and detect more types of problems.

In addition, after the test case is generated, it can be saved in the database, and then the test case can be obtained from the database and tested.

Fig. 5 is a block diagram of a device for generating test cases according to an exemplary embodiment. As shown in Figure 5, the device 500 includes:

The determination module 501 is used to display the test scenario configuration interface for the application to be tested, and determine the target test scenario configured for the application to be tested; the test scenario configuration interface supports performing selection operations on the interface to configure the required test scenarios. said target test scenarios covered;

The generating module 502 is configured to invoke a test map pre-generated for the application under test, and generate a corresponding test case based on the target test scenario, and the test case is used to test the application under test; wherein, The test map is a scene relationship knowledge graph constructed from the clustering information obtained by performing scene clustering on the page information of the application to be tested. The nodes in the scene relationship knowledge graph are used to represent the scenes abstracted from the page, and the nodes The connected edges are used to represent the controls, actions and jump information supported by the nodes.

In the above technical solution, firstly, a test scenario configuration interface for the application to be tested is displayed, and a target test scenario configured for the application to be tested is determined, wherein the test scenario configuration interface supports performing a selection operation on the interface to configure the required test scenario for the test. Covered target test scenarios; then, call the pre-generated test map for the application under test, and generate corresponding test cases based on the target test scenarios. In this way, the user only needs to click the scene on the test scene configuration interface to configure the target test scene to be covered by the test, which is convenient and fast. After that, the test case can be automatically generated based on the target test scene according to the pre-generated test map , instead of manually writing test cases, thereby reducing the complexity of obtaining test cases, thereby improving the efficiency of test case generation and application testing, and improving user experience.

Optionally, the device 500 also includes:

The clustering sub-module is used to traverse the extensible markup language information of the pages in the application to be tested, and perform scene clustering on the extensible markup language information of all pages to obtain multiple scenes;

The edge relationship abstraction submodule is used to perform edge relationship abstraction according to the scenes abstracted from each page and the historical test data related to the application to be tested, so as to obtain the edge relationship between the multiple scenes;

A generation sub-module is used to generate the test map according to the edge relationship between the multiple scenes, wherein the nodes in the edge relationship are used to represent the scene abstracted from the page, and the edges connected by the nodes are used to represent the nodes Supported controls, actions and jump information.

Optionally, the test map is updated as the test data is updated.

Optionally, the edge relationship abstraction submodule includes:

The first determination submodule is configured to determine the jump information between the pages and the trigger conditions for page jumps according to the historical test data related to the application under test, wherein the trigger conditions include the controls and said action;

The second determining submodule is used to determine the jump information between the multiple scenes according to the jump information between the pages and the scenes abstracted from each page;

The third determining submodule is used to determine the triggering condition of the scene jumping according to the triggering condition of the page jumping and the scene abstracted from each page.

Optionally, the determining module 501 includes:

The fourth determination sub-module is configured to, in response to receiving a sequence selection operation for the scenarios to be tested in the test scenario configuration interface, determine the scenarios to be tested sequentially selected by the selection operation as the target test scenario.

Optionally, the determining module 501 also includes:

The acquisition submodule is configured to respond to receiving the target test scenario in the configuration interface for the test scenario before the fourth determination submodule determines the scenario to be tested sequentially selected by the selection operation as the target test scenario. The selection operation of the test scene is to obtain the adjacent downstream scene of the scene to be tested in the test map, wherein the scene to be tested is initially the main page of the application to be tested;

The display submodule is used to display the adjacent downstream scene in the test scene configuration interface if the selection termination condition is not satisfied;

The first triggering submodule is configured to update the scene to be tested to the selected adjacent downstream scene in response to receiving a selection operation for any of the adjacent downstream scenes, and trigger the acquiring submodule to acquire the In the test map, adjacent downstream scenes of the scene to be tested;

The second triggering submodule is configured to trigger the fourth determination submodule to determine the scene to be tested sequentially selected by the selection operation as the target test scene if the selection termination condition is met.

Optionally, the generation module 502 is configured to extract the path where the target test scene is located from the test map as the test case.

The present disclosure also provides a computer-readable medium on which a computer program is stored, and when the program is executed by a processing device, the steps of the above-mentioned test case generation method provided by the present disclosure are realized.

Referring now to FIG. 6 , it shows a schematic structural diagram of an electronic device (such as a terminal device or a server) 600 suitable for implementing an embodiment of the present disclosure. The terminal equipment in the embodiment of the present disclosure may include but not limited to such as mobile phone, notebook computer, digital broadcast receiver, PDA (personal digital assistant), PAD (tablet computer), PMP (portable multimedia player), vehicle terminal (such as mobile terminals such as car navigation terminals) and fixed terminals such as digital TVs, desktop computers and the like. The electronic device shown in FIG. 6 is only an example, and should not limit the functions and application scope of the embodiments of the present disclosure.

As shown in FIG. 6, an electronic device 600 may include a processing device (such as a central processing unit, a graphics processing unit, etc.) 601, which may be randomly accessed according to a program stored in a read-only memory (ROM) 602 or loaded from a storage device 608. Various appropriate actions and processes are executed by programs in the memory (RAM) 603 . In the RAM 603, various programs and data necessary for the operation of the electronic device 600 are also stored. The processing device 601 , ROM 602 and RAM 603 are connected to each other through a bus 604 . An input/output (I/O) interface 605 is also connected to the bus 604 .

Typically, the following devices can be connected to the I/O interface 605: input devices 606 including, for example, a touch screen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; including, for example, a liquid crystal display (LCD), speaker, vibration an output device 607 such as a computer; a storage device 608 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 609. The communication means 609 may allow the electronic device 600 to communicate with other devices wirelessly or by wire to exchange data. While FIG. 6 shows electronic device 600 having various means, it should be understood that implementing or having all of the means shown is not a requirement. More or fewer means may alternatively be implemented or provided.

In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product, which includes a computer program carried on a non-transitory computer readable medium, where the computer program includes program code for executing the method shown in the flowchart. In such an embodiment, the computer program may be downloaded and installed from a network via communication means 609 , or from storage means 608 , or from ROM 602 . When the computer program is executed by the processing device 601, the above-mentioned functions defined in the methods of the embodiments of the present disclosure are performed.

It should be noted that the computer-readable medium mentioned above in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to, electrical connections with one or more wires, portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable Programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In the present disclosure, however, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave carrying computer-readable program code therein. Such propagated data signals may take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device . Program code embodied on a computer readable medium may be transmitted by any appropriate medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

In some embodiments, the client and the server can communicate using any currently known or future-developed network protocols such as HTTP (HyperText Transfer Protocol, Hypertext Transfer Protocol), and can communicate with digital data in any form or medium (eg, communication network) interconnections. Examples of communication networks include local area networks ("LANs"), wide area networks ("WANs"), internetworks (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed network of.

The above-mentioned computer-readable medium may be included in the above-mentioned electronic device, or may exist independently without being incorporated into the electronic device.

The above-mentioned computer-readable medium carries one or more programs, and when the above-mentioned one or more programs are executed by the electronic device, the electronic device: displays a test scenario configuration interface for the application program to be tested, and determines the The target test scene configured by the application program; the test scene configuration interface supports performing selection operations on the interface to configure the target test scene covered by the test; calling the pre-generated test map for the application to be tested, based on the The target test scenario generates a corresponding test case, and the test case is used to test the application to be tested; wherein, the test map is the clustering of the scene clustering for the page information of the application to be tested The scene relationship knowledge graph constructed by class information, the nodes in the scene relationship knowledge graph are used to represent the scene abstracted from the page, and the edges connecting the nodes are used to represent the controls, actions and jump information supported by the nodes.

Computer program code for carrying out operations of the present disclosure may be written in one or more programming languages, or combinations thereof, including but not limited to object-oriented programming languages—such as Java, Smalltalk, C++, and Includes conventional procedural programming languages - such as "C" or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user computer through any kind of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (for example, using an Internet service provider to connected via the Internet).

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in a flowchart or block diagram may represent a module, program segment, or portion of code that contains one or more logical functions for implementing specified executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or they may sometimes be executed in the reverse order, depending upon the functionality involved. It should also be noted that each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by a dedicated hardware-based system that performs the specified functions or operations , or may be implemented by a combination of dedicated hardware and computer instructions.

The modules involved in the embodiments described in the present disclosure may be implemented by software or by hardware. Among them, the name of the module does not constitute a limitation of the module itself under certain circumstances. For example, the determination module can also be described as "displaying the test scenario configuration interface for the application under test, and determining the configuration interface for the application under test. Modules for the configured target test scenarios".

The functions described herein above may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), System on Chips (SOCs), Complex Programmable Logical device (CPLD) and so on.

In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media would include one or more wire-based electrical connections, portable computer discs, hard drives, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), optical fiber, compact disk read only memory (CD-ROM), optical storage, magnetic storage, or any suitable combination of the foregoing.

According to one or more embodiments of the present disclosure, Example 1 provides a test case generation method, including: displaying a test scenario configuration interface for the application to be tested, and determining a target test scenario configured for the application to be tested; The test scenario configuration interface supports performing selection operations on the interface to configure the target test scenario to be covered by the test; call the pre-generated test map for the application to be tested, and generate a corresponding test based on the target test scenario Use case, the test case is used to test the application under test; wherein, the test map is a scene relationship knowledge graph constructed from the clustering information obtained by performing scene clustering on the page information of the application under test , the nodes in the scene relationship knowledge graph are used to represent the scene abstracted from the page, and the edges connected to the nodes are used to represent the controls, actions and jump information supported by the nodes.

According to one or more embodiments of the present disclosure, Example 2 provides the method of Example 1, and the method further includes: traversing the Extensible Markup Language information of the pages in the application to be tested, and performing the Extensible Markup Language performing scene clustering on the information to obtain a plurality of scenes; performing edge relationship abstraction according to the scene abstracted into each said page and the historical test data related to the application to be tested, to obtain the edge relationship between the multiple scenes; according to The edge relationship between the multiple scenes is used to generate the test map, wherein the nodes in the edge relationship are used to represent the scenes abstracted from the page, and the edges connected by nodes are used to represent the controls, actions and jumps supported by the nodes. transfer information.

According to one or more embodiments of the present disclosure, Example 3 provides the method of Example 2, and the test map is updated as the test data is updated.

According to one or more embodiments of the present disclosure, Example 4 provides the method of Example 2, the abstraction of the edge relationship is performed according to the scene abstracted from each page and the historical test data related to the application under test, including : According to the historical test data related to the application to be tested, determine the jump information between the pages and the trigger conditions for page jumps, wherein the trigger conditions include the controls and the actions; according to the The jump information between pages and the scenes abstracted from each of the pages, determine the jump information between the multiple scenes; according to the trigger conditions of page jumps and the scenes abstracted from each of the pages, determine Trigger conditions for scene jumps.

According to one or more embodiments of the present disclosure, Example 5 provides the method of any one of Examples 1-4, the determining the target test scenario configured for the application under test includes: responding to receiving the In the test scenario configuration interface, the sequential selection operation of the scenarios to be tested is determined as the target test scenario.

According to one or more embodiments of the present disclosure, Example 6 provides the method of Example 5, before the step of determining the scene to be tested sequentially selected by the selection operation as the target test scene, the determining The target test scenario configured for the application program to be tested further includes: in response to receiving a selection operation for the scenario to be tested in the configuration interface of the test scenario, acquiring the corresponding scene of the scenario to be tested in the test map Adjacent to the downstream scene, wherein, the scene to be tested is initially the main page of the application to be tested; if the selection termination condition is not satisfied, the adjacent downstream scene is displayed in the test scene configuration interface; in response to receiving Up to the selection operation for any of the adjacent downstream scenes, update the scene to be tested to the selected adjacent downstream scene, and return to the acquisition of the adjacent downstream scene of the scene to be tested in the test map If the selection termination condition is satisfied, then execute the step of determining the scene to be tested sequentially selected by the selection operation as the target test scene.

According to one or more embodiments of the present disclosure, Example 7 provides the method described in any one of Examples 1-4, the invoking the test map pre-generated for the application under test, based on the target test scenario Generating a corresponding test case includes: extracting a path where the target test scene is located from the test map as the test case.

According to one or more embodiments of the present disclosure, Example 8 provides a test case generation device, including: a determination module, configured to display a test scenario configuration interface for the application under test, and determine the configuration for the application under test The target test scenario; the test scenario configuration interface supports performing selection operations on the interface to configure the target test scenario covered by the test; the generation module is used to call the pre-generated test map for the application to be tested, Generate a corresponding test case based on the target test scenario, and the test case is used to test the application under test; wherein, the test map is obtained by performing scene clustering on the page information of the application under test The scene relationship knowledge graph constructed by the clustering information, the nodes in the scene relationship knowledge graph are used to represent the scene abstracted from the page, and the edges connecting the nodes are used to represent the controls, actions and jump information supported by the nodes.

According to one or more embodiments of the present disclosure, Example 9 provides a computer-readable medium on which a computer program is stored, and when the program is executed by a processing device, the steps of any one of the methods described in Examples 1-7 are implemented .

According to one or more embodiments of the present disclosure, Example 10 provides an electronic device, including: a storage device, on which a computer program is stored; a processing device, configured to execute the computer program in the storage device, to Implement the steps of any one of the methods described in Examples 1-7.

The above description is only a preferred embodiment of the present disclosure and an illustration of the applied technical principle. Those skilled in the art should understand that the disclosure scope involved in this disclosure is not limited to the technical solution formed by the specific combination of the above-mentioned technical features, but also covers the technical solutions formed by the above-mentioned technical features or Other technical solutions formed by any combination of equivalent features. For example, a technical solution formed by replacing the above-mentioned features with (but not limited to) technical features with similar functions disclosed in this disclosure.

In addition, while operations are depicted in a particular order, this should not be understood as requiring that the operations be performed in the particular order shown or performed in sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while the above discussion contains several specific implementation details, these should not be construed as limitations on the scope of the disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are merely example forms of implementing the claims. Regarding the apparatus in the foregoing embodiments, the specific manner in which each module executes operations has been described in detail in the embodiments related to the method, and will not be described in detail here.

Claims (10)

1. A test case generation method, comprising:

displaying a test scene configuration interface aiming at an application program to be tested, and determining a target test scene configured aiming at the application program to be tested; the test scene configuration interface supports executing selection operation on the interface to configure the target test scene required to be covered by the test;

invoking a test map which is generated in advance for the application program to be tested, and generating a corresponding test case based on the target test scene, wherein the test case is used for testing the application program to be tested; the test map is a scene relation knowledge graph constructed by clustering information obtained by performing scene clustering on page information of the application program to be tested, nodes in the scene relation knowledge graph are used for representing scenes abstracted by pages, and edges connected with the nodes are used for representing control, action and jump information supported by the nodes.

2. The method according to claim 1, wherein the method further comprises:

traversing the extensible markup language information of the pages in the application program to be tested, and performing scene clustering on the extensible markup language information of the full-quantity pages to obtain a plurality of scenes;

performing side relation abstraction according to the scene abstracted by each page and the history test data related to the application program to be tested, so as to obtain side relation among the scenes;

and generating the test map according to the edge relation among the scenes, wherein nodes in the edge relation are used for representing the scene abstracted by the page, and edges connected by the nodes are used for representing the control, action and jump information supported by the nodes.

3. The method of claim 2, wherein the test map is updated as the test data is updated.

4. The method according to claim 2, wherein the performing the side relation abstraction according to the scenario abstracted by each page and the historical test data related to the application under test includes:

determining jump information between pages and trigger conditions of page jumps according to historical test data related to the application program to be tested, wherein the trigger conditions comprise the control and the action;

Determining the jump information among the scenes according to the jump information among the pages and the scenes abstracted by each page;

and determining the trigger condition of scene jump according to the trigger condition of page jump and the scene abstracted by each page.

5. The method of any of claims 1-4, wherein the determining a target test scenario configured for the application under test comprises:

and in response to receiving sequential selection operation of scenes to be tested in the test scene configuration interface, determining the scenes to be tested sequentially selected by the selection operation as the target test scene.

6. The method of claim 5, wherein prior to the step of determining the scene under test sequentially selected by the selecting operation as the target test scene, the determining a target test scene configured for the application under test further comprises:

in response to receiving a selection operation for a scene to be tested in the test scene configuration interface, acquiring an adjacent downstream scene of the scene to be tested in the test map, wherein the scene to be tested Jing Chushi is a main page of the application program to be tested;

If the selection termination condition is not met, displaying the adjacent downstream scenes in the test scene configuration interface;

in response to receiving a selection operation for any adjacent downstream scene, updating the scene to be tested into the selected adjacent downstream scene, and returning to the step of acquiring the adjacent downstream scene of the scene to be tested in the test map;

and if the selection termination condition is met, executing the step of determining the scene to be tested, which is sequentially selected by the selection operation, as the target test scene.

7. The method of any of claims 1-4, wherein the invoking the test map pre-generated for the application under test, generating a corresponding test case based on the target test scenario, comprises:

and extracting a path of the target test scene from the test map as the test case.

8. A test case generating apparatus, comprising:

the determining module is used for displaying a test scene configuration interface aiming at the application program to be tested and determining a target test scene configured aiming at the application program to be tested; the test scene configuration interface supports executing selection operation on the interface to configure the target test scene required to be covered by the test;

The generating module is used for calling a test map which is generated in advance for the application program to be tested, generating a corresponding test case based on the target test scene, and the test case is used for testing the application program to be tested; the test map is a scene relation knowledge graph constructed by clustering information obtained by performing scene clustering on page information of the application program to be tested, nodes in the scene relation knowledge graph are used for representing scenes abstracted by pages, and edges connected with the nodes are used for representing control, action and jump information supported by the nodes.

9. A computer readable medium on which a computer program is stored, characterized in that the program, when being executed by a processing device, carries out the steps of the method according to any one of claims 1-7.

10. An electronic device, comprising:

a storage device having a computer program stored thereon;

processing means for executing said computer program in said storage means to carry out the steps of the method according to any one of claims 1-7.

Images