WO2021205589A1

WO2021205589A1 - Test script generation device, test script generation method, and program

Info

Publication number: WO2021205589A1
Application number: PCT/JP2020/015909
Authority: WO
Inventors: 弘之切貫
Original assignee: 日本電信電話株式会社
Priority date: 2020-04-09
Filing date: 2020-04-09
Publication date: 2021-10-14
Also published as: JP7380851B2; JPWO2021205589A1

Abstract

In order to enable efficiently generating highly maintainable test scripts, this test script generation device has: a first generation unit that refers to an operation log, in which manual operations on screens relating to one or more screen transitions, the objects of said operations, and information indicating the screen transitions are recorded, and that generates, for each pre-transition screen in a screen transition, a definition of a page object including a method that implements the sequence of operations that were performed from said pre-transition screen until transition to another screen; and a second generation unit that generates a test script by combining the aforementioned methods.

Description

Test script generator, test script generator and program

The present invention relates to a test script generation device, a test script generation method, and a program.

There are mainly two types of technologies for automating tests involving screen operations of applications that have screens, such as web applications and mobile applications, as "Record & Play" and "programming".

"Record & Play" is a technology that reproduces a user's operation by recording the user's operation as a script as it is and executing the script (see, for example, Non-Patent Document 1).

On the other hand, "programming" is a technique for describing a test code using a library for operating a browser as a program and executing a test using the test code (see, for example, Non-Patent Document 2).

However, the former ("Record & Play") has a problem of low maintainability because a simple list of user operations is generated as a test script. For example, since the identification information (locator) of a certain screen element and the same operation for a certain screen element appear in multiple places in the test script, when a change occurs in the locator or operation, it spans multiple places in the test script. It needs to be fixed.

On the other hand, the latter (“programming”) has the problem of being inefficient because it requires time and skill to implement the test script.

The present invention has been made in view of the above points, and an object of the present invention is to enable efficient generation of a highly maintainable test script.

Therefore, in order to solve the above problem, the test script generator refers to the operation log in which the manual operation for each screen related to one or more screen transitions, the target of the operation, and the information indicating each of the screen transitions are recorded. A first generation unit that generates a definition of a page object including a method for executing an operation sequence performed from the screen to another screen for each transition source screen in the screen transition, and the method. It has a second generation unit that generates a test script by combining the above.

It is possible to efficiently generate test scripts with high maintainability.

It is a figure which shows the hardware configuration example of the test script generation apparatus 10 in embodiment of this invention. It is a figure which shows the functional structure example of the test script generation apparatus 10 in embodiment of this invention. It is a flowchart for demonstrating an example of the processing procedure executed by the test script generation apparatus 10. It is a flowchart for demonstrating an example of the processing procedure of the page object generation processing. It is a flowchart for demonstrating an example of the process procedure of the test case generation process.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram showing a hardware configuration example of the test script generation device 10 according to the embodiment of the present invention. The test script generation device 10 of FIG. 1 has a drive device 100, an auxiliary storage device 102, a memory device 103, a CPU 104, an interface device 105, a display device 106, an input device 107, and the like, which are connected to each other by a bus B, respectively. ..

The program that realizes the processing in the test script generation device 10 is provided by a recording medium 101 such as a CD-ROM. When the recording medium 101 storing the program is set in the drive device 100, the program is installed in the auxiliary storage device 102 from the recording medium 101 via the drive device 100. However, the program does not necessarily have to be installed from the recording medium 101, and may be downloaded from another computer via the network. The auxiliary storage device 102 stores the installed program and also stores necessary files, data, and the like.

The memory device 103 reads and stores the program from the auxiliary storage device 102 when the program is instructed to start. The CPU 104 realizes the function related to the test script generation device 10 according to the program stored in the memory device 103. The interface device 105 is used as an interface for connecting to a network. The display device 106 displays a programmatic GUI (Graphical User Interface) or the like. The input device 107 is composed of a keyboard, a mouse, and the like, and is used for inputting various operation instructions.

