JP7804566B2 - Regression test management device, regression test management method, and regression test management program - Google Patents

Description

The present invention relates to a regression test management device, a regression test management method, and a regression test management program.

Patent Document 1 discloses a configuration that extracts differences between comparison source data, which is not information that indicates that an abnormality or malfunction should be determined, and comparison target data that is the subject of a regression test. If a difference is found, it is determined that an error has occurred in the regression test, and the execution results are displayed on screen.

JP 2015-43181 A

However, the invention described in Patent Document 1 above had the problem of not being able to display a screen that reproduces the operating instructions given immediately before the error occurred.

The present invention was made in consideration of the above-mentioned problems, and aims to provide a regression test management device, regression test management method, and regression test management program that enables early identification of problem areas by allowing users to navigate through the screen from the comparative differences in test evidence to the point where a phenomenon corresponding to the difference occurs.

To solve the above-mentioned problems and achieve the objectives, the regression test management device of the present invention is a regression test management device equipped with a memory unit and a control unit, wherein the memory unit comprises application storage means for storing master data including application software, test scenarios to be executed by the application software, user interface definitions for the application software, screen operation commands for automatically executing the application software, and reference evidence in accordance with the test scenarios, and the control unit comprises comparison difference means for acquiring test evidence of the test scenarios automatically executed by the application software in a specified execution environment based on the master data and acquiring comparison difference evidence between the test evidence and the reference evidence, and screen operation means for displaying, based on the master data, an execution screen in which the application software was executed up to the immediately preceding scenario immediately before the comparison difference evidence occurred in the test scenario.

In the regression test management device according to the present invention, the screen operation means further displays, based on the master data, a specifiable execution control instruction for each step scenario included in the test scenario, and, when the execution control instruction is specified, displays the execution screen in which the application software is executed up to the specified step scenario.

Furthermore, in the regression test management device according to the present invention, the screen operation means displays the execution control instructions for each step scenario included in the test scenario in a specifiable manner based on the master data, and when the execution control instructions are specified, if the specified step scenario is a step in the test scenario that follows the immediately preceding scenario, displays the execution screen in which the application software is executed up to the immediately preceding scenario.

Furthermore, in the regression test management device according to the present invention, the execution control instruction is an instruction to specify up to the step scenario following the last step scenario included in the execution schedule of the application software as the new execution schedule.

Furthermore, in the regression test management device according to the present invention, the execution control instruction is an instruction to specify up to the step scenario selected by the user in the execution schedule of the application software.

Furthermore, in the regression test management device according to the present invention, the execution control instruction is an instruction to specify up to the last step scenario included in the test scenario in the execution schedule of the application software.

Furthermore, in the regression test management device according to the present invention, the execution control instruction is an instruction to specify up to the step scenario currently being executed in the execution schedule of the application software.

Furthermore, in the regression test management device according to the present invention, the application software is software created using a low-code development tool or a no-code development tool.

The regression test management method of the present invention is a regression test management method for causing a regression test management device having a memory unit and a control unit to execute the regression test. The memory unit includes application storage means for storing master data including application software, test scenarios to be executed by the application software, a user interface definition of the application software, screen operation commands for automatically executing the application software, and reference evidence according to the test scenarios. The method includes a comparison difference step executed by the control unit, which acquires test evidence of the test scenario automatically executed by the application software in a predetermined execution environment based on the master data and acquires comparison difference evidence between the test evidence and the reference evidence, and a screen operation step, which displays an execution screen in which the application software has been executed up to the immediately preceding scenario immediately before the comparison difference evidence occurs in the test scenario, based on the master data.

The regression test management program of the present invention is a regression test management program to be executed by a regression test management device having a memory unit and a control unit, wherein the memory unit includes application storage means for storing master data including application software, test scenarios to be executed by the application software, a user interface definition of the application software, screen operation commands for automatically executing the application software, and reference evidence according to the test scenarios, and the control unit executes a comparison difference step of acquiring test evidence of the test scenario automatically executed by the application software in a predetermined execution environment based on the master data and acquiring comparison difference evidence between the test evidence and the reference evidence, and a screen operation step of displaying, based on the master data, an execution screen in which the application software was executed up to the immediately preceding scenario immediately before the comparison difference evidence was generated in the test scenario.

