JP7712980B2 - Test scenario creation support system, test scenario creation support method, and test scenario creation support program - Google Patents

Description

The present invention relates to a test scenario creation support system, a test scenario creation support method, and a test scenario creation support program.

For example, in a rapidly changing business environment, rapid release is necessary to provide valuable business solutions, and there is a demand for more efficient development and regression testing of business applications to keep up with changes in the external environment, where the speed of evolution of operating systems, browsers, etc. is accelerating. Conventionally, for example, there is a system for creating operation scenarios for applications, as disclosed in Patent Document 1.

JP 2021-9605 A

However, the above-mentioned Patent Document 1 does not state anything about efficiently creating test scenarios for testing applications by an automatic operation means (e.g., RPA) that automatically operates the application.

The present invention has been made in consideration of the above, and aims to provide a test scenario creation support system, a test scenario creation support method, and a test scenario creation support program that enable an automatic operation means that automatically operates an application to efficiently create test scenarios for testing the application.

In order to solve the above-mentioned problems and achieve the object, the present invention provides a test scenario creation support system that supports the creation of a test scenario to be executed by an automatic operation means of an application, the system including a control unit, the control unit being configured to be able to access a definition management table in which a definition name is associated with control information including a control name and its type and is registered;
The present invention is characterized in that it comprises a scenario creation means for providing a scenario creation screen, displaying a list of definitions on the scenario creation screen based on the definition management table, displaying a screen layout for a definition name selected by the scenario creator from the list of lists, displaying a list of controls that can be operated on the screen layout, displaying operation selection candidates for the control selected by the scenario creator from the list of controls, and creating a test scenario including the definition name, the control, and its operation content based on the operation selection by the scenario creator from the operation selection candidates, and registering the test scenario in a database.

According to one aspect of the present invention, the list of controls may also include controls that are commonly operated.

According to one aspect of the present invention, in addition to the definition name and the control information, the definition management table registers logic flow information including an ID, a name, and a group of flow elements connecting actions for each logic flow, in association with action information including an ID, a name, an action type, and settings for each action, and the scenario creation means may present candidates for the next operation from the operation previously selected on the scenario creation screen based on the definition management table.

According to one aspect of the present invention, the automatic operation means may include an RPA.

According to one aspect of the present invention, the test scenario creation support system may include a low-code platform or a no-code platform.

According to one aspect of the present invention, the application may include a business application.

In order to solve the above-mentioned problems and achieve the object, the present invention provides a test scenario creation support method for supporting the creation of a test scenario to be executed by an automatic operation means of an application, which is executed by an information processing system having a control unit, the control unit being configured to be able to access a definition management table in which definition names are associated with control information including control names and their types and registered, and the method includes a scenario creation step of providing a scenario creation screen executed by the control unit, displaying a list of definitions on the scenario creation screen based on the definition management table, displaying a screen layout for a definition name selected by the scenario creator from the list of definitions, displaying a list of controls that can be operated on the screen layout, displaying operation selection candidates for the control selected by the scenario creator from the list of controls, and creating a test scenario including the definition name, the control, and its operation content based on the operation selection candidate of the scenario creator, and registering the test scenario in a database.

In order to solve the above-mentioned problems and achieve the object, the present invention is a test scenario creation support program that supports the creation of a test scenario to be executed by an automatic operation means of an application, for execution by an information processing system having a control unit, the control unit being configured to be able to access a definition management table in which definition names are associated with control information including control names and their types and registered, the control unit providing a scenario creation screen, displaying a list of definitions on the scenario creation screen based on the definition management table, displaying a screen layout for a definition name selected by the scenario creator from the list, displaying a list of controls that can be operated on the screen layout, displaying operation selection candidates for the control selected by the scenario creator from the list of controls, and creating a test scenario including the definition name, the control, and its operation content based on the operation selection candidate of the scenario creator, and registering the test scenario in a database, the test scenario creation support program is characterized in that it is a test scenario creation support program for executing a scenario creation process in which the control unit provides a list of definitions on the scenario creation screen based on the definition management table, displaying a screen layout for a definition name selected by the scenario creator from the list of definitions, displaying a list of controls that can be operated on the screen layout, displaying operation selection candidates for the control selected by the scenario creator from the list of controls, and creating a test scenario including the definition name, the control, and its operation content based on the operation selection candidate of the scenario creator, and registering the test scenario in a database.

The present invention has the effect of enabling an automatic operation means that automatically operates an application to efficiently create a test scenario for testing the application.

