JP6891779B2 - Test script modifiers and programs - Google Patents

Description

The present invention relates to a test script modification device and a program.

As a method for automating tests involving screen operations, methods using capture & replay and programming are widely used.

In capture & replay, when the user performs an operation on the screen, the operation performed by the user is recorded as a test script. In the next and subsequent tests, the test can be performed automatically by executing the test script. The advantage of capture & replay is that you can easily implement a test script by operating the screen without programming skills. The disadvantages are that the test script is output as a list of operations, so the readability of the test script is low and it is difficult to modularize the test script. Selenium IDE, Selenium Builder, etc. are commonly used tools for capture and replay.

On the other hand, in the programming method, the test script is implemented using a programming language such as Ruby or Java (registered trademark). A program indicating the operation to be performed in the test is described as a test script using the API for operating the screen, and the test is automatically performed by executing the test script. The advantages of the programming method are that it is highly flexible and can be expected to be highly maintainable depending on the skill of the implementer. The disadvantage is that you need to understand the programming language to use it, and the quality of the test script depends on the skill of the implementer. Selenium Web Driver is famous as an API for operating Web screens.

Maurizio Leotta, Andrea Stocco, Filippo Ricca, Paolo Tonella, Using Multi-Locators to Increase the Robustness of Web Test Cases Internaional Conference on Software Testing, Verification and Validation (ICST) 2015 Shauvik Roy Choudhary, Dan Zhao, Husayn Versee, Alessandro Orso, Water: Web Application TEst Repair, Proceedings of the First International Workshop on End-to-End Test Script Engineering (ESTE) 2011 Why do Record / Replay Tests of Web Applications Break ?, Mouna Hammoudi, Gregg Rothermel, Paolo Tonella, Software Testing, Verification and Validation (ICST) 2016

Test scripts are used to streamline regression testing. Regression testing is a test to check whether existing functions are adversely affected when software is modified. By automating the regression test execution, man-hours can be expected to be reduced compared to when the test is executed manually.

However, when the software is modified, it may be necessary to modify the test script in accordance with the modification. If it takes a lot of man-hours to modify the test script, the expected man-hour reduction effect may not be obtained.

With any of the capture and replay and programming techniques described above, test script maintenance issues are unavoidable. When the programming method is used, it is possible to reduce the number of corrections when corrections are necessary by appropriately modularizing them.

However, even with proper modularization, maintenance work is always required, and testers do not always have such skills. Therefore, there is a strong demand in the development field that anyone can easily maintain the test script.

By the way, it is known that locator modifications account for 70% or more of all test script modifications (Non-Patent Document 3). The locator is an identifier for uniquely identifying the screen element to be operated (one element in the screen such as a button or a form) in the test script, and id, name, XPath, or the like can be used. If the id, name, XPath, etc. of the screen element are changed by modifying the application, it is necessary to modify the corresponding locator in the test script. When a person edits a locator directly, there are the following problems.
-Even if you look at the locator, you may not know which screen element you are operating, so you need to refer to the document or test procedure manual.
-In order to describe the locator in the script, it is necessary to refer to HTML or use a specific tool.
-There is a risk of making mistakes when writing a locator.

In order to reduce the burden of locator modification, research on automatic locator modification is being conducted as in Non-Patent Documents 1 and 2.

However, automatic locator correction has the following problems. That is, if an error other than the locator appears, the test script cannot be executed after that, and the error of the locator that appears after that cannot be corrected. In addition, since the accuracy of correction may be low in automatic correction, human review is required after all, and if it is incorrect, manual correction is required.

The present invention has been made in view of the above points, and an object of the present invention is to improve the accuracy and efficiency of correction of identification information of screen elements in a test script.

Therefore, in order to solve the above problem, the test script correction device performs the operation target screen element between the screen elements for each test script instruction in which the identification information of the screen element of the first screen is included as the information indicating the operation target. Of the acquisition unit that acquires the values of a plurality of indexes used for calculating the similarity of the above first screen and stores each acquired value in the storage unit, and the instruction included in the test script, the first Regarding the first command in which the first screen element related to the identification information that does not exist with respect to the second screen is the operation target, each value stored in the storage unit with respect to the first screen element and the second screen. based on the value of the plurality of indices are obtained for each screen element, the said first screen element, calculates the similarity between each screen element of the second screen, on the calculated degree of similarity Based on this, on the second screen, the search unit that searches for candidates for the screen element that is the operation target of the first command and the screen elements related to the searched candidates are displayed so that the user can know the order of the similarity. and enhancement unit for highlighting in the second screen, by the identification information of the screen element that is selected by the user from the highlighted screen element, and a correcting section for correcting the identification information for the first instruction ,
Have.