The present invention has the advantage of enabling the execution of step reproduction up to the point of an error based on the automatic regression test history. Furthermore, the present invention has the advantage of enabling the location of a problem to be identified early by using a comparison difference list program to perform the exact same operations on a screen operation program as for an automatic test with differences with a single click. Furthermore, the present invention has the advantage of reducing the development burden in low-code and no-code development. Furthermore, the present invention has the advantage of reducing the hurdles of issue identification and resolution time and the required knowledge. Furthermore, the present invention has the advantage of supporting the reproduction and confirmation of automatic test results by inputting error lines in automatic test results and reproducing the operation commands up to the point immediately before the error. Furthermore, the present invention has the advantage of improving the efficiency of checking automatic test results for web applications.

FIG. 1 is a diagram showing an example of a regression test management process according to this embodiment. FIG. 2 is a diagram showing an example of a regression test management process in this embodiment. FIG. 3 is a diagram showing an example of a regression test management process in this embodiment. FIG. 4 is a block diagram showing an example of the configuration of a regression test management device according to this embodiment. FIG. 5 is a flowchart showing an example of processing performed by the regression test management device according to this embodiment. FIG. 6 is a diagram showing an example of step execution operation of a test scenario in this embodiment. FIG. 7 is a diagram showing an example of a test scenario reading process in this embodiment. FIG. 8 is a diagram showing an example of a step execution process of a test scenario in this embodiment. FIG. 9 is a diagram showing an example of a step execution process of a test scenario in this embodiment. FIG. 10 is a diagram showing an example of a step execution process of a test scenario in this embodiment. FIG. 11 is a diagram showing an example of a step execution process of a test scenario in this embodiment. FIG. 12 is a diagram showing an example of a step execution process of a test scenario in this embodiment. FIG. 13 is a diagram showing an example of a step execution process of a test scenario in this embodiment. FIG. 14 is a diagram showing an example of a step execution process of a test scenario in this embodiment. FIG. 15 is a diagram showing an example of a step execution process of a test scenario in this embodiment. FIG. 16 is a diagram showing an example of a step execution process of a test scenario in this embodiment. FIG. 17 is a diagram showing an example of a step execution process of a test scenario in this embodiment. FIG. 18 is a diagram showing an example of a step execution process of a test scenario in this embodiment. FIG. 19 is a diagram showing an example of a step execution process of a test scenario in this embodiment. FIG. 20 is a diagram showing an example of a step execution process of a test scenario in this embodiment. FIG. 21 is a diagram showing an example of a step execution process of a test scenario in this embodiment. FIG. 22 is a diagram showing an example of a step execution process of a test scenario in this embodiment. FIG. 23 is a diagram showing an example of step execution program calling processing in this embodiment. FIG. 24 is a diagram showing an example of step execution program calling processing in this embodiment. FIG. 25 is a diagram showing an example of step execution program calling processing in this embodiment. FIG. 26 is a diagram showing an example of step execution program calling processing in this embodiment.

An embodiment of the present invention will be described in detail with reference to the drawings. However, the present invention is not limited to this embodiment.

[1. Overview]
First, an overview of the present invention will be described with reference to Figures 1 to 3. Figures 1 to 3 are diagrams showing an example of a regression test management process in this embodiment.

In a rapidly changing business environment, rapid release is essential to providing valuable business solutions. In order to keep up with changes in the external environment, where the pace of evolution in operating systems, browsers, etc. is accelerating, there is a need to improve the efficiency of business application development and testing. Therefore, it has become necessary to automate testing of developed web application software using web browsers.

In the past, when automated testing web application software, simply outputting images of test results did not allow the execution conditions of the test cases and automatic execution definitions to be understood. Even if the execution conditions of the test cases and automatic execution definitions were understood, it was difficult to reproduce delicate phenomena where whether or not a phenomenon occurred could change depending on small differences in intermediate operations.

This embodiment therefore provides a mechanism for early identification of problem areas from test evidence in automated testing of web application software. Here, when complex conditions exist for an error to occur or timing is important, high levels of concentration and precise operation are often required. However, this embodiment can perform 100% identical operations automatically any number of times, which is expected to reduce time and the burden on personnel.

For example, in this embodiment, as shown in Figure 1, when a user sets an instruction to run up to the point where the problem occurred, the comparison difference list program is executed to identify the difference (the point where the problem occurred), and as shown in Figure 2, the screen operation (step execution) program is launched, and as shown in Figure 3, it is automatically executed up to just before the point where the problem occurred (the point surrounded by the dotted line).

