Regression test execution support device, regression test execution support method, and regression test execution support program

Abstract

This invention provides a regression test execution support device, a regression test execution support method, and a regression test execution support program that enable the application of exclusion policies without creating duplicate exclusion policies by setting exclusion policies stored in a policy management table to images. [Solution] A regression test execution support device comprising a control unit, which is capable of accessing a policy management table and a scenario management table, wherein the control unit comprises exclusion policy display means for displaying policy names stored in the policy management table as an exclusion policy list screen, and exclusion policy setting means for creating a policy linking table that links acquired images with exclusion policies set by the user via the exclusion policy list screen, wherein the policy linking table stores the scenario identifier and action identifier of the scenario management table and the policy identifier of the policy management table.

Description

Technical Field

[0001] The present invention relates to a regression test execution support apparatus, a regression test execution support method, and a regression test execution support program.

Background Art

[0002] In recent years, along with the increasing scale of systems, the need for regression tests using RPA (Robotic Process Automation) has increased. One regression test method involves performing automatic operations via a program, capturing screenshots of the screen at arbitrary timings, and comparing the captured image with screenshots captured during previous regression test executions. A problem with this method is that image differences unrelated to defects or operation changes may occur during test execution.

[0003] In response to this, Patent Document 1 discloses an information processing apparatus comprising: an image storage unit that stores, in a file format, screenshots of a screen of a target application captured in an old environment and a new environment; an exclusion policy setting unit that hierarchizes files in the image storage unit in accordance with an operator's operation on a setting screen displayed on a display unit, and hierarchically sets exclusion policies for image comparison for the hierarchized files; and a comparison unit that outputs a comparison result of the screenshot images of the old environment and the new environment stored in the image storage unit in accordance with the set exclusion policies (Claim 1).

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problem to be Solved by the Invention

[0005] While Patent Document 1 allows setting exclusion policies for hierarchically structured (grouped) images, it was necessary to create and apply separate exclusion policies for images under different groups, which required considerable effort.

[0006] The present invention has been made in view of the above, and aims to provide a regression test execution support device, a regression test execution support method, and a regression test execution support program that can apply exclusion policies without creating new and duplicate exclusion policies by setting exclusion policies stored in a policy management table to captured images in a regression test executed by an automated operation means. [Means for solving the problem]

[0007] To solve the above-mentioned problems and achieve the objective, the present invention provides a regression test execution support device comprising a control unit that supports the execution of regression tests by an automated operation means, the device being able to access a policy management table that stores the policy name and policy identifier of an exclusion policy during image comparison in the regression test, and a scenario management table that stores operation information including the scenario identifier, scenario name, tag name, and action identifier of the regression test, the control unit comprising an exclusion policy display means that displays the policy names stored in the policy management table as an exclusion policy list screen, and an exclusion policy setting means that creates a policy linking table that links images acquired in the regression test with exclusion policies set by the user via the exclusion policy list screen, the policy linking table storing the scenario identifier and action identifier of the scenario management table and the policy identifier of the policy management table.

[0008] Furthermore, the regression test execution support method according to the present invention is a regression test execution support method that supports the execution of a regression test by an automated operation means, which is executed by a regression test execution support device equipped with a control unit, and includes: an exclusion policy display step which is executed by the control unit to display the exclusion policies stored in the policy management table as an exclusion policy list screen, which is accessible to the policy management table which stores the policy name and policy identifier of the exclusion policy when comparing images in the regression test, and a scenario management table which stores operation information including the scenario identifier, scenario name, tag name and action identifier of the regression test, and the policy linking step which is executed by the control unit to create a policy linking table which links the images acquired in the regression test with the exclusion policies set by the user via the exclusion policy list screen, wherein the policy linking table stores the scenario identifier and action identifier of the scenario management table and the policy identifier of the policy management table.

[0009] Furthermore, the regression test execution support program according to the present invention is a regression test execution support program that supports the execution of a regression test by an automated operation means, which is executed by a regression test execution support device equipped with a control unit, and is able to access a policy management table that stores the policy name and policy identifier of the exclusion policy when comparing images in the regression test, and a scenario management table that stores operation information including the scenario identifier, scenario name, tag name and action identifier of the regression test, and causes the control unit to execute an exclusion policy display step that displays the exclusion policies stored in the policy management table as an exclusion policy list screen, and an exclusion policy setting step that creates a policy linking table that links the images acquired in the regression test with the exclusion policies set by the user via the exclusion policy list screen, wherein the policy linking table stores the scenario identifier and action identifier of the regression test and the policy identifier of the policy management table. [Effects of the Invention]

[0010] According to the present invention, the exclusion policy stored in the policy management table can be applied to any image without creating duplicate exclusion policies. [Brief explanation of the drawing]

[0011] [Figure 1] Figure 1 is a block diagram showing an example of the configuration of the regression test execution support device according to this embodiment. [Figure 2] Figure 2 illustrates the challenges of conventional regression test execution support devices. [Figure 3] Figure 3 is a diagram illustrating the processing of a regression test execution support device according to an embodiment. [Figure 4] Figure 4 illustrates the creation of a test scenario in the regression test execution support device of the embodiment. [Figure 5] Figure 5 illustrates the creation of a test scenario using the regression test execution support device of the embodiment. [Figure 6] Figure 6 illustrates the creation of a test scenario using the regression test execution support device of the embodiment. [Figure 7] Figure 7 illustrates the creation of a test scenario in the regression test execution support device of the embodiment. [Figure 8] Figure 8 illustrates the creation of a test scenario in the regression test execution support device of the embodiment. [Figure 9] Figure 9 illustrates the creation of a test scenario in the regression test execution support device of the embodiment. [Figure 10] Figure 10 illustrates the creation of a test scenario in the regression test execution support device of the embodiment. [Figure 11] Figure 11 illustrates the creation of a test scenario in the regression test execution support device of the embodiment. [Figure 12] Figure 12 illustrates the creation of a test scenario in the regression test execution support device of the embodiment. [Figure 13]FIG. 13 is a diagram for explaining creation of a test scenario in the regression test execution support apparatus according to the embodiment. [Figure 14] FIG. 14 is a diagram for explaining creation of a test scenario in the regression test execution support apparatus according to the embodiment. [Figure 15] FIG. 15 is a diagram for explaining creation of a test scenario in the regression test execution support apparatus according to the embodiment. [Figure 16A] FIG. 16A is a diagram for explaining creation of a test scenario in the regression test execution support apparatus according to the embodiment. [Figure 16B] FIG. 16B is a diagram for explaining creation of a test scenario in the regression test execution support apparatus according to the embodiment. [Figure 17] FIG. 17 is a diagram for explaining execution settings of a test scenario in the regression test execution support apparatus according to the embodiment. [Figure 18] FIG. 18 is a diagram for explaining a regression test execution command via an execution setting list screen. [Figure 19] FIG. 19 is a diagram showing processing of a regression test under execution condition 1 (no reference image, no exclusion policy). [Figure 20] FIG. 20 is a diagram showing an example of a result confirmation screen under execution condition 1. [Figure 21] FIG. 21 is a diagram showing an example of an image confirmation screen under execution condition 1. [Figure 22] FIG. 22 is a diagram showing processing of a regression test under execution condition 2 (with reference image, no exclusion policy). [Figure 23] FIG. 23 is a diagram showing an example of a result confirmation screen under execution condition 2. [Figure 24] FIG. 24 is a diagram showing an example of an image confirmation screen under execution condition 2. [Figure 25A] FIG. 25A is a diagram for explaining creation and registration of an exclusion policy. [Figure 25B] FIG. 25B is a diagram for explaining creation and registration of an exclusion policy. [Figure 26] FIG. 26 is a diagram for explaining association of an exclusion policy with an image. [Figure 27A] Figure 27A shows the regression test process under execution condition 3 (with reference image and exclusion policy). [Figure 27B] Figure 27B shows the regression test process under execution condition 3 (with reference image and exclusion policy). [Figure 28] Figure 28 shows an example of the result confirmation screen for execution condition 3. [Figure 29] Figure 29 shows an example of an exclusion policy pattern. [Figure 30] Figure 30 shows an example of an exclusion policy pattern. [Figure 31] Figure 31 illustrates an example of the application of the regression test execution support device according to the embodiment. [Modes for carrying out the invention]

