Test scenario execution support system, test scenario execution support method, and test scenario execution support program

Abstract

To provide a test scenario execution support system capable of executing a test scenario with low setup cost when automatic operation means executes a test scenario to switch operation screens.SOLUTION: A test scenario creation and execution support system causes automatic operation means to execute a test scenario on the basis of test scenario data registered in a database, the data including a scenario ID, a scenario name, and scenario setting information in which operation contents of a parent screen and a child screen are hierarchically set. The automatic operation means performs a screen switch at a timing when a hierarchy changes.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a test scenario execution support system, a test scenario execution support method, and a test scenario execution support program. [Background technology]

[0002] In recent years, low-code development tools have been attracting attention as tools that allow for easy application development. Furthermore, the use of low-code development tools is now expanding into mission-critical enterprise systems. Under these circumstances, a system for maintaining the quality of applications created with low-code development tools is becoming essential. Regression testing using RPA is gaining attention as a means for achieving this. Conventionally, a system for creating application operation scenarios is known, for example, from Patent Document 1. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-9605 Summary of the Invention [Problem to be solved by the invention]

[0004] However, when creating a test scenario for an application to be tested by an automatic operation means (e.g., RPA) that automatically operates the application, when setting the operation instructions for the automatic operation means, the instructions must be specified serially. Therefore, in the case of a test scenario in which the operation screen is switched, such as during screen transitions or screen startup, it is necessary to specify the operation instructions to identify the screen at the time of the screen switch, which poses the problem of high setup costs for screen switching.

[0005] The present invention has been made in view of the above, and aims to provide a test scenario execution support system, a test scenario execution support method, and a test scenario execution support program that are capable of executing test scenarios with low setup costs when an automatic operation means executes a test scenario in which the operation screen is switched. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the present invention provides a test scenario execution support system that includes a control unit and in which an automatic operation means of an application executes a test scenario, wherein the automatic operation means executes a test scenario based on test scenario data registered in a database and including scenario setting information in which a scenario ID, a scenario name, and operation contents of a parent screen and a child screen are set hierarchically, and switches screens when the hierarchy changes.

[0007] According to another aspect of the present invention, the screen switching may include a screen transition or a screen activation.

[0008] According to one aspect of the present invention, the automatic operation means may (1) activate the parent screen and execute the operation content of the parent screen, and after executing the operation content of the parent screen, deactivate the parent screen, or (2) activate the child screen and execute the operation content of the small screen, and after executing the operation content of the child screen, deactivate the child screen and activate the parent screen.

[0009] According to another aspect of the present invention, the automatic operation means may include an RPA.

[0010] According to another aspect of the present invention, the test scenario execution support system may include a low-code platform or a no-code platform.

[0011] According to another aspect of the present invention, the application may include a business application.

[0012] Furthermore, in order to solve the above-mentioned problems and achieve the objectives, the present invention provides a test scenario execution support method executed by an information processing device having a control unit, characterized in that an automatic execution means executed in the control unit executes a test scenario based on test scenario data registered in a database, including scenario setting information in which a scenario ID, a scenario name, and operation contents of a parent screen and a child screen are set hierarchically, and includes an automatic execution step of switching screens when the hierarchy changes.

[0013] Furthermore, in order to solve the above-mentioned problems and achieve the object, the present invention is a test scenario execution support program to be executed by an information processing device having a control unit, characterized in that the program causes the control unit to execute an automatic execution process in which an automatic operation means executes a test scenario based on test scenario data including scenario setting information in which a scenario ID, a scenario name, and operation contents of a parent screen and a child screen are set hierarchically, which is registered in a database, and switches screens when the hierarchy changes. [Effects of the Invention]

[0014] According to the present invention, when an automatic operation means executes a test scenario in which the operation screen is switched, it is possible to execute a test scenario with low setup cost. [Brief explanation of the drawings]

