Regression test management device, regression test management method, and regression test management program

Abstract

To provide a regression test management device, a regression test management method, and a regression test management program capable of early grasping a problem occurrence place by performing screen operation up to a phenomenon corresponding to a difference occurs through a comparison difference of test evidence.SOLUTION: A method includes: acquiring test evidence of a test scenario automatically executed by application software in a predetermined execution environment on the basis of master data; acquiring a comparison difference evidence between a test evidence and a reference evidence; and displaying an execution screen on which the application software is executed up to a last minute scenario immediately before occurrence of the comparison difference evidence in the test scenario on the basis of the master data.SELECTED DRAWING: Figure 4

Description

[Technical Field]

[0001] The present invention relates to a regression test management device, a regression test management method, and a regression test management program. [Background technology]

[0002] Patent Document 1 discloses a configuration in which the difference between the source data for comparison, which is not information that should be determined to be an abnormality or malfunction, and the target data for comparison that is the subject of the regression test is extracted, and if a difference occurs, it is determined that an error has occurred in the regression test, and the execution result is displayed on the screen. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2015-43181 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the invention described in Patent Document 1 above has a problem in that it is not possible to display a screen that reproduces the operation commands made immediately before the error occurred.

[0005] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a regression test management device, a regression test management method, and a regression test management program that enable early identification of problem locations by allowing users to perform screen operations from the comparative differences in test evidence to the point where a phenomenon corresponding to the difference occurs. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the regression test management device of the present invention is a regression test management device comprising 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, a user interface definition of 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 has been executed up to a immediately previous scenario that is immediately before the comparison difference evidence occurs in the test scenario.

[0007] In addition, in the regression test management device of the present invention, the screen operation means further displays, 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, displays the execution screen in which the application software is executed up to the specified step scenario.

[0008] In addition, in the regression test management device of 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 after the immediately preceding scenario, displays the execution screen in which the application software is executed up to the immediately preceding scenario.

[0009] In addition, 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 after the last step scenario included in the execution schedule of the application software as the new execution schedule.

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

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

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

[0013] In addition, 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.

[0014] Furthermore, a regression test management method according to the present invention is a regression test management method to be executed by a regression test management device having 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, a user interface definition of the application software, screen operation commands for automatically executing the application software, and reference evidence in accordance with the test scenarios, and is characterized in including: a comparison difference step executed by the control unit, based on the master data, of acquiring test evidence of the test scenario automatically executed by the application software in a predetermined execution environment, and acquiring comparison difference evidence between the test evidence and the reference evidence; and a screen operation step, based on the master data, of displaying an execution screen in which the application software has been executed up to a immediately preceding scenario that is immediately before the comparison difference evidence occurs in the test scenario.

[0015] Furthermore, a regression test management program according to 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 comprises 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 in accordance with 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 has been executed up to a immediately preceding scenario that is immediately before the comparison difference evidence occurs in the test scenario. [Effects of the Invention]

[0016] 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 early identification of problem locations by allowing a user to perform the exact same operations of a different automatic test with a single click on a screen operation program from a comparison difference list program. 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 time required to identify and resolve issues and the level of required knowledge. Furthermore, the present invention has the advantage of supporting the reproduction and confirmation of automatic test results by enabling the input of error lines in automatic test results and the reproduction of operation commands up to the point immediately before the error. Furthermore, the present invention has the advantage of improving the efficiency of confirmation of automatic test results for web applications. [Brief explanation of the drawings]

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

[0018] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to this embodiment.

[0019] [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 regression test management processing in this embodiment.

[0020] 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 speed of evolution in operating systems and browsers is accelerating, there is a need to improve the efficiency of business application development and testing. This has made it necessary to automate testing of developed web application software using web browsers.

[0021] In the past, when automated testing web application software, simply outputting images of the 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 the phenomenon occurred could change depending on small differences in the operations involved.

[0022] Therefore, this embodiment provides a mechanism for early detection of problem areas from test evidence in automated testing of web application software. When complex conditions are required for an error to occur or timing is important, high concentration and precise operation are often required. However, this embodiment can automatically perform the same operation 100% as many times as necessary, which is expected to reduce time and the burden on personnel.

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

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

[0025] 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, a PDA (Personal Digital Assistant), a smartphone, or a tablet personal computer.

[0026] The regression test management device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. The units included in the regression test management device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0027] 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 a function of communicating data with other devices via the communication line. Here, the network 300 has a 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).

[0028] 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 cooperates with a mouse to achieve a pointing device function. In the following, 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.

[0029] The storage unit 106 stores various databases, tables, files, etc. The storage unit 106 stores computer programs that work in conjunction with an operating system (OS) to issue commands to a central processing unit (CPU) to perform various processes. The storage unit 106 may be, for example, a memory device such as a random access memory (RAM) or a read-only memory (ROM), 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.

[0030] The application database 106a stores application software. 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 according to the test scenarios. The application software may be software created using a low-code development tool or a no-code development tool.

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

[0032] 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 predetermined execution environment based on master data, and acquire comparison and difference evidence between the test evidence and reference evidence.