It is possible to improve the accuracy and efficiency of modifying the identification information of screen elements in the test script.

It is a figure for demonstrating the system configuration example in embodiment of this invention. It is a figure which shows the hardware configuration example of the test execution apparatus 10 in embodiment of this invention. It is a figure which shows the functional structure example of the test execution apparatus 10 in embodiment of this invention. It is a flowchart for demonstrating an example of the processing procedure executed by the test execution apparatus 10. It is a flowchart for demonstrating an example of a process procedure of acquisition process of screen element information of an old screen. It is a figure for demonstrating an example of a test script. It is a figure which shows the structural example of the screen element information storage unit 122. It is a flowchart for demonstrating an example of the processing procedure of the test process of a new application.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram for explaining a system configuration example according to an embodiment of the present invention. In FIG. 1, the server device 20 and the test execution device 10 are connected via a network such as a LAN (Local Area Network) or the Internet.

The server device 20 is a computer having an application that generates a screen. The old revision and the new revision of the application are implemented in the server device 20. For example, the Web server may be used as the server device 20. Note that the screen configurations (that is, the configurations of screen elements included in the screen) do not always match between revisions. Further, in the data in which the screen elements included in the screen are defined (for example, HTML (HyperText Markup Language) or XML (eXtensible Markup Language), hereinafter referred to as "screen definition data"), the same screen elements are used across revisions. The identity of the locators assigned to (corresponding screen elements) is not guaranteed. The same screen element (corresponding screen element) means, for example, a set of screen elements that have the same function and use (that is, meaning) and are recognized to be the same from the viewpoint of a person.

The screen element refers to an element such as a button, an input form, or a link that constitutes a screen (Web screen or the like). One screen element can be defined by, for example, one HTML tag or XML tag and can have a nested structure. The locator refers to the information given as an identifier to each screen element in the screen definition data. For example, id, name, XPath, etc. are used as locators.

The test execution device 10 is a computer that executes a regression test for the application of the server device 20. In a regression test, a test script created for a screen generated by an application of an old revision (hereinafter referred to as "old application") is generated by an application of a new revision (hereinafter referred to as "new application"). It is executed efficiently by applying it to the screen. The test script is data in which an operation procedure for a screen is defined, and is data including information indicating a locator of a screen element to be operated and an operation content for each operation command. A PC (Personal Computer), a smartphone, a tablet terminal, or the like may be used as the test execution device 10.

FIG. 2 is a diagram showing a hardware configuration example of the test execution device 10 according to the embodiment of the present invention. The test execution device 10 of FIG. 2 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 execution 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 execution 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. 3 is a diagram showing a functional configuration example of the test execution device 10 according to the embodiment of the present invention. In FIG. 3, the test execution device 10 includes a test script acquisition unit 11, a test execution unit 12, a screen display control unit 13, an element information acquisition unit 14, a target element candidate search unit 15, a highlight unit 16, a selection unit 17, and a test. It has a script correction unit 18, a weight calculation unit 19, 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 execution device 10.

The test execution device 10 also uses the test script storage unit 121, the screen element information storage unit 122, the screen history storage unit 123, the weight storage unit 124, and the like. Each of these storage units can be realized by using, for example, a storage device that can be connected to the auxiliary storage device 102 or the test execution device 10 via a network.

The test script acquisition unit 11 acquires the test script corresponding to the old application from the test script storage unit 121.

The screen display control unit 13 displays each of the screen of the old application (hereinafter referred to as "old screen") and the screen of the new application (hereinafter referred to as "new screen"). For example, the screen display control unit 13 may be realized based on the Web browser.

The test execution unit 12 executes a test for each of the old screen and the new screen by using the test script acquired by the test script acquisition unit 11.

The element information acquisition unit 14 acquires the values (index values) of a plurality of indexes for evaluating the similarity between the screen elements, the image data of the display range of the screen elements, and the like for each screen element of the old screen. .. The acquired index value group and image data are stored in the screen element information storage unit 122. In a broad sense, image data can be said to be an example of index values.

In the target element candidate search unit 15, during the execution of the test for the new application (new screen), the locator specified to indicate the screen element to be operated is used for the new screen among the instruction group of the test script. For commands that do not exist, search for screen element candidates that are presumed to be the operation target from the screen elements of the new screen. More specifically, the target element candidate search unit 15 is a plurality of indexes used for calculating the similarity between image elements between the screen element corresponding to the locator on the old screen and each screen element on the new screen. The candidate is searched for by comparing the values of.