[0015] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a test scenario creation and execution support system according to this embodiment. [Figure 2] FIG. 2 is a diagram for explaining a specific example of the processing of the test scenario creation and execution support system according to this embodiment. [Figure 3] FIG. 3 is a diagram for explaining a specific example of the processing of the test scenario creation and execution support system according to this embodiment. [Figure 4]FIG. 4 is a diagram for explaining a specific example of the processing of the test scenario creation and execution support system according to this embodiment. [Figure 5] FIG. 5 is a diagram for explaining a specific example of the processing of the test scenario creation and execution support system according to this embodiment. [Figure 6] FIG. 6 is a diagram for explaining a specific example of the processing of the test scenario creation and execution support system according to this embodiment. [Figure 7A] FIG. 7A is a diagram for explaining a specific example of the processing of the test scenario creation and execution support system according to this embodiment. [Figure 7B] FIG. 7B is a diagram for explaining a specific example of the processing of the test scenario creation and execution support system according to this embodiment. [Figure 8] FIG. 8 is a diagram for explaining a specific example of the processing of the test scenario creation and execution support system according to this embodiment. [Figure 9] FIG. 9 is a diagram for explaining a specific example of the processing of the test scenario creation and execution support system according to this embodiment. [Figure 10A] FIG. 10A is a diagram for explaining a specific example of the processing of the test scenario creation and execution support system according to this embodiment. [Figure 10B] FIG. 10B is a diagram for explaining a specific example of the processing of the test scenario creation and execution support system according to this embodiment. [Figure 11] FIG. 11 is a diagram for explaining a specific example of the processing of the test scenario creation and execution support system according to this embodiment. [Figure 12A] FIG. 12A is a diagram for explaining a specific example of the processing of the test scenario creation and execution support system according to this embodiment. [Figure 12B] FIG. 12B is a diagram for explaining a specific example of the processing of the test scenario creation and execution support system according to this embodiment. [Figure 13] FIG. 13 is a diagram for explaining a specific example of the processing of the test scenario creation and execution support system according to this embodiment. [Figure 14] FIG. 14 is a diagram for explaining a specific example of the processing of the test scenario creation and execution support system according to this embodiment. [Figure 15] FIG. 15 is a diagram for explaining a specific example of the processing of the test scenario creation and execution support system according to this embodiment. [Figure 16] FIG. 16 is a diagram for explaining a specific example of the processing of the test scenario creation and execution support system according to this embodiment. [Figure 17] FIG. 17 is a diagram for explaining a specific example of the processing of the test scenario creation and execution support system according to this embodiment. [Figure 18] FIG. 18 is a diagram for explaining a specific example of the processing of the test scenario creation and execution support system according to this embodiment. [Figure 19] FIG. 19 is a diagram for explaining a specific example of the processing of the test scenario creation and execution support system according to this embodiment. [Figure 20] FIG. 20 is a diagram for explaining a specific example of the processing of the test scenario creation and execution support system according to this embodiment. [Figure 21] FIG. 21 is a diagram for explaining a specific example of the processing of the test scenario creation and execution support system according to this embodiment. [Figure 22] FIG. 22 is a diagram for explaining a specific example of the processing of the test scenario creation and execution support system according to this embodiment. [Figure 23] FIG. 23 is a diagram for explaining a specific example of the processing of the test scenario creation and execution support system according to this embodiment. [Figure 24] FIG. 24 is a diagram for explaining a specific example of the processing of the test scenario creation and execution support system according to this embodiment. [Figure 25] FIG. 25 is a diagram for explaining a specific example of the processing of the test scenario creation and execution support system according to this embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0016] Hereinafter, embodiments of a test scenario creation and execution support system, a test scenario creation support method, and a test scenario creation support program according to the present invention will be described in detail with reference to the accompanying drawings. Note that the present invention is not limited to these embodiments.

[0017] [1. Overview] The outline of the present invention will be explained in the following order: (Background), (Problem 1), (Solution 1), (Problem 2), and (Solution 2).

[0018] (background) In recent years, low-code development tools have been gaining attention as tools that allow for easy application development. Furthermore, the use of low-code development tools is now expanding into mission-critical enterprise systems. In this context, a system for maintaining the quality of applications created with low-code development tools is essential. Regression testing using RPA is gaining attention as a means to achieve this.

[0019] Since there are many business uses for automating input tasks that were previously performed manually in existing applications without modifying the application, it is necessary to be able to launch multiple Excel files and input screens at the same time and operate them in parallel.As a result, the operation commands are serialized, and it is not possible to detect that an operation has finished just because one screen operation has finished, so it is highly likely that hierarchizing the command information of the scenario itself is meaningless, and explicit screen switching commands are required.

[0020] (Task 1) When issuing operation commands to RPA, the commands were set serially. This caused a readability issue in the case of RPA scenarios that involved switching between operation screens, such as screen transitions and screen startup, where it was difficult to understand the range of operations for a specific screen on the scenario creation screen.

[0021] (Solution 1) Issue 1 was resolved by incorporating a hierarchical structure when setting commands for RPA on the scenario creation screen, rather than simply specifying them serially. The hierarchical structure makes it easier to check the operation commands on the screen. This makes it possible to improve the readability of test scenarios in which operation screens are switched on the test scenario creation screen.

[0022] (Task 2) In the case of RPA scenarios where operation screens are switched, such as during screen transitions or screen startup, it is necessary to specify operation commands to identify the screen at the time of the screen switch, which poses the issue of high setup costs for screen switches.