FIG. 1 is a block diagram showing an example of the configuration of a test scenario creation support system according to the present embodiment. FIG. 2 is a diagram for explaining a specific example of the process of the test scenario creation support system according to the present embodiment. FIG. 3 is a diagram for explaining a specific example of the process of the test scenario creation support system according to the present embodiment. FIG. 4 is a diagram for explaining a specific example of the process of the test scenario creation support system according to the present embodiment. FIG. 5 is a diagram for explaining a specific example of the process of the test scenario creation support system according to the present embodiment. FIG. 6 is a diagram for explaining a specific example of the process of the test scenario creation support system according to the present embodiment. FIG. 7 is a diagram for explaining a specific example of the process of the test scenario creation support system according to the present embodiment. FIG. 8 is a diagram for explaining a specific example of the process of the test scenario creation support system according to the present embodiment. FIG. 9 is a diagram for explaining a specific example of the process of the test scenario creation support system according to the present embodiment. FIG. 10 is a diagram for explaining a specific example of the process of the test scenario creation support system according to the present embodiment. FIG. 11 is a diagram for explaining a specific example of the process of the test scenario creation support system according to the present embodiment. FIG. 12 is a diagram for explaining a specific example of the process of the test scenario creation support system according to the present embodiment. FIG. 13 is a diagram for explaining a specific example of the process of the test scenario creation support system according to the present embodiment. FIG. 14 is a diagram for explaining a specific example of the process of the test scenario creation support system according to the present embodiment. FIG. 15 is a diagram for explaining a specific example of the process of the test scenario creation support system according to the present embodiment. FIG. 16 is a diagram for explaining a specific example of the process of the test scenario creation support system according to the present embodiment. FIG. 17 is a diagram for explaining a specific example of the process of the test scenario creation support system according to the present embodiment. FIG. 18 is a diagram for explaining a specific example of the process of the test scenario creation support system according to the present embodiment. FIG. 19 is a diagram for explaining a specific example of the process of the test scenario creation support system according to the present embodiment. FIG. 20 is a diagram for explaining a specific example of the processing of the test scenario creation support system according to the present embodiment. FIG. 21 is a diagram for explaining a specific example of the processing of the test scenario creation support system according to the present embodiment. FIG. 22 is a diagram for explaining a specific example of the process of the test scenario creation support system according to the present embodiment. FIG. 23 is a diagram for explaining a specific example of the process of the test scenario creation support system according to the present embodiment. FIG. 24 is a diagram for explaining a specific example of the processing of the test scenario creation support system according to the present embodiment. FIG. 25 is a diagram for explaining a specific example of the process of the test scenario creation support system according to the present embodiment. FIG. 26 is a diagram for explaining a specific example of the processing of the test scenario creation support system according to the present embodiment. FIG. 27 is a diagram for explaining a specific example of the processing of the test scenario creation support system according to the present embodiment. FIG. 28 is a diagram for explaining a specific example of the processing of the test scenario creation support system according to the present embodiment. FIG. 29 is a diagram for explaining a specific example of the processing of the test scenario creation support system according to the present embodiment. FIG. 30 is a diagram for explaining a specific example of the processing of the test scenario creation support system according to the present embodiment. FIG. 31 is a diagram for explaining a specific example of the processing of the test scenario creation support system according to the present embodiment. FIG. 32 is a diagram for explaining a specific example of the processing of the test scenario creation support system according to the present embodiment. FIG. 33 is a diagram for explaining a specific example of the processing of the test scenario creation support system according to the present embodiment. FIG. 34 is a diagram for explaining a specific example of the processing of the test scenario creation support system according to the present embodiment. FIG. 35 is a diagram for explaining a specific example of the processing of the test scenario creation support system according to the present embodiment. FIG. 36 is a diagram for explaining a specific example of the processing of the test scenario creation support system according to the present embodiment. FIG. 37 is a diagram for explaining a specific example of the processing of the test scenario creation support system according to the present embodiment. FIG. 38 is a diagram for explaining a specific example of the processing of the test scenario creation support system according to the present embodiment. FIG. 39 is a diagram for explaining a specific example of the processing of the test scenario creation support system according to the present embodiment. FIG. 40A is a diagram for explaining a specific example of the processing of the test scenario creation support system according to the present embodiment. FIG. 40B is a diagram for explaining a specific example of the processing of the test scenario creation support system according to the present embodiment. FIG. 40C is a diagram for explaining a specific example of the processing of the test scenario creation support system according to the present embodiment. FIG. 41 is a diagram for explaining a specific example of the processing of the test scenario creation support system according to the present embodiment. FIG. 42 is a diagram for explaining a specific example of the processing of the test scenario creation support system according to the present embodiment. FIG. 43A is a diagram for explaining a specific example of the processing of the test scenario creation support system according to the present embodiment. FIG. 43B is a diagram for explaining a specific example of the processing of the test scenario creation support system according to this embodiment.

Below, embodiments of a test scenario creation 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 drawings. Note that the present invention is not limited to these embodiments.

[1. Overview]
The present invention will be outlined in the following order: (Background), (Problems), and (Solution).

(background)
In recent years, low-code development tools have been attracting attention as tools that can easily develop applications. In addition, the use of low-code development tools is expanding into the mission-critical core systems of companies. In this situation, a mechanism to maintain the quality of applications created with low-code development tools is essential. Regression testing using RPA is attracting attention as a means to achieve this.

(assignment)
However, when testing a business application using the conventional method, the following problems (1) and (2) arise.

(1) There is an issue of omissions in the creation of test patterns. Specifically, because tests are conducted after test patterns are created from the design documents, pattern omissions occur. For this reason, test code was generated and executed based on the design documents, and although routine processing could be generated automatically, non-routine processing had to be created manually.

(2) There is an issue that the testing itself is costly and difficult to perform repeatedly. Specifically, when performing comprehensive testing of business applications, clarifying the tests that should be performed manually and actually performing them entails risks and costs. With existing methods, for standardized specifications, it is possible to read the design documents, create test code, and perform automated testing, thereby reducing risks and costs. However, when testing non-standardized specifications (areas where it is difficult to interpret the design documents), test scenarios must be created manually before testing is performed, which incurs costs and makes it difficult to perform repeated testing.