[0012] Embodiments of the regression test execution support device, regression test execution support method, and regression test execution support program according to the present invention will be described in detail below with reference to the drawings. However, the present invention is not limited to these embodiments.

[0013] [1. Overview] Figure 2 illustrates the challenges of conventional regression test execution support devices. One regression testing method involves taking a screenshot of the screen at an arbitrary time and comparing it with a screenshot taken during a previous regression test to detect malfunctions. Noise may inevitably or accidentally occur when taking screenshots. For example, image confirmation screen MA-1 in Figure 2 is a screenshot taken during a regression test on 2024 / 04 / 01, and image confirmation screen MA-2 is a screenshot taken on 2024 / 04 / 02. By comparing the two images, a difference image MA-3 is generated, and if there is a difference, it is highlighted in red or other colors.

[0014] When displaying the screen, a business requirement dictates that the reference date field be set to the date the screen was launched. Therefore, each time the regression test program is run, the reference date will be detected as a difference. There is a desire to remove such foreseeable image differences as noise by applying an exclusion policy. The regression test execution support device of this embodiment can apply exclusion policies to arbitrary images by applying an exclusion policy stored in the policy management table, without creating duplicate exclusion policies. Furthermore, it is possible to set exclusion policies by specifying image regions or screen elements.

[0015] [2. Structure] An example of the configuration of the regression test execution support device 100 according to this embodiment will be described with reference to Figure 1. The regression test execution support device 100 can be configured, for example, on a low-code platform. Alternatively, it may be configured on a no-code platform. Figure 1 is a block diagram showing an example of the configuration of the regression test execution support device 100. The regression test execution support device 100 is a system for executing regression tests used by users such as scenario creators and testers. Here, a tester is a person who verifies the operation of the applications stored in the regression test execution support device 100. In addition to execution by scenario creators and testers, the execution of regression tests also includes periodic automatic execution by the system.

[0016] The regression test execution support device 100 may be a stationary information processing system such as a workstation or desktop personal computer, or an information processing system such as a commercially available notebook personal computer.

[0017] The regression test execution support device 100 comprises a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each part of the regression test execution support device 100 is connected to communicate via any communication path.

[0018] The communication interface unit 104 connects the regression test execution support device 100 to the network 300 via a communication system such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has the function of communicating data with other devices via a communication line. Here, the network 300 has the function of connecting the regression test execution support device 100 with other devices such as terminals (equipped with browsers) used by scenario creators and testers (not shown), a server 200, etc., in a way that enables mutual communication, and is, for example, the internet or a LAN (Local Area Network). Note that the development application DB 106a, the automatic operation unit 102a, and the application 102f, which will be described later, may be installed in other systems.

[0019] The input / output interface unit 108 is connected to an input device 400 and an output device 500. The output device 500 can be a monitor (including a home television), a speaker, or a printer. The input device 400 can be a keyboard, a mouse, a microphone, or a monitor that works in conjunction with the mouse to provide pointing device functionality. In the following, the output device 500 may be referred to as the monitor 114, and the input device 400 as the keyboard 112 or mouse 112.

[0020] The memory unit 106 stores various databases, tables, and files. The memory unit 106 also stores computer programs that work in cooperation with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. As the memory unit 106, for example, a memory system such as RAM (Random Access Memory) or ROM (Read Only Memory), a fixed disk system such as a hard disk, a flexible disk, and an optical disk can be used.

[0021] The storage unit 106 includes a development application DB 106a, etc. The development application DB 106a is a development database that stores a scenario management table 106b, a definition management table 106c, an execution setting management table 106d, a policy linking table 106e, a policy management table 106f, an execution result table 106g, an execution result details table 106h, a comparison image management table 106i, a reference image management table 106j, a file comparison result management table 106k, a layout definition table 106l, etc.

[0022] The scenario management table 106b stores the regression test scenarios executed by the automated operation unit 102a, which will be described later. As shown in an example in Figure 16B, the scenario management table 106b includes the regression test scenario identifier, scenario CD, scenario name, tag name, and operation information. The operation information in the scenario management table 106b includes, for example, a start action identifier and action for each regression test. The tag name is a name set based on the execution frequency of the regression test (daily, monthly, as needed, etc.). The start action identifier is a list of identifiers for the RPA operation that starts the regression test. An action means the smallest unit of operation and is defined by an action identifier and operation type. An operation type is a classification of RPA operations, and typical operation types include "launch screen," "operate screen," "operate basic page," "operate system common search dialog," "pause," and "screenshot."

[0023] The definition management table 106c can be composed of tables that associate and register, for example, a definition ID, a definition name, control information, action information, and logic flow information, as shown in an example in Figure 6.

