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 an exclusion policy master to captured images. [Solution] A regression test execution support device comprising a control unit, which is capable of accessing an exclusion policy master and a scenario management table, wherein the control unit comprises exclusion policy display means for displaying policy names stored in the exclusion policy master 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 exclusion policy master.

Description

Technical Field

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

Background Art

[0002] In recent years, with the increasing scale of systems, the need for regression tests using RPA (Robotic Process Automation) has been growing. As one of the regression test methods, there is a method in which automatic operations are performed by a program, screen shots of the screen are taken at arbitrary timings, and the screen shots taken when the regression test was previously executed are compared with the images. As a problem of this method, there may be cases where differences in images that have nothing to do with defects or operation changes occur during test execution.

[0003] On the other hand, Patent Document 1 discloses an image storage unit that stores screen shots of the old environment and the new environment of the screen of a target application in a file format, and according to the operation of an operator on a setting screen displayed on a display unit, hierarchizes the files in the image storage unit, and an exclusion policy setting means for hierarchically setting an exclusion policy for image comparison for the hierarchized files, and a comparison means for outputting a comparison result of the images of the screen shots of the old environment and the new environment in the image storage unit according to the set exclusion policy. An information processing apparatus characterized by including these is described.

Prior Art Documents

Patent Documents

[0004] [[ID=XX]]

Patent Document 1

Summary of the Invention

Problems 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 an exclusion policy master 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 a regression test by an automated operation means, wherein the device is able to access an exclusion policy master that stores the policy name and policy identifier of the exclusion policy during image comparison in the regression test, and a scenario management table that stores operation information including the scenario identifier, scenario name, regression test name, and action identifier of the regression test, and the control unit comprises an exclusion policy display means that displays the exclusion policies stored in the exclusion policy master 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, wherein the policy linking table stores the scenario identifier and action identifier of the regression test and the policy identifier of the exclusion policy master.

[0008] Furthermore, the regression test execution support device according to the present invention is characterized by comprising: an exclusion policy management table creation means that stores exclusion policies created by the user via the exclusion policy editing screen together with automatically assigned policy identifiers in the exclusion policy master, and creates an exclusion policy management table that includes policy identifiers, policy names, and exclusion areas.

[0009] Furthermore, the regression test execution support device according to the present invention is capable of accessing an execution setting management table that includes an execution setting name set for the purpose of performing the regression test, an execution target, and an execution setting identifier, and the automatic operation means is characterized in that, based on the execution setting name specified by the execution setting instruction from the user, it obtains the execution target of the specified execution setting name from the execution setting management table, extracts the regression test of the execution target from the scenario management table, and executes it.

[0010] Furthermore, the regression test execution support device according to the present invention is characterized in that, in each action of the regression test, the automatic operation means refers to the policy linking master, 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.

[0011] Furthermore, the regression test execution support device according to the present invention is characterized by comprising an execution setting management table creation means that creates the execution setting management table using an execution pattern set by the user via an execution setting editing screen.

[0012] 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 allows access to an exclusion policy master 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, regression test name, and action identifier of the regression test, and which is executed by the control unit to display the exclusion policies stored in the exclusion policy master as an exclusion policy list screen, and an exclusion policy setting step which creates a policy linking table which links images acquired in the regression test 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 regression test and the policy identifier of the exclusion policy master.

[0013] 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 an exclusion policy master 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, regression test 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 exclusion policy master 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 exclusion policy master. [Effects of the Invention]

[0014] According to the present invention, there is an effect that an exclusion policy stored in an exclusion policy master can be applied to any image without duplicating the exclusion policy.

Brief Description of Drawings