[0023] (Solution 2) When focusing on ERP unit testing, operations are completed starting from a specific screen, unlike business operations that span various applications and screens. Given this situation, imposing constraints on RPA operations makes it possible to set more complete commands. Issue 2 was resolved by incorporating a hierarchical structure when setting commands, rather than simply specifying them serially. Because the timing of screen changes coincides with the timing of screen changes, commands that specify the screen can be omitted, reducing setup costs. This makes it possible to run test scenarios with low setup costs when RPA executes test scenarios that involve switching operation screens.

[0024] [2. Configuration] An example of the configuration of a test scenario creation and execution support system 100 according to this embodiment will be described with reference to FIG. 1. The test scenario creation and execution support system 100 can be configured, for example, on a low-code platform. It may also be configured on a no-code platform. FIG. 1 is a block diagram showing an example of the configuration of the test scenario creation and execution support system 100. The test scenario creation and execution support system 100 is a system for creating and executing test scenarios used by scenario creators and executors. The test scenario creation and execution support system 100 is equipped with the functions described in [3. Specific examples of processing] below, and is configured to be able to execute the processing described therein.

[0025] The test scenario creation and execution support system 100 may be a stationary information processing system such as a workstation or a desktop personal computer, or an information processing system such as a commercially available notebook personal computer.

[0026] The test scenario creation and execution support system 100 comprises a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. The units comprised in the test scenario creation and execution support system 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 test scenario creation and execution support system 100 to a network 300 via a communication system such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function for exchanging data with other devices via the communication line. Here, the network 300 has a function for communicatively connecting the test scenario creation and execution support system 100 to other devices such as terminals (with browsers) used by scenario creators and testers (not shown) and a server 200, and is, for example, the Internet or a LAN (Local Area Network). Note that the definition management table 106a, development application DB 106b, automatic operation unit 102a, and application 102c (described later) may be installed in other systems.

[0028] An input system 112 and an output system 114 are connected to the input / output interface unit 108. The output system 114 may be a monitor (including a home television), a speaker, or a printer. The input system 112 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with the mouse to achieve a pointing device function. In the following, the output system 114 may be referred to as the monitor 114, and the input system 112 may be referred to as the keyboard 112 or the mouse 112.

[0029] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs that work in conjunction with an OS (Operating System) to issue commands to a CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 106. The storage unit 106 can be, for example, a memory system such as RAM (Random Access Memory) or ROM (Read Only Memory), a fixed disk system such as a hard disk, a flexible disk, an optical disk, etc.

[0030] The storage unit 106 includes a definition management table 106a and a development application DB 106b. The definition management table 106a can be configured as a table or the like in which definition IDs, definition names, control information, pull-down allocation information, pull-down information, logic flow information, action information, and event allocation definition information are associated and registered, for example.

[0031] The control information may include an ID, a control name, and its type. The logic flow information may include an ID, a name, and a group of flow elements that connect actions for each logic flow. The action information may include an ID, a name, an action type, and settings for each action.

[0032] The development application DB 106b is a database for storing data such as test scenarios. The test scenario (also called a "scenario management table") may include scenario setting information in which a scenario ID, a scenario name, and operation contents of a parent screen and a child screen are set hierarchically.

[0033] The control unit 102 is a CPU or the like that performs overall control of the test scenario creation and execution support system 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 operations based on these stored programs.

[0034] The control unit 102 conceptually comprises an automatic operation unit 102a, a scenario creation unit 102b, and and an application 102c.

[0035] The automatic operation unit 102a performs a regression test by executing automatic operations on the application 102c in accordance with a test scenario registered in the development application DB 106b. The automatic operation unit is, for example, an RPA execution program (RPA tool). Instead of RPA, RDA (Robotic Desktop Automation) or the like may be used.

[0036] Specifically, the automatic operation unit 102a executes a test scenario based on a test scenario registered in the development application DB 106b, including scenario setting information in which a scenario ID, a scenario name, and operation contents of a parent screen and a child screen are set hierarchically, and switches screens when the hierarchy changes. Screen switching may include screen transitions or screen activation. The automatic operation unit 102a may (1) activate the parent screen and execute the operation contents of the parent screen, and after executing the operation contents of the parent screen, deactivate the parent screen, or (2) activate the child screen and execute the operation contents of the small screen, and after executing the operation contents of the child screen, deactivate the child screen and activate the parent screen.

[0037] In response to a request from the scenario creator's terminal, the scenario creation unit 102b provides a scenario menu screen or a scenario creation screen for creating a test scenario, creates a test scenario in accordance with the scenario creator's operations on the scenario creation screen, and stores the test scenario in the development application DB 106b.