[0024] The execution setting management table 106d contains the execution setting name, execution target, and execution setting identifier, which are set for the purpose of performing regression testing. As shown in Figure 17 as an example, the execution setting management table 106d stores an automatically assigned identifier (execution setting identifier), a name (execution setting name), and an execution target (type, tag name). In the execution setting management table 106d in Figure 17, identifier "J1" is the execution setting management table for "daily regression testing," and identifier "J2" is the execution setting management table for "weekly regression testing." "Daily regression testing" is a tag intended for periodic execution, approximately once a day, and "weekly regression testing" is a tag intended for periodic execution, approximately once a week. If the "daily" tag is associated with the scenario management table 106b, that regression test is for "daily regression testing," and if the "weekly" tag is associated, that regression test is for "weekly regression testing." Other tags include "monthly (approximately once a month)" and "as needed (executed as required)."

[0025] The policy linking table 106e is an information table that shows whether or not an exclusion policy is set for each action in the regression test. As shown in Figure 26 as an example, the policy linking table 106e stores the regression test scenario identifier and action identifier in association with the policy identifier.

[0026] The policy management table 106f stores the definitions of exclusion policies for image comparison in regression tests. The policy management table 106f stores automatically assigned policy identifiers, policy names, and exclusion methods. As shown in Figure 25B as an example, the policy management table 106f stores definitions for two policy identifiers: "P1" for "specifying screen elements" and "P2" for "specifying regions" as exclusion methods. The policy identifier "P1" for "specifying screen elements" is defined by the "screen identifier" and "screen element identifier" of the screen element to be excluded, while the policy identifier "P2" for "specifying regions" is defined by the identifier, X coordinate, Y coordinate, width, and height of the region to be excluded.

[0027] The execution results table 106g is a table containing information about the execution results of the regression test. As shown in an example in Figure 19, the execution results table 106g includes an automatically assigned execution ID, user information, a regression test execution setting identifier, execution start date and time, execution end date and time, status information, etc.

[0028] The execution results details table 106h is a table containing result information about the scenarios, actions, etc., for which regression tests are performed. As shown in an example in Figure 19, the execution results details table 106h includes the execution ID, scenario identifier, action identifier, execution start date and time, execution end date and time, status information, etc.

[0029] The comparison image management table 106i is a table that stores screenshot files taken during regression testing. As shown in Figure 19 as an example, the comparison image management table 106i stores the captured image data with the execution ID, scenario identifier, and action identifier associated with it.

[0030] The reference image management table 106j stores data related to reference images. Reference images are images previously captured by the regression test program and considered as references. As shown in examples in Figures 21 and 27A, the reference image management table 106j stores captured image data with a scenario identifier and an action identifier associated with it.

[0031] The file comparison result management table 106k is a table that stores files containing the difference images between the comparison image and the reference image. As shown in examples in Figures 22 and 27B, the file comparison result management table 106k stores the difference image data, along with the execution ID, scenario identifier, action identifier, and comparison result.

[0032] The control unit 102 is a CPU or similar component that comprehensively controls the regression test execution support device 100. The control unit 102 has internal memory for storing control programs such as the OS, programs that define various processing procedures, and required data, and executes various information processing based on these stored programs.

[0033] Functionally, the control unit 102 includes an automatic operation unit 102a, an exclusion policy display unit 102b, an exclusion policy setting unit 102c, a policy management table creation unit 102d, an execution setting management table creation unit 102e, an application 102f, and the like.

[0034] The automated operation unit 102a performs automated operations on application 102f according to the regression test scenarios registered in the scenario management table 106b. The automated operation unit 102a is, for example, an RPA-based regression test execution program. Here, a regression test execution program is a program that operates the screens of the application provided by the low-code development platform, and is the main entity that performs operations in the regression test. A scenario (test scenario) is a test scenario configured so that the RPA execution program can operate the screens of the application provided by the low-code development platform according to the expected operation procedures.

[0035] Specifically, the automated operation unit 102a retrieves the execution setting to be executed from the execution setting management table 106d based on the execution setting name specified by the user or by periodic automatic execution, extracts the regression test scenario corresponding to the specified execution setting from the scenario management table 106b, and executes it.

[0036] The exclusion policy display unit 102b displays the exclusion policies stored in the policy management table 106f as an exclusion policy list screen. In the exclusion policy list screens MJ-1 and MJ-2 shown as examples in Figures 25A and 25B, exclusion policies stored in the policy management table 106f, such as "Exclude notification area" and "Exclude reference date," are displayed.

[0037] The exclusion policy setting unit 102c creates a policy linking table 106e that links the images obtained from the regression test with the exclusion policies set by the user via the exclusion policy list screen MJ.

[0038] The policy management table creation unit 102d stores exclusion policies created by the user via the exclusion policy editing screen MB in the policy management table 106f, along with automatically assigned policy identifiers.

[0039] Application 102f is, for example, one or more business applications. The applications are stored in the memory unit 106, but the applications stored in the memory unit 106 that are executed by the control unit 102 are functionally referred to as application 102f of the control unit 102.

[0040] [3. Prerequisites for Processing] This section describes the prerequisites for the processing according to this embodiment.

[0041] (3-1) Overall diagram of the low-code platform Low-code platforms consist of a configuration screen operated by developers and an execution screen operated by users.

[0042] Figure 3 illustrates the execution flow of a regression test in the regression test execution support device 100 of the embodiment. The developer creates a test scenario using drag-and-drop operations with the mouse 400 on the scenario creation screen and instructs the regression test program to execute it using the execution settings. The created test scenario is stored in the scenario management table 106b. The created regression test scenario is set to start execution in a batch process, such as daily, by the low-code execution platform, and the execution results, such as image comparison results, are written to the file comparison result management table 106k, etc. The tester checks the execution results on the result confirmation screen MI. They also set a reference image and create and apply an image comparison policy.

[0043] (3-2) Creating Test Scenario Refer to Figures 4 to 15 to explain how to create a test scenario. Figure 4 shows an example of the display of the scenario list screen (MC) and the scenario creation screen (MD). When a scenario creator wants to create a new scenario, they create the new scenario from the scenario list screen (MC). The scenario list screen (MC) has a button to create a new scenario ("New Scenario Button"), and clicking this button launches the scenario creation screen (MC), allowing the user to create a scenario.

[0044] The Scenario List screen (MC), as shown in Figure 4, displays a list of test scenarios registered in the Scenario Management Table 106b (shown in Figure 15), including the scenario name, last updater, and update date and time, as well as a "New Scenario" button for creating a new scenario. To create a new scenario, press the "New Scenario" button, and the Scenario Creation screen (MD) will appear.