2. Configuration
An example of the configuration of the regression test management device 100 according to this embodiment will be described with reference to Fig. 4. Fig. 4 is a block diagram showing an example of the configuration of the regression test management device 100 according to this embodiment.

As shown in FIG. 4, the regression test management device 100 is a commercially available desktop personal computer. Note that the regression test management device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may also be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

The regression test management device 100 comprises a control unit 102, a communication interface unit 104, a memory unit 106, and an input/output interface unit 108. Each unit of the regression test management device 100 is connected to each other so that they can communicate with each other via any communication path.

The communication interface unit 104 communicatively connects the regression test management device 100 to the network 300 via a communication device 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 management device 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network).

An input device 112 and an output device 114 are connected to the input/output interface unit 108. The output device 114 may be a monitor (including a touch panel), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that functions as a pointing device in conjunction with a mouse. Note that, below, the output device 114 may be referred to as the monitor 114 or the printer 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 stores computer programs that work in conjunction with the OS (Operating System) to issue commands to the CPU (Central Processing Unit) to perform various processes. The storage unit 106 can be, for example, a memory device such as RAM (Random Access Memory) or ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, or an optical disk. The storage unit 106 includes an application database 106a.

The application database 106a stores application software. Here, the application database 106a may store master data including the application software, test scenarios to be executed by the application software, user interface definitions for the application software, screen operation commands for automatically executing the application software, and reference evidence in accordance with the test scenarios. The application software may also be software created using a low-code development tool or a no-code development tool.

The control unit 102 is a CPU or the like that provides overall control of the regression test management device 100. The control unit 102 has internal memory for storing control programs such as an OS, programs that define various processing procedures, and required data, and executes various information processing operations based on these stored programs. Functionally, the control unit 102 is equipped with a comparison/difference unit 102a and a screen operation unit 102b.

The comparison and difference unit 102a acquires test evidence of a test scenario automatically executed by application software, and acquires comparison and difference evidence between the test evidence and reference evidence. Here, the comparison and difference unit 102a may acquire test evidence of a test scenario automatically executed by application software in a specified execution environment based on master data, and acquire comparison and difference evidence between the test evidence and reference evidence.

The screen operation unit 102b displays an execution screen in which the application software is executed. Here, the screen operation unit 102b may display an execution screen in which the application software is executed up to the immediately preceding scenario, which is immediately before the occurrence of comparison difference evidence in the test scenario, based on the master data. Furthermore, the screen operation unit 102b may display, based on the master data, a specifiable execution control instruction for each step scenario included in the test scenario, and, when an execution control instruction is specified, display an execution screen in which the application software is executed up to the specified step scenario. Furthermore, the screen operation unit 102b may display, based on the master data, a specifiable execution control instruction for each step scenario included in the test scenario, and, when an execution control instruction is specified, display an execution screen in which the application software is executed up to the immediately preceding scenario, if the specified step scenario in the test scenario is a step after the immediately preceding scenario. Here, the execution control instruction may be an instruction to specify up to the step scenario one step after the last step scenario included in the application software's execution schedule as a new execution schedule. Furthermore, the execution control instruction may be an instruction to specify up to a user-selected step scenario as the application software's execution schedule. The execution control instruction may also be an instruction to specify up to the last step scenario included in the test scenario in the execution schedule of the application software.The execution control instruction may also be an instruction to specify up to the currently executing step scenario in the execution schedule of the application software.

3. Specific Examples
A specific example of this embodiment will be described with reference to FIGS.

[Regression test management process]
An example of a regression test management process in this embodiment will now be described with reference to Fig. 5. Fig. 5 is a flowchart showing an example of a process performed by the regression test management device 100 in this embodiment.

As shown in FIG. 5, the comparison and difference unit 102a acquires test evidence of a test scenario automatically executed by application software in a specified execution environment based on the master data stored in the application database 106a, and acquires comparison and difference evidence between the test evidence and the reference evidence (step SA-1).

Here, the comparison difference unit 102a determines whether comparison difference evidence has been obtained (step SA-2).

If the comparison difference unit 102a determines that comparison difference evidence could not be obtained (step SA-2: No), it transitions to step SA-3.

Then, the screen operation unit 102b displays on the output device 114 execution control instructions for each step scenario included in the test scenario so that the execution control instructions can be specified, and determines whether the user has specified an execution control instruction via the input device 112 (step SA-3).