(Solution)
In this embodiment, the low-code platform stores all of the property information of the controls to be operated and the processing logic within the events, making it possible to view the screen design and set controls and operation information without having to execute the target job.

In this embodiment, when an automated operation means (e.g., RPA) creates a test scenario for executing E2E regression testing of an application, the scenario can be created efficiently by using information on the low-code platform.

Specifically, the test scenario creation support system of this embodiment is equipped with a function for selecting operable controls, a function for presenting operations for the control to be operated, and a function for suggesting the next operation based on the previous operation, enabling efficient creation of test scenarios.

2. Configuration
An example of the configuration of a test scenario creation support system 100 according to this embodiment will be described with reference to FIG. 1. The test scenario creation 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 support system 100. The test scenario creation support system 100 is a system used by a scenario creator to create test scenarios. The test scenario creation 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.

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

The test scenario creation support system 100 includes a control unit 102, a communication interface unit 104, a memory unit 106, and an input/output interface unit 108. Each unit included in the test scenario creation support system 100 is connected to each other so that they can communicate with each other via any communication path.

The communication interface unit 104 communicatively connects the test scenario creation support system 100 to the network 300 via a communication system such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of communicatively connecting the test scenario creation support system 100 to other devices such as a terminal (not shown) used by a scenario creator or tester, 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.

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 works with a mouse to provide 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.

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

The memory 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 that associates and registers, for example, a definition ID, a definition name, control information, pull-down assignment information, pull-down information, logic flow information, action information, and event assignment definition information.

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.

The development application DB 106b is a database for storing data such as test scenarios.

The control unit 102 is a CPU or the like that provides overall control of the test scenario creation 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.

The control unit 102 is conceptually composed of an automatic operation unit 102a, a scenario creation unit 102b, and
and an application 102c.

The automatic operation unit 102a performs regression testing by executing automatic operations on the application 102c according to 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.

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

Specifically, the scenario creation unit 102b displays a list of definition lists on the scenario creation screen based on the definition management table 106a, displays a screen layout for the definition name selected by the scenario creator from the list of lists, displays a list of controls that can be operated on the screen layout, displays operation selection candidates for the control selected by the scenario creator from the list of controls, and creates a test scenario including the definition name, control, and its operation content based on the operation selection by the scenario creator from the operation selection candidates, and registers it in the development application DB 106b.

The list of controls may include controls that have a common target.

The scenario creation unit 102b may present candidates for the next operation on the scenario creation screen based on the previously selected operation, based on the definition management table 106a.

Application 102c is, for example, one or more business applications. The applications are stored in the memory unit 106, and the application stored in the memory unit 106 and executed by the control unit 102 is conceptually expressed as application 102c of the control unit 102 in terms of function.

3. Specific Examples
A specific example of the processing of the test scenario creation support system 100 (scenario creation unit 102b) of this embodiment will be described with reference to Fig. 2 to Fig. 41. Fig. 2 to Fig. 41 are diagrams for explaining a specific example of the processing of the test scenario creation support system 100 of this embodiment.

[3-1. Overview of scenario creation]
Here, an overview of test scenario creation by the test scenario creation support system 100 of this embodiment will be described with reference to Figures 2 to 4. Figure 2 is a diagram for explaining the overview of test scenario creation, where (A) shows an example of a scenario creation screen display, and (B) shows an example of a test scenario to be created. The scenario creator creates a scenario on the scenario creation screen provided.

As shown in FIG. 2(A), the scenario creation screen has setting fields 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 "Set" is selected, the scenario setting area is displayed, and when "Execute" is selected, the scenario execution area is displayed. In the example shown in the figure, "Set" is selected and the scenario setting area is displayed.

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

As shown in Figure 2 (B), the test scenario includes a scenario CD, a scenario name, and RPA operation content (action). The RPA operation content includes screen launch, page operation, screenshots, etc.

In the example shown in the figure, the scenario CD is "S-01-001-0020", the scenario name is "Will an error occur if unauthorized characters are entered in the supplier name in the supplier master?", and the RPA operation contents are: Launch screen: Supplier master maintenance (launches the supplier master maintenance screen), Basic page operation: Text supplier name Enter text, Screenshot: File name S-01-001-00XX-1.png (takes a screenshot and sets the file name to S-01-001-00XX-1.png).

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

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

Figure 4 is a diagram explaining the basic operations when creating a scenario. Here, we explain the operations when creating a test scenario to check whether the supplier name in the supplier master is correctly modified and registered. As shown in (A), display the supplier master maintenance (list) screen, select the details of supplier CD=C001, for example, as the object of modification, and click the Modify button. As shown in (B), display the selected data, as shown in (C), change the supplier name, register the changes with the Register button, and as shown in (D), confirm that the supplier name has been updated.

[3-2. Test scenario creation]
Test scenario creation will be described with reference to Figures 5 to 19. Figure 5 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.

As shown in Figure 5 (A), the scenario menu screen displays a scenario list showing the title, last updater, and update date and time of the test scenarios registered in the development application DB 106b, and a "New Scenario" button for creating a new scenario. When creating a new scenario, pressing the "New Scenario" button displays a scenario creation screen as shown in Figure 5 (B).

As shown in Figure 5 (B), the scenario creation screen has setting fields 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. When creating a new scenario, the operation to launch the screen is set automatically. Normally, the operation to launch the screen is set in the steps indicated by the dashed lines in the figure.