[0045] The scenario creation screen MD includes fields for setting the scenario CD and scenario name, a tag selection field, and a toggle button to switch between displaying the scenario setting area and the scenario execution area. Selecting "Settings" displays the scenario setting area, and selecting "Execute" displays the scenario execution area. In the example shown in the figure, "Settings" is selected and the scenario setting area is displayed. When creating a new scenario, the operation to launch the screen is set automatically. In the original procedure shown in the figure, the operation to launch the screen is set using the dashed lines. Tags are set according to the purpose and perspective of the test, and can be selected according to the test execution frequency (daily, monthly, as needed, etc.), the type of application being tested (master maintenance, master list, etc.), the purpose of regression testing (unit test, scenario test, batch no-impact test after program modification or environment change, etc.), the scope of test personnel (developer, tester, system-based automatic execution, etc.), and differences depending on the stage (early development, pre-delivery, post-operation, etc.).

[0046] The scenario creator sets the operations in the order in which the RPA will actually execute them. First, as shown in Figure 5, enter the scenario CD and scenario name. In the example shown in the same figure, the scenario CD is "S001" and the scenario name is "Does the new customer registration work correctly?". Refer to Figures 6 to 8 to explain how to set up the RPA operations (launching the screen, operating the screen).

[0047] (1) Select the definition to operate on. Figure 6 is a diagram illustrating the selection of definitions to be operated on. Figure 6 shows an example of the display of the scenario setting area MD-1 on the scenario creation screen MD, and an example of a definition name registered in the definition management table 106c (data such as control information, action information, and logic flow information are omitted).

[0048] In Figure 6, the scenario setting area MD-1 displays a list of all definition names present in the definition management table 106c (for example, Customer Master Maintenance (List), Customer Master Maintenance, Customer Search, Customer Master List, ...) as options. Select the definition name of the definition you want to operate on from the list. In this example, Customer Master Maintenance (List) is selected.

[0049] (2) Based on the selected definition (the definition ID is stored in the background when selected), a screen layout is created using the control information in definition management table 106c and displayed below the selected list. Hereinafter, "screen layout" refers to the screen design created from the control information stored in definition management table 106c.

[0050] Figure 7 shows an example of the display of the scenario setting area MD-2 on the scenario creation screen MD. As shown in Figure 7, below the selected definition name "Customer Master Maintenance (List)", the screen layout "Customer Master Maintenance (List) screen layout" is created and displayed based on the control information of the definition management table 106c associated with the selected definition name.

[0051] (3) Set the operation to be performed (action operation). Here, you choose whether to operate on the selected defined control or to perform other fixed operations. Figure 8 shows a list of configurable actions, including typical actions, operations, and descriptions. Here, an action refers to the smallest unit of operation. Examples of actions include "click the edit button" and "take a screenshot".

[0052] For example, the action "Launch Screen" is a "screen operation" action that sets the screen that the robot will launch first. The action "Operate Screen" is a "screen operation" action that launches or transitions from the currently running screen to another screen. The action "Basic Page Operation" is a "screen operation" action that operates controls within a specified definition. The action "Operate System Common Search Dialog" is a "screen operation" action that operates the system common search dialog. The action "Pause" is an "other" action that pauses (puts to sleep) the robot execution. The action "Screenshot" is an "other" action that saves the screen content as an image.

[0053] From here, we will skip the creation of the operation scenario for the list screen and start explaining how to create a scenario for operating the customer master maintenance screen.

[0054] (Example of operation selection 1: Operate the controls on the screen) Here, we will explain the basic page operations as actions.

[0055] 1. Click the "Add Operation" button. Refer to Figure 9 to explain what happens when you click the "Add Operation" button in the scenario setting area.

[0056] Figure 9 shows an example of the display in the scenario setting area MD-3. In the scenario setting area MD-3, the "Add Operation" button is displayed on the left, and the selected definition and its screen layout are displayed on the right. Clicking the "Add Operation" button displays the operation selection screen ME-1. On the operation selection screen ME-1, you can select "Screen Operation" or "Other" as the operation content, and "Basic Page Operation," "Screen Operation," or "Screen Operation by Page ID" as the operation. Here, operating controls within the definition is referred to as "Basic Page Operation." Also, starting to operate on other definitions in the low-code base is referred to as "Screen Operation."

[0057] 2. Select the control to operate within the definition. Refer to Figure 10 to explain how to select the control to operate within the definition. Figure 10 shows an example of the display of the scenario setting area MD-4 when the operation content "Screen Operation" and operation "Basic Page Operation" are selected in the operation selection screen ME-1 in Figure 9.

[0058] As shown in Figure 10, in the scenario setting area MD-4, "Please set up page operations" is displayed on the left. On the right, a list of control targets is displayed, showing the controllable controls within the set definition and the system's common controls that are not based on the definition settings.

[0059] In this example, the operable controls displayed within the selected definition "Customer Master Maintenance" are "Text Customer Code," "Text Revision Date," "Text Customer Name," and "Register Button (Modify)." Additionally, "Message Box Yes" and "Message Box No" are displayed as system-wide operable controls independent of the definition settings. The following explanation uses the case where "Text Customer Name" is selected as an example.

[0060] (3).2. This section explains the selection of actions based on the control selected in this section.

[0061] (Selection operation example 1: Enter text) Refer to Figure 11 to explain Selection Operation Example 1 (Entering Text). Figure 11 shows an example of the display when "Text Customer Name Text" is selected in the Scenario Setting Area MD-4 of Figure 10. As shown in Figure 11, in the Scenario Setting Area MD-5, on the right side, operation selection candidates are displayed for the control selected in Operation Target Selection, and an operation can be selected. In this example, "Enter Text" is selected as the operation. On the left side, a title is displayed which combines the name of the control selected in Operation Target Selection with the name of the operation selected in Operation Selection. In this example, the title "Enter Text in Text Customer Name Text" is displayed, which combines the Operation Target Selection "Text Customer Name Text" and the Operation Selection "Enter Text".

[0062] (Selection example 2: Click the control) Refer to Figure 12 to explain Selection Operation Example 2 (Clicking a Control). Figure 12 shows an example of the display when a button or similar is selected in the Scenario Setting Area MD-6 and "Click" is selected in the Operation Selection. In the example shown in Figure 12, "Register Button (New)" is selected in the Operation Target Selection, "Click" is selected in the Operation Selection, and the title "Click Register Button (New)" is displayed.

[0063] (Selection operation example 3: Operating other fixed operations) This section explains RPA operations such as taking screenshots and pausing.

[0064] 1. Click the "Add Operation" button in the scenario settings area. Refer to Figure 13 to explain what happens when you click the "Add Operation" button in the scenario settings area.

[0065] Figure 13 shows an example of the display of the scenario setting area MD-7. In Figure 13, clicking the "Add Operation" button displays the operation selection screen ME-2. On the operation selection screen ME-2, select "Other" for the operation content and "Screenshot" for the operation.