FIG. 2 is a diagram showing a functional configuration example of the test script generation device 10 according to the embodiment of the present invention. In FIG. 2, the test script generation device 10 includes an operation log recording unit 11, a page object generation unit 12, a test case generation unit 13, and the like. Each of these parts is realized by a process of causing the CPU 104 to execute one or more programs installed in the test script generation device 10. The test script generation device 10 also uses the operation log storage unit 121. The operation log storage unit 121 can be realized by using, for example, an auxiliary storage device 102, a storage device that can be connected to the test script generation device 10 via a network, or the like.

Hereinafter, the processing procedure executed by the test script generation device 10 will be described. FIG. 3 is a flowchart for explaining an example of a processing procedure executed by the test script generation device 10.

In step S101, the operation log recording unit 11 logs the test based on the manual operation by the tester for the application for which the test script is generated (hereinafter, referred to as “target application”) (hereinafter, referred to as “operation log”). Is recorded in the operation log storage unit 121. The operation log includes information indicating each of the operation under test, the operation target, and the screen transition in chronological order. The information indicating the operation is information on the operation type such as click, double-click, and input. The operation target information is identification information (for example, HTML attributes such as id, name, and xpath) of the operated screen element (HTML element, etc.). The screen transition information is information including identification information (title, URL, etc.) of the transition source screen and identification information (title, URL, etc.) of the transition destination screen.

Recording of the operation log may be performed using a known method. For example, in the case of a Web application, a source code (script or the like) for detecting an operation on the screen is embedded in each HTML element in the HTML of each screen of the Web application, and the operation log recording unit 11 May record an operation log in response to the detection of the operation. Alternatively, the operation log may be recorded using the method disclosed in "https://www.ieice.org/ken/paper/2019052581N3/".

When the operation log recording is completed, step S102 and subsequent steps are executed. In addition, after step S102, it may be executed at an asynchronous timing with respect to step S101.

In step S102, the page object generation unit 12 executes the page object generation process with reference to the operation log. A page object is an object that has an operation sequence for an element (screen element) in a screen (page) as a method. Specifically, the page object generation unit 12 generates a definition of a page object class having a method corresponding to an operation sequence for the screen in the operation log for each screen transitioned in the operation log in the test script.

Subsequently, the test case generation unit 13 generates a test case by combining the methods defined in each page object, and adds the test case to the test script (S103). A test case is a unit of a test that starts from a certain screen and generates a screen transition corresponding to a path to the end screen in the screen transition. One test script contains one or more test cases.

Subsequently, the details of step S102 will be described. FIG. 4 is a flowchart for explaining an example of the processing procedure of the page object generation processing. Note that, for convenience, FIG. 4 describes a procedure for generating a class definition of a page object (that is, one page object) for one screen. Therefore, the processing procedure of FIG. 4 is executed for each screen of the transition source or transition destination in the operation log. However, if the transition to the same screen occurs a plurality of times in the operation log, the processing procedure may be executed once for the same screen. Hereinafter, the screen to be processed is referred to as a "target screen", and the page object for the target screen is referred to as a "target object".

In step S201, the page object generation unit 12 refers to the operation log and identifies the screen element that has been the operation target even once on the target screen.

Subsequently, the page object generation unit 12 adds the field (attribute) definition to the class definition of the target object for each screen element targeted for operation (S202). The name of each field (field name) is a variable name for identifying the screen element, and its value is the actual locator (for example, in the definition of HTML) of the screen element. The value used as the locator may be prioritized in the order of id, name, label, and xpath, with an emphasis on change resistance.

In the following step S203 and subsequent steps, the page object generation unit 12 executes a process for generating a method definition of the target object. In this process, a series of operations performed by the tester from the transition to the target screen to the departure from the target screen are treated as a meaningful group of operations. A series of operations performed from the transition to the target screen to the departure is called an "operation sequence". In addition, "until leaving" means until the transition from the target screen to another screen or until the end of a series of operations on the target screen.