If the screen operation unit 102b determines that an execution control instruction has been specified (step SA-3: Yes), it proceeds to step SA-8.

On the other hand, if the screen operation unit 102b determines that an execution control instruction has not been specified (step SA-3: No), it transitions the processing to step SA-4.

Then, the screen operation unit 102b displays on the output device 114 an execution screen that executes the application software up to the final step scenario included in the test scenario based on the master data stored in the application database 106a (step SA-4), and the process ends.

On the other hand, if the comparison difference unit 102a determines that comparison difference evidence has been obtained (step SA-2: Yes), it transitions to step SA-5.

Then, the screen operation unit 102b displays on the output device 114 execution control instructions for each step scenario included in the test scenario so that the execution control instructions can be specified, and determines whether the user has specified an execution control instruction via the input device 112 (step SA-5).

If the screen operation unit 102b determines that an execution control instruction has not been specified (step SA-5: No), it proceeds to step SA-6.

Then, based on the master data stored in the application database 106a, the screen operation unit 102b displays on the output device 114 an execution screen in which the application software has been executed up to the immediately preceding scenario immediately before the occurrence of comparison difference evidence in the test scenario (step SA-6), and then ends the process.

On the other hand, if the screen operation unit 102b determines that an execution control instruction has been specified (step SA-5: Yes), it transitions the processing to step SA-7.

Then, the screen operation unit 102b determines whether the specified step scenario is a step after the immediately preceding scenario in the test scenario (step SA-7).

Then, if the screen operation unit 102b determines that the specified step scenario is a step later than the immediately preceding scenario in the test scenario (step SA-7: Yes), it transitions the processing to step SA-6.

On the other hand, if the screen operation unit 102b determines that the specified step scenario in the test scenario is not a step later than the immediately preceding scenario (it is an earlier step) (step SA-7: No), it transitions the processing to step SA-8.

Then, the screen operation unit 102b displays on the output device 114 an execution screen that executes the application software up to the specified step scenario based on the master data stored in the application database 106a (step SA-8), and the process ends.

Here, an overview of step execution of a test scenario in this embodiment will be described with reference to Figures 6 and 7. Figure 6 is a diagram showing an example of step execution operation of a test scenario in this embodiment. Figure 7 is a diagram showing an example of test scenario loading processing in this embodiment.

As shown in FIG. 6, the step execution program in this embodiment uses the screen operation program to execute screen operation commands until the "current line" numbers 1 to 4 reach the number specified by the "scheduled execution number." Also, as shown in FIG. 6, the step execution program and screen operation program in this embodiment operate asynchronously, referencing and updating each other's resources as they operate. Also, as shown in FIG. 6, when the step execution program in this embodiment is started, the "scheduled execution number" is 0. When the "execution control button" is pressed, the "scheduled execution number" is updated and screen operation commands are executed up to the updated scheduled execution number. Also, as shown in FIG. 6, in this embodiment, if the user wants to pause processing midway, they can press the stop button (square button), which changes the number of the currently "current line" to the "scheduled execution number" and pauses the screen operation. Also, as shown in FIG. 6, when the step execution program in this embodiment is called from the comparison difference list program, it is started with the line number of the action where the issue occurred specified as the "scheduled execution number."

Furthermore, as shown in FIG. 7, in the test scenario loading process of this embodiment, a screen operation command is obtained from the definition ID of the test execution target, and the low-code execution platform is operated in accordance with the screen operation command. Here, the low-code execution platform in this embodiment is a program that analyzes the content set in the low-code development platform and is executed as a business application. Here, the low-code development platform in this embodiment is a tool for setting the layout and logic flow. Furthermore, the screen operation program in this embodiment is a program that operates the screen of the application provided by the low-code execution platform, and is the entity that performs the operation in automatic regression testing.

Furthermore, an example of screen startup and operation processing in this embodiment will be described with reference to Figures 8 to 11. Figures 8 to 11 are diagrams showing an example of step execution processing of a test scenario in this embodiment.

As shown in Figure 8, the screen operation program in this embodiment operates the low-code execution platform to launch the screen of the specified definition ID, enters "abc" in the text box as shown in Figure 9, clicks "Button 1" as shown in Figure 10, and takes a screenshot as shown in Figure 11.

Furthermore, as shown in Figure 12, an example of step execution processing of a test scenario in this embodiment will be described. Figure 12 is a diagram showing an example of step execution processing of a test scenario in this embodiment.