[0015] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a regression test execution support apparatus according to the present embodiment. [Figure 2] FIG. 2 is a diagram for explaining the setting of an exclusion policy for an image. [Figure 3] FIG. 3 is a diagram for explaining the processing of the regression test execution support apparatus according to the embodiment. [Figure 4] FIG. 4 is a diagram showing the relationship between a scenario editing screen and a scenario management table. [Figure 5] FIG. 5 is a diagram showing the relationship between an execution setting editing screen and an execution setting management table. [Figure 6] FIG. 6 is a diagram for explaining an execution command for a regression test on an execution setting list screen. [Figure 7] FIG. 7 is a diagram showing the processing of a regression test under execution condition 1 (no reference image, no exclusion policy). [Figure 8] FIG. 8 is a diagram showing an example of a result confirmation screen under execution condition 1. [Figure 9] FIG. 9 is a diagram showing an example of an image confirmation screen under execution condition 1. [Figure 10] FIG. 10 is a diagram showing the processing of a regression test under execution condition 2 (with reference image, no exclusion policy). [Figure 11] FIG. 11 is a diagram showing an example of a result confirmation screen under execution condition 2. [Figure 12] FIG. 12 is a diagram showing an example of an image confirmation screen under execution condition 2. [Figure 13] FIG. 13 is a diagram for explaining the creation and registration of an exclusion policy. [Figure 14] FIG. 14 is a diagram for explaining the association of an exclusion policy with an image. [Figure 15]FIG. 15 is a diagram showing the process of the regression test under Execution Condition 3 (with a reference image and an exclusion policy). [Figure 16] FIG. 16 is a diagram showing an example of the result confirmation screen under Execution Condition 3. [Figure 17] FIG. 17 is a diagram showing an example of the pattern of the exclusion policy. [Figure 18] FIG. 18 is a diagram showing an example of the pattern of the exclusion policy.

Embodiments for Carrying Out the Invention

[0016] Hereinafter, embodiments of the regression test execution support device, the regression test execution support method, and the regression test execution support program according to the present invention will be described in detail based on the drawings. Note that the present invention is not limited by this embodiment.

[0017] [1. Configuration] An example of the configuration of the regression test execution support device 100 according to this embodiment will be described with reference to FIG. 1. The regression test execution support device 100 can be configured with, for example, a low-code base. Note that it may be configured with a no-code base. FIG. 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 a regression test used by users such as scenario creators and testers. Here, a tester is a person who checks the operation of the applications stored in the regression test execution support device 100. In addition, the execution of the regression test includes regular automatic execution by the system in addition to scenario creators and testers.

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

[0019] 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.

[0020] 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.

[0021] 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.

[0022] 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.

[0023] The storage unit 106 includes a development application DB 106a, etc. The development application DB 106a is a development database that stores an exclusion policy master 106b, a scenario 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, etc.

[0024] The exclusion policy master 106b stores the exclusion policies used for image comparison in regression tests. The exclusion policy master 106b includes the policy name and an automatically assigned policy identifier.

[0025] The scenario management table 106c stores the regression test scenarios executed by the automated operation unit 102a, which will be described later. As shown in an example in Figure 4, the scenario management table 106c includes the regression test scenario identifier, scenario CD, scenario name, tag name, and operation information. The operation information in the scenario management table 106c 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."

[0026] 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 an example in Figure 5, 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 5, 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 about once a day, and "weekly regression testing" is a tag intended for periodic execution about once a week. If the "daily" tag is associated with the scenario management table 106c, 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)."

[0027] 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 15 as an example, the policy linking table 106e stores the regression test scenario identifier and action identifier in association with the policy identifier.

[0028] The policy management table 106f stores information about areas of an image that are excluded from comparison under an exclusion policy. As shown in Figure 15 as an example, the policy management table 106f stores information about the policy identifier, policy name, and excluded area for each exclusion policy. The excluded area is defined by an identifier, X coordinate, Y coordinate, width, and height.

[0029] Execution Results Table 106g is a table containing information on the execution results of regression tests. Execution Results Table 106g includes an automatically assigned execution ID, user information, regression test execution setting identifier, execution start date and time, execution end date and time, status information, etc.

[0030] The execution results details table 106h is a table containing result information about the scenarios and actions used in the regression test. 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.

[0031] The comparison image management table 106i is a table that stores screenshot files taken during regression testing. The comparison image management table 106i stores each captured image with an associated execution ID, scenario identifier, and action identifier.

[0032] The reference image management table 106j contains reference images, which are images previously captured by the regression test program and considered as references. Each captured image is associated with a scenario identifier and an action identifier and stored accordingly.