In step S203, the page object generation unit 12 extracts the operation sequence for the target screen from the operation log. There is a possibility that a plurality of operation sequences will be extracted for one screen. This is because there can be a plurality of operation procedures for a certain screen. In the present embodiment, each operation sequence is a candidate for the method of the target object.

Subsequently, the page object generation unit 12 executes the loop process L1 for each extracted operation sequence. The operation sequence targeted for processing in the loop processing L1 is hereinafter referred to as a “target operation sequence”.

In step S204, it is determined whether or not the target operation sequence is included in another operation sequence for the target screen (hereinafter, simply referred to as "another operation sequence"). That is, when all the operation columns extracted for the target screen are adopted as methods, there is a possibility that a large number of duplicate methods will be generated when the operation log is long. The determination is for suppressing the generation of duplicate methods.

Here, the operation column A is included in the operation column B when A = B, or when the operation target column of A is A'and the operation target column of B is B', A'. Is defined as a subsequence of B'. For example, when A'= [a, b, d] and B'= [a, b, c, d], the operation sequence A is included in the operation sequence B because A'is a subsequence of B'. Will be done. At this time, since only the operation target is considered, the inclusion relationship is recognized even if the input values are different. On the other hand, when A'= [a, b, d] and B'= [a, c, d], the operation sequence A and the operation sequence B do not have an inclusion relationship with each other.

When the target operation string is included in another operation column (Yes in S204), the page object generation unit 12 operates whether or not the screen of the transition destination between the target operation column and the other operation sequence is the same. Judgment is made with reference to the log (S205). When the screen of the transition destination between the target operation sequence and the other operation sequence is the same (Yes in S205), the page object generation unit 12 does not generate the definition of the method that executes the target operation sequence.

On the other hand, when the target operation sequence is not included in the other operation sequence (No in S204), or when the transition destination screen between the target operation row and the other operation sequence is different (No in S205), the page object generation unit 12 Generates a definition of a method that executes the target operation sequence for the target object, and adds the definition to the test script (S205). At this time, the locator of the screen element targeted for each operation constituting the target operation sequence is replaced with the field name generated in step S202. By doing so, resistance to changes in the locator of each screen element is ensured. The method name is, for example, "goto <transition destination screen name> <serial number>". The developer may modify the generated method definition.

By generating a method in the processing procedure shown in steps S204 to S206, a method in which the transition destination and the operation target are unique and the operation sequence to be executed is long is generated.

Subsequently, the details of step S103 of FIG. 3 will be described. The test case generation unit 13 generates a test case to be included in the test script by combining the methods defined in the class of each page object generated in step S102.

Specifically, what kind of test case should be automated depends on the case, but in this embodiment, an example of generating a test case under the following conditions will be described.
(1) The test case group covers all screen transitions in the operation log.
(2) One test case visits the same screen only once.
(3) Under the conditions of (2), a test case in which the screen transition sequence is maximized is adopted.

The test cases that satisfy the conditions (1) to (3) often confirm one use case, and are considered to be the minimum test cases with high versatility. Even if the test case is flawed, the generated page object and test case script are highly reusable and can be modified efficiently by the developer.

An example of a test case generation method (a test case generation method satisfying the above conditions (1) to (3)) that covers screen transitions and maximizes the screen transition sequence will be described.

By analyzing the operation log, the screen transition diagram of the target application can be restored within the range of the operation log. The screen transition diagram is a graph of a tree structure in which the screen of the transition source or the transition destination is a node and the screen transition is an edge. A full search is performed on this screen transition diagram by a method such as depth-first search. As a result, the path (route) that starts from the node (root node) on the top page (login screen, etc.) and ends at the terminal node, and does not transition to the same screen (node) twice. Get a list of. One test case is a script that continuously calls the method of the page object corresponding to each screen related to the screen transition so that the screen transition related to the path is generated for each acquired path. The method corresponding to a certain screen transition is a method of the page object corresponding to the transition source screen of the screen transition, and is a method including the screen name of the transition destination screen in the method name.