As shown in FIG. 12, in this embodiment, the step execution program acquires the definition ID passed from the outside (comparison difference list program) (step SB-1), then the step execution program acquires screen operation commands from the screen operation command table using the definition ID and displays them in the action list (step SB-2), and the step execution program launches the screen operation program as a separate process (asynchronously) (passing the definition ID as an argument) (step SB-3).

As shown in FIG. 12, in this embodiment, the step execution program determines whether the "execution control button" has been pressed (step SB-4). If the "execution control button" has not been pressed (step SB-4: No), processing proceeds to step SB-6. If the "execution control button" has been pressed (step SB-4: Yes), the step execution program updates the "scheduled execution number" according to the button pressed (step SB-5), and processing proceeds to step SB-6.

As shown in FIG. 12, in this embodiment, the step execution program determines whether the "Close button (X button)" has been pressed (step SB-6). If the "Close button" has not been pressed (step SB-6: No), processing proceeds to step SB-4. If the "Close button" has been pressed (step SB-6: Yes), it determines whether the screen operation program is running (step SB-7).

As shown in FIG. 12, in this embodiment, if the screen operation program is running (step SB-7: Yes), the step execution program terminates the screen operation program (step SB-8) and processing ends; if the screen operation program is not running (step SB-7: No), processing ends.

As shown in FIG. 12, in this embodiment, when the step execution program launches the screen operation program (step SB-3), the screen operation program acquires the definition ID passed from the outside (step execution program) (step SC-1), the screen operation program acquires a screen operation command from the screen operation command table using the definition ID (step SC-2), the screen operation program launches the screen (step SC-3), the screen operation program acquires the next screen operation command (step SC-4), the screen operation program updates the number being executed (step SC-5), the screen operation program acquires the "scheduled execution number" (step SC-6), the screen operation program determines whether the number being executed is smaller than the "scheduled execution number" (step SC-7), and if the number being executed is not smaller than the "scheduled execution number" (step SC-7: No), processing proceeds to step SC-6. If the number being executed is smaller than the "scheduled execution number" (step SC-7: Yes), processing proceeds to step SC-8.

As shown in FIG. 12, in this embodiment, the screen operation program determines whether the screen operation command is a ScreenShot command (step SC-8). If the screen operation command is not a ScreenShot command (step SC-8: No), the screen operation program operates the screen in accordance with the screen operation command (step SC-9), and processing proceeds to step SC-11. If the screen operation command is a ScreenShot command (step SC-8: Yes), the screen operation program outputs a screenshot (step SC-10), and processing proceeds to step SC-11.

As shown in FIG. 12, in this embodiment, the screen operation program determines whether operation was successful (step SC-11). If operation was not successful (step SC-11: No), the screen operation program outputs an error log (step SC-12). After processing ends, if operation was successful (step SC-11: Yes), the screen operation program outputs a normal operation log (step SC-13).

Then, as shown in FIG. 12, in this embodiment, the screen operation program determines whether or not the next screen operation command exists (step SC-14). If the next screen operation command exists (step SC-14: Yes), processing proceeds to step SC-4. If the next screen operation command does not exist (step SC-14: No), processing ends. In this way, in this embodiment, processing is repeated for each screen operation command that has been read.

Here, as shown in FIG. 12, in this embodiment, when the "Stop button (square button)" is pressed on the execution screen, the display changes to "Executing up to 3," and operations up to 2 are completed, and the operation is paused after execution up to just before 3. At this time, as shown in FIG. 12, in this embodiment, an "arrow mark" is displayed on the "3 line." Next, as shown in FIG. 12, in this embodiment, when the "Play button (triangle button)" is pressed, the display changes to "Executing up to 4," operation 3 is performed, and the operation is paused after execution up to just before 4.

Furthermore, an example of step execution processing of a test scenario in this embodiment will be described with reference to Figures 13 to 22. Figures 13 to 22 are diagrams showing an example of step execution processing of a test scenario in this embodiment.

As shown in Figure 13, in this embodiment, the step execution program is launched, and the screen operation program and browser are also launched, but since the "scheduled execution number" is 1, no further operations are performed.

As shown in Figure 14, in this embodiment, when the fourth line is selected and the "Play to specified line button (triangle vertical bar button)" is pressed, the "Scheduled execution number" is changed to "Running up to 4."

As shown in Figure 15, in this embodiment, the "currently executing number < scheduled execution number" occurs, so action 1 is executed.