The highlight unit 16 highlights (highlights) a plurality of candidates searched by the target element candidate search unit 15 on a new screen.

The selection unit 17 accepts the user to select one of the highlighted screen elements.

The test script modification unit 18 modifies the test script to a state corresponding to the new application (new screen) based on the selection result by the user.

The weight calculation unit 19 stores the weights for each index used by the target element candidate search unit 15 in the screen history storage unit 123 when calculating the similarity between each screen element of the old screen and each screen element of the new screen. Calculate statistically based on the stored information. The calculation result (weight of each index) is stored in the weight storage unit 124. In the present embodiment, the weight calculation method is not limited to a predetermined method.

The screen history storage unit 123 stores image data and index value groups for each screen element of the screen of each revision of the application.

The test execution device 10 may have the function of the server device 20. In this case, the server device 20 does not have to be arranged.

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

In step S101, the screen display control unit 13 displays the screen (old screen) of the old application of the server device 20 on the display device 106. Specifically, the screen display control unit 13 accesses the old application of the server device 20, downloads the screen definition data, and displays the old screen based on the screen definition data.

Subsequently, the test script acquisition unit 11 acquires the test script corresponding to the old application from the test script storage unit 121 and stores it in the memory device 103 (S102). In the following, the “test script” refers to a test script stored in the memory device 103.

Subsequently, the test execution device 10 executes the acquisition process of the screen element information of the old screen (S103). In step S103, while executing the test script on the old screen, each screen element targeted for execution in the test script among the screen elements of the old screen is evaluated for similarity with other screen elements. Each value (index value) of the plurality of indexes, image data of the display range of the screen element, and the like are acquired. The acquired index value group and image data are stored in the screen element information storage unit 122.

Subsequently, the test execution device 10 executes the test process of the new application (S104). In the test process, the test script corresponding to the old screen is applied to the new screen, and the regression test is executed for the new application. In the process of regression testing, if the screen element corresponding to the locator (hereinafter referred to as "target locator") that is the operation target of the operation instruction in the test script does not exist on the new screen, the screen element corresponding to the target locator Candidates are searched for. Information or the like stored in the screen element information storage unit 122 is used to search for the candidate. When the candidate is searched, the candidate is highlighted on the new screen. When one of the highlighted candidates is selected by the user, the target locator is rewritten by the selected candidate locator, and the regression test is continued.

Subsequently, the details of step S103 will be described. FIG. 5 is a flowchart for explaining an example of the processing procedure of the acquisition process of the screen element information of the old screen.

In step S201, the test execution unit 12 determines whether or not the next instruction c is present in the test script. The next instruction c means an instruction whose execution order is the first among the unexecuted instructions.

FIG. 6 is a diagram for explaining an example of a test script. In FIG. 6, the screen g1 is an example of the displayed screen. The screen definition data h1 is screen definition data for a part of the screen g1 (screen element e1). Table T1 is a tabular representation of the test script for screen g1.

In table T1, each row corresponds to one operation. That is, the test script includes instructions, locators, values, etc. for each operation. The instruction is information indicating the type of operation. In FIG. 6, "type", "click" and the like are exemplified. “Type” means inputting a value to the screen element to be operated. "Click" means a click of a screen element to be operated. The locator is the locator of the screen element to be operated. The value is a value applied to the screen element to be operated. In this way, the test script includes the operation content (instruction and value) and the operation target (locator) for each operation. The test script also defines the order of each operation. For example, in table T1, the top row is executed first.

When the test script has the following instruction c (Yes in S201), the test execution unit 12 executes the instruction c for the screen element corresponding to the instruction c on the old screen (S202).

Subsequently, the element information acquisition unit 14 identifies the screen element (hereinafter, referred to as “target element”) operated by the command c (S203). The target element may be specified by, for example, the locator corresponding to the instruction c. Subsequently, the element information acquisition unit 14 acquires each index value related to the target element from the screen definition data of the old screen (S204). Here, index values of a plurality of indexes are acquired.