[0033] 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 a previous scenario, which is immediately before the occurrence of comparison difference evidence, in the test scenario, based on master data. Furthermore, the screen operation unit 102b may display an execution control instruction for each step scenario included in the test scenario in a specifiable manner based on the master data, 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 an execution control instruction for each step scenario included in the test scenario in a specifiable manner based on the master data, and, when an execution control instruction is specified, display an execution screen in which the application software is executed up to the previous scenario, if the specified step scenario in the test scenario is a step after the previous 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 execution schedule of the application software as a new execution schedule. Furthermore, the execution control instruction may be an instruction to specify up to a step scenario selected by the user as the execution schedule of the application software. 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.

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

[0035] [Regression test management process] An example of the 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 the process of the regression test management device 100 in this embodiment.

[0036] As shown in FIG. 5, the comparison 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 difference evidence between the test evidence and the reference evidence (step SA-1).

[0037] Here, the comparison difference unit 102a determines whether or not comparison difference evidence has been acquired (step SA-2).

[0038] If the comparison difference unit 102a determines that comparison difference evidence has not been acquired (step SA-2: No), the comparison difference unit 102a moves the process to step SA-3.

[0039] 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 or not the execution control instructions have been specified by the user via the input device 112 (step SA-3).

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

[0041] On the other hand, if it is determined that an execution control instruction has not been specified (step SA-3: No), the screen operation unit 102b shifts the process to step SA-4.

[0042] 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 ends the processing.

[0043] On the other hand, if the comparison difference unit 102a determines that comparison difference evidence has been acquired (step SA-2: Yes), it shifts the processing to step SA-5.

[0044] 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 or not the execution control instructions have been specified by the user via the input device 112 (step SA-5).

[0045] If it is determined that an execution control instruction has not been specified (step SA-5: No), the screen operation section 102b shifts the process to step SA-6.

[0046] 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, which is immediately before the comparison difference evidence occurs in the test scenario (step SA-6), and ends the processing.

[0047] On the other hand, if it is determined that an execution control instruction has been specified (step SA-5: Yes), the screen operation section 102b shifts the process to step SA-7.

[0048] Then, the screen operation unit 102b determines whether or not the specified step scenario is a step subsequent to the immediately preceding scenario in the test scenario (step SA-7).

[0049] If the screen operation unit 102b determines that the specified step scenario is a step subsequent to the immediately preceding scenario in the test scenario (step SA-7: Yes), the screen operation unit 102b shifts the process to step SA-6.

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

[0051] Then, the screen operation unit 102b causes the output device 114 to display an execution screen in which the application software has been executed up to the specified step scenario based on the master data stored in the application database 106a (step SA-8), and ends the process.

[0052] Here, an outline of step execution of a test scenario in this embodiment will be described with reference to Fig. 6 and Fig. 7. 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 test scenario reading processing in this embodiment.

[0053] As shown in FIG. 6 , the step execution program in this embodiment uses the screen operation program to execute screen operation commands until the "currently executing 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 the screen operation program in this embodiment operate asynchronously, referencing and updating each other's resources while 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 "currently executing line" to the "scheduled execution number," and the screen operation is paused. 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 problem occurred specified as the "scheduled execution number."

[0054] 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 of 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 of this embodiment is a tool for setting the layout and logic flow. Also, the screen operation program of this embodiment is a program that operates the screen of the application provided by the low-code execution platform, and is the subject that performs the operation in the automatic regression test.

[0055] An example of a screen startup / operation process in this embodiment will be described with reference to Fig. 8 to Fig. 11. Fig. 8 to Fig. 11 are diagrams showing an example of a step execution process of a test scenario in this embodiment.

[0056] 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 as instructed, enters "abc" in the text box as in Figure 9, clicks "Button 1" as in Figure 10, and takes a screenshot as in Figure 11.

[0057] An example of step execution processing of a test scenario in this embodiment will be described below as shown in Fig. 12. Fig. 12 is a diagram showing an example of step execution processing of a test scenario in this embodiment.

[0058] 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), the step execution program acquires a screen operation command from the screen operation command table using the definition ID and displays it in the action list (step SB-2), and the step execution program starts the screen operation program in a separate process (asynchronously) (passing the definition ID as an argument) (step SB-3).

[0059] As shown in FIG. 12, in this embodiment, the step execution program determines whether the "execution control button" has been pressed (step SB-4), and if the "execution control button" has not been pressed (step SB-4: No), the processing proceeds to step SB-6, and 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 the processing proceeds to step SB-6.

[0060] Then, as shown in FIG. 12, in this embodiment, the step execution program determines whether the "close button (cross button)" has been pressed (step SB-6), and if the "close button" has not been pressed (step SB-6: No), the processing proceeds to step SB-4, and if the "close button" has been pressed (step SB-6: Yes), it determines whether the screen operation program is running (step SB-7).

[0061] 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 the processing ends, and if the screen operation program is not running (step SB-7: No), the processing ends.