The scenario creator sets up the operations in the order that the RPA will actually execute them.

First, enter the scenario CD and scenario name as shown in Figure 6. In the example shown in the figure, the scenario CD "S-01-001-0020" and the scenario name "Is the corrected 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 Figures 7 to 9.

(1) Select the definition to operate on.
Fig. 7 is a diagram for explaining the selection of a definition to be operated. Fig. 7(A) is a diagram showing a display example of a scenario setting area of a scenario creation screen. Fig. 7(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).

In FIG. 7 (A), the scenario setting area displays a list of all definition names that exist in the definition management table 106a (e.g., Supplier Master Maintenance (List), Supplier Master Maintenance, Supplier Search, Supplier Master List, ...) as options in a list. Select the definition name for the definition you want to operate from the list. In this example, Supplier Master Maintenance (List) has been selected.

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

Figure 8 is a diagram showing an example of the display of the scenario setting area of the scenario creation screen. As shown in Figure 8, 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 of the definition management table 106a linked to the selected definition name.

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

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 and transitions from the 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 (sleeps) 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.

From here, we will skip the part about creating an operation scenario for the list screen and start by explaining how to create a scenario for operating the customer master maintenance screen.

(Example 1: Operate the controls on the screen)
Here, basic page operations will be described as RPA operations.

1. Click the "Add Operation Button." With reference to Figure 10, we will explain the process that occurs when you click the "Add Operation" button in the scenario setting area.

Figure 10 (A) is a diagram showing an example of the display of the scenario setting area. In the scenario setting area, as shown in Figure 10 (A), an "Add operation" button and a "Start screen" button are displayed on the left, and the selected definition and its screen layout are displayed on the right. When the "Add operation" button is clicked, an operation selection screen as shown in Figure 10 (B) is displayed. On the operation selection screen, it is possible to 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, operating a control within a definition is referred to as "basic page operation". Also, starting the operation of another definition of the low-code platform is referred to as "Operate screen".

2. Select the control to be operated within the definition. Details will be explained in the "Creation Assistance Function (1)" below. Selection of the control to be operated within the definition will be explained with reference to FIG. 11. FIG. 11 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 in FIG. 10 (B).

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

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 "Register Button (Edit)." Additionally, "Message Box Yes" and "Message Box No" are displayed as controls that can be operated across the system regardless of the definition settings. The following explains the case where "Text Customer Name Text" has been selected as an example.

3.2. Explains how to select the action based on the control selected in. For more details, see "Creation Assistance Function (2)" below.

(Selection operation example 1: Entering characters)
Selection operation example 1 (inputting characters) will be described with reference to FIG. 12. FIG. 12 shows a display example when "text supplier name text" is selected in the selection of the operation object in the scenario setting area of FIG. 11. As shown in FIG. 12, in the scenario setting area, operation selection candidates are displayed on the right side for the control selected in the selection of the operation object, and the operation can be selected. In this example, "character 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 selection of the operation object with the name of the operation selected in the selection of the operation. In this example, the title "Input text of text supplier name text" is displayed that combines the selection of the operation object "text supplier name text" and the selection of the operation "character input".

(Selection operation example 2: Click on the control)
Selection operation example 2 (clicking a control) will be described with reference to Figures 13 and 14. Figure 13 is a diagram showing a display example when a button or the like is selected in the scenario setting area and click is selected as the operation selection. The example shown in Figure 13 shows an example when "Register button (modify)" is selected as the operation target selection, "Click" is selected as the operation selection, and the title "Click the register button (modify)" is displayed.

Figure 14 shows an example of the display when using the assist function to set the next operation in the scenario setting area. Details will be explained in the "Creation Assist Function (3)" section below. The example shown in Figure 14 shows the case where clicking the Register button (Edit) was selected as the previous operation in Figure 13, and "Click Yes in the message box" was presented as the next operation candidate and OK was selected, and the content is reflected in the scenario setting area.

(Operation content selection example 2: Operate other fixed operations)
Here, screenshots, pause, etc. will be explained as RPA operations.

1. Click the "Add Operation Button" in the scenario setting area. The process when the "Add Operation Button" is clicked in the scenario setting area will be explained with reference to Figure 15.

Figure 15 (A) is a diagram showing an example of the display of the scenario setting area. When the "Add operation button" is clicked in Figure 15 (A), an operation selection screen as shown in Figure 15 (B) is displayed. In the operation selection screen, select the operation content "Other" and the operation "Screenshot".

2. Set up screenshot capture. Figure 16 shows an example of the display of the scenario setting area when the operation content "Other" and the operation "Screenshot" are selected on the operation selection screen in Figure 15 (B).

As shown in Figure 16, 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. In addition, the left side displays a capture icon and the title "File name Screenshot name + ".png"".

The completed test scenario is saved in the development application DB 106b. Figure 17 shows an example of the display of the scenario creation screen where the RPA operation settings have been completed. By clicking the register 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.

Here, the play icon indicates the opening of the RPA operation screen and screen operation. The screen icon indicates the basic page operation of RPA operation. The capture icon indicates a screenshot of the PRA operation. This indicates that the operation in the topmost box directly below the screen opening and screen operation is the RPA operation performed on that screen.