The indicators are, for example, the attributes of the screen element (id, type, class, name, tag name, etc.), the position information of the screen element (XPath, x coordinate, y coordinate, width, height), and the text related to the screen element (XPath, x coordinate, y coordinate, width, height). Link text, nearby text, URL, etc.). The link text is an index when the screen element is a link, and indicates a character string to which the link is attached. The text in the vicinity is text displayed around the display range of the screen element (for example, within a range of a predetermined number of pixels such as top, bottom, left, right, etc.). The display range of the screen element may be, for example, the minimum circumscribing rectangle of the screen element. In addition, the index value may be acquired for each of about 20 kinds of indexes.

Subsequently, the element information acquisition unit 14 stores the acquired index value group in the screen element information storage unit 122 in association with the target element (S205).

Subsequently, the element information acquisition unit 14 acquires a screenshot (image data) of the old screen (S206). Subsequently, the element information acquisition unit 14 acquires (cuts out) image data of the display range of the target element from the screenshot (S207). The display range of the target element can be specified based on, for example, the position information of the target element included in the screen definition data of the old screen. Subsequently, the element information acquisition unit 14 stores the acquired image data in the screen element information storage unit 122 in association with the target element (S208).

When step S202 and subsequent steps are executed for all the instructions of the test script (No in S201), the processing procedure of FIG. 5 ends. As a result, the screen element information storage unit 122 stores the index value group and the image data of each screen element operated by the test script among the screen elements of the old screen.

FIG. 7 is a diagram showing a configuration example of the screen element information storage unit 122. As shown in FIG. 7, the screen element information storage unit 122 stores the index value group and the image data for each screen element to be operated in the order of the instructions executed in the test script. In FIG. 7, the column of "screen elements" may be, for example, a locator of screen elements.

Subsequently, the details of step S104 of FIG. 4 will be described. FIG. 8 is a flowchart for explaining an example of the processing procedure of the test processing of the new application.

In step S301, the screen display control unit 13 displays the screen (new screen) of the new application of the server device 20 on the display device 106. Specifically, the screen display control unit 13 accesses the new application of the server device 20, downloads the screen definition data, and displays the new screen based on the screen definition data.

Subsequently, steps S302 and subsequent steps are executed in order from the first instruction of the test script. The test script is a test script stored in the memory device 103 in step S102. That is, the test script is a test script corresponding to the old application.

In step S302, the test execution unit 12 determines whether or not the next instruction c is present in the test script. When the test script has the following instruction c (Yes in S302), the test execution unit 12 executes the instruction c for the screen element corresponding to the instruction c on the new screen (S303).

Subsequently, the test execution unit 12 determines whether or not the locator of the instruction c is incorrect (S304). That is, the presence or absence of the locator in the screen definition data of the new screen is determined. The determination can be made by referring to the screen definition data of the new screen. If the locator of the instruction c is correct (No in S304), steps S302 and subsequent steps are repeated.

When the locator of the instruction c is incorrect (that is, when the screen element related to the locator is not included in the new screen) (Yes in S304), the target element candidate search unit 15 uses the locator (hereinafter, "former locator"). ”), The target element candidate search process is executed (S305). In the target element candidate search process, candidates for screen elements (hereinafter referred to as “target elements”) corresponding to the locator of the instruction c (hereinafter referred to as “target element candidates”) are searched among the screen elements of the new screen. Will be done. In the search, the similarity between each screen element of the new screen and the screen element having the locator on the old screen (hereinafter referred to as "original element") is calculated. Details of the similarity will be described later.

If the screen element having the locator of the instruction c is not included in the new screen, the execution of the instruction c fails in step S303. Therefore, the steps S304 and subsequent steps may be executed when the execution of the instruction c fails.

Subsequently, the highlight unit 16 highlights and displays one or more target element candidates searched in the target element candidate search process on a new screen (S306). At this time, the color of the highlight may be changed according to the similarity so that the user can understand the order of the similarity. The form of highlighting is not limited to a predetermined one. For example, a frame may be added around the target element candidate, or a color may be added to the background of the target element candidate. Further, when the target element candidate is a character string, the typeface of the character string may be changed. Highlighting may be performed by other methods.

Subsequently, the selection unit 17 accepts the selection (for example, click) of any target element candidate from the highlighted target element candidates from the user (S307). In step S306, a list of target element candidates may be displayed. In step S307, any target element candidate may be selected by the user from the list. That is, the GUI (Graphical User Interface) for accepting the target element candidate from the user does not have to be limited to a predetermined one.

Subsequently, the test script modification unit 18 modifies the locator of the instruction c in the test script by the locator of the selected target element candidate in the test script (S308). That is, the locator of the instruction c is replaced by the locator of the selected target element candidate.