[0066] 2. Configure the screenshot settings. Figure 14 shows an example of the display of the scenario setting area when "Other" and "Screenshot" are selected in the operation selection screen ME-2 shown in Figure 13.

[0067] As shown in Figure 14, in the scenario setting area MD-8, the right side is used to set (input) the screenshot name and the confirmation content. In this example, the scenario creator sets (inputs) the screenshot name "Screenshot 1" and the confirmation content "Confirm that the customer name is registered". With this setting, a screenshot will be taken with the file name being the screenshot name + ".png". On the left side, a capture icon and the title "File name Screenshot name + ".png"" will be displayed.

[0068] The completed test scenario is saved in the scenario management table 106b. Figure 15 shows an example of the display of the scenario management table 106b after the action operation settings have been completed. A test scenario consists of an identifier, code, name, start action identifier, and action content (each action operation). In the example shown in Figure 15, the scenario CD is "S002", the scenario name is "Does customer registration (modification) work correctly?", the action operation start key is "A1", the action operation content is "Action identifier: A1", "Operation type: Launch screen", "Screen type: Low-code platform", "Target: Customer master maintenance (list) (definition ID)", "Action identifier list: A11, B1, A12", ...

[0069] The "Action Identifier List" is a list of action operation keys for operations performed within the screen, specified by the action operation keys. It is controlled to be nested when drawn to the screen, and the processing order is from left to right.

[0070] (3-3) Editing Test Scenario Figures 16A and 16B illustrate the editing of a test scenario in the regression test execution support device 100 of the embodiment. When a scenario creator edits a scenario, they select the scenario to edit from the scenario list screen MC. In the scenario list screen MC in Figure 16A, scenario CD "S002" and scenario name "Does the registration destination (modification) work correctly?" are selected. Clicking this launches the scenario editing screen ME, allowing the scenario to be edited. The edited test scenario is stored in the scenario management table 106b.

[0071] (3-4) Setting up the execution of the test scenario To execute a test scenario, an execution setting is created that defines the units of the scenario to be executed. Figure 17 is a diagram illustrating the execution setting of a test scenario in the regression test execution support device 100 of the embodiment.

[0072] First, select the regression test to be configured from the execution settings list screen MG. In Figure 17, the daily regression test is selected, and pressing the "Edit" button transitions to the execution settings editing screen MH. On the execution settings editing screen MH, the execution setting name is automatically entered, and tag specification is selected. Select "Daily" from the tag selection field, select "Tag Specification" as the target of the scenario to be executed, and press the "Register" button to register the configured execution setting in the execution settings management table 106d.

[0073] [4. Processing] A specific example of the processing of the regression test execution support device 100 of this embodiment will be described with reference to Figures 18 to 31. In the following description, we will explain the case where the automatic operation unit 102a is a regression test execution program.

[0074] Figure 18 illustrates the execution command for a regression test using the execution settings list screen MG. The execution settings list screen MG displays a list of execution settings registered in the execution settings management table 106d. To execute a regression test, select an execution setting name from the execution settings list and press the "Execute" button. When the "Execute" button is pressed, the regression test program retrieves the execution settings (type, tags) of the specified execution setting name from the execution settings management table 106d, reads the regression test scenario that corresponds to the retrieved execution setting, and executes the process.

[0075] Next, we will explain the processing of the regression test execution support device 100 when a regression test scenario is executed under various conditions.

[0076] (Execution condition 1: No reference image, no exclusion policy) Figure 19 shows the regression test process under execution condition 1 (no reference image, no exclusion policy), and Figure 20 shows an example of the image comparison results under execution condition 1. Figure 21 shows an example of the MA image confirmation screen under execution condition 1.

[0077] First, when the execution setting name is specified on the execution setting list screen MG and the "Execute" button is pressed, the user information that instructed the regression test, the execution setting identifier, the execution start date and time, and the status are registered in the execution result table 106g along with the execution ID which is automatically assigned. The regression test program retrieves the regression test scenario to be executed from the scenario management table 106b in the development application DB 106a (step S1). Here, as shown in the execution result table 106g, the execution setting identifier "J1" is specified, and scenarios tagged "for daily regression tests," such as scenario CDs "S001," "S002," "S003," etc., are retrieved (step S2). The regression test program executes the actions A1 to A9 to be processed for the retrieved scenarios according to the scenario management table 106b (step S3). Operations corresponding to each action are performed (step S4), and the execution ID, scenario identifier, action identifier, execution start date and time, execution end date and time, and status information are registered in the execution result details table 106h.

[0078] The regression test program determines whether an action is a screenshot acquisition operation (step S5) when an action is executed. If it is a screenshot acquisition operation (step S5: Yes), it saves the screenshot file to the comparison image management table 106i (step S6). If it is not a screenshot acquisition operation (step S5: No), it terminates execution. In this case, since actions A4 and A9 are screenshot acquisition operations, the screenshot data files are saved to the comparison image management table 106i along with the execution ID, scenario identifier, and action identifier.

[0079] Next, the regression test program determines whether or not a reference image exists (step S7). If there is no reference image in the reference image management table 106j (step S7: No), the program terminates. If there is a reference image in the reference image management table 106j (step S7: Yes), the program determines whether or not there is policy linking information in the policy linking table 106e (step S8). In this case, there is no reference image, so the program terminates. Upon termination, the execution completion date and status in the execution result table 106g-1 are updated.

[0080] If policy linking information exists in the policy linking table 106e (Step S8: Yes), the exclusion policy is retrieved (Step S9), the retrieved image is compared with the reference image (Step S10), and the comparison result is saved in the file comparison result management table 106k (Step S11).

[0081] In the MI-1 results confirmation screen shown in Figure 20, the columns for execution settings, execution user (execution start date and time), and scenario information are displayed from left to right, and the comparison results are displayed for each action on the right. In the MI-1 results confirmation screen, the results are displayed for each execution unit (each scenario), and the comparison results are displayed for actions that take screenshots. In the MI-1 results confirmation screen in Figure 20, the comparison results for execution settings (for daily regression testing), execution user (user 1, 1 hour ago), and scenario CD (S002) are displayed, and the 4th and 9th rows of the comparison results (actions A4 and A9) show that screenshots were taken. In this case, there is no reference image, so "No reference" is displayed in the comparison results column.