As shown in Figure 16, in this embodiment, when process 1 is completed, a log is output by the screen operation program, the "current number" is updated, and the indicator on the screen is updated.

As shown in Figure 17, in this embodiment, the "currently executing number < scheduled execution number" occurs, so action 2 is executed.

As shown in Figure 18, in this embodiment, if the "Stop button (square button)" is pressed while action 2 is being executed, the "Number currently being executed" is 2, so the "Number scheduled to be executed" is changed to "Executing up to 3."

As shown in Figure 19, in this embodiment, when process 2 is completed, the screen operation program outputs a log, updates the "currently running number," and updates the indicator on the screen. At this point, in this embodiment, since the "currently running number < scheduled to be executed number" is no longer the case, the screen operation program goes into standby mode.

Then, as shown in Figure 20, in this embodiment, if the "Play button (triangle button)" is subsequently pressed, the "Scheduled execution number" will change to "Executing up to 4."

As shown in Figure 21, in this embodiment, the "currently executing number < scheduled execution number" occurs, so action 3 is executed.

As shown in Figure 22, in this embodiment, when process 3 is completed, the screen operation program outputs a log, updates the "currently running number," and updates the indicator on the screen. At this point, in this embodiment, since the "currently running number < scheduled to be executed number" is no longer the case, the screen operation program goes into standby mode.

Furthermore, with reference to Figure 23, an overview of the step execution program call process from the comparison difference list program in this embodiment will be described. Figure 23 is a diagram showing an example of the step execution program call process in this embodiment.

In this embodiment, for the program on the screen shown in the right diagram of Figure 23, assuming that clicking a button copies the text content to a label, a scenario is tested in which (1) definition is launched from the menu, (2) abc is entered into the text, (3) the button is clicked, and (4) it is confirmed that abc is displayed in the label, executing the operations shown in the left diagram of Figure 23. Here, in this embodiment, if an error occurs at timing (3) for some reason, for example, the automatic test operation will stop.

Furthermore, with reference to Figures 24 to 26, an example of step execution program calling processing from the comparison difference list program in this embodiment will be described. Figures 24 to 26 are diagrams showing an example of step execution program calling processing in this embodiment.

In this embodiment, as shown in Figure 24, the step execution program is launched from the comparison difference list program, and as shown in Figure 25, the launched step execution program sets the "scheduled execution number" to 3, which was passed from the comparison difference list program, and as shown in Figure 26, operations are executed up to the operation 3 where the error occurred. At this time, as shown in Figure 26, in this embodiment, the button is disabled, and the direct cause of the error can be notified to the user by disabling the button. In other words, as shown in Figure 26, in this embodiment, when an attempt is made to execute action 3, an error occurs because the button cannot be pressed, and processing stops (a phenomenon recorded in the comparison difference list program).

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

Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to SDGs goals 12, 13, and 15.

Furthermore, this embodiment can contribute to strengthening control and governance, thereby contributing to Goal 16 of the SDGs.

5. Other Embodiments
The present invention may be implemented in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

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 using known methods.

In addition, the processing procedures, control procedures, specific names, registered data for each process, information including parameters such as search conditions, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.

Furthermore, with regard to the regression test management device 100, the components shown in the figure are functional concepts and do not necessarily have to be physically configured as shown.

For example, all or any part of the processing functions of the regression test management device 100, particularly the processing functions performed by the control unit 102, may be implemented by a CPU and a program interpreted and executed by the CPU, or may be implemented as hardware using wired logic. The program is recorded on a non-transitory, computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the regression test management device 100 as needed. In other words, a computer program that works in conjunction with the OS to issue commands to the CPU and perform various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into RAM, and works in conjunction with the CPU to form the control unit.

In addition, this computer program may be stored on an application program server connected to the regression test management device 100 via any network, and all or part of it may be downloaded as needed.

In addition, the program for executing the processing described in this embodiment may be stored on a non-temporary computer-readable recording medium, or may be configured as a program product. Here, this "recording medium" includes memory cards, USB (Universal Serial Bus) memories, 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 more. This includes any "portable physical media" such as a Blu-ray Disc (registered trademark) and a Blu-ray (registered trademark) Disc.