[0033] 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. The file comparison result management table 106k stores the difference image, along with the execution ID, scenario identifier, action identifier, and comparison result.

[0034] 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.

[0035] 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.

[0036] The automated operation unit 102a performs automated operations on application 102f according to the regression test scenarios registered in the scenario management table 106c. The automated operation unit 102a is, for example, an RPA 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.

[0037] 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 instructed by the user or by periodic automatic execution, extracts the regression test scenario corresponding to the instructed execution setting from the scenario management table 106c, and executes it.

[0038] The exclusion policy display unit 102b displays the exclusion policies stored in the exclusion policy master 106b as an exclusion policy list screen. In the exclusion policy list screen MA shown as an example in Figure 2, exclusion policies stored in the exclusion policy master 106b, such as "Exclude notification area" and "Exclude reference date," are displayed.

[0039] 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 MA.

[0040] The policy management table creation unit 102d stores the exclusion policies created by the user via the exclusion policy editing screen in the exclusion policy master 106b along with the automatically assigned policy identifier, and also creates a policy management table 106f that includes the policy identifier, policy name, and exclusion area.

[0041] 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.

[0042] [2. 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 2 to 18. In the following description, we will explain the case where the automatic operation unit 102a is a regression test execution program.

[0043] Figure 2 illustrates the setting of an exclusion policy for images. In the regression test execution support device 100 according to this embodiment, the user selects an exclusion policy to be set for images taken in the regression test from among the exclusion policies displayed on the exclusion policy list screen MA. When the checkbox for an exclusion policy displayed on the exclusion policy list screen MA, as shown in Figure 2, is checked and saved, the specified exclusion policy is set on the image confirmation screen MB. In Figure 2, the exclusion policy "Exclude Reference Date" is selected and displayed on the image confirmation screen MB.

[0044] Figure 3 illustrates the processing of the regression test execution support device 100 according to this embodiment, where Figure 3(A) shows the execution of a regression test scenario and Figure 3(B) shows the process of confirming the results of image comparison. The regression test execution support device 100 creates a regression test scenario using the scenario creation screen, and the created scenario is stored in the development application DB as a scenario management table 106c. Furthermore, when an execution setting name is selected from the execution settings in the execution setting management table 106d stored in the development application DB and an execution instruction is given to the regression test program, the regression test program reads the regression test scenario of the specified execution setting and executes the process. The execution results are written to the development application DB, and the captured image and the reference image are compared. On the results confirmation screen, the execution results are confirmed, the reference image is set, and the image comparison policy (exclusion policy) is applied and created.

[0045] Figure 4 shows the relationship between the scenario editing screen and the scenario management table. When a scenario is selected on the scenario list screen MC, which is shown as an example in Figure 4, the user transitions to the scenario editing screen MD. After finishing editing the scenario on the scenario editing screen MD and pressing the "Register" button, the edited content is stored in the scenario management table 106c.

[0046] Figure 5 shows the relationship between the execution settings editing screen and the execution settings management table. To register the execution settings for a regression test, select the execution settings on the execution settings list screen ME (shown as an example in Figure 5), press the "Edit" button, and then specify the target of the scenario to be executed on the execution settings editing screen MF that appears, and register it. In the example shown in Figure 5, the execution setting name "Daily Regression Test" is selected, and "Tagged" is selected as the target of the scenario to be executed. Upon registration of this execution setting, the execution settings management table 106d is stored. In the execution setting management table 106d, the execution setting identifier "J1" will execute the regression test scenario tagged "Daily".

[0047] Figure 6 illustrates the execution command for a regression test using the execution settings list screen. The execution settings list screen ME 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.

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

[0049] (Execution condition 1: No reference image, no exclusion policy) Figure 7 shows the regression test process under execution condition 1 (no reference image, no exclusion policy), and Figure 8 shows an example of the image comparison results under execution condition 1. Figure 9 shows an example of the image confirmation screen under execution condition 1.

[0050] First, when the execution setting name is specified on the execution setting list screen ME 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 106c 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 106c (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.

[0051] 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 files are saved to the comparison image management table 106i along with the execution ID, scenario identifier, and action identifier.

[0052] 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. When the program terminates, the execution termination date and time and status in the execution result table 106l are updated.

[0053] 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).

[0054] In the results confirmation screen MG shown in Figure 8, the fields 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 results confirmation screen MG, the results are displayed for each execution unit (each scenario), and the comparison results are displayed for actions that take screenshots. In the results confirmation screen MG in Figure 8, the comparison results are for execution settings (for daily regression testing), execution user (user 1, 1 hour ago), and scenario CD (S002). The 4th and 9th rows of the comparison results (actions A4 and A9) show that screenshots were taken, and in this case there is no reference image, so the result "No reference" is displayed.

[0055] When you click and select the comparison result on the results confirmation screen MG, you will be taken to the image confirmation screen MB, which is shown as an example in Figure 9. Figure 9 shows the image confirmation screen MB after selecting the 9th row (Action A9) of the comparison result in Figure 8, with the difference image, comparison image, and reference image from left to right. Here, the reference image is an image previously taken by the regression test program and considered as the reference; in this case, there is no reference image, so "No reference image exists" is displayed. The comparison image is an image taken by the most recent regression test program, and the difference image is an image that highlights the difference between the comparison image and the reference image. Since there is no reference image, "No difference image exists" is displayed for the difference image. After confirming the images, you can add, update, or add exclusion policies for reference images on the image confirmation screen MB as needed. By clicking the "Make this image the reference image" button displayed on the comparison image, you can add the most recently taken image as the reference image. The added reference image file is stored in the reference image management table 106j along with the scenario identifier and action identifier.

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

[0057] Similar to execution condition 1, when the execution setting name is specified on the execution setting list screen ME 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. The regression test program obtains the scenario of the regression test to be executed from the scenario management table 106c 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 106c 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.

[0058] 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 files are saved to the comparison image management table 106i along with the execution ID, scenario identifier, and action identifier.

[0059] 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 (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) is saved in the file comparison result management table 106k 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 a difference 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 are updated in the execution result table 106l.

[0060] Figure 11 shows an example of the results confirmation screen MG, which displays the comparison result information for scenario CD "S002" in the file comparison result management table 106k. The 4th and 9th rows of the comparison result (actions A4 and A9) indicate that screenshots have been taken, with "No difference" displayed in action A4 on the 4th row and "Difference found" in action A9 on the 9th row.

[0061] Selecting A9 in the comparison results on the results confirmation screen MG will transition to the image confirmation screen MB, an example of which is shown in Figure 12. In Figure 12, the difference image, comparison image, and reference image are displayed from left to right. Here, the reference image is an image previously taken by the regression test program and considered as the reference, the comparison image is an image taken by the most recent regression test program, and the difference image is an image that highlights the differences between the comparison image and the reference image. In the difference image, the differences are highlighted. In the difference image in Figure 12, the "day" part of the different reference dates (reference image: 2024 / 04 / 01, comparison image: 2024 / 04 / 02) is highlighted.

[0062] 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 exclusion policy master 106b can be applied to the image. In addition, exclusion policies that are not registered in the exclusion policy master 106b are registered in the exclusion policy master 106b after creation, so they can be applied to the image without creating new, duplicate exclusion policies.

[0063] Figure 13 illustrates the creation and registration of exclusion policies. Clicking the "Add" button in the exclusion policy list screen (MA) shown in Figure 13 transitions to the policy editing screen (MI). The policy editing screen (MI) displays fields for entering the image to which the exclusion policy applies and the policy name. In Figure 13, the numerical portion of the reference date is highlighted with a frame, and "Exclude Reference Date" is entered as the policy name. When the user identifies the area to be excluded, enters the exclusion policy name, and clicks the "Save" button, a policy management table 106f containing the automatically assigned policy identifier, policy name, and excluded area is registered. After registration, the policy name of the created exclusion policy is displayed on the policy editing screen (MI), allowing the created exclusion policy to be applied to captured images. In addition to specifying excluded areas, exclusion policies can also be configured to exclude color changes, among other things.

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

[0065] (Execution condition 3: Reference image available, exclusion policy in place) Figure 15 shows the regression test process under execution condition 3 (with reference image and exclusion policy), and Figure 16 shows an example of the results confirmation screen under execution condition 3.

[0066] Under execution condition 3, the processing of steps S1 to S6 is performed as in execution condition 2 (not shown in the diagram), and the acquired screenshot file is saved as the comparison image management table 106i. Also, in this case, since there is a reference image (step S7: Yes), the regression test program determines whether or not there is policy linking information in the policy linking table 106e (step S8). The presence or absence of policy linking information is checked based on the scenario identifier action identifier in the reference image management table 106j. If the image was taken with scenario identifier "S2" and action identifier "A9", the program checks in the policy linking table 106e whether a policy is linked to the action identifier "A9" with scenario identifier "S2". In this case, since the policy identifier "P1" is registered in the policy linking table 106e for the image with scenario identifier "S2" and action identifier "A9" (step S8: Yes), the policy identifier is obtained, and exclusion policy information for policy identifier "P1", such as policy name and exclusion area, is obtained from the policy management table 106f (step S9). After obtaining the exclusion policy information, the acquired image is compared with the reference image, applying the exclusion policy (step S10). The comparison result (difference image) is saved in the file comparison result management table 106k along with the execution ID, scenario identifier, and action identifier (step S11). The file comparison result management table 106k contains the comparison results for the difference image of scenario identifier "S1" and action identifier "A4", and the difference image of scenario identifier "S2" and action identifier "A4", with no difference found. The difference image of scenario identifier "S1" and action identifier "A9", and the difference image of scenario identifier "S2" and action identifier "A9", with no difference found (policy applied). When the execution is completed, the execution completion date and time and status are updated in the execution result table 106l. The image comparison process first compares the acquired image with the reference image, and if a difference exists, it adjusts the comparison result by applying the exclusion policy. Therefore, even when an exclusion policy is applied, there are cases where the comparison result is "no difference".

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

[0068] When you select A9 in the comparison results on the results confirmation screen MG, you are taken to the image confirmation screen MB, which is shown as an example in Figure 16. 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.

[0069] The above describes how regression tests are processed using exclusion policies in the regression test execution support device 100. Other exclusion policies besides "exclusion of the reference date" are described below.

[0070] Figures 17 and 18 illustrate examples of exclusion policy patterns. Figure 17 explains "Exclusion of Notifications," and Figure 18 explains "Exclusion of Case Number in Details." As shown in Figure 17, notifications may be displayed during regression testing, and depending on the timing of the image capture, the display may be partially open or beginning to close. Since the difference in the notification portion is an image difference unrelated to a bug or change in operation, an exclusion policy can be set as "Exclusion of Notifications." Also, as shown in Figure 18, the case number is automatically assigned, so it changes to requiring registration. Since the difference in the case number is also an image difference unrelated to a bug or change in operation, an exclusion policy can be set as "Exclusion of Case Number in Details."

[0071] 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, 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 exclusion policy master, it is possible to easily set new exclusion policies to images.

[0072] [3. 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.

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

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

[0075] [4. 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.

[0076] 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.

[0077] 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.

[0078] 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.

[0079] 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.

[0080] 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.

[0081] 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.

[0082] 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.

[0083] 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.

[0084] 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.

[0085] 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]

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

[0087] 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 Exclusion Policy Master 106c Scenario 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 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, An exclusion policy master that stores the policy name and policy identifier of the exclusion policy used for 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 exclusion policy master 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 exclusion policy master.

2. A policy management table creation means stores exclusion policies created by the user via the exclusion policy editing screen in the exclusion policy master along with automatically assigned policy identifiers, and creates an exclusion policy management table that includes the policy identifier, policy name, and exclusion area. 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, An exclusion policy master that stores the policy name and policy identifier of the exclusion policy used for 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 exclusion policy master 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 of the scenario management table and the policy identifier of the exclusion policy master.

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, An exclusion policy master that stores the policy name and policy identifier of the exclusion policy used for 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 exclusion policy master 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 exclusion policy master.

Images