[0082] When you click and select the details of the comparison results on the results confirmation screen MI-1, you will be taken to an image confirmation screen, which is shown as an example in Figure 21. Figure 21 is the image confirmation screen when the 9th row of the comparison results in Figure 20 (Action A9: File name Screenshot2.png) is selected, and from left to right are the difference image MA-4, the comparison image MA-5, and the reference image MA-6. Here, the reference image MA-6 is an image that was previously taken by the regression test program and considered as the reference, but in this case there is no reference image, so it displays "No reference image exists". The comparison image MA-5 is an image taken by the most recent regression test program, and the difference image MA-4 is an image that highlights the difference between the comparison image MA-5 and the reference image MA-6. Since there is no reference image for the difference image MA-4, it displays "No difference image exists". After confirming the images, you can add, update, or add exclusion policies for reference images on the image confirmation screen as needed. By clicking the "Use this image as reference image" button displayed on comparison image MA-5, the most recently captured image can be added as reference image MA-7. The file data of the added reference image is stored in the reference image management table 106j along with the scenario identifier and action identifier.

[0083] (Execution condition 2: Reference image exists, no exclusion policy) Figure 22 shows the regression test process under execution condition 2 (reference image available, no exclusion policy), and Figure 23 shows an example of the results confirmation screen under execution condition 2. Figure 24 shows an example of the image confirmation screen under execution condition 2.

[0084] Similar to execution condition 1, when the execution setting name is specified on the execution setting list screen MG and the "Execute" button is pressed, the user information that instructed the regression test, the execution setting identifier, the execution start date and time, and the status are registered in the execution result table 106g-2 along with the execution ID. The regression test program obtains the scenario of the regression test to be executed from the scenario management table 106b in the development application DB 106a (step S1). Here, scenario CDs "S001", "S002", "S003", etc. are obtained (step S2). The regression test program executes the actions A1 to A9 to be processed according to the scenario management table 106b for the obtained scenarios (step S3). The operation corresponding to each action is performed (step S4), and the execution ID, scenario identifier, action identifier, execution start date and time, execution end date and time, and status information are registered in the execution result details table 106h-1.

[0085] The regression test program determines whether an action is a screenshot acquisition operation (step S5) when an action is executed. If it is a screenshot acquisition operation (step S5: Yes), it saves the screenshot data file to the comparison image management table 106i-1 (step S6). If it is not a screenshot acquisition operation (step S5: No), it terminates execution. In this case, since actions A4 and A9 are screenshot acquisition operations, the screenshot data file is saved to the comparison image management table 106i-1 along with the execution ID, scenario identifier, and action identifier.

[0086] Next, the regression test program determines whether or not a reference image exists (step S7). In this case, since a reference image exists in the reference image management table 106j-1 (step S7: Yes), it determines whether or not policy linking information exists in the policy linking table 106e (step S8). In this case, since no exclusion policy is registered in the policy linking table 106e (step S8: No), the program performs a comparison process between the acquired image and the reference image without acquiring an exclusion policy (step S10), and the comparison result (difference image) data is saved in the file comparison result management table 106k-1 along with the execution ID, scenario identifier, and action identifier (step S11). Here, the comparison results registered are "no difference" for the difference image of scenario identifier "S1" and action identifier "A4", and for the difference image of scenario identifier "S2" and action identifier "A4", and "difference found" for the difference image of scenario identifier "S1" and action identifier "A9", and for the difference image of scenario identifier "S2" and action identifier "A9". When execution is complete, the execution completion date and time and status in the execution result table 106g-3 are updated.

[0087] Figure 23 shows an example of the results confirmation screen MI-2, which displays the comparison result information for scenario CD "S002" in the file comparison result management table 106k-1. The 4th and 9th lines of the comparison results (actions A4 and A9) are screenshots, and the action A4 on the 4th line shows "No difference" and the action A9 on the 9th line shows "Difference found".

[0088] Selecting A9 in the comparison results on the MI-2 results confirmation screen will take you to an image confirmation screen, as shown in Figure 24. In Figure 24, the difference image MA-8, comparison image MA-9, and reference image MA-10 are displayed from left to right. Here, the reference image MA-10 is an image previously captured by the regression test program and considered the reference image, the comparison image MA-9 is an image captured by the most recent regression test program, and the difference image MA-8 is an image that highlights the differences between the comparison image MA-9 and the reference image MA-10. In the difference image MA-8, the difference portion is highlighted. In the difference image MA-8 in Figure 24, the "day" portion of the different reference dates (reference image: 2024 / 04 / 01, comparison image: 2024 / 04 / 02) between the reference image MA-10 and the comparison image MA-9 is highlighted.

[0089] The reference date in the image is a business specification that changes each time the regression test is run, and it is a difference that we want to remove as noise. In the regression test execution support device 100 of this embodiment, exclusion policies registered in the policy management table 106f can be applied to the image. In addition, exclusion policies that are not registered in the policy management table 106f are registered in the policy management table 106f after creation, so they can be applied to the image without creating new, duplicate exclusion policies.

[0090] Figures 25A and 25B illustrate the creation and registration of exclusion policies. Clicking the "Add" button on the exclusion policy list screen MJ-1 shown in Figure 25A transitions to the policy editing screen MB-1. The policy editing screen MB-1 displays fields for entering the image to which the exclusion policy will be applied, the policy name, and the method for specifying the exclusion area. In Figure 25A, "Specify screen element" is selected as the method for specifying the exclusion area.

[0091] When the "Specify Screen Element" button is pressed, the user transitions to the policy editing screen MB-2. On the policy editing screen MB-2, screen and control selection fields are displayed. In the screen selection field, definitions stored in the definition management table 106lc-1 are displayed, such as Customer List, Customer Master Maintenance, Customer Search, Customer Master List, Office Search, and Office Master Maintenance. In the control selection field, for the definition selected in the screen selection field, the layout definition table 106m stored in the definition management table 106c-1 is displayed as an option.

[0092] When a screen and control are selected on the policy editing screen MB-2 and the "Save" button is pressed, the exclusion policy with the selected content is registered in the policy management table 106f. The exclusion policy set here (identifier P1) is registered with the name "Exclusion by Reference Date", the exclusion method "Specify Screen Element", and the screen identifier "screen1" and screen element identifier "Control1-5" as the target of exclusion. Once registered in the policy management table 106f, the name of the exclusion policy is displayed on the exclusion policy list screen MJ-2, and the specified exclusion policy can be applied to any image by specifying it on the exclusion policy list screen MJ-2.

[0093] Furthermore, if "Specify Area" is selected as the exclusion method on the policy editing screen MB-1, the user can specify the area to be excluded on the screen, thereby setting the excluded area (identifier, X coordinate, Y coordinate, width, height). In addition to specifying the excluded area, exclusion policies can also be set to exclude color changes, etc.