Figure 18 is a diagram showing an example of a data image of a test scenario to be registered. A test scenario is composed of a scenario CD, a scenario name, a start RPA operation key, and RPA operation content (each RPA operation). In the example shown in Figure 18, the scenario CD is "S-01-001-0020", the scenario name is "Is the correction registration of the supplier name in the supplier master correct?", the RPA operation start key is "A1", the RPA operation content is "Start RPA operation key: A1", "Operation type: Launch screen", "Screen type: Low-code platform", "Target: Supplier master maintenance (list) (definition ID)", "Child RPA operation keys: A11, A12, A13, B1, A14", ...

"Child RPA operation keys" are a list of RPA operation keys for operations performed within the screen specified by the RPA operation key, and are controlled so that they are nested when drawn on the screen, with the order of processing being from left to right.

After creating a scenario, check the execution. Figure 19 is a diagram showing an example of the display when "Execute" is selected on the scenario creation screen. As shown in Figure 19, the scenario execution area on the scenario creation screen displays an "Execution instruction button", an "Execution status update button", and the RPA operation content. When the execution instruction button is pressed, the test scenario is executed by the RPA execution program. In addition, the execution status can be checked by pressing the "Execution status update button". When checking the execution status, icons indicating execution success or failure (a system error has occurred during the RPA operation) are displayed.

[3-3. Test scenario execution image]
An image of test scenario execution will be described with reference to Figs. 20 to 23. Here, an example of the scenario "Will an error occur if characters are entered on a reference date?" will be used for explanation. Fig. 20 is a diagram for explaining reading of a test scenario. In Fig. 20, when a scenario CD is specified on the scenario creation screen, the RPA operation contents of the test scenario are displayed in the scenario execution area from the development application DB 106b using the scenario CD as a key. Then, when the "execution instruction button" is pressed, an instruction is given to the RPA execution program to execute the test scenario of the specified scenario CD, and the RPA execution program reads the test scenario of the specified scenario CD from the development application DB 106b and performs processing according to the operation execution order of the test scenario.

The screen startup will be described with reference to FIG. 21. FIG. 21 is a diagram for explaining the screen startup. In FIG. 21, the RPA execution program acquires the RPA operation key (in the example shown in the figure, "A1") designated as the start RPA operation key of the test scenario of the scenario CD instructed from the development application DB 106b, reads the RPA operation content (RPA operation key: A1, operation type: start screen, target: definition ID of customer master maintenance (list)) set in the acquired RPA operation key, and operates the application (in the example shown in the figure, customer master maintenance (list)) to start the screen.

The operations on the screen will be described with reference to FIG. 22. FIG. 22 is a diagram for explaining the operations on the screen. In FIG. 22, the RPA execution program reads the RPA operation contents of the test scenario of the scenario CD instructed from the development application DB 106b (in the example shown in the figure, RPA operation key: A11, operation type: basic page operation, target: control ID of text reference date, operation contents: character input, value: a) and operates the application.

Taking a screenshot will be described with reference to FIG. 23. FIG. 23 is a diagram for explaining taking a screenshot. In FIG. 23, the RPA execution program reads the RPA operation contents of the test scenario of the scenario CD instructed from the development application DB 106b (in the example shown in the figure, RPA operation key: A12, operation type: screenshot, file name: S-01-001-0030-1, confirmation item: is a date error displayed?), takes a screenshot of the screen, and creates a file named S-01-001-0030-1.png.

[3-4. Test scenario creation assistance function (1)]
The test scenario creation assistance function (1) will be described with reference to Figures 24 to 31. The objects of operations that can be operated by RPA use the control information (setting information on the low-code platform) in the definition management table 106a, and present the operable controls since they are predetermined.

In Figure 24, (A) shows the scenario setting area of the scenario creation screen. (B) shows an image of the screen layout. The screen layout is made up of a master page (a group of buttons) and placeholders. A "master page" is a page that brings together functions common to the screen (a group of buttons for displaying data, adding, modifying, deleting, etc.). By inheriting the master page, the cost of setting up the inherited page can be reduced. Operations are unified because the controls placed on the master page cannot be changed at the inherited page.

A "placeholder" is content that allows the inheritor to place its own controls on the inheritor screen. The placeholder is carried over to the inheritor screen, and by placing a control on the placeholder, the control is registered in the child element properties of the placeholder.

Figure 25 is a diagram showing an example of definition management table 106a. The example of definition management table 106a shown in Figure 25 includes a definition ID, definition name, control information, action information, logic flow information, and master page information (definition ID of the master page linked to the definition). The control information of the selected definition is obtained from the definition management table 106a and set in the list of operation target selections in the scenario setting area of the scenario creation screen. The control information of the master page stores control information that is common to multiple definitions. If a definition matching the definition ID of the master page information exists, its control information is also referenced.

In the example shown in the figure, the definition name "Customer Master Maintenance" is linked to the master page information "Master Maintenance Common Master Page Definition ID." The control information for the definition name "Master Maintenance Common Master Page" is control element 1 (ID: XXXM1..., name: Register button (modify), type: Button), control element 2 (placeholder) (ID: XXXP1...), etc. The control information for the definition name "Customer Master Maintenance" is control element 1 (ID: XXXP1..., child element: XXXX1..., child element: XXXX2...), control element 2 (ID: XXXX1..., name: Text customer code, type: string text box), and control element 3 (ID: XXXX2..., name: Text revision date, type: date text box). The ID of control element 2 (placeholder) of the "Master Maintenance Common Master Page" (XXXP1...) is linked to the ID of control element 1 of the control information of the "Customer Master Maintenance" (XXXP1...).