Subsequently, steps S302 and subsequent steps are repeated. That is, the regression test is continued. As described above, in the present embodiment, when the instruction in which the screen element corresponding to the locator is not found is executed, the locator is modified at that time and the test is continued.

Subsequently, the details of the target element candidate search process will be described. Here, the locator of the screen element e (that is, the original element) to be operated by the instruction c is defined as le. Also, let E be a set of screen elements existing on the screen (new screen) of the new application.

In the present embodiment, the target element candidate search unit 15 quantitatively calculates the similarity of the screen elements before and after the modification using a plurality of indexes of the screen elements, so that the screen elements are semantically equal to e. Estimate e'∈ E. The higher the similarity, the more likely it is to be a modified locator. The indicators used are classified into the following four categories.
・ Attributes (id, class, name, etc.)
・ Position (XPath, coordinates)
・ Text (link text, nearby text)
-Image (rendered screen element image)
That is, the index stored in the screen element information storage unit 122 is used.

The target element candidate search unit 15 first calculates the similarity in each index for e and e', and then integrates them to calculate one similarity. The value of each index related to e is stored in the screen element information storage unit 122 (for example, it is stored in the screen element information storage unit 122 in association with le). On the other hand, the value of each index related to e'may be calculated by the same method as that calculated for e, for example, at the timing of step S305.