[0038] Specifically, the scenario creation unit 102b provides a scenario creation screen based on the definition management table 106a, displays the settings of the operation details of the parent screen and the child screen hierarchically on the scenario creation screen so that the settings of the operation details of the parent screen and the child screen are clear, creates a test scenario based on the operations of the scenario creator on the scenario creation screen, and registers it in the development application DB 106b. The scenario creation screen may display a button for adding operation details of the parent screen and a button for adding operation details of the child screen.

[0039] The application 102c is, for example, one or more business applications. The applications are stored in the storage unit 106, and the applications stored in the storage unit 106 and executed by the control unit 102 are expressed functionally as the application 102c of the control unit 102.

[0040] [3. Specific examples of processing] Specific examples of the processing of the test scenario creation and execution support system 100 (scenario creation unit 102b, automatic operation unit 102a) of this embodiment will be described with reference to Fig. 2 to Fig. 25. Fig. 2 to Fig. 25 are diagrams for explaining specific examples of the processing of the test scenario creation and execution support system 100 of this embodiment.

[0041] [3-1: Processing Overview] Here, an overview of the processing of the test scenario creation and execution support system 100 according to this embodiment will be described with reference to FIGS.

[0042] (Current Issues) When issuing instructions to an RPA for an operation, the instructions must be specified serially. This has led to issues such as poor readability of the scenario and the cost of screen switching settings. Figure 2 is a diagram used to explain the current issues, showing an example of a part of the scenario setting screen. As shown in the figure, since instructions must be specified serially, it can be difficult to understand which child screen processing begins and ends. In addition, the original screen must be selected again.

[0043] (Outline of proposed system) 3 is a diagram showing an example of a scenario creation screen according to the present embodiment. On the scenario setting screen, the readability of the scenario is improved and the cost of screen switching settings is reduced by structuring the screen switching settings hierarchically.

[0044] The scenario creation screen has a setting field for the scenario CD and scenario name, and a switch button for switching between the display of the scenario setting area and the scenario execution area. When "Setting" is selected, the scenario setting area is displayed, and when "Execution" is selected, the scenario execution area is displayed. In the example shown in the figure, "Setting" is selected and the scenario setting area is displayed.

[0045] In the scenario setting area, the screen switching settings are hierarchically structured (nested), with the child screen "Customer Master Maintenance" displayed below the parent screen "Master Maintenance (List)."

[0046] When the scenario creator specifies the scenario CD and scenario name on the scenario creation screen, selects the operation target (control) in the scenario setting area, and selects the operation, a test scenario corresponding to the operation content is registered in the development application DB 106b.

[0047] Figure 4 is a diagram for explaining the execution of a test scenario. Figure 4(A) shows an example of the display of the scenario execution area on the scenario creation screen, and Figure 4(B) shows an example of the screen of an application to be automatically operated. A test scenario is executed by the RPA execution program (automatic operation unit 102a) when a tester or scenario creator presses the execution instruction button in the scenario execution area on the scenario creation screen, or when the batch manager automatically issues an execution instruction.

[0048] For example, when a tester or scenario creator presses the execution button on the scenario screen in Figure 4(A) and then presses the execution instruction button to instruct execution, or when a batch manager instructs execution, the RPA execution program interprets the scenario content registered in the development application database and automatically operates the application (Figure 4(B)) that is executed on the low-code execution platform.

[0049] (About scenario creation) Figure 5 is a diagram explaining the basic operations when creating a scenario. Here, we will explain the operations when creating a test scenario to check whether the customer name in the customer master is correctly corrected. As shown in (A), display the customer master maintenance (list) screen, select the details of customer CD=C001, for example, as the target for correction, and click the Edit button. As shown in (B), display the selected data on the customer master maintenance screen, change the customer name as shown in (C), register the changes with the Register button, and confirm that the customer name has been updated as shown in (D).

[0050] Hereafter, the customer master maintenance (list) screen from which the screen is launched will be referred to as the "parent screen," and the customer master maintenance screen to which the screen is launched will be referred to as the "child screen."

[0051] Figure 6 is a diagram showing an example of the scenario creation screen. For details on the scenario creation procedure, see "3-2. RPA Operation Settings Details." By clicking the registration button on the scenario creation screen, a test scenario is created according to the RPA operation settings on the scenario creation screen and saved in the development application DB 106b.

[0052] In the scenario setting area, the RPA operation details for the parent screen and child screens are displayed hierarchically (nested structure). The hierarchical structure makes it easier to check the operation commands for the parent screen and child screens, improving readability.