[0094] Figure 26 illustrates the association of exclusion policies with images. By checking the checkbox for the selected exclusion policy in the exclusion policy list screen MJ-2 shown in Figure 26 and clicking the "Save" button, the image and the exclusion policy can be associated. This association displays the exclusion policy name in the image, and the exclusion policy setting unit 102c registers the policy association table 106e-1. It is also possible to apply multiple exclusion policies to a single image. Figure 26 shows a case where the scenario identifier "S2", action identifier "A9", and policy identifier "P1" are set.

[0095] (Execution condition 3: Reference image available, exclusion policy in place) Figures 27A and 27B show the regression test process under execution condition 3 (with reference image and exclusion policy), and Figure 28 shows an example of the results confirmation screen under execution condition 3.

[0096] In execution condition 3, the processing of steps S1 to S5 is performed as in execution condition 2 (not shown in the diagram), and the acquired screenshot file is saved as comparison image management table 106i-2 (step S6). Also, in this case, there is a reference image (step S7: Yes), so the regression test program determines whether or not there is policy linking information in policy linking table 106e-1 (step S8). The presence or absence of policy linking information is checked based on the scenario identifier action identifier in reference image management table 106j-2. If the image was taken with scenario identifier "S2" and action identifier "A9", then it is checked in policy linking table 106e-1 whether a policy is linked with scenario identifier "S2" and action identifier "A9". In this case, since the policy identifier "P1" is registered in the policy association table 106e-1 for the image with the action identifier "A9" of the scenario identifier "S2" (Step S8: Yes), the policy identifier is retrieved, and exclusion policy information for policy identifier "P1", such as policy name and exclusion method, is retrieved from the policy management table 106f (Step S9). After retrieving the exclusion policy information, the exclusion method of the policy is checked (Step S12), and if the exclusion method is "specify screen element", the position and size of the element are retrieved from the currently running screen based on the screen element identifier (Step S13). The screen element identifier "Control1-5" is of type "Date Text Box" in the layout definition table 106m (the part enclosed by the thick line in the result confirmation screen MA-12), and the X coordinate "1150", Y coordinate "50", width "100", and height "30" of the "Date Text Box" are retrieved from JavaScript (registered trademark). Furthermore, the policy exclusion method is checked (step S12), and if the exclusion method is "specify area", the excluded area set in policy management table 106f is retrieved from the currently running screen.

[0097] Subsequently, the acquired image is compared with the reference image, applying the exclusion policy (step S10). The comparison results (difference images) are saved in the file comparison result management table 106k-2 along with the execution ID, scenario identifier, and action identifier (step S11). The file comparison result management table 106k-2 contains the comparison results for the difference images of scenario identifier "S1" and action identifier "A4," and the difference images of scenario identifier "S2" and action identifier "A4," with no difference found. The difference images of scenario identifier "S1" and action identifier "A9," and the difference images of scenario identifier "S2" and action identifier "A9," are also recorded as no difference (policy applied). Upon completion of execution, the execution completion date and time and status in the execution result table are updated. The image comparison process first compares the acquired image with the reference image, and if a difference exists, it adjusts the comparison results by applying the exclusion policy. Therefore, even when an exclusion policy is applied, there may be cases where the comparison result is "no difference."

[0098] Figure 28 shows an example of the results confirmation screen MI-3, where the comparison results for each action are displayed in the comparison results column on the right. In Figure 28, the 4th and 9th rows of the comparison results (actions A4 and A9) are screenshots, and in this case, the 4th row for action A4 shows "No difference," and the 9th row for action A9 shows "No difference" and the result "Policy." The "Policy" display indicates that there is no difference as a result of applying the exclusion policy.

[0099] Selecting A9 in the comparison results on the results confirmation screen MI-3 transitions to the image confirmation screen MA-14, an example of which is shown in Figure 28. The displayed image also shows the policy name "Exclude Reference Date," and the difference (the "day" part of the reference date) is highlighted, with the results "No Difference" and "Policy" displayed.

[0100] The above describes the processing of regression tests with exclusion policies applied in the regression test execution support device 100. However, in addition to "exclusion of the reference date," other exclusion policies such as "exclusion of notifications" and "exclusion of case numbers in the details" can also be set.

[0101] Figures 29 and 30 illustrate examples of exclusion policy patterns. Figure 29 explains "Exclusion of Notifications," and Figure 30 explains "Exclusion of Case Number in Details." As shown in Figure 29, notifications may be displayed during regression testing, and depending on the timing of the capture, the display may be partially open or beginning to close. Since differences in the notification portion are image differences unrelated to bugs or changes in operation, an exclusion policy can be set as "Exclusion of Notifications." Also, as shown in Figure 30, since case numbers are automatically assigned, they change to requiring registration. Differences in case numbers are also image differences unrelated to bugs or changes in operation, so an exclusion policy can be set as "Exclusion of Case Number in Details." When setting "Exclusion of Notifications" or "Case Number in Details" as exclusion policies, you can either "Specify an Area" or "Specify a Screen Element." Note that when setting an exclusion policy by "Specifying a Screen Element," there is no need to recreate the policy even if the display area changes due to external factors such as changes in the OS version or monitor size (see Figure 31), or internal factors such as changes in the corresponding window size due to changes in product specifications. As shown in Figure 31, when the monitor size changes, the position (X coordinate) of the date text box also changes, so if you have specified an area, you will need to recreate the policy. Also, since it can follow design changes such as the movement of objects on the screen, the exclusion policy settings using "Specify screen elements" can also handle changes in the display area. This improves the maintainability of automated regression testing not only during the initial development of the product, but also for gradual improvements and continuous changes accompanying releases.

[0102] As described above, according to this embodiment, differences in images unrelated to defects or changes in operation are managed as exclusion policies in the master data, and exclusion policies can be applied to any image, eliminating the need to create duplicate exclusion policies and apply them to images. Furthermore, by creating the necessary exclusion policies as needed and registering them in the policy management table, it is easy to set new exclusion policies to images.