FIG. 5 is a flowchart for explaining an example of the processing procedure of the test case generation process.

In step S301, the test case generation unit 13 generates a screen transition diagram of the target application based on the operation log. The screen transition diagram may be generated by using a known method.

Subsequently, the test case generation unit 13 searches a list of paths that are paths from the root node to the terminal node in the screen transition diagram and do not include the same node twice (S302).

Subsequently, the test case generation unit 13 continuously calls the method of the page object corresponding to each screen related to the screen transition so that the screen transition related to the path is generated for each searched path. Generate a test case and add the generated test case to the test script (S303).

If the function of the target application is added after the test script of the target application is generated, it is necessary to test the additional function. In this case, the additional function may be manually tested and the operation log may be recorded for the test. By executing steps S102 and S103 of FIG. 3 based on the operation log, it is possible to add a page object to the added function or screen, add a method to an existing page object, and the like. can.

As described above, according to the present embodiment, the test script is automatically generated based on the operation log recorded in the manual operation (manual test). In addition, the test script is generated by a combination of methods of page objects generated for each screen of the target application. By generating page objects based on operation logs instead of crawling logs, the possibility of unnecessary screen transitions being recorded in the log is reduced, and the generation of unnecessary page objects can be suppressed, meaning. In addition, the locator of the screen element of each screen is basically hidden by the field name (attribute name) of the page object, so the place where the locator appears is the page. Limited to object field definitions. In addition, a series of operations (login operation, etc.) for each screen are hidden in the method of the page object. As a result, it is possible to reduce the amount of modification of the test script when the locator is changed or when the operation of the screen element itself is changed. Therefore, according to the present embodiment, it is possible to efficiently generate a test script with high maintainability. That is, it is possible to generate a highly maintainable automated test script simply by performing a manual test. Even if a function is added to the test target, a test script can be generated for the new function as appropriate.

In the present embodiment, the page object generation unit 12 is an example of the first generation unit. The test case generation unit 13 is an example of the second generation unit.

Although the embodiments of the present invention have been described in detail above, the present invention is not limited to such specific embodiments, and various modifications are made within the scope of the gist of the present invention described in the claims.・ Can be changed.

10 Test script generation device 11 Operation log recording unit 12 Page object generation unit 13 Test case generation unit 100 Drive device 101 Recording medium 102 Auxiliary storage device 103 Memory device 104 CPU
105 Interface device 106 Display device 107 Input device 121 Operation log storage B bus

Claims

Refer to the operation log in which the manual operation for each screen related to one or more screen transitions, the target of the operation, and the information indicating each of the screen transitions are recorded, and for each transition source screen in the screen transition, the screen concerned. The first generator that generates the definition of the page object that contains the method that executes the operation sequence performed from to the transition to another screen, and
By combining the above methods, a second generator that generates a test script and
A test script generator characterized by having.
The first generation unit is a case where the transition destination screens of the first operation row and the second operation row for the same screen are the same, and the operation target row of the first operation row is , If it is a subsequence of the operation target column of the second operation column, the method that executes the first operation column is not generated for the page object for the screen.
The test script generator according to claim 1.
The second generator combines the methods so that all screen transitions included in the operation log occur.
The test script generator according to claim 1 or 2.
The second generator combines the methods so that the same screen only transitions once.
The test script generator according to any one of claims 1 to 3, wherein the test script generator is characterized by the above.
The second generator combines the methods so that the screen transition sequence is maximized.
The test script generator according to claim 4.
Refer to the operation log in which the manual operation for each screen related to one or more screen transitions, the target of the operation, and the information indicating each of the screen transitions are recorded, and for each transition source screen in the screen transition, the screen concerned. The first generation procedure to generate the definition of the page object including the method that executes the operation sequence performed from to the transition to another screen, and
By combining the above methods, the second generation procedure to generate the test script and
A test script generation method characterized by a computer running.
A program characterized by operating a computer as a test script generator according to any one of claims 1 to 5.