With reference to Figures 26 to 31, we will explain how to add configuration information to the definition management table 106a and add an operable target.

Figure 26 shows a list of typical operable objects, showing the control and the operable object. As shown in Figure 26, typically, in the case of the control "Text Box," the operable object is "Text."

Referring to Figures 27 and 28, we will explain how to add an operable object "pull-down button" to a control "text box."

Figure 27 is a diagram showing an example of the definition management table 106a when a pull-down function is set in a text box. The definition management table 106a includes pull-down assignment information and pull-down information in addition to control information. A pull-down is determined to have been assigned if the ID, which is the control element of the control information, matches the control ID, which is the pull-down assignment element of the pull-down assignment information.

In the example shown in the figure, for the definition name "Customer Master Maintenance", the control information is control element 1 (ID: XXX1, name: text customer code, type: string text box), the pull-down assignment information is pull-down assignment element 1 (control ID: XXX1, pull-down ID: SSS1), and the pull-down information is pull-down element 1 (pull-down ID: SSS1, pull-down name: customer suggestion).

In Figure 28, if a pull-down button function is added to the "Text Box" control (Figure 28 (A)), a "pull-down button" will be displayed in the selection list of operation targets in the scenario setting area of the scenario creation screen, as shown in Figure 28 (B). A pull-down button is a button that is attached to a selection-type control, as shown in Figure 28 (C). Pressing this button will display a list of pre-determined options.

Referring to Figures 29 and 30, we will explain how to add a "Calendar" to the "Date Text Box" control as an operable object.

Figure 29 shows an example of the definition management table 106a when a calendar function is set in a date text box. In the example shown in the figure, for the definition name "Customer Master Maintenance", the control information is control element 1 (ID: XXX2, name: text revision date, type: text box, calendar display: TRUE).

In Figure 30, if a calendar function is added to the "Text Box" control (Figure 30 (A)), "Calendar" will be displayed in the selection list of operation targets in the scenario setting area of the scenario creation screen, as shown in Figure 30 (B).

Figure 31 shows an example of a list of controls to which RPA operable objects are added through settings, showing the controls, settings, and operable objects. In Figure 31, for example, in addition to the above, "Text" can be added to the control "Single Select Box" and a "Download Button" can be added to the control "File Upload" as operable objects.

[3-5. Test scenario creation assistance function (2)]
The test scenario creation assistance function (2) will be described with reference to Figures 32 to 36. The target of the operations that RPA can perform is determined in advance using the control information (setting information on the low-code platform) in the definition management table 106a, and the operations that can be used for each control are presented. Figure 32 shows an example of the display of the scenario setting area on the scenario creation screen.

Figure 33 shows an example of a list of operations that can be performed on a control. As shown in Figure 33, in the case of a representative control, "Label cell of detail control," the available operation is "click."

Referring to Figures 34 and 35, we will explain how to add "drag and drop" as an available operation to the control "detail control label cell."

In FIG. 34, (B) shows an example of a designer setting screen. The designer setting screen is a separate screen used by developers for developing applications, and the settings for the behavior of detail controls are saved in an item that allows rearrangement of rows by drag and drop, which is a control element of the control information. The settings are referenced to add options for drag and drop operations to the control information.

(C) is a diagram showing an example of the definition management table 106a when a drag-and-drop pull function is set in the label cell of a detail control. The content set in the above-mentioned designer setting screen is set in the control information. In the example shown in the figure, for the definition name "Customer Master Maintenance", the control information is control element 1 (ID: XXX3, name: detail control, type: detail control, allow row sorting by drag-and-drop: TRUE) and control element 2 (ID: XXX4, name: label customer name, type: string label cell, primary key: FALSE).

(D) shows an example of drag-and-drop behavior on the screen when a test scenario is executed.

Figure 35 shows an example of the display in the scenario setting area of the scenario creation screen. In Figure 35 (A), if a drag-and-drop function is added to the control "detail control label cell", "drag-and-drop" is displayed as an operation selection option. Note that, as shown in Figure 35 (B), the drag-and-drop operation does not operate the detail control, but rather the control placed in the detail control, so it is not displayed as an option available for the detail control itself.

Figure 36 shows an example of a list of controls to which RPA operations can be added through settings, showing the controls, settings, and targets that can be operated. In Figure 36, for example, in addition to the above, a "drag and drop" operation can be added to the control "text cell of detail control."

[3-6. Test scenario creation assistance function (3)]
37 to 41, the test scenario creation assist function (3) will be described. The test scenario creation assist function (3) will describe a function for assisting in the creation of the next operation after a specific operation.

Figure 37 is a diagram for explaining the general settings of an RPA operation. In the scenario setting area of the scenario creation screen shown in Figure 37, as shown in (A), press the "Add operation button" and select the operation content and operation on the selection screen shown in (B) to set the RPA operation.

The assist function (3) uses the configuration information on the low-code platform, so it analyzes the logic flow information assigned to the previous operation and displays candidates for the next operation. Here, we will explain the process when the registration button is pressed as an example.