[0053] The play icon indicates the opening and operation of the RPA operation screen. The screen icon indicates the basic page operation of RPA operation. The capture icon indicates a screenshot of the RPA operation. In the example shown in the figure, the Client Master Maintenance (List) (parent screen) displays the RPA operation details: "Click the Display button," "Click the Client CD specified row in the Display Detail Control Label cell," and "Click the Edit button." The Client Master Maintenance (child screen) displays the RPA operation details: "Enter text in the Text Client Name text," "Click the Register button (Edit button)," and "Click Yes in the Message Box." In this way, when commands involve operations on different screens, a nested structure makes it clear that the operations are on different screens. When executing a test scenario with the RPA execution program, the nested structure allows the end of screen operations to be detected, so even if the scenario settings do not include commands to identify and switch screens, the target screen can be automatically detected and the screen switching process can be performed internally.

[0054] 7A and 7B are diagrams showing an example of a data image of a test scenario (scenario management table). The scenario management table is composed of a scenario CD, a scenario name, and scenario setting information (start RPA operation key, RPA operation). By incorporating a hierarchical structure setting in the scenario setting information, the timing of a hierarchical change in the RPA execution program corresponds to the timing of screen switching, so commands to specify the screen can be omitted, making it possible to reduce setting costs.

[0055] In the example shown in the figure, the scenario CD is "S-01-001-0020", the scenario name is "Is the correction registration of the customer name in the customer master correct?", the RPA operation start key is "A1", the RPA operation is "RPA operation key: A1, operation type: launch screen, screen type: low-code platform, target: customer master maintenance (list) (definition ID), RPA operation key list: A11, A12, A13, B1, A14", ...

[0056] "Operation type" is a classification of RPA operations (see Figure 18 for details). "RPA operation key list" is a list of RPA operation keys that can be operated on the relevant screen (the active screen at the time of execution).

[0057] 8 and 9 show the correspondence between the scenario creation screen and the scenario setting information in the scenario management table (test scenario). Specific operation types have an RPA operation key list attribute, which is a list of operations performed by the keys in this list on the corresponding screen. In this example, the specific operation types are Launch Screen, Operate Screen, and Operate System-wide Search Dialog.

[0058] In Figure 9, "Enter characters in the text customer name text" in the customer master maintenance (child screen) corresponds to RPA operation key "B11" in the RPA operation key list, "Click the register button (edit button)" corresponds to RPA operation key "B12" in the RPA operation key list, and "Click message box yes" corresponds to RPA operation key "B13" in the RPA operation key list.

[0059] (About scenario execution) 10A and 10B are diagrams showing the flow of scenario execution by the RPA execution program. The RPA execution program executes the scenario in the scenario management table. In the diagram, the left side shows the scenario management table, the center shows the processing flow, and the right side shows the state of the browser after the command is executed.

[0060] First, start the browser and go to the supplier master maintenance (list) (step S1). Activate the browser URL "Customer Master Maintenance (List)" and the window URL "Customer Master Maintenance (List)".

[0061] Execute the commands A11 to A13 (step S2). The browser URL "Customer Master Maintenance (List)" and the window URL "Customer Master Maintenance (List)" are made inactive.

[0062] The customer master maintenance screen is activated (step S3). The browser URL "Customer Master Maintenance" and the window URL "Customer Master Maintenance" are activated.

[0063] The instructions B11 to B13 are executed (step S4). The browser URL "Customer Master Maintenance" and the window URL "Customer Master Maintenance" are made inactive.

[0064] The launch screen (Customer Master Maintenance (List)) is activated (Step S5). Here, the timing of the screen change is the timing of the change in the hierarchy of the scenario setting information (child screen and parent screen), so no settings exist. The browser URL "Customer Master Maintenance (List)" and the window URL "Customer Master Maintenance (List)" are activated.

[0065] The instruction at A14 is executed (step S6).

[0066] Figure 11 is a diagram explaining the activation method. A search is performed for a URL that matches the currently running browser (the browser being managed by RPA startup) and identified. A URL search is also performed for windows within the identified browser, and any that match are activated. By performing a general search for windows with the corresponding URL, it is possible to accommodate a variety of startup patterns. As shown in (A) and (B), when a dialog is launched using an iframe, the URL of the window also changes to the URL of the page displayed inside.

[0067] (Example of startup pattern for diagram screen) An example of screen transition and dialog activation will be described with reference to FIGS. 12A and 12B.

[0068] 1. Launch the Customer Master List. (A) shows an example of the Customer Master Maintenance (List) screen. The browser URL "Customer Master Maintenance (List)" and the window URL "Customer Master Maintenance (List)" will become active.

[0069] 2. Go to Customer Master Maintenance. (B) shows an example of the Customer Master Maintenance screen. The browser URL "Customer Master Maintenance" and the window URL "Customer Master Maintenance" will become active.

[0070] 3. Launch Address Search. (C) shows an example of the Address Search screen. The URL "Address Search" in the window becomes active.