A "program" is a data processing method written in any language or description method, and may be in any format, such as source code or binary code. It should be noted that a "program" is not necessarily limited to a single structure, but also includes a distributed structure consisting of multiple modules or libraries, or a structure that achieves its function by working in conjunction with a separate program, such as an OS. The specific structure and reading procedure for reading a recording medium in each device shown in this embodiment, as well as the installation procedure after reading, can use well-known structures and procedures.

The various databases stored in the memory unit 106 are storage devices such as memory devices such as RAM and ROM, fixed disk devices 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.

The regression test management device 100 may also be configured as an information processing device such as a known personal computer or workstation, or as an information processing device connected to any peripheral device. The regression test management device 100 may also be implemented by installing software (including programs, data, etc.) that causes the device to perform the processing described in this embodiment.

Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the figures, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various additions or functional loads. In other words, the above-mentioned embodiments may be implemented in any combination, or embodiments may be implemented selectively.

This invention is useful in a variety of industries, including the IT industry, which deals with application software.

REFERENCE SIGNS LIST 100 Regression test management device 102 Control unit 102a Comparison difference unit 102b Screen operation unit 104 Communication interface unit 106 Storage unit 106a Application database 108 Input/output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (10)

A regression test management device comprising a storage unit and a control unit,
The storage unit
an application storage means for storing master data including application software, a test scenario to be executed by the application software, a user interface definition of the application software, a screen operation command for automatically executing the application software, and reference evidence in accordance with the test scenario;
Equipped with
The control unit
a comparison difference means for acquiring test evidence of the test scenario automatically executed by the application software in a predetermined execution environment based on the master data, and acquiring comparison difference evidence between the test evidence and the reference evidence;
a screen operation means for displaying an execution screen in which the application software has been executed up to a previous scenario immediately before the comparison difference evidence occurs in the test scenario based on the master data;
A regression test management device comprising: The screen operation means
The regression test management device according to claim 1, further comprising: displaying, based on the master data, execution control instructions for each step scenario included in the test scenario in a specifiable manner; and, when the execution control instructions are specified, displaying the execution screen in which the application software is executed up to the specified step scenario. The screen operation means
The regression test management device according to claim 2, characterized in that the execution control instructions for each step scenario included in the test scenario are displayed in a specifiable manner based on the master data, and when the execution control instructions are specified, if the specified step scenario in the test scenario is a step later than the immediately preceding scenario, the execution screen in which the application software is executed up to the immediately preceding scenario is displayed. The execution control instruction is
4. The regression test management device according to claim 2, wherein the instruction specifies up to the step scenario immediately following the last step scenario included in the execution schedule of the application software as the new execution schedule. The execution control instruction is
4. The regression test management device according to claim 2, wherein the instruction specifies up to the step scenario selected by the user in the execution schedule of the application software. The execution control instruction is
4. The regression test management device according to claim 2, wherein the instruction specifies up to the last step scenario included in the test scenario in the execution schedule of the application software. The execution control instruction is
4. The regression test management device according to claim 2, wherein the instruction specifies up to the step scenario currently being executed in the execution schedule of the application software. The application software includes:
4. The regression test management device according to claim 1, wherein the software is created using a low-code development tool or a no-code development tool. A regression test management method to be executed by a regression test management device having a storage unit and a control unit,
The storage unit
an application storage means for storing master data including application software, a test scenario to be executed by the application software, a user interface definition of the application software, a screen operation command for automatically executing the application software, and reference evidence in accordance with the test scenario;
Equipped with
Executed in the control unit:
a comparison difference step of acquiring test evidence of the test scenario automatically executed by the application software in a predetermined execution environment based on the master data, and acquiring comparison difference evidence between the test evidence and the reference evidence;
a screen operating step of displaying an execution screen in which the application software has been executed up to a previous scenario immediately before the comparison difference evidence occurs in the test scenario based on the master data;
A regression test management method comprising: A regression test management program to be executed by a regression test management device having a storage unit and a control unit,
The storage unit
an application storage means for storing master data including application software, a test scenario to be executed by the application software, a user interface definition of the application software, a screen operation command for automatically executing the application software, and reference evidence in accordance with the test scenario;
Equipped with
In the control unit,
a comparison difference step of acquiring test evidence of the test scenario automatically executed by the application software in a predetermined execution environment based on the master data, and acquiring comparison difference evidence between the test evidence and the reference evidence;
a screen operating step of displaying an execution screen in which the application software has been executed up to a previous scenario immediately before the comparison difference evidence occurs in the test scenario based on the master data;
A regression test management program for running the test.