Figure 38 is a diagram for explaining the processing when the registration button is pressed. The processing when the registration button is pressed will be explained with reference to Figure 38. First, pre-registration processing is executed (step S1), and a confirmation message for selecting "Yes" or "No" is displayed (step S2). If the "Yes" button is selected in the confirmation message, registration processing is executed (step S3), and if the "No" button is selected, the flow ends.

Of these, the pre-registration process (step S1) and the registration process (step S3) are in-page actions, and the process of displaying a confirmation message for selecting "Yes" or "No" (step S2) is an action within the master page.

Here, "action" refers to something that is placed on the low-code platform to perform processing, such as an action that displays a message or an action that performs processing. "Action in a master page" refers to an action placed on a page that brings together functions common to the screen. By inheriting, the cost of setting up on the inheriting page can be reduced. Since changes cannot be made on the inheriting page, processing is unified for actions placed on the master page.

"In-page action" refers to an action placed on a page (a destination page such as customer master maintenance). When inheriting a master page, placeholder actions are placed so that they can be implemented on the destination, and the destination sets an action that performs its own processing within the placeholder action. For example, in the case of customer master maintenance, this would be the pre-registration processing (step S1) and registration processing (step S3).

Figure 39 shows an example of the display of the scenario creation screen when displaying candidates for the next operation. In Figure 39 (A), in the scenario setting area of the scenario creation screen, "Register button (modify)" is selected as the operation target and "Click" is selected as the operation selection (previous action). In this state, when the "Add operation button" is clicked, the logic flow information linked to the previous action is analyzed and a recommended operation screen is displayed as shown in Figure 39 (B), presenting recommended operation contents. In this example, the basic page operation "Click message box" is suggested as the recommended operation content. When the user agrees with this suggestion and presses the Confirm button, it is set (reflected) in the operation target selection and operation selection in the scenario setting area of the scenario creation screen, as shown in Figure 39 (C).

Figures 40A to 40C are diagrams showing an example of the definition management table 106a when a function for displaying candidates for the next operation content is set. In this example, the definition names "Master page for master maintenance screen" and "Customer master maintenance" are shown as examples. The logic flow information is set with information set for each logic flow (ID, name, and a group of flow elements that connect actions, etc.). The previous action ID is the ID of the action that is processed first, and the next action ID is the ID of the action that is executed after the previous action is executed. The callback key is a key for determining the result of a selection made by the user when the action is executed. The action information is set with information set for each action (ID, name, action type, and each setting, etc.).

Figure 41 is a diagram showing an example of an analysis flow of logic linked to a previous action. In Figure 41, the type of the previous action is obtained (step S11). It is determined whether the obtained previous action is a basic page or not (step S12), and if the obtained previous action is a basic page action ("Yes" in step S12), the identification ID of the set control is obtained (step S13). It is determined whether the identification ID of the obtained control exists in the definition management table 106a (step S14), and if the identification ID of the obtained control exists in the definition management table 106a ("Yes" in step S14), it is determined whether logic flow information is set or not (step S15).

If logic flow information has been set ("Yes" in step S15), it is determined whether or not there is a process that the RPA can operate (step S16). Processes that the RPA can operate are those for which actions such as message display actions, screen startup actions, and screen transition actions are set in the logic flow information in the definition management table 106a. If there is a process that the RPA can operate ("Yes" in step S16), the next operation is proposed (step S17).

On the other hand, if the operation is not a basic page operation ("No" in step S12), if the identification ID of the acquired control does not exist in the definition management table 106a ("No" in step S14), if logic flow information is not set ("No" in step S15), or if there is no process that can be operated by the RPA ("No" in step S16), the process ends (step S7).

A specific processing image when the Register button is pressed will be described with reference to Figures 42, 43A, 43B, and the flow in Figure 41 above. A logic flow (logic flow 1 in Figure 40) that performs the registration process is assigned to the Register button in advance (S15 in Figure 41). Since it is a common specification that a confirmation message appears after clicking the Register button, a message display action is set in the definition management table 106a. As the processing operated by the RPA includes clicking the messages "Yes" and "No," the operation proposed as the next operation candidate is "clicking the message box." A specific processing image when the Register button is pressed will be described below.

Figure 42 is a diagram showing an example of a customer master maintenance screen. Figures 43A and 43B are diagrams showing an example of a definition management table 106a. The example of the definition management table 106a shown in Figures 43A and 43B includes a definition ID, a definition name, control information, action information, logic flow information, master page information (definition ID of the master page linked to the definition), and event assignment definition information.

Event allocation definition information is used to link control information and logic flow information, and includes a control ID, event type, and logic flow ID. In the example shown in the figure, the control ID is "XXXM1...", the event type is "click", and the logic flow ID is "XXXX...".

When the Register button is clicked on the supplier master maintenance screen (see FIG. 42 (A)), the click operation is an operation on the basic page (steps S11 and S12 in FIG. 41), so the control ID "XXXM1..." of the Register button on the master maintenance common master page is obtained, and the logic flow ID ("XXXX...") linked to the control ID "XXXM1..." by the event allocation definition information is obtained, and a flow element is obtained from the logic flow information using the logic flow ID ("XXXX...") as a key (S13 to S15 in FIG. 41). If the obtained flow element is a process that can be operated by RPA, an operation candidate is proposed (S16 and S17 in FIG. 41). Id_action element 3 of the press-holder 1 action of flow element 1 is not a process operated by RPA, so it is not an operation candidate. The Id_action element 2 of the message display action of flow element 2 is a message display action, and is a process operated by RPA, so it is proposed as an operation candidate (see (B) and (C) of Figure 42).