[0071] 4. Obtain the value using the address search and close the search screen. (D) shows an example of the Customer Master Maintenance screen. The browser URL "Customer Master Maintenance" and the window URL "Customer Master Maintenance" will become active.

[0072] 5. Register in Customer Master Maintenance and return to the Customer Master List. (E) shows an example of the Customer Master Maintenance (List) screen. The browser URL "Customer Master Maintenance (List)" and the window URL "Customer Master Maintenance (List)" will become active.

[0073] An example of launching a new browser will be described with reference to FIG. 1. Launch the Customer Master List. (A) shows an example of the Customer Master Maintenance (List) screen. The browser URL "Customer Master Maintenance (List)" and the window URL "Customer Master Maintenance (List)" will become active.

[0074] 2. Launch Customer Master Maintenance. (B) shows an example of the Customer Master Maintenance screen. The browser URL "Customer Master Maintenance" and the window URL "Customer Master Maintenance" will become active.

[0075] 3. Launch the Customer Master List. (C) shows an example of the Customer Master Maintenance (List) screen. The browser URL "Customer Master Maintenance (List)" and the window URL "Customer Master Maintenance (List)" will become active.

[0076] [3-2.RPA operation setting details] The detailed RPA operation settings will be explained with reference to Figs. 14 to 25. Fig. 14 shows examples of the display of a scenario menu screen and a scenario creation screen, where (A) shows an example of the scenario menu screen and (B) shows an example of the display of the scenario creation screen. When a scenario creator creates a new scenario, they create the new scenario from the scenario menu screen. The scenario menu screen has a button for creating a new scenario ("New Scenario Button"), and clicking this button launches the scenario creation screen, allowing the user to create a scenario.

[0077] As shown in Fig. 14(A), the scenario menu screen displays a list of scenarios that show the title, last updater, and update date and time of the test scenarios registered in the development application DB 106b, as well as a "New Scenario" button for creating a new scenario. When creating a new scenario, pressing the "New Scenario" button displays the scenario creation screen shown in Fig. 14(B).

[0078] As shown in Figure 14(B), the scenario creation screen has fields for setting the scenario CD and scenario name, and a switch button for switching between the display of the scenario setting area and the scenario execution area. When "Settings" is selected, the scenario setting area is displayed, and when "Execution" is selected, the scenario execution area is displayed. In the example shown in the figure, "Settings" is selected and the scenario setting area is displayed. When creating a new scenario, the operation to launch the screen is set automatically. Normally, the operation to launch the screen is set by following the steps indicated by the dashed lines in the figure.

[0079] The scenario creator sets up the operations in the order in which they will actually be executed by the RPA.

[0080] First, enter the scenario CD and scenario name as shown in Fig. 15. In the example shown in the figure, the scenario CD "S-01-001-0020" and scenario name "Is the correct registration of the supplier name in the supplier master correct?" are entered. The settings for RPA operations (launching the screen, operating the screen) will be explained with reference to Figs. 16 to 18.

[0081] (1) Select the definition to operate. Fig. 16 is a diagram for explaining the selection of a definition to operate. Fig. 16(A) is a diagram showing an example of the display of the scenario setting area on the scenario creation screen. Fig. 16(B) is a diagram showing an example of a definition name registered in the definition management table 106a (data such as control information, action information, and logic flow information are omitted).

[0082] In Figure 16 (A), the scenario setting area displays a list of all definition names that exist in the definition management table 106a (for example, Customer Master Maintenance (List), Customer Master Maintenance, Customer Search, Customer Master List, ...) as options. Select the definition name of the definition to operate on from the list. In this example, Customer Master Maintenance (List) is selected.

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

[0084] Figure 17 is a diagram showing an example of the display in the scenario setting area of ​​the scenario creation screen. As shown in Figure 17, under the selected definition name "Customer Master Maintenance (List)", a screen layout "Customer Master Maintenance (List) Screen Layout" is created and displayed based on the control information in the definition management table 106a linked to the selected definition name.

[0085] (3) Set the operation content (RPA operation). Here, select whether to operate the control of the selected definition or perform other fixed operations. Figure 18 shows a list of RPA operations that can be set, along with typical RPA operations, operation content, and their explanations.

[0086] For example, the RPA operation "Launch screen" has the operation content "screen operation" and is an RPA operation that sets the screen that the robot will first launch. The RPA operation "Operate screen" has the operation content "screen operation" and is an RPA operation that launches or transitions from the currently launched screen to another screen. The RPA operation "Basic page operation" has the operation content "screen operation" and is an RPA operation that operates a control within a specified definition. The RPA operation "Operate system-wide search dialog" has the operation content "screen operation" and is an RPA operation that operates the system-wide search dialog. The RPA operation "Pause" has the operation content "Other" and is an RPA operation that pauses (puts to sleep) the execution of the robot. The RPA operation "Screenshot" has the operation content "Other" and is an RPA operation that saves the contents of the screen as an image.

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