Let I be the set of indexes that e and e'have in common, and let ei be the value of i ∈ I in e. Here, Max (i) is the maximum value that | ei-e'i | can take, Lev (ei, e'i) is the Levenshtein distance between ei and e'i, and MaxLength (ei, e'i). ) Is the longer character string length of the character string lengths of ei and e'i, and the target element candidate search unit 15 has a similarity s (ei, e'i) between ei and e'i. 0 ≦ s (ei, e'i) ≦ 1) is calculated as follows.

If ei is a number:

ｅｉが画像または特定の文字列（タグ名など）の場合：

If ei is an image or a specific string (such as a tag name):

ｅｉが任意の文字列の場合：

If ei is an arbitrary character string:

各指標について算出された類似度ｓ（ｅｉ，ｅ'ｉ）を統合するにあたって、それぞれ画面要素の類似度に寄与する度合いが異なると考えられる。例えば、異なる画面要素が同じｉｄを持つことはないが、異なる画面要素が同じｃｌａｓｓを持つことは起こりうるため、ｃｌａｓｓの一致はｉｄの一致に比べて類似度に寄与する度合いが小さいと考えられる。これを考慮し、対象要素候補探索部１５は、各指標について、ｓ（ｅｉ，ｅ'ｉ）を算出した後、重み記憶部１２４に記憶された重みｗｉで加重平均を計算することで、ｅとｅ'との類似度Ｓ（ｅ、ｅ'）（０≦Ｓ（ｅ、ｅ'）≦１）を算出する。

In integrating the similarity s (ei, e'i) calculated for each index, it is considered that the degree of contribution to the similarity of the screen elements is different. For example, different screen elements do not have the same id, but different screen elements can have the same class, so class matching is considered to contribute less to similarity than id matching. .. In consideration of this, the target element candidate search unit 15 calculates s (ei, e'i) for each index, and then calculates the weighted average with the weight wi stored in the weight storage unit 124. And e'similarity S (e, e') (0 ≦ S (e, e') ≦ 1) is calculated.

対象要素候補探索部１５は、類似度ＳがＮ番目までの画面要素ｅ'を対象要素候補の探索結果とする。又は、類似度Ｓが閾値以上である全ての画面要素ｅ'が対象要素候補とされてもよい。

The target element candidate search unit 15 sets the screen element e'with the similarity S up to the Nth as the search result of the target element candidate. Alternatively, all screen elements e'in which the similarity S is equal to or greater than the threshold value may be selected as target element candidates.

For example, if N = 4, the target element candidate search unit 15 outputs four target element candidates e'1, e'2, e'3, and e'4 as search results in the order of similarity S.

The highlight section 16 distinguishes e'1 to e'4 by highlighting them with different colors. The user selects and clicks on a screen element that he or she thinks should be manipulated from among the highlighted ones. The test script modification unit 18 replaces the locator of the instruction c with the locator of the screen element clicked by the user. For example, if e'2 is selected, the locator of instruction c is rewritten to locator le'2. When the locator modification for instruction c is complete, the test resumes. By repeating this operation until the test is completed, the correction work is completed.

As described above, according to the present embodiment, candidates for screen elements to be operated in the test in the modified application (new application) are recommended visually on the browser in an easy-to-understand manner, and from one or more candidates. The test script is modified based on the candidates selected by the user. Therefore, it is possible to improve the accuracy and efficiency of the correction of the identification information of the screen element in the test script.

For example, since it is not necessary to understand in advance which screen element each instruction of the test script was trying to operate, it is possible to reduce the need for the person in charge of testing to refer to a document or the like.

In addition, since it can be modified by simply clicking a screen element on the browser, it is possible to reduce the need for the tester to refer to HTML or use a specific tool to describe the locator. At this time, humans always check it, so it can be corrected correctly.

In addition, mistakes when modifying the locator are reduced, and there is no need to repeatedly execute tests to check the operation.

In addition, even if an error other than the locator appears, only that part can be corrected by a human, and the locator can be corrected interactively.

In the present embodiment, the test execution device 10 is an example of a test script correction device. The locator is an example of identification information. The old screen is an example of the first screen. The new screen is an example of the second screen. The element information acquisition unit 14 is an example of an acquisition unit. The target element candidate search unit 15 is an example of the search unit. The test script correction unit 18 is an example of the correction unit. The highlight section 16 is an example of a highlight section. The screen element information storage unit 122 is an example of a storage unit. The original element is an example of the first screen element.

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 aspects are within the scope of the gist of the present invention described in the claims. It can be transformed and changed.

10 Test execution device 11 Test script acquisition unit 12 Test execution unit 13 Screen display control unit 14 Element information acquisition unit 15 Target element candidate search unit 16 Highlight unit 17 Selection unit 18 Test script correction unit 19 Weight calculation unit 20 Server device 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 Test script storage unit 122 Screen element information storage unit 123 Screen history storage unit 124 Weight storage unit B bus

Claims (4)

For each instruction of the test script in which the identification information of the screen element of the first screen is included as the information indicating the operation target, the value of a plurality of indexes used for calculating the similarity between the screen elements of the operation target. Is acquired with respect to the first screen, and each acquired value is stored in the storage unit.
Among the instructions included in the test script, the first instruction in which the first screen element related to the identification information that does not exist with respect to the second screen is the operation target is stored in the storage unit with respect to the first screen element. Similarity between the first screen element and each screen element of the second screen , based on the respective values and the values of the plurality of indicators acquired for each screen element of the second screen. A search unit that calculates the degree and searches for a candidate for a screen element that is an operation target of the first instruction on the second screen based on the calculated similarity.
A highlighting section that highlights the screen elements related to the searched candidates on the second screen so that the user can understand the order of the similarity.
The identification information of the screen element that is selected by the user from the highlighted screen element, and a correcting section for correcting the identification information for said first instruction,
A test script modification device characterized by having. The search unit calculates the similarity between the value related to the first screen element and the value related to each screen element of the second screen for each index, and the similarity for each index is calculated for each index. By calculating the weighted average based on the weight, the similarity between the first screen element and each screen element of the second screen is calculated.
The test script correction device according to claim 1 , wherein the test script is modified. It has a test execution unit that executes a plurality of instructions included in the test script in order on the second screen.
When the test execution unit determines in the first instruction to be executed that the first screen element related to the identification information that does not exist on the second screen is the operation target.
The search unit searches for candidates for the operation target of the first instruction on the second screen, and searches for candidates.
The highlighting section highlights the screen element related to the searched candidate.
The correction unit corrects the first instruction based on the identification information of the screen element related to the candidate selected by the user.
The test execution unit executes the modified first instruction, and then executes the instruction following the first instruction.
The test script correction device according to claim 1 or 2, wherein the test script is modified. For each instruction of the test script in which the identification information of the screen element of the first screen is included as the information indicating the operation target, the value of a plurality of indexes used for calculating the similarity between the screen elements of the operation target. With respect to the first screen, and the acquisition procedure of storing each acquired value in the storage unit,
Among the instructions included in the test script, the first instruction in which the first screen element related to the identification information that does not exist with respect to the second screen is the operation target is stored in the storage unit with respect to the first screen element. Similarity between the first screen element and each screen element of the second screen , based on the respective values and the values of the plurality of indicators acquired for each screen element of the second screen. A search procedure for calculating the degree and searching for a candidate for a screen element to be operated by the first instruction on the second screen based on the calculated similarity.
A highlighting procedure for highlighting the screen elements related to the searched candidates on the second screen so that the user can see the order of the similarity.
The identification information of the screen element that is selected by the user from the highlighted screen element, the modification procedure to modify the identification information for said first instruction,
A program characterized by having a computer execute.

Images