[0062] As shown in FIG. 12, in this embodiment, when the step execution program starts 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 based on the definition ID (step SC-2), the screen operation program starts the screen (step SC-3), the screen operation program acquires the next screen operation command (step SC-4), and the screen operation The program updates the number being executed (step SC-5), the screen operation program obtains the "scheduled execution number" (step SC-6), the screen operation program determines whether the number being executed for the screen operation command is smaller than the "scheduled execution number" (step SC-7), and if the number being executed for the screen operation command is not smaller than the "scheduled execution number" (step SC-7: No), processing proceeds to step SC-6, and if the number being executed for the screen operation command is smaller than the "scheduled execution number" (step SC-7: Yes), processing proceeds to step SC-8.

[0063] Then, 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), and 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, and 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.

[0064] As shown in FIG. 12, in this embodiment, the screen operation program determines whether the operation was successful (step SC-11), and if the operation was not successful (step SC-11: No), the screen operation program outputs an error log (step SC-12), and once the processing is completed, if the operation was successful (step SC-11: Yes), the screen operation program outputs a normal operation log (step SC-13).

[0065] 12, in this embodiment, the screen operation program determines whether or not there is a next screen operation command (step SC-14), and if there is a next screen operation command (step SC-14: Yes), the process proceeds to step SC-4, and if there is no next screen operation command (step SC-14: No), the process ends. In this way, in this embodiment, the process is repeated for the number of screen operation commands that have been read.

[0066] 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 executed up to just before 3, and then the operation is paused. At this time, as shown in FIG. 12, in this embodiment, an "arrow mark" is displayed on the "line for 3." Subsequently, as shown in FIG. 12, in this embodiment, when the "Play button (triangle button)" is pressed, the display changes to "Executing up to 4," and operations 3 are performed, and the operation is executed up to just before 4, and then the operation is paused.

[0067] An example of step execution processing of a test scenario in this embodiment will be described with reference to Fig. 13 to Fig. 22. Fig. 13 to Fig. 22 are diagrams showing an example of step execution processing of a test scenario in this embodiment.

[0068] As shown in FIG. 13, in this embodiment, the step execution program is started, and the screen operation program and browser are also started, and since the "scheduled execution number" is 1, no further operations are performed.

[0069] As shown in FIG. 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 "Executing up to 4."

[0070] Then, as shown in FIG. 15, in this embodiment, since "the number being executed<the number scheduled to be executed", action 1 is executed.

[0071] Then, as shown in FIG. 16, in this embodiment, when the process 1 is completed, a log is output by the screen operation program, the "number in progress" is updated, and the indicator on the screen is updated.

[0072] Then, as shown in FIG. 17, in this embodiment, since "the number being executed<the number scheduled to be executed", action 2 is executed.

[0073] As shown in FIG. 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."

[0074] 19, in this embodiment, when the process of 2 is completed, the screen operation program outputs a log, updates the "number in execution," and updates the indicator on the screen. At this time, in this embodiment, since the "number in execution < number scheduled to be executed" is no longer the case, the screen operation program goes into standby.

[0075] Then, as shown in FIG. 20, in this embodiment, if the "play button (triangle button)" is subsequently pressed, the "scheduled execution number" is changed to "executing up to 4."

[0076] Then, as shown in FIG. 21, in this embodiment, since "the number being executed<the number scheduled to be executed", action 3 is executed.

[0077] 22, in this embodiment, when the process of 3 is completed, the screen operation program outputs a log, updates the "number in execution," and updates the indicator on the screen. At this time, in this embodiment, since the "number in execution < number scheduled to be executed" is no longer the case, the screen operation program goes into standby.

[0078] An overview of the step execution program calling process from the comparison difference list program in this embodiment will be described with reference to Fig. 23. Fig. 23 is a diagram showing an example of the step execution program calling process in this embodiment.

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

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

[0081] In this embodiment, as shown in Fig. 24, the step execution program is launched from the comparison difference list program, and as shown in Fig. 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 Fig. 26, operations are executed up to the operation 3 where the error occurred. At this time, as shown in Fig. 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. That is, as shown in Fig. 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).

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

[0083] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.

[0084] Furthermore, this embodiment can contribute to strengthening control and governance, which can contribute to the achievement of Goal 16 of the SDGs.

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

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

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

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

[0089] 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. That is, a computer program for providing instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (hard disk drive). The computer program is executed by being loaded into RAM and cooperates with the CPU to form the control unit.

[0090] In addition, this computer program may be stored in 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.

[0091] Furthermore, the program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium or configured as a program product. Here, the term "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) disc.

[0092] Furthermore, a "program" is a data processing method written in any language or description method, and does not matter whether it is in the form of source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by cooperating with a separate program, such as an OS. Note that the specific configuration 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 configurations and procedures.

[0093] The various databases stored in the memory unit 106 are storage means 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 providing websites.

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

[0095] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit depending on various additions or functional loads. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Industrial Applicability]

[0096] The present invention is useful in various industries including the IT industry related to application software. [Explanation of symbols]

[0097] 100 Regression Test Management Device 102 Control section 102a Comparison and difference section 102b Screen operation section 104 Communication interface unit 106 Storage section 106a Application Database 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network

Claims

1. 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:

2. 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.

3. 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.

4. 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.

5. 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.

6. 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.

7. 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.

8. 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.

9. 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:

10. 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.

Images