[0088] (Example 1: Operate the controls on the screen) Here, we will explain basic page operations as RPA operations.

[0089] 1. Click the "Add Operation Button." Referring to Figure 19, the process when the "Add Operation" button is clicked in the scenario setting area will be explained.

[0090] Figure 19(A) is a diagram showing an example of the display of the scenario setting area. As shown in Figure 19(A), in the scenario setting area, on the left side, an "Add Operation" button 500 in the Supplier Master Maintenance frame and an "Add Operation" button 501 in the Supplier Master Maintenance (List) frame are displayed, and on the right side, the selected definition and its screen layout are displayed.

[0091] You can add an operation to be performed in Customer Master Maintenance by clicking the "Add Operation" button 500 in the Customer Master Maintenance (child screen) frame. Also, you can add an operation to be performed in Customer Master Maintenance (list) by clicking the "Add Operation" 501 in the Customer Master Maintenance (list) (parent screen) frame.

[0092] Clicking the "Add Operation" button 500 or 501 displays an operation selection screen as shown in Figure 19(B). On the operation selection screen, you can select "Screen Operation" or "Other" as the operation content, and "Basic Page Operation," "Operate Screen," or "Operate Screen with Specified Page ID" as the operation. Here, "Basic Page Operation" refers to operating a control within a definition. Also, "Operate Screen" refers to starting to operate another definition on the low-code platform.

[0093] 2. Select the control to operate within the definition. The selection of the control to operate within the definition will be described with reference to Figure 20. Figure 20 is a diagram showing an example of the display of the scenario setting area when the operation content "screen operation" and the operation "basic page operation" are selected on the operation selection screen of Figure 19 (B).

[0094] As shown in Figure 20, in the scenario setting area, "Please select page operation" is displayed on the left side. On the right side, a list of operation targets (controls) is displayed, including operable controls within the selected definition and common controls for the system that are not dependent on the definition settings.

[0095] In this example, the operable controls within the selected definition "Customer Master Maintenance" are "Text Customer Code Text," "Text Revision Date Text," "Text Customer Name Text," and the "Register Button (Modify)" located on the master page inherited by Customer Master Maintenance. In addition, "Message Box Yes" and "Message Box No" are displayed as controls that can be operated system-wide regardless of the definition settings. A "master page" is a page inheritance that brings together functions common to the screen (displaying, adding, modifying, deleting data), reducing the cost of setting up the inheritor. Controls located on the master page cannot be changed on the inheritor, so operation is unified. The following explains the case where "Text Customer Name Text" is selected as an example.

[0096] Explain the selection of actions depending on the control selected in 3.2.

[0097] (Selection operation example 1: Entering characters) Selection operation example 1 (entering text) will be explained with reference to Figure 21. Figure 21 shows a display example when "Text Customer Name Text" is selected in the operation target selection in the scenario setting area of ​​Figure 20. As shown in Figure 21, in the scenario setting area, operation selection candidates are displayed on the right side for the control selected in the operation target selection, and the operation can be selected. In this example, "Text input" is selected as the operation selection. Also, on the left side, a title is displayed that combines the name of the control selected in the operation target selection with the name of the operation selected in the operation selection. In this example, the title "Enter text for text customer name text" is displayed, combining the operation target selection "Text Customer Name Text" and the operation selection "Text input".

[0098] (Selection operation example 2: Click the control) Selection operation example 2 (clicking a control) will be described with reference to Fig. 22 and Fig. 23. Fig. 22 and Fig. 23 are diagrams showing a display example when a button or the like is selected in the scenario setting area and click is selected in the operation selection. The example shown in Fig. 22 shows an example when "Register button (edit)" is selected in the operation target selection, "Click" is selected in the operation selection, and the title "Click the register button (edit)" is displayed.

[0099] The example shown in Figure 23 shows the case where, in Figure 22, clicking the registration button (modify) was selected as the previous operation, and the next operation candidate, "Click Yes in the message box," was presented and OK was selected, and the content was reflected in the scenario setting area.

[0100] (Operation content selection example 2: Operate other fixed operations) Here, we will explain RPA operations such as screenshots and pausing.

[0101] 1. Click the "Add Operation Button" in the scenario setting area. Referring to Figure 24, the process when the "Add Operation Button" is clicked in the scenario setting area will be described.

[0102] Fig. 24(A) is a diagram showing an example of the display of the scenario setting area. When the "Add Operation Button" is clicked in Fig. 14(A), an operation selection screen such as that shown in Fig. 24(B) is displayed. In the operation selection screen, select the operation content "Other" and the operation "Screenshot".