As described above, according to this embodiment, a definition management table 106a in which definition names are associated with control information including control names and their types and a scenario creation screen are provided, and a list of definitions is displayed on the scenario creation screen based on the definition management table, a screen layout for the definition name selected by the scenario creator from the list of definitions is displayed, a list of controls that can be operated on the screen layout is displayed, and operation selection candidates for the control selected by the scenario creator from the list of controls is displayed. Based on the operation selection candidate of the scenario creator from the operation selection candidates, a test scenario including the definition name, the control, and its operation content is created and registered in the development application DB 106b. This makes it possible to efficiently create test scenarios for testing an application by an automatic operation means that automatically operates the application.

[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 making it possible to contribute to goals 8 and 9 of the SDGs.

In addition, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, which can contribute to the achievement of SDGs goals 12, 13, and 15.

In addition, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

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

For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using a known method.

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

In addition, with regard to the test scenario creation support system 100, each component shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure.

For example, the processing functions of the test scenario creation support system 100, particularly the processing functions performed by the control unit, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transient computer-readable recording medium that contains 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 support system 100 as necessary. That is, a computer program is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) to give instructions to the CPU in cooperation with the OS and perform various processes. This computer program is executed by being loaded into RAM, and cooperates with the CPU to form the control unit.

This computer program may also be stored in an application program server connected to the test scenario creation support system 100 via any network, and all or part of it may be downloaded as needed.

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

A "program" is a data processing method written in any language or description method, and may be in any format, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a distributed configuration consisting of multiple modules or libraries, and a program that works in conjunction with a separate program, such as an OS, to achieve its function. Note that the specific configuration and reading procedure for reading a recording medium in each system shown in the embodiments, as well as the installation procedure after reading, can use well-known configurations and procedures.

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.

The test scenario creation 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 to which any peripheral system is connected. The test scenario creation support system 100 may be realized by implementing software (including programs or data, etc.) that causes the system to realize the processing described in this embodiment.

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

This invention can be used in all business sectors and industries.

100 Test scenario creation support system 102 Control unit 102a Automatic operation unit 102b Scenario creation unit 102c Application 104 Communication interface unit 106 Storage unit 106a Definition management table 106b Development application DB
108 Input/Output Interface Unit 112 Input System 114 Output System 200 Server 300 Network

Claims (8)

A test scenario creation support system that supports creation of a test scenario to be executed by an automatic operation means of an application, comprising:
The control unit is
The system is configured to be able to access a definition management table in which definition names are associated with control information including control names and their types,
a scenario creation screen, based on the definition management table, displaying a list of definitions on the scenario creation screen, displaying a screen layout for a definition name selected by the scenario creator from the list, displaying a list of controls that can be operated on the screen layout, displaying operation selection candidates for the control selected by the scenario creator from the list of controls, and creating a test scenario including the definition name, the control, and its operation content based on the operation selection by the scenario creator from the operation selection candidates, and registering the test scenario in a database. The test scenario creation support system according to claim 1, characterized in that the list of controls includes controls that are commonly operated. In the definition management table, in addition to the definition name and the control information, logic flow information including an ID, a name, and a flow element group connecting actions for each logic flow, and action information including an ID, a name, an action type, and a setting for each action are registered in association with each other,
The test scenario creation support system according to claim 1, characterized in that the scenario creation means presents candidates for the next operation from the previously selected operation on the scenario creation screen based on the definition management table. The test scenario creation support system according to any one of claims 1 to 3, characterized in that the automatic operation means includes RPA. The test scenario creation support system according to any one of claims 1 to 3, characterized in that the test scenario creation support system includes a low-code platform or a no-code platform. The test scenario creation support system according to claim 1, characterized in that the application includes a business application. A test scenario creation support method for supporting creation of a test scenario to be executed by an automatic operation means of an application, the method being executed by an information processing system having a control unit, comprising:
The control unit is
The system is configured to be able to access a definition management table in which definition names are associated with control information including control names and their types,
Executed in the control unit:
a scenario creation screen, based on the definition management table, displaying a list of definitions on the scenario creation screen, displaying a screen layout for a definition name selected by the scenario creator from the list, displaying a list of controls that can be operated on the screen layout, displaying operation selection candidates for the control selected by the scenario creator from the list of controls, creating a test scenario including the definition name, the control, and its operation content based on the operation selection by the scenario creator from the operation selection candidates, and registering the test scenario in a database. A test scenario creation support program for supporting creation of a test scenario to be executed by an automatic operation means of an application, the test scenario creation support program being executed by an information processing system having a control unit, the test scenario creation support program comprising:
The control unit is
The system is configured to be able to access a definition management table in which definition names are associated with control information including control names and their types,
In the control unit,
A test scenario creation support program for executing a scenario creation process that provides a scenario creation screen, displays a list of definitions on the scenario creation screen based on the definition management table, displays a screen layout for a definition name selected by the scenario creator from the list of lists, displays a list of controls that can be operated on the screen layout, displays operation selection candidates for the controls selected by the scenario creator from the list of controls, creates a test scenario including the definition name, the control, and its operation content based on the scenario creator's selection of an operation from the operation selection candidates, and registers the test scenario in a database.