[0103] [5. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving operational efficiency and promoting appropriate management decisions by companies, thereby contributing to SDGs Goals 8 and 9.

[0104] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and digital processes, thereby contributing to SDGs Goals 12, 13, and 15.

[0105] Furthermore, this embodiment can contribute to strengthening control and governance, thereby enabling contributions to SDG Goal 16.

[0106] [6. Other Embodiments] In addition to the embodiments described above, the present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims.

[0107] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically by known methods.

[0108] Furthermore, the processing procedures, control procedures, specific names, information including parameters such as registration data and search conditions for each process, screen examples, and database configuration shown in this specification and in the drawings may be changed at will unless otherwise specified.

[0109] Furthermore, with respect to the regression test execution support device 100, each component shown in the diagram is a functional concept and does not necessarily need to be physically configured as shown.

[0110] For example, the processing functions of the regression test execution support device 100, particularly those performed in the control unit, may be implemented entirely or partially by a CPU and a program interpreted and executed by the CPU, or they may be implemented as wired logic hardware. The program is recorded on a non-temporary computer-readable recording medium containing programmed instructions for the information processing system to execute the processing described in this embodiment, and is mechanically read by the regression test execution support device 100 as needed. That is, a storage unit such as ROM or HDD (Hard Disk Drive) contains a computer program that works in cooperation with the OS to give instructions to the CPU and perform various processing tasks. This computer program is executed by being loaded into RAM and works in cooperation with the CPU to constitute the control unit.

[0111] Furthermore, this computer program may be stored on an application program server connected to the regression test execution support device 100 via any network, and it is possible to download all or part of it as needed.

[0112] Furthermore, the program for executing the processing described in this embodiment may be stored on a non-temporary computer-readable recording medium, or it may be configured as a program product. Here, "recording medium" includes any "portable physical medium" such as memory cards, USB (Universal Serial Bus) memory, SD (Secure Digital) cards, flexible disks, magneto-optical disks, ROMs, EPROMs (Erasable Programmable Read Only Memory), EEPROMs (Registered Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROMs (Compact Disk Read Only Memory), MOs (Magneto-Optical disks), DVDs (Digital Versatile Disks), and Blu-ray (Registered Trademark) Discs.

[0113] Furthermore, "program" refers to a data processing method described in any language or writing method, regardless of its format, such as source code or binary code. Note that "program" is not necessarily limited to a single, monolithic structure; it also includes distributed structures consisting of multiple modules or libraries, and those that work in cooperation with other programs, such as an operating system, to achieve their functions. Regarding the specific configuration and reading procedures for reading the recording medium in each system shown in the embodiments, as well as the installation procedures after reading, well-known configurations and procedures can be used.

[0114] The various databases stored in the memory unit include memory systems such as RAM and ROM, fixed disk systems such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and website provision.

[0115] Furthermore, the regression test execution support device 100 may be configured as an information processing system such as a known personal computer or workstation, or as an information processing system to which any peripheral system is connected. Alternatively, the regression test execution support device 100 may be implemented by implementing software (including programs or data, etc.) that enables the processing described in this embodiment into the system.

[0116] Furthermore, the specific forms of system distribution and integration are not limited to those shown in the diagram, and all or part of it can be configured by functionally or physically distributing and integrating it in any unit according to various additions or functional loads. In other words, the embodiments described above may be implemented in any combination, or the embodiments may be implemented selectively. [Industrial applicability]

[0117] This invention is applicable to all industries and sectors. [Explanation of Symbols]

[0118] 100 Regression Test Execution Support Device 102 Control Unit 102a Automatic operation section 102b Exclusion Policy Display Section 102c Exclusion Policy Settings Section 102d Policy Management Table Creation Section 102e Execution Settings Management Table Creation Section 102f Application 104 Communication Interface Section 106 Storage section 106a Development application database 106b Scenario Management Table 106c Definition Management Table 106d Execution Settings Management Table 106e Policy Mapping Table 106f Policy Management Table 106g Execution Result Table 106h Execution Results Detailed Table 106i Comparison Image Management Table 106j Reference Image Management Table 106k File Comparison Results Management Table 106l Layout Definition Table 108 Input / Output Interface Section 200 servers 300 Networks 400 Input Devices 500 Output Device

Claims

1. A regression test execution support device equipped with a control unit and supporting the execution of regression tests by an automated operation means, A policy management table that stores the policy name and policy identifier of the exclusion policy used in the image comparison in the regression test, A scenario management table that stores operational information including the scenario identifier, scenario name, tag name, and action identifier for the regression test, Accessible, The control unit, An exclusion policy display means that displays the policy names stored in the policy management table as an exclusion policy list screen, An exclusion policy setting means creates a policy linking table that links the images obtained in the regression test with the exclusion policies set by the user via the exclusion policy list screen, Equipped with, The regression test execution support device is characterized in that the policy linking table stores the scenario identifier and action identifier from the scenario management table and the policy identifier from the policy management table.

2. A policy management table creation means creates an exclusion policy management table containing an automatically assigned policy identifier, policy name, and elements to be excluded, based on exclusion policies created by the user via the exclusion policy editing screen. The regression test execution support device according to claim 1, characterized by comprising the following:

3. An execution setting management table containing the execution setting name, the execution target, and the execution setting identifier, which are set for the purpose of performing the aforementioned regression test. Accessible, The regression test execution support device according to claim 1, characterized in that the automatic operation means obtains the execution target of the execution setting name specified by the execution setting instruction from the execution setting management table, extracts the regression test of the execution target from the scenario management table, and executes it, based on the execution setting name specified by the execution setting instruction from the user.

4. The regression test execution support device according to claim 3, characterized in that the automated operation means, in each action of the regression test, refers to the policy linking table, obtains the setting information of the exclusion policy, and, if an exclusion policy is set, compares the image of the old environment obtained in the regression test with the image of the new environment according to the set exclusion policy and outputs the comparison result.

5. An execution setting management table creation means that creates the execution setting management table using the execution pattern set by the user via the execution setting editing screen. The regression test execution support device according to claim 3, characterized by comprising the above.

6. A regression test execution support method that supports the execution of a regression test by an automated operation means, which is performed by a regression test execution support device equipped with a control unit, A policy management table that stores the policy name and policy identifier of the exclusion policy used in the image comparison in the regression test, A scenario management table that stores operational information including the scenario identifier, scenario name, tag name, and action identifier for the regression test, Accessible, To be executed by the control unit, An exclusion policy display step that displays the exclusion policies stored in the policy management table as an exclusion policy list screen, An exclusion policy setting step creates a policy linking table that links the images obtained in the regression test with the exclusion policies set by the user via the exclusion policy list screen, Includes, A regression test execution support method characterized in that the policy linking table stores the scenario identifier and action identifier from the scenario management table and the policy identifier from the policy management table.

7. A regression test execution support program that assists in the execution of a regression test by an automated means, which is executed by a regression test execution support device equipped with a control unit, A policy management table that stores the policy name and policy identifier of the exclusion policy used in the image comparison in the regression test, A scenario management table that stores operational information including the scenario identifier, scenario name, tag name, and action identifier for the regression test, Accessible, The control unit, An exclusion policy display step that displays the exclusion policies stored in the policy management table as an exclusion policy list screen, An exclusion policy setting step creates a policy linking table that links the images obtained in the regression test with the exclusion policies set by the user via the exclusion policy list screen, A regression test execution support program characterized in that it executes the following, and the policy linking table stores the scenario identifier and action identifier of the regression test and the policy identifier of the policy management table.

Images