[0103] 2. Set up screenshot capture Fig. 25 is a diagram showing an example of how the scenario setting area is displayed when the operation content "Other" and the operation "Screenshot" are selected on the operation selection screen of Fig. 24(B).

[0104] As shown in Figure 25, in the scenario setting area, the screenshot name and confirmation details are set (input) on the right side. In this example, the scenario creator sets (inputs) the screenshot name "S-01-001-0020-1" and the confirmation details "Confirm that only the client name has been changed and registered." With this setting, a screenshot is taken with the screenshot name + ".png" as the file name. Also, a capture icon and the title "File name Screenshot name + ".png"" are displayed on the left side. The completed test scenario is saved in the development application DB 106b.

[0105] As described above, according to this embodiment, the automatic operation unit 102a executes a test scenario based on test scenario data registered in the development application DB 106b, including scenario setting information in which the scenario ID, scenario name, and operation contents of the parent screen and child screen are set hierarchically, and switches screens when the hierarchy changes. Therefore, when executing a test scenario in which the operation screen is switched, it is possible to execute a test scenario with low setting costs.

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

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

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

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

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

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

[0112] Furthermore, with regard to the test scenario creation and execution support system 100, the components shown in the figure are functional concepts, and do not necessarily have to be physically configured as shown in the figure.

[0113] For example, all or any part of the processing functions of the test scenario creation and execution support system 100, particularly the processing functions performed by the control unit, 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 system to execute the processes described in this embodiment, and is mechanically read by the test scenario creation and execution support system 100 as needed. That is, a computer program for issuing 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). This computer program is executed by being loaded into RAM and cooperates with the CPU to form the control unit.

[0114] In addition, this computer program may be stored in an application program server connected to the test scenario creation and execution support system 100 via any network, and it may be possible to download all or part of it as needed.

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

[0116] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as source code or binary code. Note that a "program" is not necessarily limited to a single program, but also includes programs that are distributed as multiple modules or libraries, or programs that achieve their functions by cooperating with other programs, such as an OS. Note that well-known configurations and procedures can be used for the specific configurations and reading procedures for reading a recording medium in each system described in the embodiments, as well as installation procedures after reading.

[0117] The various databases stored in the memory unit are storage means such as memory systems such as RAM and ROM, fixed disk systems such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and providing websites.

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

[0119] Furthermore, the specific form of distribution and integration of the system is not limited to that shown in the drawings, and all or part of the system can be configured by functionally or physically distributing and integrating in any unit according to 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]

[0120] The present invention can be used in all business sectors and industries. [Explanation of symbols]

[0121] 100 Test scenario creation and execution support system 102 Control section 102a Automatic operation section 102b Scenario Creation Department 102c Application 104 Communication interface unit 106 Storage section 106a Definition management table 106b Development application DB 108 Input / Output Interface Section 112 Input System 114 Output System 200 servers 300 Network

Claims

1. A test scenario execution support system including a control unit, in which an automatic operation means for an application executes a test scenario, The automatic operation means executes a test scenario based on test scenario data registered in a database, the test scenario data including scenario setting information in which a scenario ID, a scenario name, and operation contents of a parent screen and a child screen are set hierarchically, and switches screens when the hierarchy changes.

2. 2. The test scenario execution support system according to claim 1, wherein the screen switching includes a screen transition or a screen activation.

3. The test scenario execution support system according to claim 1, characterized in that the automatic operation means (1) activates a parent screen and executes the operation content of the parent screen, and after the operation content of the parent screen is executed, deactivates the parent screen, and (2) activates a child screen and executes the operation content of a small screen, and after the operation content of the child screen is executed, deactivates the child screen and activates the parent screen.

4. 2. The test scenario execution support system according to claim 1, wherein the automatic operation means includes an RPA.

5. The test scenario execution support system according to claim 1 , wherein the test scenario execution support system includes a low-code platform or a no-code platform.

6. 6. The test scenario execution support system according to claim 1, wherein the application includes a business application.

7. A test scenario execution support method executed by an information processing device having a control unit, Executed in the control unit: A test scenario execution support method characterized in that the automatic operation means executes a test scenario based on test scenario data registered in a database, the test scenario data including scenario setting information in which a scenario ID, a scenario name, and operation contents of a parent screen and a child screen are set hierarchically, and switches screens when the hierarchy changes.

8. A test scenario execution support program for causing an information processing device having a control unit to execute the test scenario execution support program, The control unit This test scenario execution support program allows an automatic operation means to execute a test scenario based on test scenario data registered in a database, including scenario setting information in which a scenario ID, a scenario name, and operation contents of a parent screen and a child screen are set hierarchically, and to execute an automatic execution process of switching screens when a hierarchy changes.

Images